Why 'Just Keep Applying' Is Bad Advice

“Keep applying” is bad advice.

Not because persistence doesn’t matter. It does. But most engineers are applying harder when they should be applying differently.

I spent 12 years at Meta reviewing resumes and running hiring loops. The people who broke out of the black hole weren’t sending more applications. They fixed what was broken at the top of the funnel and then applied.

Your resume is probably getting filtered before a human sees it

Most companies use Applicant Tracking Systems to filter resumes before a recruiter ever opens them. The system scans for keyword matches. If your resume doesn’t have them, it’s rejected automatically.

This isn’t a FAANG-only phenomenon. A 50-person Series B startup with a recruiter handling 300 applications a week uses the same tools.

The fixes are boring but they work:

• Single-column layout. No tables, no graphics, no text boxes.
• Keywords pulled directly from the job description. Not synonyms, not paraphrases. The exact words they used.
• Standard section headings: Experience, Skills, Education. Not “What I’ve Built” or “My Journey.”

If you’re getting a callback rate under 5% on roles that should be a fit, this is almost certainly the problem.

Volume without a feedback loop is just noise

If you’ve sent 50+ applications and heard nothing, that’s data. Stop. Fix the resume before sending 50 more.

Most job seekers don’t track their applications systematically. They send, wait, move on, send again. Without tracking you can’t see patterns - which job titles are getting responses, which companies, which resume versions.

A simple spreadsheet: company, role, date applied, response (yes/no/ghosted), notes. A week of data tells you more than a month of sending blind.

A good engineer and a good candidate are different skills

I’ve rejected strong engineers on paper because they couldn’t articulate what they’d actually accomplished. Not because they hadn’t accomplished anything. Because they’d written their resume the way engineers write documentation. Here’s what the system does. Here are the technologies used.

Hiring managers aren’t reading for comprehension. They’re scanning for evidence of impact.

The difference between these two bullets is the difference between a callback and a rejection:

Bad: “Worked on database optimization project to improve query performance”

Good: “Reduced p99 API latency from 2.1s to 340ms by rewriting 3 critical query paths, eliminating the leading source of customer escalations for the quarter”

Same work. One tells me what you did. One tells me what it meant.

Referrals bypass the entire system

A referral, even a weak one, gets your resume looked at by a human. A cold application to the same role might not.

Most engineers underuse this. They don’t want to feel like they’re asking for a favor. But a LinkedIn message to an engineer (not a recruiter) at a target company asking for a 15-minute conversation is not begging. It’s how hiring actually works. The engineer who recommends you has almost no downside and gets a referral bonus if you get hired.

If you’re applying cold to every role, you’re playing the hardest version of the game.

The market is hard. But most people are losing in the resume round.

Job searches in 2025-2026 are taking longer. The market is rough. That’s real.

But the engineers getting interviews aren’t necessarily stronger than the ones who aren’t. They have resumes that work, they’re using their networks, and they’re applying strategically rather than at volume.

If you’ve been applying for months and getting nothing back, the answer isn’t more applications. It’s a better resume.

The SWE Resume System is a set of five guides built on the frameworks I developed hiring at Meta, including the OPA framework for writing achievement bullets that show impact, not just activity. If you’ve been sending applications into the void, start there.