Why you never hear which line lost it

You rarely hear which line lost the application because nothing in shortlisting requires the reader to say, and often there is no single line to name. The reader may only have failed to find what the posting asked for, or found another application easier to choose. A silent rejection therefore tells you almost nothing about any one line, which is why the useful move is to run the reader's check yourself before you apply.

What follows covers what the reader was deciding, what a silence can and cannot tell you, an example of a line that is fine and still does not show the ask, and how to find the weak spot yourself.

What the reader was deciding

A recruiter reading a CV is not asking whether you could do the job. They are asking whether they can tell, from the page, that you could. Those are different questions. The first is about you. The second is about what the page shows.

That is why a rejection can feel unfair. You may well be able to do the work. A reader may not have decided you could not. They may only have found nothing on the page that showed it.

Why the reason never gets sent

A shortlist can be built without writing a reason for every CV left off it. Giving feedback is a separate job from choosing who goes forward, and a rejection that says nothing is what you get when only the first job is done.

Even a recruiter willing to explain would often have little specific to say. If the trouble is that nothing on the page showed what the role needed, there is no single line to point at.

What a silence cannot tell you

A silent rejection cannot tell you whether a line was weak, whether something the posting asked for was missing, or whether another application was simply easier to choose. Those look identical from your side.

So treat one silence as no information about any particular line. Guessing which line lost it after the fact is a poor use of effort, and the honest alternative is to check before the next application goes out. Why a CV passes the ATS and is still rejected covers a related distinction, between being found and being convincing.

A line that is fine and still does not show the ask

Here is an invented posting ask and CV line, written for this article and not taken from any real posting or CV. The posting asks for someone who can "resolve customer problems and write help articles others can follow." The CV says: "Helped students with laptop and account problems at a university IT help desk."

The line is true and reasonable. It shows the first half of the ask. It does not show the second, so a reader looking for help articles finds nothing to point at.

A rewrite would say: "Resolved laptop and account problems at a university IT help desk, and wrote the desk's guide to resetting a forgotten password." Nothing about the person changed. The line now shows both halves of the ask.

How to find the weak spot yourself

You can run the reader's test before you apply. Take the posting and pick out its main asks. For each ask, look for the line on your CV that shows it, and give yourself only a short look.

If you cannot find one, that is the weak spot, whether the line is missing, too general or hard to reach. Then ask someone who does not know your work to do the same. They only have the page, which is the position the recruiter was in.

What to make of a rejection

Silence from several similar roles proves nothing about a specific line. It is a good reason to run the check on the next posting before you apply, rather than after.

MyRecruiterCheck's application checker compares your CV with one job description and reports strengths, areas to improve and an Interview Score based on the evidence in your CV. Your first check is free, see the free CV checker. For the wider picture of what a recruiter looks at, see how a recruiter evaluates your CV.