Honest feedback accompanies maybe one rejection in fifty. That is not a statistic anyone in recruitment is proud of, but the reasons behind it are worth understanding, because they change what you should do about it.
Almost none of them are about the quality of your application.
Reason one: legal exposure
The biggest single driver, and the one nobody says out loud to candidates.
A written sentence like "we felt you lacked the commercial maturity for this level" can appear in a discrimination claim. Legal and HR functions across the industry have converged on the same guidance: say as little as possible, in writing, to unsuccessful candidates.
So the template says the company has decided to move forward with other candidates whose experience more closely matches current needs. That sentence is engineered to contain zero information. That is its function.
With algorithmic fairness now an active regulatory priority in several jurisdictions and new legislation appearing around AI in hiring, this caution is increasing rather than easing. Do not expect it to improve.
Reason two: arithmetic
A role with six hundred applicants produces perhaps eleven interviews.
Personalised feedback for the remaining five hundred and eighty-nine, at even five minutes each, is roughly fifty hours of work. That is more than a full working week, for one role, and it does not exist in any budget.
It is not going to happen — not through indifference, but because there is no version of the maths in which it does.
For the eleven who interviewed, feedback is achievable and you should ask for it. For the rest, silence is structural.
Reason three: candidates argue
Anyone who has given honest feedback has had the experience of it turning into a negotiation. You explain the gap; the candidate explains why you are wrong about the gap; twenty minutes later you are still discussing a decision that was final before the conversation started.
Only a minority of candidates do this. It takes very few before people stop offering.
Reason four, the honest one: cowardice
Sometimes the real reason is uncomfortable to say. The hiring manager did not warm to you. Someone internal was always going to get it. The role changed mid-process. Budget was pulled and nobody wants to admit the last three weeks of your time were wasted.
"We went with another candidate" is easier than any of those. That is not a defence of the practice, just an accurate description of it.
What this means for you
You are operating with no feedback loop, and that is the hardest part of a modern job search — harder than the rejections themselves.
Without feedback you cannot distinguish between:
- a CV problem
- a match problem
- an interview problem
- a ghost job
- an internal candidate
- ordinary bad luck
Then changes get made at random. New template, new summary, new photo, more applications — none of it informed by anything, because nothing came back.
You cannot fix a process you cannot measure. The answer is not to keep requesting feedback that companies are structurally unable to give. It is to build your own diagnostic loop.
Building the feedback loop yourself
Signal 1: Is my CV the problem?
Get it scored before you send it, rather than inferring from silence afterwards. The LeveliU CV Analyzer rates your CV 0 to 100 from an HR recruiter's perspective and lists what is missing, which claims read as unproven, and what to change. It also estimates a salary range, which is a useful check on whether you are pitching at the right level.
This is the feedback a recruiter would give you if they had fifty spare hours. Getting it in advance is strictly better than getting it never.
Signal 2: Is my match the problem?
The most common cause of unexplained rejection, and the easiest to diagnose.
Take your last ten applications. Paste each job description into the Job Match Engine. Look at the scores.
People who do this exercise frequently discover their average match was around 45%. That solves the entire mystery in fifteen minutes. They were not being rejected for anything wrong with them; they were applying to roles they were never positioned to win, and the silence was the system working as designed.
Going forward, the Go / No-Go verdict gives you a decision before you invest, rather than a guess afterwards.
Signal 3: Is my interview the problem?
If you get interviews but no offers, the CV and match are fine. The problem is downstream, and it is the hardest thing to see in yourself.
The Interview Coach lets you rehearse role-specific questions and get feedback on your answers, particularly the three-questions-deep follow-ups that separate people who did the work from people who were near it. Rehearsing out loud against your own material exposes which answers fall apart under pressure while there is still time to rebuild them.
Signal 4: Was the role even real?
Sometimes there is nothing to diagnose. Between 18% and 30% of postings may be ghost jobs, and a meaningful share of the rest have an internal candidate already lined up.
Build this into your model. If you have a documented 85% match, a strong CV, and still get silence, the most likely explanation is often that there was no job.
The one place you can still get real feedback
Ask, but ask correctly, and only after an interview.
What does not work: "Could you provide feedback on my application?" This triggers the legal-caution reflex and produces the template.
What sometimes works is a short, specific, low-stakes question that can be answered in one line and does not sound like the opening of a dispute:
> "Thanks for letting me know — genuinely appreciated. No need for a full debrief, but if there was one area you'd want to see stronger if I applied again in a year, I'd find that useful."
Roughly one in four recruiters will answer that. It is framed as future-oriented rather than a challenge to the decision, it is capped at one sentence, and it gives an easy exit. Send it once. Do not follow up.
And build relationships rather than transactions. Recruiters share useful information with people they have spoken to more than once.
The reframe that matters most
Silence is not a verdict. It is an absence of data, and it has been getting treated as a judgment.
Once you have your own diagnostic loop — CV scored, match checked, interviews rehearsed, ghost jobs discounted — a rejection stops being an unanswerable question about your worth and becomes a data point in a process you control.
That shift is worth more than any feedback email you were hoping for.
---
FAQ
Why do recruiters not respond after an interview?
Usually a combination of legal caution around written feedback, sheer volume, and the absence of any budget or process for it. It is rarely a specific comment on you.
How do I ask for feedback after a job rejection?
Keep it short, future-focused and capped: ask for one area to strengthen if you applied again in a year, and explicitly say a full debrief is not needed. That framing gets a reply far more often than a general request.
Is no response the same as a rejection?
Practically, yes, after about three weeks. It can also mean the role was frozen, filled internally, or never real. Do not read it as an evaluation of your application.
How can I tell whether my CV or my match is the problem?
Diagnose them separately. Score your CV, then run your last ten job descriptions through a match analysis. If the CV scores well but matches average under 60%, it is a targeting problem rather than a document problem.
What if I get interviews but never offers?
Your CV and targeting are working; the gap is in how you evidence experience under questioning. Rehearse the three-questions-deep version of your own stories out loud before the next one.
---
Get the feedback nobody is going to send you. Score your CV free in the LeveliU app.
