Interview prep is one of those areas where you can spend either four hours or forty, and the difference in outcomes is much smaller than the difference in effort. The candidates who interview well are not the ones who memorized the most answers. They are the ones who deeply rehearsed a small number of them.
Here is the list of questions worth getting genuinely sharp on, plus how to think about each.
1. "Tell me about yourself."
This is not an icebreaker. It is the question your interviewer will use to frame the rest of the conversation. Have a two-minute answer ready that hits three beats: where you are now, the through-line that brought you here, and what you are looking to do next. Keep it specific, keep it tight, and end on a sentence that points toward the role you are interviewing for.
2. "Walk me through your resume."
A variation on the first question, but more chronological. Practice telling the story of your resume in five minutes maximum. For each role, hit one sentence on context, one or two on what you actually did, and one on why you moved on. Do not narrate every bullet. Most candidates spend too long on early roles and run out of time before they get to the most recent - which is the one the interviewer cares about most.
3. "Tell me about a project you are proud of."
Have two prepared. Both should be projects where you can describe the situation, the actions you specifically took, and the outcome. Avoid choosing a project where the most impressive thing was something a teammate did. The interviewer is trying to understand your contribution, not the team's.
4. "Tell me about a time something went wrong."
Almost every interview has some version of this question. The trap is to either pick something trivial ("I once forgot to mute on a call") or to blame someone else. Pick a real situation, name your own role in it honestly, and describe what you learned and changed afterward. Interviewers are not looking for perfect candidates - they are looking for candidates who can talk about failure without flinching.
5. "Why this role / why this company?"
The fastest signal of an unprepared candidate is a generic answer here. Spend twenty minutes reading the company's site, recent news, and product. Identify two or three concrete things that make this specific opportunity interesting to you, and weave them into a one-minute answer that links your background to those things.
6. Your role-specific question
Every role has a "main" question - the one the interview will keep circling back to. For engineering roles it is often a technical deep-dive; for product, a product critique; for sales, a discovery exercise. Identify the main question for your role and rehearse it as if it were the only thing the interviewer was going to ask. Most of your preparation hours should go here.
7. "Do you have any questions for us?"
Yes, you do. Prepare three thoughtful questions in advance, and pick whichever two best fit the conversation. Avoid questions you could have answered by reading the company's site. Ask things only an insider can answer: how decisions get made, how the team measures success, what the previous person in this role found hardest. Show you are interviewing them, too.
A simple rehearsal habit
Record yourself answering each of these out loud. Listen to the playback once. The first listen is uncomfortable; the second one is where you actually notice the filler words, the rambling sections, and the spots where you trail off. Twenty minutes of self-review beats two hours of silent re-reading.
