70 Applications, No Offer. What's Actually Going Wrong.

A post hit Reddit this week. Senior engineer, Germany, 70+ applications, multiple final rounds, zero offers.

The comments were full of people saying “same.” They’re right. This is happening everywhere.

But “it’s a tough market” is only half the story. The other half is that most engineers are losing at specific, identifiable points in the process, and fixing the wrong one wastes months.

During my time running hiring at Meta, I watched thousands of candidates move through the pipeline. The ones who stalled almost always stalled at the same places. There are only three.

Stage 1: Your resume never reaches a human

Signs: callback rate under 5%. Hearing nothing back even on roles where you’re clearly qualified.

The most common cause isn’t a weak resume. It’s an invisible one.

Most companies run resumes through Applicant Tracking Systems before a recruiter ever opens them. The system scans for keyword matches against the job description. If your resume says “improved system performance” and the JD says “reduced latency,” the ATS may not connect them. Your resume gets filtered before anyone has a chance to disagree with the robot.

Format matters just as much as content. Two-column layouts get mangled by parsers (content ends up in wrong fields or gets dropped entirely). Graphics, charts, and icons are invisible to the system. Your carefully designed skills section with progress bars? The ATS sees a blank space.

Then there’s the content itself. Bullets that describe what your job was instead of what you accomplished. No numbers anywhere on the page. If a recruiter does see your resume after the ATS lets it through, vague descriptions of responsibilities give them nothing to grab onto.

If you’re applying to roles where you’re genuinely qualified and hearing nothing back, stop applying. Fix the resume first. Sending 50 more applications with a broken resume doesn’t produce different results. It produces 50 more rejections.

Stage 2: You’re getting interviews but not advancing

Signs: passing recruiter screens, reaching technical or onsite rounds, then silence.

This usually comes down to one of three things.

You’re technically strong but not communicating it clearly. In an interview, knowing the answer isn’t enough. You have to show your reasoning in real time. Interviewers are trained to look for specific signals: how you break down the problem, how you handle ambiguity, whether you consider edge cases before being prompted. If you’re not delivering those signals proactively, even the right answer can look weak. I’ve seen candidates solve the problem correctly and still get a “no hire” because the interviewer couldn’t follow their thought process.

The behavioral questions are hurting you. “Tell me about a conflict with a teammate.” “Describe a time you failed.” Most engineers treat these as an obstacle between them and the technical rounds. But at every company above a certain size, behavioral signals carry as much weight as technical ones. When the hiring committee meets, a weak behavioral signal can kill an otherwise strong packet.

You might be targeting the wrong level. If you’re consistently making it to the final round and stopping there, it’s worth asking whether you’re applying at the right seniority. A strong senior engineer interviewing for staff will pass the technical screens but miss the system design and leadership signals. That’s not a skills problem. It’s a targeting problem.

Stage 3: Final round, no offer

This is the hardest one, because you did almost everything right.

At this stage it usually comes down to one of a few things: leveling (you performed at the level below what the role requires), a specific red flag from a particular answer or reference check, or dynamics that had nothing to do with you. The role filled internally. Budget changed. You were second and the first person accepted.

The practical advice here is counterintuitive. If you’re consistently reaching final rounds, you’re not broken. Your resume works. Your interview skills work. You need more volume. Five final rounds with zero offers is unlucky. Fifteen with zero offers is a pattern worth investigating. But at five, the most likely answer is that you need more at-bats.

Diagnose the stage before you fix anything

70 applications with zero interviews is Stage 1. Stop applying. Fix the resume.

10 applications, 8 interviews, zero final rounds is Stage 2. The resume is working. Interview performance needs work.

5 final rounds, zero offers is Stage 3. The process is working. You need more attempts and honest feedback on what’s costing you at the close.

Most people treat job searching as a single problem. It isn’t. The fix depends entirely on where you’re losing, and most engineers have never stopped to figure that out.

If you’re losing at Stage 1, the SWE Resume System covers exactly this. Built from the frameworks I used evaluating candidates at Meta, including how to write bullets that lead with outcomes instead of activities and how to get past ATS filtering before a human ever sees your name.