One failed interview is a single data point, not a verdict on you. Write down what happened while it is fresh, separate what you can fix from what was noise, practise the specific weak spot, and get your next application out within a week so fear does not set the schedule.
What people tell me
I finally got an interview for a role I really wanted. I prepared, but in the technical round I froze on a problem I think I could normally solve, and later I also struggled to explain a project I built. I got the rejection email a few days later. Since then I have not applied anywhere. Every time I open a job listing I imagine going through that again and close the tab. I feel embarrassed and I am starting to wonder if I am just not good enough.
A composite of the messages behind this question, with personal details left out.
Key takeaways
- A rejection is one sample from a noisy process. Many strong engineers fail several interviews before an offer.
- Within 48 hours, write down every question and where you struggled. Memory fades and fear rewrites it.
- Sort what went wrong into skill gaps, performance under pressure, and things outside your control.
- Practise the specific weak spot out loud, not your general knowledge.
- Send one new application within a week. Avoidance grows every day you wait.
First, put the rejection in proportion
Interviews are a noisy measurement. The same candidate can pass with one interviewer and fail with another, pass on Tuesday and fail on Thursday. Many engineers I know, including very good ones, collected a string of rejections before their first offer. It is uncomfortable to hear, but failing interviews is a normal part of getting hired, not evidence that you do not belong.
What makes it feel worse is that you wanted this role. When you care, a rejection lands as a judgement on you as a person. It is not. It is feedback on how one conversation went.
Write it down while it is fresh
Within a day or two, write down everything you remember:
- Every question, in as much detail as you can recall.
- Where you felt confident and where you got stuck.
- What you said about your projects, and where the explanation fell apart.
- Anything the interviewer hinted at or asked twice.
Do this before fear rewrites the story into "I was terrible at everything". It is rarely true. Usually there were two or three specific moments that went badly and several that went fine.
Sort what went wrong
Put each problem into one of three columns:
| Skill gap | Performance under pressure | Outside your control |
|---|---|---|
| You did not know how to approach the problem type | You knew it but froze or rushed | They hired internally or chose more experience |
| You could not explain a design choice in your project | You stopped talking while thinking | The role changed or headcount was cut |
| A concept you had never studied | Nerves made you skip clarifying questions | Interviewer style or mood |
Only the first two columns are yours to work on. The third column is real and it is not your fault. Let it go.
Fix the specific weak spot
Resist the urge to "study everything again". Target what the notes show:
- If you froze on a problem type, find ten problems of the same shape and solve them over two weeks, out loud, with a timer.
- If you struggled to explain your project, write a one-page explanation: what it does, why you chose the stack, one hard problem you solved, one thing you would change. Then say it out loud until it sounds natural.
- If nerves were the issue, do mock rounds with a friend or record yourself solving a problem while talking. The goal is to make the format familiar.
Ask for feedback, once and politely
You can reply to the rejection with a short note:
Thank you for letting me know, and for your time. If you are able to share any feedback on where I could improve, I would really appreciate it.
Many companies will not answer, and that is fine. Some will, and even one sentence can be useful. Do not argue with the decision or ask them to reconsider.
Beat the avoidance with a deadline
Fear grows the longer you stay away. Set a rule: one new application within seven days of the rejection, whether you feel ready or not. You do not need to be fully recovered to send an application. You recover by sending it.
It also helps to keep several applications moving at once, so no single interview carries all your hopes. When one role is your only chance, every question feels like it decides your future. When you have five conversations going, each one matters less and you perform better.
Change the story you tell yourself
"I failed an interview" is accurate. "I am not good enough" is a conclusion the evidence does not support. A more useful framing: "I found out exactly what to practise next." That is what the interview gave you, even if it did not give you the job.
A worked example
Here is what a post-interview note looked like for one composite case I see often:
- Question 1: find duplicates in a list. Solved, but slowly, and forgot to mention the empty list case.
- Question 2: merge overlapping intervals. Froze for about four minutes, then wrote a partial solution.
- Project discussion: could not explain why I chose MongoDB over PostgreSQL. Said "it is popular".
Sorted, that becomes one skill gap (interval and sorting problems), one performance issue (going silent when stuck) and one preparation gap (not having reasons for project decisions). That is a two-week plan, not a crisis: ten sorting and interval problems solved out loud, a written paragraph on every major choice in the project, and two mock rounds to practise talking through being stuck.
A self-check before your next application
Answer these honestly. If you can say yes to most, you are ready to apply again:
- Can I name the two or three specific things that went wrong?
- Have I practised each of them at least five times since?
- Can I explain every project on my CV, including one decision I would change?
- Do I have more than one application in progress?
Readiness is not the absence of fear. It is having done something about the causes.
If you are still stuck
Read A job search is a pipeline, not a performance for how to keep one result from dominating, and Fifteen problem shapes and the move that solves each if problem solving was the weak spot. The companies directory can help you find the next few places to apply. If you want someone to look at your specific situation, join Sefism and, as a member, book a 1:1 session.
Was this answer helpful?
Read next
- A Job Search Is a Pipeline, Not a PerformanceMost people run a job search as a series of hopeful individual events, which fails for a structural reason: the response rate on cold applications is low enough that any single one is close to noise. The people who find work reliably are running a pipeline instead. Thirteen heuristics for the mechanics, which are the part you actually control.
- Fifteen Problem Shapes and the Move That Solves EachThe usual way to learn algorithms is to work through a long list of problems and hope something generalises, which leaves most people with a hundred solutions memorised and no idea what to do with the hundred and first. There are perhaps a dozen shapes of problem, each with a move that usually works. Fifteen of those shapes and how to recognise them.
- How to Apply for Software Engineering JobsA job search is often a hundred applications, and knowing that before you start changes how you run it. How to write a resume where every line says what changed, why referrals outperform everything else, how many applications to keep live, what to track so you know whether the problem is the resume or the interview, and what to do in the ten minutes after an offer arrives.
Your situation is not quite this one?
Members get written answers to their own questions, a roadmap built for them and feedback on their projects. Early access is open to X and Instagram followers and university students. Prefer to talk? A free call works too.