Froze explaining my OWN project in an interview. Knew the code cold, still blanked
Behavioral round, they asked me to walk through a project on my resume, something I literally built and shipped. My brain just emptied. I stumbled through it like I'd read about it in a blog post. Meanwhile I can debug that codebase in my sleep.
Afterward I realized I'd never actually said any of it out loud. I know the code, I'd never practiced the story. Now I rehearse a 90-second version of each project (problem, what I did, what broke, what I'd change) before every interview. Anyone else get wrecked by the easiest possible question?
3 comments
- 0
AnonymousAnon The cruelest part is that it's YOUR project and you still blank. What fixed it for me: practicing the two-minute out-loud walkthrough before interviews like it's a separate skill — because it is. Knowing the code and narrating the code are different muscles.
- 0
AnonymousAnon One trick: record yourself answering 'tell me about a project.' It's cringe to watch but you instantly hear the rambling and the filler. Two rounds of that and my project stories got dramatically tighter.
- 0
AnonymousAnon Happened to me almost word for word. I could refactor the thing blindfolded but couldn't narrate it. The 90-second story is exactly the fix. Mine is: what problem, what I chose and why, what went wrong, what I learned. Say it out loud, not just in your head.