How many applications per offer: the job search funnel

You sent eighty applications in a month, went to a few interviews, and there is no offer. The feeling is "nobody wants me." Nothing can be done with that conclusion, because it does not say what to change.

It helps to count a job search as a funnel. Some processes drop out at every stage, and there is almost always one stage where the losses are clearly larger than elsewhere. That is the one to fix. A hint about where to look comes from interview reviews of Sobes users: across 20.6 thousand reviews, the average success score is 83% for HR interviews, 61% for technical ones and 52% for system design. These are scores of answers, not pass rates, but the gap between stages is visible.

The stages

A typical path in IT looks like this:

1. Application. You sent a resume or a recruiter wrote to you.
2. Invitation. The company replied and suggested a call.
3. Screening. A talk with the recruiter: experience, motivation, money, format.
4. Technical interview. One or several sections: theory, live coding, system design.
5. Final. A conversation with the manager or the team.
6. Offer.

Companies name the stages differently, some add a take-home task, some have two technical rounds. For the math it does not matter: count the transitions you actually have.

How to calculate your conversion

All you need is counters: how many processes reached each stage. The conversion of a stage is the number of processes that moved on divided by the number that reached it.

Below is a sample calculation. The numbers are made up for illustration and do not describe the market: your funnel may look completely different.

In this example, one offer took 60 applications. A more useful number is the lowest conversion among the stages you can influence by preparing. Here it is the technical interview: of twelve processes, four moved on.

Let's check what improving each stage would give with the same 120 applications:

• Invitations go from 15% to 20%: 24 invitations, 16 passed screenings, 5 passed technical rounds, 2 or 3 offers.
• Half pass the technical round instead of a third: the same 18 invitations and 12 screenings, but 6 passed technical rounds and 3 offers.

In this made-up example, working on the technical stage gives more than rewriting the resume. For another person it is the opposite: at 3% invitations almost nothing reaches the technical round, and it is too early to prepare for it.

Two warnings about counting. Percentages mislead on small numbers: two finals and one offer is not "a 50% conversion", it is two cases. Draw conclusions where you have at least ten processes. And count separately the applications you sent yourself and the inbound messages from recruiters: inbound converts to an invitation differently by definition.

Where the bottleneck is and what to do about it

Few invitations

Many applications, almost no replies. There are usually three reasons.

The resume does not show what the posting is looking for: key technologies are missing from the experience section, the headline does not match the role name. How to fix that is covered in the post on a resume that gets past ATS and HR.

The filters are too wide: you apply to everything that mentions Python, including roles of a different grade and profile. Narrow the search and compare the conversion before and after.

The resume is not seen: it has not been updated for a while and has sunk in the search results. There is a separate post on that: how to bump your resume on hh.ru and set up filters (hh.ru is the main job board in Russia).

Dropping out at screening

You get calls, but the process ends after the talk with the recruiter. Most often expectations on money and format do not match, or your self-introduction did not line up with the resume. Check three answers: about yourself, why you are leaving, what number you want. All three are covered in the post on the HR screening.

Dropping out at the technical round

A single overall number helps little here, you need to see which topics cost you points. Write down the questions right after each interview and, after three or four interviews, look at what repeats. How to run such a review is described in "Failed a job interview? What to do next".

Dropping out at the final

The people who reach the final are the ones the company is technically ready to hire. A rejection here is usually about motivation, expectations of the role or money. Ask the recruiter for feedback: at this stage the reason is usually specific and easier to name.

Time counts too

Besides conversion, look at how many days a process sits at each stage. If three weeks pass between screening and the technical round, you are losing time rather than processes: in those weeks other companies manage to make an offer, and the timelines drift apart. Reminding the company about yourself and asking for the date of the next step at the end of every call helps here.

Where to get the numbers

A table in your notes is enough: a row per company, columns with stage dates and the outcome. The main thing is to enter rejections and silence too, otherwise the funnel will look better than it is.

The Sobes tracker counts this for you. A job card moves through stage columns, and the statistics show how many processes reached each stage, which stage the rejections came from and how long cards stay at a stage. A rejection is attributed to the stage you moved the card from, so you can see exactly where processes break off. The statistics can be exported to PDF.

What to do this week

Put all processes from the last two months into one table and calculate the four transitions. Pick the one stage with the worst conversion and one change for it: a new resume, different filters or three sessions on a weak topic. Recalculate after twenty to thirty new applications. Changing everything at once is not worth it: you will not know what worked.