What to do after a rejection (and what a rejection actually means)

A rejection email is one of the least informative documents in professional life. It is written to be legally safe and emotionally neutral, sent at scale, and deliberately vague. Reading it for meaning is like reading a receipt for a story.

Here is what to do with one anyway.

Read what stage it came from

The stage tells you far more than the wording.

Rejected without a screen, within days. The most common outcome, and the least about you. Typical causes: they had internal candidates, someone was referred, the requirements were harder than advertised, the role was paused or filled, your work authorisation did not fit, or the recruiter had eighty applications and stopped at forty. There is no signal here to act on.

Rejected after a recruiter screen. Now there is a little signal. Something in the first fifteen minutes did not line up: level, compensation expectations, location, notice period, or your account of what you have done. All of those are diagnosable, and most are fixable in how you present them.

Rejected after a technical or take-home stage. Real signal about the work. Worth reflecting on, worth asking about.

Rejected at the final stage. Usually means you were competitive and someone else was preferred, sometimes on something as thin as one interviewer's preference for a different profile. This is the stage where staying in touch is genuinely worth it. Companies do come back — when the second headcount opens, or when the person who got it did not work out.

The wording almost never means anything

• "We've decided to move forward with other candidates" — the default template, sent at every stage.
• "We were impressed by your background, but…" — also the default template.
• "We'll keep your CV on file" — technically true in that the ATS keeps everything, and occasionally true in the useful sense.
• "We've decided not to move forward at this time" — no information about this time versus other times.

The exception worth noticing: a rejection with a specific reason in it ("we're looking for someone with more experience leading a team of this size") was written by a person who thought about you. That is a signal, and it is also a door — that person is worth a courteous reply.

Asking for feedback: when it works

It works occasionally, and it costs one short email. Improve your odds:

• Ask the person you spoke to, not the automated address.
• Ask within a couple of days, while you are still recent to them.
• Ask a narrow question. "Do you have any feedback?" is easy to ignore. "Was the gap mainly the depth of Kubernetes experience, or the leadership scope?" can be answered with one line, and often is.
• Make it easy to be honest. Say plainly that you are asking to calibrate, not to reopen the decision.
• Accept silence. Many companies have a policy against giving individual feedback for legal reasons. Silence is not rudeness; it is a compliance department.

Expect a reply maybe one time in five, and expect it to be brief. One useful sentence about your level or your interview framing can be worth a great deal.

Reapplying

Common employer practice, though it varies:

• A different role at the same company: almost always fine, immediately, provided it is genuinely a different fit and you are not accumulating applications on one record.
• The same role after rejection: usually pointless unless the posting is old and something material about you has changed.
• The same company after a late-stage rejection: often the best application you can make, three to nine months later, referencing the previous process. You are a known quantity with a real internal advocate somewhere.

Some employers configure a formal cooldown, often six or twelve months. If you were told one, respect it; if you were not, judge on whether anything has changed.

The ten-minute routine

Rejections deserve a fixed, small amount of process — enough to extract the signal, not enough to relitigate.

1. File it. Record the company, the role, the date, and the stage you reached. You will want this in three months when a recruiter from that company emails you.
2. If it came after a conversation, send one line of thanks. Two sentences. It costs nothing and it is remembered surprisingly often.
3. Ask the narrow feedback question if you got past the first screen.
4. Log anything you would do differently, in a sentence. Not a self-assessment — one concrete thing.
5. Close it and move on. The correct emotional weight of a first-stage rejection is approximately zero, and treating it as data rather than judgement is what lets you keep going at a steady pace.

What to actually change, and when

Do not change your approach on one rejection. Change it on a pattern:

• Lots of applications, almost no first replies. The problem is upstream: which roles you are applying to, or the top third of your résumé. Not the interview.
• Screens that consistently end after the compensation or level conversation. You are aiming at the wrong band, up or down. Fix the target, not the pitch.
• Technical stages that consistently go badly. A practice problem, not a job-search problem. Worth pausing volume and spending a week on it.
• Final rounds you keep losing. Frustrating, and often the closest to good news — it usually means the profile works and the delta is narrow. This is where mock interviews and a sharper narrative pay off.

The thing nobody says

Hiring outcomes are noisy in a way that is genuinely unfair. The same application can be rejected at one company and moved to a final round at a near-identical one, because someone was busy, or because a referral arrived first, or because the hiring manager had just had a bad experience with a candidate from your background.

That is not a reason for fatalism; it is a reason for volume with attention, kept up over a period of weeks. The noise averages out over enough attempts. It does not average out over five.