Why the best engineer loses the submission
The strongest CV ranks first and gets rejected at interview. The submission that closes is rarely the best candidate on paper — and once you see why, you can’t unsee it.
There are two questions a recruiter can ask about a role, and they are not the same question. The first is who is the best engineer? The second is who does this client actually say yes to? Sourcing answers the first. Placement is decided by the second. Confuse them and you submit the strongest CV, feel good about it, and lose.
The mistake is buried in the word “submission.” A submission isn’t a candidate. It’s a bet on a chain of things that all have to be true at once:
candidate × available × rate that closes the margin × client accepts the profile × candidate accepts the client × timing
The CV is one factor in six. It tells you whether the person can do the job. It says almost nothing about the other five — and the other five are where placements are won and lost.
What “best” quietly costs you
The candidate who looks best on paper is often best because of the things that sink the submission. Seniority above what the role needs reads, to a hiring manager, as flight risk and a rate they can’t justify. A pristine stack of brand-name employers can signal someone who’ll be gone the moment a permanent offer lands. The cleaner the CV, the more questions a sharp client asks about why this person is on the contract market at all.
A client opens a senior backend contract. Candidate A: ten years, ex-FAANG, immaculate. Candidate B: seven years, less famous logos, but two of them are in the client’s exact domain — payments, with the compliance scar tissue that comes with it.
A ranks first on every keyword. B gets the offer — because the lead engineer has been burned before by someone who needed six weeks to understand why a payment can’t simply be retried, and B clearly already knows.
Nothing about that outcome is visible in a match score. It lives in what the client has rejected before, what their team distrusts, and what “senior” means to them this quarter.
Rank submissions, not people
The shift is small to say and hard to do: stop ranking candidates and start ranking submissions. The output that helps a recruiter isn’t a verdict — “Candidate B, 87% match.” It’s an honest trade-off:
- B is the stronger bet — domain fit the client has rewarded before, a rate that clears the margin, available on the start date.
- A has more raw firepower — but the rate sits above where this client has historically closed, and the over-qualification is a real interview risk to confirm, not a reason to cut.
That output respects the recruiter. It doesn’t break if the client picks A, and it surfaces the one thing the CV was hiding.
The part the eye misses
A good recruiter feels most of this. The value isn’t replacing that instinct — it’s catching the case where the instinct is busy. The over-qualification that reads as a win. The rate that’s €40 over a ceiling nobody wrote down. The gap between what the job description asks for and what this client has actually hired three times running.
The best engineer is a fact about a person. The winning submission is a fact about a moment — this client, this margin, this start date, this risk tolerance. Treat them as the same thing and you’ll keep submitting the best CV and wondering why it lost.