What a rejection email actually tells you

"We have carefully reviewed your application and have decided to move forward with other candidates."

That sentence is the standard closing line of a job application, and it says almost nothing. But knowing what it does not say turns out to be more useful than what it does.

What the sentence actually means

"We have carefully reviewed" is often untrue. The same template goes out both to the application a person read and rejected, and to the one an automated filter dropped before any human saw it. You cannot tell which from the email.

"We decided to move forward with other candidates" is an outcome, not a reason. The phrasing is deliberately neutral: it makes no claim, so there is nothing in it to argue with.

"We will keep your CV on file" is usually not a real promise. Some companies genuinely revisit candidates; for most this is the closing courtesy of the email. Do not wait on it.

Rejections that give a reason are the minority

A rejection email with an actual reason in it is rare, and companies avoid it deliberately: writing one takes time, and a badly worded reason carries legal risk. So a template goes out instead.

When a reason does appear, it is usually one of three:

• Language. "The language level required for the role" — the most common concrete reason in cross-border applications.
• Location or work authorisation. "Your current location", or a visa requirement. Neither is something you can fix, but both should change what you target.
• Years of experience. "The level of experience we are looking for." The most common and the least informative.

Worth noting: salary expectations and technical shortcomings are almost never stated in writing. When those are the reason, they do not appear in the email.

The timing tells you more than the text

• Within hours, or the same day: automated screening. Your CV did not reach a person. Usually one filter criterion — years of experience, location, a keyword.
• Within one or two weeks: normal screening. It was probably read, and others were preferred.
• All at once after the posting closed: the pool was closed. You were not singled out; the process ended.
• After an interview: this is the one point where you can actually get information.

If it came after an interview: ask

Replying to a post-interview rejection with one short question is both reasonable and often productive. Do not ask "why didn't I get it?" — that puts the reader on the defensive. Ask instead: what would make me a stronger candidate next time?

The second question is risk-free to answer, and you have a real chance of getting something back. It is the one concrete thing a rejection email can be turned into.

If no answer comes, leave it there.

What a rejection is actually good for

A single rejection means nothing statistically. The distribution is what carries information:

• If most applications get no reply at all, the problem is usually that the CV is not clearing the first screen.
• If fast rejections dominate, you are being filtered out — read the hard requirements in the posting more carefully.
• If post-interview rejections dominate, the CV is working and the problem is further down the process.

Telling those three apart means counting rejections — and almost nobody counts rejections, because they all get deleted.

The simplest way to keep them countable is a sheet: a status and a date per application, reviewed monthly. Template here. e-kariyerim reads them out of your inbox instead: it recognises a rejection email, offers to mark the matching application, you confirm — and it records the stated reason separately when there is one.

One rejection teaches you nothing. Forty of them do, but only if they were counted.

Related: how long to wait after applying.