How to Respond to Job Rejection (and When to Ask for Feedback)

Rejection is the default state of job searching. You will hear no far more often than you hear yes, and that doesn't stop being true at any level of seniority. How you handle rejection matters less than it feels in the moment — but the rejections you handle well can quietly become the interviews and offers you get eighteen months later.

First: Separate the Feeling from the Response

Don't reply to a rejection on the day you get it, especially not one you cared about. Give yourself a night. The first draft you want to write — the one explaining why they were wrong, or asking pointed questions about what happened — is almost never the one you should send.

Rejection stings because you made yourself vulnerable and the answer was no. That's a real feeling. Process it with a friend, a walk, or nothing at all. But don't process it in writing with someone who has power over your career.

Whether to Reply at All: Yes

Even when the form email says "no reply needed," send one. Two sentences. It takes thirty seconds and keeps the door open for roles that don't exist yet. Most candidates disappear after a rejection; the ones who respond warmly are remembered for years.

What to Actually Write

Structure: thanks, acknowledge the outcome without apologising for yourself, leave the door open.

That's it. No self-justification, no "but I really thought…", no gratitude that sounds like flattery. Just warm, brief, professional.

Asking for Feedback: When and How

You can ask, and sometimes you'll get useful answers. But calibrate your expectations — most companies have legal policies against giving specific feedback, and most interviewers don't remember enough detail to help a week later. Expect a general answer at best.

When to ask

• You had multiple rounds. One-round rejections rarely produce useful feedback.
• You had a warm contact in the process — recruiter, hiring manager, employee referral. Cold-email HR is the lowest-yield option.
• You're specifically trying to improve, not looking for reassurance.

How to ask

Key phrases: "specific", "work on", "completely understand if it's not possible". You're framing it as self-improvement, not as protest, and you're giving them easy permission to decline.

What to Do With the Feedback

If you get real feedback, it falls into three buckets, and how you react depends on which:

1. Feedback about the role fit

"We went with someone with more direct experience in [domain]." This is not about you — it's about the specific match. No change required beyond being realistic about which roles you're close on.

2. Pattern feedback you've heard before

If two or three interviewers mention the same thing, it's real. "Your examples tend to be at the team level — we wanted to see more evidence of cross-org impact." Take it seriously. Refine your stories.

3. One-off subjective feedback

"You seemed a bit nervous early on." Useful as data, but don't overfit. One observation from one person on one day isn't a pattern.

The move is to notice themes across multiple rejections, not to rewrite yourself after each one. Keep a running note of feedback you've received; at five rejections, look for patterns.

Staying in Touch

A rejection is often a timing mismatch, not a skills mismatch. The person who interviewed you will move to another company, or will have a different role open in six months, or will remember you when a more junior or senior version of the same role comes up. Your job is to stay on the map without being a nuisance.

• Connect on LinkedIn if you haven't already, with a short reference to the process.
• Comment occasionally on their posts or their company news. Once a quarter is plenty.
• Send one useful thing a year — an article, an intro, a congratulations on a promotion. No ask.

A year later you're a warm known quantity. When they're hiring again, you're the candidate they already trust.

When to Reapply

Most companies have informal policies about reapplying — often six to twelve months. You can reapply sooner if:

• The role is genuinely different (not the same title one level up).
• You've added a specific capability the last rejection was about ("I've now led a cross-team initiative, which was the concern last time").
• The previous rejection was clearly about role fit, not you.

When you do reapply, reference the prior process directly: "I interviewed for [role] in [month]. Since then I've [specific change]. I'd love to be considered for [new role]." It's candid and it signals growth.

Things Not to Do

• Argue the decision. You won't win it, and you'll be remembered for the worst possible reason.
• Ask for the name of the person who got the job. Nobody is going to tell you, and asking looks bitter.
• Vent about the company publicly. The recruitment industry is tiny and screenshots are forever.
• Ghost the recruiter. They're a future ally. Treat them like one.

The Bottom Line

Rejection is not a verdict on you — it's one data point on one role at one moment. Reply warmly, ask for feedback if the context is right, look for patterns across multiple rejections rather than overfitting to one, and stay lightly in touch with people who interviewed you. The rejections you handle with grace are the seeds of the offers you get next time.