Job Search Diagnostic

Application Funnel Calculator

Built by an ex-Google recruiter Last updated Runs in your browser, no signup

Your Application Funnel

When a tech job search isn't producing offers, the broken stage tells you exactly what's wrong. Enter your numbers, see where you sit versus benchmarks for your role and target tier, plus a one-page diagnosis and an estimated weeks-to-offer.

Reading the result

How to read your funnel

The point of the calculator isn't the score, it's locating which stage is your bottleneck.
Each stage has it's unique challenges, and unique solutions.

1

Apps → Phone screen

Tells you if the issue is your resume. If your callback rate is too low, it means you need to optimize for recruiter screens. Request a resume review to know exactly what to fix.

2

Phone → Onsite

Recruiter screens aim at evaluating basic fit for a role. Recruiters at that stage are not looking to eliminate you, but rather to confirm that you fit the criteria. This step reveals whether you are applying to the right roles.

3

Onsite → Final

These are proper skill tests, for both hard skills (coding, system design, role-related knowledge) and soft skills (leadership, critical thinking, etc.). Issues encountered here mean you need to work on your interviewing skills.

4

Final → Offer

There is much less to work on at this stage. If you get rejected here, it's often because another candidate scored higher. Increasing this ratio means continuous work on your skills.

Stage diagnostics

What's actually broken at each stage

From hundreds of funnel reviews, here are the patterns I see most often per stage. Match the symptom to the fix.

Stage 1

Apps → Phone screen

Resume / targeting

If you're sending 80+ applications and getting under 5% phone-screen rate, the resume is the bottleneck. Not the volume.

  • Profile summary that says nothing. "Passionate engineer" is wallpaper. Put your level, your stack, your two highest-impact wins, and target role in the first 3 lines.
  • Keyword density too low. ATS rerank by keyword overlap. If the JD says "Kubernetes" 6 times and you say it once, you sit below the threshold.
  • Level mismatch. Senior bullets that sound mid (no scope, no influence). Recruiters don't reach out for "Senior" titles with mid-level signal.
  • Channel mix too cold. If >70% is LinkedIn / job boards / cold, even a strong resume gets diluted. Push referrals to 25%+; one warm intro can replace 30 cold apps.
Read: how recruiters screen resumes →
Stage 2

Phone → Onsite

Pitch + initial tech

You get on calls but don't advance. Phone screens combine the recruiter pitch and the first technical filter, so the bottleneck is one of the two.

  • "Tell me about yourself" is rambly. 30 seconds, recruiter language: title + level + last project + impact + why-this-role. They're scoring conciseness.
  • Comp number is off-band. 20% above the band kills the call. 20% below makes them downlevel you. Mid-band wins.
  • Coding rust on the easy problems. If you haven't drilled LeetCode-easy / mediums in 12+ months, expect 2-3 weeks of warm-up to be screen-ready.
  • Role-shape mismatch. Pitching IC when the role is lead (or vice versa) ends the call. Anchor scope to the JD.
Read: how to answer open-ended questions →
Stage 3

Onsite → Final

Skills / multi-format

Onsites are the multi-round filter. If you're not advancing to final, you're failing the same format twice in a row without diagnosing it.

  • Senior+ failing on system design, not coding. Most common pattern. Fix: 8-10 mock designs across read-heavy / write-heavy / streaming / multi-region.
  • Algo coding at mid-level. Onsite coding tightens up screen-level problems with follow-ups. Practice 2-round formats, not single 30-minute drills.
  • Role-specific deep-dive blindspot. DevOps gets Linux internals. ML gets stats / experiment design. Map the most-likely deep-dive for your role and own it.
  • You don't ask follow-ups. Strong onsite candidates clarify the prompt and time-budget themselves. Going silent on ambiguity reads as junior.
Read: interview prep guides →
Stage 4

Final → Offer

Behavioral / leveling

Final rounds are where hiring committee assigns level and scores behavioral on rubric. At senior+ this is where most candidates lose offers.

  • Behavioral answers are stories, not STAR. Top tier rubrics score on Situation / Task / Action / Result with a measurable result. Free-form anecdotes lose.
  • Scope reads one level below target. "I built X" instead of "I led the team that delivered X" downlevels you on hiring committee.
  • No impact metrics. If you can't quantify outcome, the loop assumes you didn't drive it. Bring 2-3 numbers per story.
  • Many offers but low base. That's a negotiation issue, not a loop issue. Different fix.

Methodology

Where the benchmarks come from

This is the build-or-bluff question, and the honest answer matters. The benchmarks come from three layers, disclosed up front:

1 · Public market data

Hired State of Software Engineers, HackerRank developer survey, LinkedIn workforce reports, Indeed Hiring Lab. Defensible mid-market response and conversion baselines.

2 · Founder calibration

12 years recruiting including Google. FAANG-tier numbers nobody else can credibly publish, particularly at Senior+ where public data is thin.

3 · Aggregated tool usage

Submissions are anonymized and aggregated to refine benchmarks over time. No login required, no resume uploaded, math runs in your browser.

Frequently asked

Questions about the funnel calculator

The most common questions from candidates running this on themselves.

What is a normal recruiter response rate for software engineering jobs?

Cold-apply response rates typically run 5 to 15 percent for software engineers. Referrals run 30 to 60 percent. Inbound recruiter messages convert much higher because the recruiter has already pre-qualified you. The benchmark moves with role family (DevOps and Security run higher than Full-Stack), target level (Senior+ runs lower), company tier (FAANG is brutal), and whether sponsorship is needed.

How many applications does it take to get a tech job?

It depends entirely on which stage you're losing at. Most engineers aim for a 5 to 15 percent app-to-recruiter rate, then 50 to 70 percent recruiter-to-tech, then 30 to 50 percent tech-to-onsite. The total ranges from ~40 cold applications for a strong mid-market candidate to 250+ for a brand-mismatched FAANG target. The calculator shows you which assumption is failing.

Why am I not getting interviews even though I'm qualified?

The most common cause when applications aren't converting to recruiter responses is resume targeting: keyword mismatch, weak profile summary, or a level mismatch versus the JD. The calculator isolates this by comparing your stage-by-stage rates to benchmarks for your specific role family and target tier. If apps-to-recruiter is below the p25 band, the resume is almost always the answer.

Are my submissions stored or shared?

No. The calculation runs entirely in your browser. Nothing is uploaded, no signup is required, and no resume or personal data is collected. The methodology section describes a future option to opt into anonymized aggregation, but that's off by default.

How do you know what good benchmarks look like at FAANG?

FAANG-tier numbers come from founder calibration: 12 years of recruiting including time at Google, where I screened thousands of engineers and saw which funnels produced offers. Public sources don't reliably publish FAANG-specific funnel rates, and the ones that do are usually small samples. The calculator discloses this so you can weight the verdict accordingly.

How long until I should re-run the calculator?

Roughly every 30 days, or after a meaningful change like a resume rewrite, a switch from cold apply to referrals, or moving from mid-market to FAANG targets. Below 20 to 30 applications the rates are too noisy to be diagnostic.

What to use next

Related tools and guides

Tools that complement the funnel diagnostic, paired by which stage they fix.

Profile Summary Guide

For Stage 1-2 fixes. The 3-line template that recruiters actually read first.

Read the guide →

Interview Prep Guides

For Stage 3-4 fixes. Coding, system design, and behavioral frameworks for FAANG and top startups.

Read the guides →

If your top of funnel is broken, the resume is usually why

The number one cause of applications-to-recruiter rates below benchmark is a resume that misses on keywords, level, or summary. Recruiters skim in seconds. If yours doesn't pass the screen, nothing downstream matters.

Free, personally reviewed within 12 hours by a former Google recruiter.

Get a Free Resume Review today

I review personally all resumes within 12 hrs

PDF, DOC, or DOCX · under 5MB

Disclaimer. Benchmarks reflect aggregate market data plus founder calibration; individual outcomes depend on resume quality, market timing, target tier, and many factors outside of any calculator. Treat the verdict as directional, not deterministic. Submissions are not stored.