Skip to content

Early accessPlaceMeFast is not publicly available yet. Join the list to be told when it opens.

The Job Search Numbers Worth Watching

Applications sent is the number everyone tracks and the least useful one available. Four measurements that actually tell you what to change about a stalled search.

By TODO_BEFORE_LAUNCH(PlaceMeFast)6 min read

In short

  • Applications sent measures effort, not progress, and it rewards exactly the volume behaviour that hurts a senior search.
  • The number that matters is where candidacies die. Each of the four possible answers points at a different fix.
  • Response rate by source usually shows that the channel absorbing most of your effort is not the one producing results.
  • Any metric you have to maintain by hand will decay. Design for the version that updates itself.

Every job-search tool shows you applications sent. It is the easiest number to produce and the least informative one available.

It measures effort. It goes up when you work harder and stays flat when you think harder, which is precisely backwards for a senior search where targeting matters more than volume.

Here are four measurements that actually change what you do.

1. Where candidacies die

The single most useful thing you can know about your own search.

Take your last five or ten closed processes and record the last stage each one reached. The distribution points at one of four diagnoses, and they call for completely different responses.

Dying at application, with no acknowledgement. Nobody engaged at all. Either you are applying to roles you are not a credible candidate for, or your materials are not surfacing — often because the document parses badly and never appears in the searches recruiters run against the pool.

The fix is targeting or mechanics. Applying to more will multiply the same broken input.

Dying after the recruiter screen. Someone engaged, spoke to you, and stopped. Your positioning is not landing — the story of what you do and why you are moving is not coherent in twenty minutes to someone who does not know your context.

The fix is the story, not the volume.

Dying after the hiring-manager conversation. You got to the person who owns the role and it did not convert. Usually scope fit: you are being read as too senior, too junior, or from too far outside the domain.

The fix is which roles you pursue, and often means narrowing rather than widening.

Dying at final stage. You are competitive and losing to other competitive people. Uncomfortable, but this is the healthiest of the four.

This is the only case where more applications genuinely helps, because your conversion rate is real and the process really is partly a numbers game at this point.

Most people who respond to a stalled search by applying harder are in case one and applying the remedy for case four.

2. Response rate by source

Track how each process started: cold application to a posting, inbound recruiter approach, referral, direct outreach to a hiring manager, or an agency submission.

Then look at what fraction of each reached a human conversation.

These rates differ enormously, and almost always in the same direction — warm routes convert at a multiple of cold ones. After two or three months you will have enough to see your own numbers rather than the general claim.

The reason this is worth measuring rather than assuming: it usually reveals that most of your effort is going into the channel producing the fewest results. Cold applications are the easiest thing to do more of, which is exactly why they absorb the time.

That is an argument for reallocating effort, not for abandoning cold applications. But you cannot reallocate what you have not measured.

3. Time in stage, and time since last contact

Two related numbers that answer different questions.

Time in stage tells you how the market is behaving. Processes that used to move in a week now taking three is a signal about hiring conditions or about your targeting having shifted upward, where processes are inherently slower.

Time since last contact is the operationally important one. Most stalled processes do not end with a rejection — they go quiet. Without this number, "quiet" is invisible, and you will believe you have eight live processes when four of them have not moved in a month.

Anything past about three weeks with no contact should be treated as stalled by default: follow up once, then mark it dead. Leaving it ambiguous is how a pipeline comes to look far healthier than it is, which then leads to the wrong decision about whether to be adding to it.

4. Active count

How many processes are genuinely live right now — not applications sent, not companies contacted. Processes where a human is engaged and something is expected to happen.

Both directions of this number are informative.

Too few — one or two — and every rejection is destabilising, which affects how you negotiate and how you come across. It also removes any leverage at offer stage.

Too many — fifteen or twenty — and none of them are getting real attention. At senior level, where each process may involve preparation for multiple stakeholders, this is not sustainable and the quality drop is visible.

Somewhere around five to ten live processes is where a senior search tends to function well: enough that no single outcome is decisive, few enough that each gets prepared for properly.

The numbers not to bother with

Applications sent. Discussed above. It measures the input you should be trying to reduce per unit of result.

Profile views. Weakly correlated with anything. It rises when you post something, which is not the same as being considered for a role.

Rejection count. Emotionally salient, informationally empty on its own. What matters is at which stage, which is measurement one.

Any "match score" from a tool with no access to the employer's system. It is scoring against a model of its own invention. Treat it as a hint about your materials, never as a prediction about the outcome.

Design for the version that maintains itself

The practical failure of all of this is that a manual system decays. Logging a rejection has no immediate benefit — the payoff arrives weeks later when you need to reconstruct the pattern — so it slips, and a week-stale record stops being worth updating at all.

The state you need is mostly arriving in your inbox anyway: confirmations, rejections, scheduling threads, recruiter replies. Each one marks a stage transition that someone else already recorded for you.

Whatever you use, the test is not which system is most capable. It is which one you will still be updating in month four.

The point of measuring

Not optimisation. A senior job search is not a funnel to be tuned, and treating it as one produces exactly the volume behaviour that makes it worse.

The point is diagnosis. A search that is not working feels uniformly bad, and that uniform feeling produces uniformly wrong responses — apply to more things, widen the targeting, lower the expectations.

Knowing that eight of your last ten candidacies ended at application with no acknowledgement, while the two that came through referrals both reached final round, converts a vague sense of failure into a specific and actionable fact. That is the whole value of it.

PlaceMeFast is in early access

AI that finds, tailors, and applies to the right jobs. Join the list to hear when it opens.

Get early access