Rejection is the default outcome of job searching. The acceptance rate at top tech companies is under 1%. Even at companies where you're a strong fit, most candidates don't get offers. Understanding this statistically doesn't make any individual rejection feel better — but it should change how you respond to it.
Here's exactly what to do.
In the First 24 Hours: Don't Spiral
The immediate instinct after a rejection is either to catastrophize ("I'm bad at interviews and will never get a good job") or rationalize ("they were looking for someone with a different background"). Both are unproductive.
What to do instead:
Feel the disappointment. It's real. Don't rush past it. 24 hours is a reasonable window to be frustrated before you start being productive about it.
Don't do anything job-search-related for the rest of that day. Applying to 10 jobs in the emotional aftermath of a rejection produces poor applications. Your brain isn't working well enough to make good decisions.
Don't send an angry or emotional response. The recruiter who rejected you may well be a future interviewer at a company you want to work at, or a connection who can make a referral. Respond professionally or don't respond at all.
How to Respond to a Rejection (Template)
If you were rejected by a recruiter or after a phone screen, you don't need to respond at all. If you made it to the final round, a brief, gracious response is worth sending:
Hi [Name],
Thank you for letting me know, and for the time your team invested in the process. I genuinely enjoyed learning about [specific thing about the company or role]. I understand the decision, and I hope our paths cross again in the future.
Best, [Your name]
This is short, professional, and leaves the door open. It takes 2 minutes and costs nothing.
How to Ask for Feedback
Most recruiters won't give meaningful feedback without being asked directly. Most won't give it even when asked. But it's worth asking — 20% of the time you'll get something actionable.
Good ask:
"I'd value any feedback on how I performed in the technical or behavioral rounds, even briefly. I'm actively working to improve and any specific observations would be genuinely helpful."
What usually happens:
- 40%: generic response ("you were a strong candidate but we had a competitive slate")
- 40%: no response
- 20%: actual useful feedback ("your system design was strong but we had concerns about X")
If you get useful feedback, treat it as gold. Write it down. Identify whether it's fixable (a skill gap you can close) or not (they needed 5 years of a specific technology you don't have).
Analyzing Why You Were Rejected
Rejection has different root causes and they require different responses:
You didn't pass the coding round. The fix is more deliberate practice. Not more practice — deliberate practice. Identify the specific problem types you struggled with, practice those specifically, and do mock interviews under real time pressure.
You didn't pass system design. Usually means one of: weak foundational knowledge (read DDIA), poor interview format execution (learn the structure), or insufficient scale intuition. Mock interviews with feedback are the fastest fix here.
You didn't pass behavioral. Often means answers were too vague, used "we" instead of "I," lacked quantified results, or the stories didn't map to the values they were looking for. Record yourself answering behavioral questions and listen back critically.
You were rejected after an offer was made (rare). Sometimes compensation negotiations break down, background checks surface issues, or the role was eliminated. These are usually external factors.
You passed everything but didn't get selected. This happens. Strong candidate, better candidate was selected. You can't control this. Move on and apply again later.
Should You Re-Apply?
Most companies allow re-applications after 6–12 months. Whether to re-apply depends on:
Why were you rejected? If you can point to a specific, closable gap — a skill you didn't have, a format you didn't know, a level of complexity you couldn't handle — and you've genuinely closed it, re-applying is reasonable.
How early were you cut? Rejected after an onsite with strong feedback is different from rejected after a phone screen. The further you got, the better case you can make that the next attempt will go differently.
Is the role or team a strong fit? If you were a strong match for the role but the timing was off (they had multiple strong candidates), re-applying for a similar role is worth doing.
Template for a re-application: When you apply again, in your cover letter or introduction: "I interviewed for this role in [date] and wasn't selected. Since then I've [specific things you've done to address the gap], and I believe I'm now a stronger candidate for the position."
This is direct and respects the recruiter's time. Don't pretend the previous application didn't happen.
How Many Rejections Is Normal?
These numbers vary significantly by level, company, and market conditions, but as rough reference points:
- Entry level (new grad): 20–50 applications to get 2–5 final rounds, 1–2 offers
- Mid-level (3–5 years): 10–30 applications to get 3–8 final rounds, 2–4 offers
- Senior (5+ years): 5–20 applications to get 3–6 final rounds, 2–3 offers
If you're applying in high volumes and getting to zero final rounds, the bottleneck is your resume or screen. Fix that first.
If you're getting to final rounds but not getting offers, the bottleneck is your interview performance. Practice specifically for final-round formats.
If you're getting offers but rejecting them, you have a different (good) problem.
Staying Motivated Through a Long Search
The job search is a campaign, not a sprint. Long searches (3–6 months) are common, especially for senior roles or competitive companies. Here's what helps:
Track your pipeline, not your rejections. A spreadsheet with every active application, every stage you're in, and every next action turns a pile of rejections into a managed process. You can see that you have 8 active conversations even if 12 others closed as no.
Set process goals, not outcome goals. "I will apply to 5 qualified roles this week and do one mock interview" is achievable regardless of external decisions. "I will get an offer this month" is not in your control.
Take breaks without guilt. A day off from the job search doesn't make you lazy — it makes you sustainable. You will make better decisions and present better in interviews after adequate rest than after a 70-hour grind week.
Keep your skills sharp. The worst thing about a long search is skills atrophy. Do LeetCode, work on a side project, contribute to open source. These keep your mind sharp and give you things to talk about in interviews.
Every no moves you closer to the right yes — but only if you learn from each one. CareerLift helps you identify where you're losing interviews and practice specifically to close those gaps.