The interview questions almost everyone gets, and how to prep each one

These are the questions worth preparing before any interview, whatever the job. The middle column is the question the interviewer is actually trying to answer, which is rarely the one they asked out loud.

The times are a budget, not a measurement. They assume you already know your own history and need to shape it, not dig it up.

This is the easiest question to ramble on, and rambling here does the most damage, because it sets the frame for the next forty minutes. The interviewer is not asking for your life story. They want to know why you're sitting in this chair.

How to prep it in 20 minutes

1. Write one sentence on what you do now, with one result.
2. Write one sentence on how you got here, naming the reason behind the move that matters most.
3. Write one sentence connecting the two to this role.
4. Say it out loud with a timer until it's under 90 seconds without reading.

The failure mode is reciting your resume in order from your first job. Start with the present. If they want the history, they'll ask "walk me through your resume," and you'll answer that separately.

Two questions are hiding in this one, and interviewers often ask them separately: why this role, and why this company. Prepare both.

For the role, pick two things the job description emphasizes and connect each to something you've done or are deliberately moving toward. For the company, find one specific thing: a product decision, a market it's entering, a technical choice it wrote about. Something you could only know from using the product or reading closely.

Generic praise for the mission or the culture is the miss. If your sentence would work unchanged for the company's closest competitor, it isn't an answer yet. Company guides help most here, because they cover what a particular team cares about; browse the interview guides by company and role, for example the Google product manager guide.

Prep these as a pair. Both test whether you see yourself the way your colleagues do.

For the strength, name one, not three, and pick the one this role needs most. Back it with a single short story that has a result. Then say where it would show up in this job.

For the weakness, choose something real that isn't central to the role, name a moment it cost you, and describe what you now do about it. The disguised strength ("I'm a perfectionist," "I care too much") reads as dodging the question, which is worse than any honest weakness.

Give one honest reason, framed as what you want next, then turn to this role within a couple of sentences. Credit your current employer for something. Stop.

The trouble with this question is that the true answer is often a bad manager, a reorg or pay, and those are legitimate reasons. Said out loud in an interview, though, they sound like you're running away, and the interviewer starts to wonder what you'd say about them. "I want to do more of X, and my current role has moved toward Y" is honest and doesn't invite a follow-up you'd rather not answer.

Expect at least one behavioral question, even in a quick screen or a round billed as technical. You can't predict the exact wording, but you can have three or four stories ready that each show a real result. The STAR interview answers guide covers how to build them and what the follow-up questions will probe.

"No, I think you've covered everything" ends the interview on a shrug. Bring two or three questions that show you've thought about doing the job, not about getting it. Questions about what the first few months look like, what a strong performer in the role does differently, or what the team is struggling with right now all work. Save pay and benefits for the recruiter.

These come up often enough to prepare for, and each has an obvious answer that hurts you.

"What are your salary expectations?"

The trap is naming a number before you've looked anything up, or naming one so low it anchors the offer. Research the range first: if the posting lists one, start there, and check what similar roles pay in the same city. When asked, give a range you'd be happy at the bottom of, or say you'd like to understand the full scope of the role first and ask what range they've budgeted. Both are normal.

"Where do you see yourself in five years?"

The trap is a title two levels up, or a plan that leaves the company, like starting your own business. Describe the skills or scope you want to have built, and show how this role starts that. Keep it plausible for the company in front of you.

"Can you explain this gap in your resume?"

The trap is a long, apologetic explanation. Say what the gap was in one sentence, mention anything you did during it that's relevant, and move on to why you're ready now. Over-explaining makes a non-issue look like an issue.

"Is there anything else we should know?"

The trap is saying "no." This is a free minute. Use it to name the one thing about you that fits the role and hasn't come up yet, in two sentences, and then thank them.

If you only have an hour before an interview, this is the order that pays off most.

Say everything out loud at least once. Answers that read well on paper often run long or stall when spoken, and you'd rather find that out at your desk. For a technical role, add the role-specific rounds on top of this; the Google software engineer guide shows what that looks like for one loop.

Don't memorize the sample answers. Other candidates can read them too, and a borrowed answer sounds borrowed the moment a follow-up arrives. Use the structure, fill it with your own specifics, and practice saying it until you could start from any sentence. The goal is to know what you'll say, not the exact words you'll say it in.