20 Common Job Interview Questions (and How to Answer Them)

Almost every interview question, however it's phrased, is testing one of three things: can you do the job, will you actually do it well day to day, and will the team want to work with you. Once you see that pattern, "What's your greatest weakness?" and "Tell me about a conflict with a coworker" stop feeling like trick questions and start feeling like the same handful of questions wearing different outfits.

Here are the 20 you're most likely to get, grouped by what they're really testing, with a structure for answering each one on the spot.

The one method that answers most of these: STAR

For any question that starts with "Tell me about a time…" or "Give me an example of…", structure your answer in four parts:

• Situation — the context, in one sentence.
• Task — what you specifically needed to do or decide.
• Action — what you actually did (the longest part of the answer).
• Result — the outcome, ideally with a number.

Most weak interview answers skip straight from Situation to a vague Result ("...and it worked out great") without ever explaining the Action — which is the part that actually proves the skill. If you take one thing from this article, it's to slow down on the Action step.

Opening questions

1. "Tell me about yourself."

Not an invitation for your life story — a request for a 60-second frame the rest of the interview hangs on. Structure: current role and its scope, one or two relevant highlights from your path here, then why this specific role.

"I'm a product designer with six years in B2B SaaS, most recently leading design for a reporting suite used by 40,000 weekly users. Before that I worked in-house at an agency, which is where I learned to defend design decisions to non-designers — a skill I use constantly now. I'm looking at this role because it's the first one I've seen that combines the systems-thinking I do now with the 0-to-1 work I miss from my agency days."

2. "Why do you want to work here?"

Tests whether you researched the company at all, or are running a mail-merge interview circuit. A real answer names something specific — a product you've used, a decision they've publicly made, a problem you can see from outside that you'd want to help solve. "Great culture" and "exciting growth" answer nothing; assume the interviewer has heard both a hundred times this quarter.

3. "Why are you leaving your current job?" / "Why did you leave your last job?"

Stay factual and forward-looking. "I've learned everything I can in this scope and I'm looking for [specific thing this role offers]" beats any version of "my manager was terrible," even when it's true. Interviewers read complaints about a previous employer as a preview of how you'll talk about them someday.

Behavioral questions (use STAR)

4. "Tell me about a time you failed."

Tests self-awareness, not perfection. Pick a real failure with real stakes — not a humblebrag disguised as a flaw ("I work too hard") — and spend most of the answer on what you changed afterward. The lesson matters more than the mistake.

5. "Tell me about a conflict with a coworker or manager."

Tests whether you can disagree professionally and reach resolution — not whether you've ever been right. Describe the disagreement neutrally, focus on how you resolved it (usually: more communication, not more conflict), and never make the other person the villain of the story.

6. "Tell me about a time you led a project" (or "led without authority").

Even individual contributors get this one — leadership doesn't require the word "manager" in your title. Any time you set the direction, coordinated other people, or made the call when no one else would counts.

7. "Describe a time you had to learn something quickly."

Tests adaptability. The best answers show a system, not just an outcome: how you approached learning it, not just that you eventually figured it out.

8. "Give an example of going above and beyond."

Pick something with a measurable result, not just extra hours worked. "I stayed late a lot" isn't a story; "I noticed X was broken, nobody had asked me to fix it, and fixing it saved the team Y" is.

Self-assessment questions

9. "What's your greatest strength?"

Pick a strength the job posting actually needs, then prove it with a specific result rather than just naming it — the same principle as choosing skills for your resume: the word alone convinces no one, evidence does.

10. "What's your greatest weakness?"

The most over-coached question in interviewing, and interviewers can tell. A fake weakness ("I'm too much of a perfectionist") lands worse than a real, moderate one paired with what you're doing about it: "I default to written communication over verbal, which I've been correcting by speaking up earlier in meetings rather than following up afterward in Slack."

11. "Where do you see yourself in five years?"

Tests whether the role is a genuine step on your path or a placeholder while you look for something else. You don't need a rigid five-year plan — you need to show this role plausibly leads somewhere you actually want to go.

12. "What are you looking for in your next role?"

Answer honestly and specifically — vague answers ("growth," "a good culture") suggest you'd take any offer, which undersells your fit for this one in particular.

Situational / hypothetical questions

13. "How would you handle disagreeing with your manager's decision?"

Tests judgment under a real workplace tension: candor versus deference. The strongest answer shows you'd voice the disagreement once, clearly, with reasoning — then commit to the decision once it's made, rather than either staying silent or relitigating it.

14. "How do you prioritize when everything feels urgent?"

Wants a real method, not "I just work hard." Naming an actual framework — impact versus effort, deadline proximity, who's blocked by what — shows you have a repeatable system rather than winging it under pressure.

15. "What would you do in your first 30/60/90 days?"

Common for management and senior roles. A strong answer front-loads listening and learning (first 30: understand the team, the systems, the current problems) before committing to specific changes — proposing sweeping changes on day one reads as someone who didn't bother to learn the context first.

16. "Tell me about a time you disagreed with data or a decision you thought was wrong."

Tests intellectual honesty. Show that you raised the concern through the right channel, with reasoning — and that you can also be the one who was wrong, gracefully, if that's how the story actually ended.

Closing questions

17. "Do you have any questions for us?"

Always say yes — and have three ready. Questions about the team's current challenges, how success is measured in the role, or what happens next in the process all show genuine engagement. Skipping this entirely is one of the most common ways a strong interview ends on a flat note.

18. "What's your salary expectation?"

Research a realistic range beforehand (sites like Levels.fyi, Glassdoor, and your network all help) and give a range, not a single number — "I'm targeting $75–85K based on my research into this role and market" leaves room to negotiate without either lowballing yourself or naming a number that rules you out.

19. "When can you start?"

A logistics question, not a trick one — answer with your real notice period. If you're currently employed, two weeks is standard and expected; naming it doesn't cost you anything.

20. "Is there anything else you'd like us to know?"

A genuine open door, not a formality. Use it if there's context your resume and answers didn't cover — a gap, a nontraditional path, a reason you're especially excited about this specific opportunity — not to repeat something you've already said.

Before the interview: connect it back to your resume

Every behavioral question above is really asking you to retell a story that's already summarized as a single bullet point on your resume — so the fastest prep is rereading your own resume and expanding your strongest three or four bullets into full STAR stories before you walk in. If a bullet doesn't have a story behind it yet, that's worth noticing before the interview, not during it.

Frequently asked questions

How many questions should I prepare for? You won't get all 20 in one interview, but preparing STAR stories for 4–5 core experiences lets you flex the same stories to answer most behavioral questions, whichever specific wording comes up.

Should I memorize exact answers? Memorize the structure and the key facts (numbers, outcomes), not a word-for-word script — a memorized answer sounds memorized, and it falls apart the moment the interviewer asks a follow-up you didn't script for.

What if I don't have an example for a question? Broaden the source: school projects, volunteer work, and personal projects all count if you don't have a direct professional example yet — this is the same principle covered in our guide to writing a resume with no experience.

Should my interview answers match my resume and cover letter? They should reinforce each other, not repeat verbatim — the resume states the fact, the cover letter gives it context, and the interview is where you tell the full story behind it.