realized i've been prepping for interviews backwards this whole time

spent weeks grinding leetcode and behavioral frameworks, then bombed the easiest question in my last interview: 'walk me through this project on your resume.'

i had a solid answer in my head, obviously—i built the thing. but when the interviewer asked me to explain the architecture and why we made certain decisions, i fumbled hard. started rambling about tech stack details nobody cared about, forgot to mention the actual business impact, couldn't articulate why i made trade-offs that seemed obvious at the time.

the weirdest part? i'd practiced system design for hours. memorized STAR examples. but the questions directly about my own resume—the things i should know better than anyone—i'd never once said out loud before that call.

started thinking about how backwards that is. interviewers always ask about your resume. it's the most predictable part of the process. but most prep advice focuses on algorithm problems or generic behavioral stuff, not the specific projects and roles you're actually going to get grilled on.

after that interview i started using this tool called nxtinterview that generates questions based on your actual resume—asks you to defend your choices, explain gaps, dive into specifics. turns out when you practice talking about your own work out loud a few times, you stop sounding like you're seeing it for the first time.

last two interviews went way smoother. still prep leetcode and all that, but now i also rehearse the stuff that's 100% guaranteed to come up.

anyway, if you've ever blanked on a 'tell me about this project' question, might be worth trying. helped me stop overthinking the predictable stuff. (nxtinterview.com if you want to check it out—i don't work for them, just found it useful.)