jobhunt.coach

Writing

Qualified but not getting interviews? Audit the funnel first

An application passes through stages: you choose a posting, a form screens you, software parses your documents, a human skims them, and someone decides whether to talk to you. Failure at any stage produces the same output on your end, which is nothing. That's what makes self-diagnosis hard. The rejection email, when it comes at all, doesn't say which stage killed you.

Start with targeting, because it's the cheapest to check. "Qualified" is doing a lot of work in the question. Qualified against the posting's listed requirements, or qualified relative to the people you're competing with? Applying to a popular posting costs nearly nothing, so popular postings collect far more applications than anyone reads carefully, and being qualified stops being the filter; being obviously, specifically relevant is. A batch of applications to roles where your experience is adjacent rather than central can go silent while you meet every listed requirement on paper.

Next, look for hard blockers, because they're the most commonly misdiagnosed. When we built jobhunt.coach's fit analysis, the instructions ended up spending a whole paragraph forcing a distinction the first attempts kept blurring: a gap is not a disqualifier. A gap is fewer years than asked, or adjacent instead of exact experience. Requirement lists are wish-lists, and employers routinely hire people missing items on them, so a gap is a negotiation point. A disqualifier is different in kind: work authorization, a mandatory license or clearance, an onsite requirement you can't meet. Those are usually screened by a form checkbox before any human reads your prose. If your target roles carry a disqualifier you keep hoping the résumé will outweigh, the résumé never gets the chance. No rewrite fixes a checkbox.

Only after those two checks does the résumé itself become the suspect, and even then what matters is whether the claims are checkable. "Contributed to backend services" survives a skim without leaving anything behind. Scope, numbers you can defend, and what was yours versus the team's give a skimming reader something to stop on. That kind of revision is worth doing. It's also different work from polishing, and I'd call it evidence-tightening rather than rewriting.

There's a mechanical layer too: parsing software sits between your PDF and the first human, and I've written elsewhere about what that software actually checks. It's worth ruling out, though in my experience people overweight it precisely because it's the failure mode that isn't their fault.

The last hypothesis is the channel. If every application goes cold into a portal, you're entering at the funnel's widest, most crowded point. A referral enters the same funnel several stages later. If you've made forty cold applications and zero attempts to reach a human at a company you care about, the fix probably isn't in your documents at all.

How do you tell which of these is your problem? Honestly: slowly, and with records. Treat it like debugging. Change one variable across your next batch, not four, and write down what you changed and what came back, because a month from now you will not remember which applications went out with which version. Keep the batch sizes honest too. Ten applications is a small sample; a quiet ten tells you much less than it feels like it does.

I should say plainly what this audit can't do. Nobody can look at a résumé alone and tell you why you're not getting interviews, whatever a paid review promises. The résumé is one stage of five. And sometimes the answer is the market: a hiring slowdown in your niche produces exactly the same silence as a broken funnel, and no amount of auditing your own side reveals it. If your peers with comparable experience are also hearing nothing, that's real information, and the response is patience and channel work rather than another rewrite.

jobhunt.coach automates the parts of this that automate well: the fit analysis separates gaps from genuine disqualifiers before you apply, and the tracker keeps the records the debugging depends on. But the loop itself, changing one thing and watching what happens, is yours to run either way. Rewrite the résumé if the audit points there. Just do the audit first.