Job interview questions follow predictable patterns. Once you know the patterns — and the frameworks for answering them — every interview gets easier. We've collected the top 50 interview questions, with sample answer frameworks for the ones that show up most.
We won't give you scripted answers to memorize. Recruiters can tell. Instead, you'll get the structure behind each answer, with examples you can adapt to your real experience.
The 5 question categories every interview covers
Almost every interview question falls into one of five buckets:
- Behavioral ('Tell me about a time when…') — STAR method territory
- Common / general ('Tell me about yourself') — openers and closers
- Technical / role-specific — tests your hard skills
- Situational / hypothetical ('What would you do if…') — judgment and problem-solving
- Personal / fit — culture, motivation, self-awareness
The STAR method, briefly
Most behavioral interview questions are best answered with STAR: Situation (1-2 sentences of context), Task (what you needed to do), Action (what you specifically did), Result (the outcome, with numbers if possible).
Practice your stories until you can tell each one in under 90 seconds. Long answers lose the recruiter.
Common interview questions (with answer frameworks)
1. Tell me about yourself
The 90-second version: present → past → future. Start with your current role, briefly cover how you got there, then say what you're looking for next.
“I'm a senior product manager at Northwind, where I lead our workflow tools portfolio. Before that I spent four years as an associate PM at a Series A startup, where I shipped my first product from zero to $2M ARR. I'm now looking for a senior PM role at a Series B+ company where I can help scale a product org.”
2. Why this company?
Don't say 'it seems like a great opportunity.' Name one specific thing — a product, a recent launch, a values decision — that made you apply.
“I've been following Acme's pivot into developer tools since your Series B, and the API platform work especially caught my eye. The combination of technical depth and the early-stage energy is exactly what I'm looking for.”
3. Why this role?
Tie the role to your career trajectory. Show it's a logical next step, not a random jump.
“I've spent the last three years as an IC and I'm ready to lead a team. This role's mix of IC work and team leadership feels like the right bridge — I can keep shipping while building the management muscle I want to develop.”
4. What are your strengths?
Pick two strengths, each backed by a one-sentence example. Skip 'team player' — pick something specific.
“My two strongest are stakeholder alignment and writing. On alignment: I led a six-month project where I had to get product, engineering, and legal on the same page about a sensitive feature. On writing: I maintain our team's decision logs, which the whole org uses for context.”
5. What's your biggest weakness?
Pick a real weakness — not 'I work too hard' — and say what you're doing about it.
“I've historically struggled with delegating — I'd rather do it myself than explain it. Over the last year I've been deliberately handing off projects earlier, even when it's uncomfortable, and it's made my team stronger and freed me up for higher-leverage work.”
Behavioral interview questions (with STAR frameworks)
6. Tell me about a time you led a project
Pick a project with a clear scope, a team, and a measurable result. Walk through STAR. Focus on your role, not the team's.
“Situation: Our support team was drowning in tickets after a pricing change. Task: I needed to reduce ticket volume without hiring. Action: I built a self-serve FAQ from the top 20 ticket topics and embedded it in the billing flow. Result: Ticket volume dropped 35% in two months, CSAT went up 6 points.”
7. Describe a conflict with a coworker
Don't pretend you've never had one. Pick a real disagreement, show how you resolved it, and focus on what you learned.
“A teammate and I disagreed on whether to ship a feature with known bugs or delay the release. I proposed we quantify the bug impact together — turned out two of the three affected only 1% of users. We shipped with a fix for the third, on time. The lesson: get specific before you take a position.”
8. Tell me about a failure
Pick a real failure, not a humblebrag. Show what you learned and what you do differently now.
“I shipped a feature without enough user research and we had to roll it back within a week. It cost the team two weeks of rework. The lesson I took: even when stakeholders push for speed, I now insist on at least one round of user testing before shipping anything user-facing.”
9. Describe a time you influenced without authority
Show how you persuaded someone who didn't report to you — through evidence, relationships, or shared goals.
“I needed engineering to prioritize a UX fix they saw as low-impact. I pulled the data showing the issue was causing 12% of support tickets, then framed the fix as a clear ROI for engineering. They picked it up the next sprint.”
10. Tell me about a time you shipped under a tight deadline
Pick a story where you made smart tradeoffs to hit the deadline — not where you worked 80 hours and burned out.
“We had a launch date we couldn't move and a feature list that didn't fit. I proposed cutting two of the lower-impact features and shipping them in v1.1. We hit the date, the launch landed well, and the cut features shipped two weeks later with no customer pushback.”
Technical interview questions
11. Walk me through how you would design X
Talk through your thinking out loud. The process matters more than the final answer. Ask clarifying questions first.
For engineering: clarify requirements, sketch the system at a high level, then drill into components. For product: clarify the user and problem, propose a solution, then discuss tradeoffs and metrics.
12. Tell me about a technical decision you made that turned out to be wrong
Show you can evaluate past decisions honestly. Pick a real one, explain your reasoning at the time, and explain what you'd do differently with the benefit of hindsight.
Situational interview questions
13. What would you do in your first 30 days?
Most hiring managers want to hear: listen, learn, ship something small, build relationships. Don't promise to overhaul everything in week one.
“I'd spend the first two weeks listening — meeting the team, understanding the current state, and learning the systems. By week three I'd aim to ship something small to build trust, and by day 30 I'd have a 90-day plan to discuss with you.”
14. How would you handle a stakeholder who disagrees with your recommendation?
Show that you'd seek to understand their concern first, then bring evidence — not authority.
Strong answer framework: "I'd start by asking them to walk me through their concern — usually there's context I'm missing. Then I'd bring whatever data or examples could help us converge on a decision. If we still disagreed, I'd escalate to a decision-maker rather than argue in circles."
Personal and fit questions
15. Why are you leaving your current job?
Never badmouth. Frame it as moving toward something, not away from something.
“I've learned a lot at Northwind and I'm grateful for the experience, but I'm looking for a role with more scope and a team I can help scale. This role at Acme feels like the natural next step.”
16. Where do you see yourself in five years?
Honest but aligned with the role. You don't need a 5-year plan, but you should have a direction.
“I want to be a staff engineer — building systems at scale and mentoring more junior engineers. The work I'd do in this role over the next couple of years would be a direct step in that direction.”
17. What are your salary expectations?
Deflect if you can — turn it back to their range. If pressed, give a range with your target at the bottom. Our salary negotiation guide covers this in depth.
Questions you should ask them
'Do you have any questions for us?' is a test, not a formality. Have 5-7 ready. You'll usually get to ask 2-3.
- What does success look like in this role at 30, 90, and 180 days?
- What's the biggest challenge the team is facing right now?
- How does the team make decisions — consensus, lead, or top-down?
- What's the trajectory of the person who previously held this role?
- What would surprise a new hire about the culture?
- How is performance measured, and how often?
- What are you most excited about for the company this year?
Questions to avoid
- 'What does your company do?' (you should know)
- 'How much does it pay?' (too early)
- 'Do I have to work weekends?' (sounds like a red flag)
- 'How quickly can I get promoted?' (sounds entitled)
- Anything you could have googled
Technical and case interview formats
Different formats reward different prep:
- Coding interview: talk through your thinking out loud; the process matters more than the final answer
- System design: clarify requirements, sketch high-level, then drill in
- Case interview: structure the problem, ask clarifying questions, walk through your math
- Take-home: budget 2-4 hours, not 12 — a clean submission beats an over-engineered one
How to handle questions you don't know
Don't bluff. Say 'I don't know, but here's how I'd figure it out' and walk through your thinking. Recruiters respect honesty; they detect bluster instantly.
“I haven't worked with that specific tool, but from what I understand it's similar to [tool you know]. I'd start by reading the docs, looking for an equivalent pattern, and asking a teammate who's used it before.”
The day-of checklist
- Test your tech (camera, mic, lighting) 30 minutes before for video interviews
- Arrive 10-15 minutes early for in-person
- Bring 2-3 printed resume copies for in-person
- Have your STAR stories and questions ready
- Send a thank-you email within 24 hours (templates in our thank-you email guide)
Practice out loud
Reading your answers silently doesn't prepare you to say them. Practice out loud — ideally with a friend playing the interviewer. The first time you say an answer out loud, it'll sound worse than you expected. The fifth time, it'll sound natural.
The candidates who get offers aren't always the most qualified. They're the most prepared. Run through these questions, prepare your STAR stories, and walk in ready. Forge the kind of interview performance that earns the offer. ✨