Jul 31, 2026

3 rejections in a row taught me i was practicing answers, not interviews

bombed three backend engineer interviews in six weeks. knew my leetcode, had good answers written down for behavioral stuff. still couldn't land an offer.

the problem wasn't that i didn't know what to say — i had a doc with like 40 curated STAR stories. the problem was that when someone actually asked me a question in real-time, my brain would freeze for a second, then word-vomit, then i'd realize halfway through i was telling the wrong story.

i was practicing answers in isolation. i wasn't practicing the actual back-and-forth of an interview — the pressure of someone waiting for you to respond, the follow-up questions you can't predict, the weird silence when you finish talking and they just stare at you.

for my fourth attempt i started doing timed mock interviews instead of just reviewing notes. used a tool called nxtinterview that lets you pick a job description and does a full interview simulation with real-time questions. not pre-recorded — it actually responds to what you say and asks follow-ups. the difference was immediate. i started recognizing when i was rambling, when an answer was too short, how to recover when i blanked.

got the offer two weeks ago. same prep materials as before, but i'd actually practiced delivering them under pressure instead of just rehearsing in my head.

full disclosure: just a user, not affiliated with the product or anything. but if you're in the same spot i was — knows the content but can't perform when it counts — this shift helped me a lot.

anyone else had this problem? where you knew your stuff but couldn't execute in the room?