Handle Rejection and Keep Going — Career Growth for Engineers, Part 10
Career Growth for Engineers · Part 10
A senior engineer is turned down for a staff role after a five-round loop. The recruiter's email is polite and says nothing specific. They replay every answer for a week, decide the system design round must have gone badly, and spend the next month drilling distributed systems. Then they are rejected again, by a different company, after a loop where they felt the design round went well. Only when a former colleague who works at the second company tells them informally what happened do they find out: both rejections came from the same gap, which wasn't design at all. In both behavioural rounds they had described influence as "I convinced my manager", and both committees read it as someone who escalates rather than builds agreement.
One rejection told them almost nothing. Two, compared, told them exactly what to fix. They had spent a month fixing the wrong thing because they treated the first rejection as a verdict instead of a data point.
The working claim: a single rejection is mostly noise; a pattern across rejections is signal. Handling rejection well means protecting your ability to keep searching while you collect enough data to see the pattern.
Before you start
List the rejections from your current search or promotion attempt: the company or cycle, the stage you reached, and any feedback, even vague.
Note the date and how you felt afterwards, honestly. The point is to see how rejection is affecting your search, not to judge the feeling.
Have the story bank from Part 9 and any interview notes to hand.
Step 1: Expect it, and know what it does and doesn't mean (10 min)
Hiring decisions depend on many things outside your control: how many strong candidates applied, an internal candidate, a change in budget or headcount, the particular interviewers, or the role being redefined halfway through. A rejection after a final round often means you were close and someone else fitted a specific need slightly better.
That doesn't make the rejection painless, and it shouldn't make you dismiss it. It means the rejection is one noisy reading. Treating it as a final verdict on your ability is the most expensive mistake, because it changes your behaviour based on very little information.
Test you can run: for your most recent rejection, write down three explanations that have nothing to do with your ability (an internal candidate, budget, a different profile wanted). If you find the alternatives implausible, ask yourself what evidence you actually have for the explanation you chose.
Step 2: Ask for specifics, once, and make it easy to answer (10 min)
Many companies won't give detailed feedback, often for legal reasons. Some will, especially through a recruiter who wants you to apply again. Ask once, politely, with a narrow question that is easy to answer: "Was there one area where the panel felt I fell short of the level? I'd find it useful for my development." For an internal promotion, the question to your manager is the same, and they have far less reason not to answer it.
Former colleagues or contacts at the company (Part 7) can sometimes give you more context informally. Don't press them for confidential details.
Test you can run: count how many rejections you've received and how many times you asked for specific feedback. If you asked fewer than half the time, you are leaving the most useful data uncollected.
Step 3: Look for the pattern across rejections (15 min)
Once you have three or more rejections, compare them. Put each in a row with the stage reached, the round that seemed weakest, and any feedback:
Company / cycle | Stage reached | Weakest round (your view) | Feedback given | Notes |
A | Final | Design | None | Felt rushed on scaling |
B | Final | Behavioural | "Influence examples" | Similar story used |
C | Phone screen | Coding | "Didn't finish" | Problem type I'd skipped |
Patterns appear quickly: rejections clustering at one stage, one type of round, one theme in the feedback, or one type of company. A single "didn't finish" is noise. Three rejections at the final stage with feedback about influence is a clear signal about one story or one way of describing your work.
Test you can run: cover the "your view" column and look only at stage and feedback. Does a pattern appear that differs from what you assumed? Your own view of which round went badly is often wrong, as it was in the opening example.
Step 4: Write it out, then put it down (15 min)
Rumination, replaying the interview for days, uses the energy you need for the next one. There is good evidence for a structured alternative. In Spera, Buhrfeind and Pennebaker's 1994 study, 63 recently laid-off professionals were randomly assigned to write about their thoughts and feelings about losing their jobs, to write about a neutral topic, or not to write. The expressive-writing group was re-employed faster: after eight months, about half had full-time jobs, compared with fewer than a fifth in the other groups. They didn't get more interviews. Writing seemed to change how they came across in the interviews they did get.
The method is simple: for a few days, write for about 20 minutes about the rejection and how it affected you, privately, without editing. Then stop.
Test you can run: after your next rejection, write for 20 minutes the same day, then note on a scale of 1 to 10 how much it occupies you the next day, compared with your last rejection. If writing helps, you'll see it in that number.
Step 5: Be accurate with yourself, not harsh (10 min)
Many engineers believe harsh self-criticism keeps them sharp. The evidence points the other way. Breines and Chen (2012) found in four experiments that people who responded to a failure with self-compassion, an accurate and kind view of what happened, were more motivated to improve than those who focused on boosting their self-esteem. In one experiment, after failing a difficult test, the self-compassion group spent more time studying for a second attempt.
Self-compassion isn't excusing yourself. It is describing the failure the way you'd describe a respected colleague's: specifically, without catastrophising, and with an eye on what to do next.
Test you can run: write down what you said to yourself after your last rejection. Would you say it to a colleague you respect who'd had the same result? If not, rewrite it as you would to them, and keep the part that names something to fix.
Step 6: Keep the search effective, not just busy (10 min)
Kanfer, Wanberg and Kantrowitz's 2001 meta-analysis found that job-search behaviour, how much effort and how intensively people searched, was clearly related to finding work, and that a person's beliefs about whether they could succeed shaped how much they searched. Rejection lowers those beliefs, which lowers search effort, which leads to fewer offers. Breaking that loop is the practical point of the steps above.
Keep the search effective: a steady weekly target of applications and conversations, at least half through your network rather than cold, and your pattern analysis feeding into what you practise. Keep a short list of real wins (projects shipped, problems solved, feedback received) to read when your confidence is low. It is evidence, not decoration.
Test you can run: compare the number of applications and conversations you had in the two weeks before your last rejection with the two weeks after. A big drop means the rejection is shrinking your search, which matters more than the rejection itself.
Worked example: one search, three rejections, one fix (composite scenario)
Context. A senior engineer at a healthcare software company applies for staff roles at three companies over two months.
Decision. After the first rejection (final round, no feedback), they resist changing their preparation. They ask the recruiter one narrow question and get no answer. After the second (final round), the recruiter says "the panel wanted stronger influence examples". After the third, a contact at the company mentions informally that the committee read one story as escalation.
Reasoning. With three data points in the table, the pattern is clear: all three reached the final round, and two of three point at the same story. The design rounds, which the engineer had been worrying about, weren't the problem.
What happened. They rewrite the influence story to show how they built agreement across two teams before taking a decision to their director, and practise it in a mock interview. They also write for 20 minutes after each rejection and keep their weekly application and conversation targets steady. The fourth loop ends in an offer. The interviewer's feedback specifically mentions the influence example.
Lesson. The first rejection, taken alone, would have sent them to fix the wrong thing. The pattern, collected while keeping the search going, pointed at a single story.
Trade-offs to make deliberately
Choice | You gain | You risk |
Wait for a pattern before changing course | Fixes aimed at the real gap | Repeating a mistake a couple more times |
Ask every time for specific feedback | The most useful data available | Mostly polite non-answers; ask once, then move on |
Write it out after each rejection | Less rumination, better interviews | Twenty minutes of discomfort |
Keep search volume steady | Protects your odds while confidence recovers | Effort when motivation is low |
Common failure modes
Treating one rejection as a verdict. It is one noisy reading.
Fixing the round you think went badly. Your own view is often wrong.
Never asking for feedback. The most useful data goes uncollected.
Harsh self-talk. It lowers motivation rather than raising standards.
Shrinking the search after rejection. Fewer applications means fewer offers, regardless of skill.
Final takeaway
Rejection is part of every search and every promotion attempt, and a single one tells you little. Keep the search going, ask for specifics, write it out instead of replaying it, and wait for the pattern across several rejections before deciding what to fix. Your next action: put your rejections from the last year into the table in Step 3 and look for the pattern before changing anything about your preparation.
This is the last part of the Career Growth for Engineers path. To keep going, browse the other paths in the Learning Center.
Sources
Spera, S. P., Buhrfeind, E. D. and Pennebaker, J. W. (1994). Expressive Writing and Coping with Job Loss. Academy of Management Journal, 37(3), 722–733.
Breines, J. G. and Chen, S. (2012). Self-Compassion Increases Self-Improvement Motivation. Personality and Social Psychology Bulletin, 38(9), 1133–1143.
Kanfer, R., Wanberg, C. R. and Kantrowitz, T. M. (2001). Job Search and Employment: A Personality–Motivational Analysis and Meta-Analytic Review. Journal of Applied Psychology, 86(5), 837–855.
Continue the Career Growth for Engineers path
Previous — Part 9: Prepare for Interviews
Start again — Part 1: Understand Engineering Levels
Part of the Career Growth for Engineers learning path. Related: Burnout Is a Systems Problem.
