What actually happens after you apply
Every application our users track gets stamped with the fit score the posting had before they applied. This page is what those stamps add up to, published with the sample size attached to each one.
Results are preliminary
We are tracking 4 applications and 0 interviews so far. That is not enough to publish an interview rate. A score band needs at least 50 tracked applications before we put a percentage next to it, and no band is there yet. Until then this page shows raw counts only. No rate, no multiplier, no claim.
The sample
Four counts define everything below. Jobs scored is how much work the engine has done. Applications tracked is how many of those a user marked Applied. Interviews and offers are transitions recorded after that, timestamped when they happened.
4,405
Jobs scored
4
Applications tracked
0
Interviews recorded
0
Offers recorded
Interview rate by score band
Applications are bucketed by the score the posting held at the moment it was scored, not by a score recalculated afterward. The bar length is the share of tracked applications sitting in that band. The number on the right is the interview rate, which stays blank until the band clears 50 applications.
0 tracked applications, 0 interviews
3 tracked applications, 0 interviews
1 tracked application, 0 interviews
0 tracked applications, 0 interviews
Does a high score change the odds?
This is the comparison the page exists to make: how much more often a strong match turns into an interview than a long shot does. We cannot make it yet.
The multiplier needs both the 80+ band and the sub-60 band to hold 50 tracked applications each. The 80+ band currently holds 0 and the sub-60 band holds 0. When both clear the floor, the number appears here automatically, whatever it turns out to be.
Response speed and offer rate
Days to first response is the gap between the applied timestamp and the first Interview or Offer transition on the same job. Applications that never moved are excluded from that average, since a silent rejection has no end date to measure to. Offer rate counts offers against every application in the band, including the silent ones.
| Score band | Applications | Avg days to response | Offer rate |
|---|---|---|---|
| 80+ | 0 | Not enough data | Not enough data |
| 70-79 | 3 | Not enough data | Not enough data |
| 60-69 | 1 | Not enough data | Not enough data |
| <60 | 0 | Not enough data | Not enough data |
Methodology
How the data is collected
Every job on a ShouldApply dashboard carries a status. When a user moves one to Applied, the applied timestamp is written to the job row. Later transitions to Interview or Offer write a separate history row with their own timestamps. This page reads both tables directly, groups applications by the stored fit score, and counts transitions. Nothing here comes from a survey, a self-reported outcome form, or an estimate.
Sample sizes and the 50-application floor
No band publishes a rate below 50 tracked applications. At 10 applications, a single interview moves the rate by 10 points, which makes the percentage a story about one person rather than a pattern. Bands under the floor render their raw counts in gray and nothing else. The floor is applied per band, not to the total, so a healthy 80+ band does not license a claim about the sub-60 band.
Known limitations
Three of them, stated plainly. Status changes are self-reported, so applications that quietly died are undercounted relative to ones that went somewhere. Users choose which jobs to apply to, which means a high-scoring application also tends to be one the person actually wanted, and the score is not the only thing that changed. And the sample skews toward people who care enough about their search to track it, who are not a random draw from the job market.
Freshness
This page rebuilds every 24 hours against live counts. Last built September 2, 2026. The earliest tracked application in the sample is from March 2026. Read how the score is calculated for the five dimensions behind every band on this page, or ghost job detection for why some applications never get a response at all.
Why this page exists
Every job search tool claims it improves your odds. Almost none of them show the denominator. We would rather publish a page that currently says the numbers are not ready than one that turns 4 applications into a confident-sounding multiplier.
The scoring engine can be judged on its own terms in the meantime. It reads a job description against your profile across five weighted dimensions, tells you which requirements you miss and what each miss costs, and flags postings that show low hiring intent before you spend an afternoon on them. That work is verifiable the moment you score a job. Whether it moves the interview rate is a separate question, and this is where we will answer it.
See your scores
Score three jobs free and read the gap analysis on each one. No credit card, no trial timer.
Questions about this data
Where does this data come from?
From the status history on jobs our own users tracked. When you move a job to Applied, Interview, or Offer on your dashboard, that transition is written to a job_status_history row with a timestamp. This page reads those rows, groups them by the fit score the job had when it was scored, and counts how many reached each stage. Nothing is surveyed, estimated, or modeled.
Why are some numbers missing?
A score band only publishes a rate once it holds at least 50 tracked applications. Below that, one lucky interview swings the percentage by double digits, so we show the raw count instead of a number that looks precise and is not. Bands fill in on their own as tracking volume grows.
Does a high score guarantee an interview?
No. The score measures how well your profile matches what the posting asks for. It cannot see the internal candidate who already has the job, the req that got frozen last week, or the recruiter who never opens the ATS. A high score means you are a defensible applicant, not a scheduled one.
Why measure from applied, not from scored?
Most scored jobs are never applied to, which is the point of scoring them. Measuring interviews as a share of everything scored would drag every band toward zero and say more about how selective people are than about whether the score predicts anything. Applications are the honest denominator.
Can users game these numbers?
Status changes are self-reported, so yes, in principle. Two things limit it. The people entering the data are the people relying on it to decide where to apply next, so there is no upside to lying to themselves. And the counts are dominated by the plain mechanics of a job search, where an unreported interview is far more common than a fabricated one, which makes the interview rates here a floor rather than a ceiling.
How often does this page update?
It rebuilds every 24 hours against live database counts. There is no cached snapshot or hand-entered spreadsheet behind it. If tracking volume triples tomorrow, the bands here reflect that within a day.
Related: How scoring works · Ghost jobs guide · Pricing