惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

B
Blog
V
Vulnerabilities – Threatpost
Apple Machine Learning Research
Apple Machine Learning Research
V
V2EX
博客园 - 叶小钗
阮一峰的网络日志
阮一峰的网络日志
人人都是产品经理
人人都是产品经理
Latest news
Latest news
博客园 - 三生石上(FineUI控件)
美团技术团队
aimingoo的专栏
aimingoo的专栏
Google Online Security Blog
Google Online Security Blog
Security Archives - TechRepublic
Security Archives - TechRepublic
T
Threatpost
Y
Y Combinator Blog
T
Tailwind CSS Blog
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
A
Arctic Wolf
C
Cyber Attacks, Cyber Crime and Cyber Security
小众软件
小众软件
Recent Commits to openclaw:main
Recent Commits to openclaw:main
T
Tenable Blog
W
WeLiveSecurity
L
LINUX DO - 热门话题
D
Docker
Cyberwarzone
Cyberwarzone
量子位
A
About on SuperTechFans
The Last Watchdog
The Last Watchdog
雷峰网
雷峰网
C
CERT Recently Published Vulnerability Notes
P
Palo Alto Networks Blog
The Hacker News
The Hacker News
Blog — PlanetScale
Blog — PlanetScale
P
Proofpoint News Feed
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
F
Full Disclosure
The Cloudflare Blog
T
The Blog of Author Tim Ferriss
T
The Exploit Database - CXSecurity.com
Engineering at Meta
Engineering at Meta
O
OpenAI News
Hacker News - Newest:
Hacker News - Newest: "LLM"
Scott Helme
Scott Helme
IT之家
IT之家
S
Secure Thoughts
MongoDB | Blog
MongoDB | Blog
L
Lohrmann on Cybersecurity
博客园 - 司徒正美
Google DeepMind News
Google DeepMind News

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant Common SOC 2 Failures (Real World) Stop Vibe-Checking Your AI App: A Practical Guide to Evals How to Use SonarQube and SonarScanner Locally to Level Up Your Code Quality Your Next To-Do App Is Dead — I Replaced Mine with an OpenClaw AI Sign a Nostr event in 60 lines of Python using coincurve — no nostr-sdk, no nbxplorer, no rust toolchain ITGC Audit Explained Like You’re in Big 4 Patch Tuesday abril 2026: Microsoft parcha 163 vulnerabilidades y un zero-day en SharePoint Stop scraping everything: a better way to track competitor price changes Listing on MCPize + the Official MCP Registry while routing payments OUTSIDE the marketplace — how I kept 100% of my x402 revenue Building an AI-Powered Risk Intelligence System Using Serverless Architecture Why We Ripped Function Overloading Out of Our AI Toolchain Testing AI-Generated Code: How to Actually Know If It Works SaaS Churn Is Killing Your Business. Here Is What to Do About It (Without a Support Team) The Speed of AI Is No Longer Linear - And Self-Improving Models Are Why How to Implement RBAC for MCP Tools: A Practical Guide for Engineering Teams From Standard Quote to Persuasive Proposal: AI Automation for Arborists I built a CLI that scaffolds complete multi-tenant SaaS apps Axios CVE-2025–62718: The Silent SSRF Bug That Could Be Hiding in Your Node.js App Right Now The dashboard that ended our friendship Data Pipelines Explained Simply (and How to Build Them with Python) The Hidden Cost of AI Systems Nobody Talks About. undefined vs undeclared, and how typeof behaves Switching from file-based jobs to NATS/Kafka in Rust without changing code io_uring Adventures: Rust Servers That Love Syscalls Why Agentic AI is Killing the Traditional Database The POUR principles of web accessibility for developers and designers Quantum Neural Network 3D — A Deep Dive into Interactive WebGL Visualization How To Install Caveman In Codex On macOS And Windows Automation Pipeline Reliability: Why Your Workflow Breaks When Nobody Is Watching I Built an 'Open World' AI Coding Agent — It Works From ANY Folder From Freelancing to Product: A Tech Service Company's SaaS Transformation China's AI Giants: Adding Tencent Hunyuan & ByteDance Doubao to AI University (74 Providers) On the Vibe Coders and Their Lies clerk: Auto-Summarize Your Claude Code Sessions AI Weekly — 2026/04/10–04/17 | The Model Lockdown Is Here, but the Toolchain Is the Real Battleground AI 週報 — 2026/04/10–2026/04/17 模型封鎖潮來了,但工具鏈才是真戰場 Maybe this is how Open-Source apps are born... 🚀 Fine-Tune LLMs with LoRA and QLoRA: 2026 Guide tRPC v11 + Next.js App Router: End-to-End Type Safety Without the Boilerplate ShadCN UI in 2026: Why I Stopped Installing Component Libraries and Started Owning My Components SaaS Billing in React Server Components: Stripe + Supabase Without a Single `useEffect` Join our DEV Weekend Challenge — $1,000 in Prizes Across TEN winners! Submissions Due April 20 at 6:59 AM UTC. Implementing FSRS Spaced Repetition in Flutter + Supabase — Adding Memory Science to an AI Learning App "I Texted My Localhost From the Train — Claude Code Fixed the Bug Before I Got Home" I Built a Sales Prep AI and It Went Deeper Than Expected Design to Code #2: One JSON, Eleven Outputs Solving the 100M-Row Problem: A Summary Table Pattern for High-Volume Push Notification Logs Flutter Web With Wasm: What Actually Changes For Developers I Built 50 Royalty-Free Soundtracks for My Side Project in a Weekend Using AI Music Generation The Vibe Coding Security Checklist: 7 Things to Check Before You Ship Stop Letting Googlebot Guess Fix Your React App's SEO Right Desconstruindo o Streaming do LinkedIn: Como Criar um Engine de Extração de Vídeo de Alta Performance com HLS e FFmpeg (EDA Part-1) EDA (Exploratory Data Analysis) Explained With Real Life — Why Looking at Your Data Is the Most Important Step in Machine Learning Brand Relationship Management at Scale: Our 4-Touch Outreach System for 200+ Brands Why String.fromEnvironment() Might Return an Empty String in Dart JGuardrails 1.0.0 — Hardening Java LLM Apps Against Jailbreaks, Toxicity, and Prompt Injection Plan and Schedule a Full Week of Threads Content From One Claude Conversation Coding Cat Oran Ep3, Five Tables Changed Everything Updated: BFF Pattern I'm done watching freelancers get buried by 200 proposals. So I'm building the alternative. This is my first post BFS Algorithm in Java Step by Step Tutorial with Examples Tracking LLM Pricing Monthly: An Open Dataset for 22 AI Models How We Measure Content ROI on a Comparison Site: Revenue Attribution Without Perfect Data Introducing Nova AI Ops: The AI-Native Operating System for SRE Teams I built a free desktop video downloader for Windows — Grabbit How Talkie OCR Helps Vision-Impaired & Dyslexic Users Read the World Around Them VRCFaceTracking安装和iPhone面捕配置教程,有bug Even CrowdStrike Can't See Your Agents The Automation Gold Rush: What n8n Workflows and Claude Are Opening Up for Developers Right Now
How to Apply to 100 Jobs in One Afternoon (Without Sending Junk)
Mohammed Ame · 2026-05-17 · via DEV Community

The advice you'll find everywhere is: quality over quantity. Tailor every resume. Research every company. Craft every cover letter.

That advice was written for a different market.

In 2025, recruiting benchmarks from Gem's dataset of 140 million applications showed that candidates are roughly three times less likely to be hired today than they were three years ago. Pass-through rates are dropping. Interviews per hire are rising. Time to hire is getting longer.

The math has changed. Quality still matters. But volume now matters too.

The problem: if tailoring one resume takes 20 minutes, applying to 100 jobs takes 33 hours. That's a full work week just on applications. Most people can't do that. So they either blast an untailored resume everywhere, or they apply to 10 jobs carefully and wait.

Neither works very well.

There's a third option.

The Batch Approach

The core idea: do your tailoring work in batches instead of one application at a time.

Instead of: pick job, tailor resume, apply, pick next job, repeat.

You do: collect 20-30 job URLs, process all of them at once, submit in sequence.

This sounds small, but it changes everything about how you spend your time and energy.

Step 1: Build Your Job List First (30-45 minutes)

Most people open a job board, see a role, and immediately start applying. This is inefficient. You context-switch constantly and never build momentum.

Instead, spend 30-45 minutes doing nothing but collecting jobs.

Open LinkedIn, Indeed, or whatever boards you use. Search for your target roles. Open each listing that looks relevant. Copy the URL. Paste it into a spreadsheet.

Your criteria at this stage should be loose: does this role roughly match what you do? If yes, save it. You're not committing to applying yet. You're building a list.

Aim for 30-50 jobs per session. This sounds like a lot. It isn't. At 1-2 minutes per listing, that's 30-60 minutes of searching.

Once your list is done, go through and eliminate obvious mismatches. You'll probably cut 20-30%. What's left is your batch.

Step 2: Prepare One Strong Base Resume (one-time, 1-2 hours)

If you haven't done this yet, do it now. A base resume is your starting point: your full experience, your best bullet points, your accomplishments in their strongest form.

This is the document you tailor from, not the document you submit.

A few things that make tailoring faster later:

  • Write each bullet point in outcome language ("increased X by Y," not "responsible for X")
  • Include more detail than you'll submit (you'll cut to fit, not add)
  • Keep it in a format that's easy to edit (Google Docs or Word, not PDF)

You only do this once. Every application after this is a variation of this document.

Step 3: Process the Batch (the actual bulk apply)

Now you work through your job list. For each role:

  1. Open the job description
  2. Identify the 3-5 most repeated keywords or phrases
  3. Check your base resume: do your bullet points reflect this language?
  4. Rephrase any bullets that can be improved without being dishonest
  5. Rewrite your 2-3 line summary to match this specific role
  6. Export and submit

If you're doing this manually, each application takes 15-20 minutes once you have the method down. A batch of 20 jobs takes 4-6 hours. Spread over two days, that's manageable.

If you're using a tool that automates steps 2-5, a batch of 20 jobs can take under an hour. I built BulkResumes for exactly this: paste your base resume, paste a list of job URLs, and it generates individually tailored resumes and cover letters for each one. The underlying logic is the same as the manual method, just automated.

Either way, the batch approach is the same. You're not rushing. You're removing the setup overhead that makes individual applications feel so slow.

What "Tailored" Actually Means at Scale

There's a fear that applying to 100 jobs means sending 100 generic resumes. It doesn't have to.

Tailoring has a spectrum:

  • Generic (same resume, zero changes): works only if you're extremely well-matched to every role
  • Light tailoring (summary rewritten, 2-3 bullet points rephrased): takes 10 minutes, meaningfully increases relevance
  • Deep tailoring (every section customized, company research incorporated): takes 60-90 minutes, appropriate for high-priority roles

The batch approach doesn't mean you always do light tailoring. It means you sort your applications by priority and allocate effort accordingly.

Tier 1 (your top 5-10 roles): deep tailoring. Research the company. Write a specific cover letter. Spend the time.

Tier 2 (solid matches): standard tailoring. 15-20 minutes each.

Tier 3 (stretch or speculative): light tailoring. Summary plus 2 bullets. Submit and move on.

Most people only have a Tier 1 mindset. They apply to 10 jobs as if they were all dream jobs, then give up when nothing happens. The batch approach forces you to think in tiers and get things moving.

The Quality Check That Actually Matters

There's one thing that kills bulk applications: submitting resumes with errors, wrong company names, or copy-paste artifacts from previous tailoring.

Before each submission:

  • Read the first paragraph of your summary out loud. Does it sound like it was written for this job?
  • Check that your resume doesn't still say the previous company name or role anywhere
  • Confirm contact info and formatting are intact

That's it. Two minutes. Anything more and you're over-optimizing.

The Honest Reality

Volume without targeting is noise. If you're applying to every job on the board regardless of fit, you'll get a response rate of near zero and burn out fast.

Volume with basic targeting and light tailoring is signal. You're showing up in relevant searches, your resume language matches what they're looking for, and you're submitting enough applications that the math works in your favor.

The goal isn't 100 applications. The goal is 100 relevant applications with resumes that aren't working against you.

In a market where you're three times less likely to be hired than a few years ago, that means you need to apply to more jobs than before, tailor more consistently than before, and waste less time per application than before.

The batch approach gives you all three.

A Simple System to Start Today

  1. Today (30 min): Build a list of 20-30 jobs you're genuinely qualified for. Don't apply yet.
  2. Tomorrow morning (2 hrs): Polish your base resume so it's strong on its own.
  3. Tomorrow afternoon (2-3 hrs): Work through your batch. Tailor and submit each one.
  4. Repeat weekly: New batch every Monday. Track what you sent. Follow up on anything that goes quiet after 2 weeks.

That's roughly 10-15 applications a week done properly, or 40-60 a month. In a tough market, that's enough volume to get the math working for you.

Start with the list.