realized i've been prepping for interviews completely backwards

spent weeks grinding leetcode and studying system design, then bombed an interview because i couldn't explain a gap on my own resume without sounding defensive.

the irony hit me hard after that call. i had practiced every possible algorithm question, memorized behavioral frameworks, even did mock technicals with friends. but when the interviewer asked "so what were you doing between these two roles?" i fumbled. sounded evasive. couldn't articulate why i left my last company without it coming across weird.

the thing is, resume questions are the most predictable part of any interview. they're right there in front of both of you. every gap, every job hop, every bullet point is fair game. and yet i never once practiced answering them out loud. i just assumed i'd wing it because "i know my own story."

turns out knowing your story and being able to tell it clearly under pressure are two very different things. after that interview i started rehearsing resume walkthroughs like i would any other prep. recorded myself explaining transitions, tested different ways to frame that one project that didn't ship, timed how long my answers ran.

last week i used this tool called nxtinterview that actually generates questions based on your resume and lets you practice answering them. not affiliated with them, just found it helpful because it pulled stuff i wouldn't have thought to prep for — like why i used a specific tech stack or how i prioritized features on a vague bullet point. made me realize how many assumed-obvious things on my resume actually need a prepared explanation.

anyway. if you're prepping, don't skip the most predictable questions just because they feel easy.

the resume-based practice was the part that actually helped me smooth out the rough edges before my next real interview.