50 Most Common Interview Questions — With Answer Frameworks for Every One

1. "Tell me about yourself."

What they're asking: Give me a reason to keep this interview going. Are you at the level I need? Is your background relevant?

How to answer: Use Present-Past-Future. Present: your current role, level, and domain. Past: the most relevant part of your experience for this role. Future: what you are targeting and why this role fits. 90 seconds. No career autobiography.

Example opening: "I'm a senior data engineer at [Company], where I lead the infrastructure for our customer data platform — 400M+ events per day across 12 data sources. Before that I spent 3 years at [Company] building real-time pipelines for fraud detection. I'm now looking for a staff-level role where I can own platform direction, not just execution."

2. "Walk me through your resume."

What they're asking: Help me understand your career arc and whether the progression makes sense for this role.

How to answer: Narrate your career with a through-line — the connecting theme across every role. Do not just list jobs chronologically. Make each transition sound intentional, not reactive. Focus more time on recent, relevant experience.

3. "What are you working on right now?"

What they're asking: Are you engaged and current? Can you describe technical or functional work at a level of depth that proves your role?

How to answer: Describe your current project with specific details — scope, your specific contribution, the problem being solved, and the business context. Avoid generalities.

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

How to answer: Name one specific thing about the company — a product decision, engineering approach, mission element, or team structure — that is genuinely interesting to you. Connect it to your own goals. Avoid: "great culture," "exciting opportunity," "I've always admired your company."

5. "Why are you leaving your current role?"

How to answer: Never criticize your employer, manager, or colleagues. Frame your answer around what you are optimizing for next — scope, ownership, technical domain, leadership opportunity — not what you are escaping. "I want to work on X" is always better than "I am unhappy with Y."

6. "Where do you want to be in 5 years?"

How to answer: Be specific about direction without signaling that you are using this role as a stepping stone. Connect your 5-year goal to what this role can develop and deliver. "I want to be leading a platform engineering org" is better than "I want to be a VP somewhere."

7. "Why should we hire you?"

How to answer: Name three specific things you bring that are directly relevant to this role — not generic strengths like "I work hard" or "I'm a team player." Lead with your most distinctive capability, back it with a specific example, and connect to what the role needs.

8. "What do you know about our company?"

How to answer: Demonstrate depth, not breadth. It is better to know one thing specifically — a recent product launch, an engineering blog post, a strategic shift — than to know ten things shallowly. Interviewers remember candidates who noticed something they did not expect you to notice.

9. "What are your salary expectations?"

How to answer: Delay as long as possible by asking about the budgeted range first. If pressed, anchor at the top of your researched range — you can always negotiate down but rarely negotiate up. Never give a number before they do if you can avoid it.

10–19: Core behavioral questions

• 10. Tell me about a time you led a team through a difficult situation.
• 11. Describe a conflict with a coworker or stakeholder and how you resolved it.
• 12. Tell me about the most complex problem you have solved.
• 13. Describe a time you had to make a decision with incomplete information.
• 14. Tell me about a time you failed and what you learned.
• 15. Describe a time you influenced without direct authority.
• 16. Tell me about a time you had to prioritize under pressure.
• 17. Describe the most impactful project you have worked on.
• 18. Tell me about a time you gave or received critical feedback.
• 19. Describe a time you had to change course midway through a project.

For full answer frameworks on all 30 behavioral questions, see the Behavioral Interview Questions guide →

STAR answer framework — quick reference

• S — Situation: 1 sentence. Context and constraint. Do not over-explain.
• T — Task: What you specifically needed to accomplish and why it mattered.
• A — Action: 60% of your answer. Your specific decisions, reasoning, and execution.
• R — Result: Quantified outcome. Numbers matter — use them.
• + Consequence (senior level): What happened downstream for the team or business.

20–29: Situational questions

• 20. What would you do in your first 30 days in this role?
• 21. How would you approach a project where the requirements kept changing?
• 22. What would you do if you disagreed with a decision your manager made?
• 23. How would you handle a team member who was consistently underperforming?
• 24. What would you do if you were given two equally urgent projects?
• 25. How would you build alignment across teams that have competing priorities?
• 26. What would you do if a stakeholder rejected your recommendation?
• 27. How do you approach learning a new domain quickly?
• 28. What would you do if you discovered a critical issue the day before launch?
• 29. How do you decide what to work on when everything feels important?

Answer situational questions with specific past examples, not hypothetical responses. "When this happened, I..." always beats "I would..."

Role-specific question types

Software engineers: System design questions (architecture tradeoffs, failure modes), debugging and incident response, code quality and technical debt management, mentorship of junior engineers.

Product managers: Prioritization frameworks, customer discovery process, how you measure success, how you work with engineering, how you handle scope creep.

Engineering managers: How you build high-performing teams, how you handle underperformance, how you balance technical work with people management, how you communicate upward.

Data professionals: How you communicate findings to non-technical stakeholders, how you ensure data quality, how you scope and scope-limit analyses, how you measure the impact of your work.

Finance and operations: How you build financial models under uncertainty, how you influence business decisions, how you manage across ambiguous data, how you present to senior leadership.

30–40: Strong closing questions

• 30. What does success look like in this role in the first 90 days?
• 31. What is the biggest challenge the team is currently facing?
• 32. How are decisions made on this team — and where does this role sit in that process?
• 33. What does the onboarding experience look like for this role?
• 34. What makes someone exceptional in this role versus just good?
• 35. How does this team measure impact?
• 36. What is the relationship between this team and [adjacent team]?
• 37. What do you personally enjoy most about working here?
• 38. What are the biggest growth opportunities for someone in this role?
• 39. Is there anything about my background that gives you hesitation?
• 40. What are the next steps in the process and timeline?

Questions to avoid

• Anything about salary, PTO, or benefits in early rounds — it signals you are optimizing for the wrong things
• "What does your company do?" — this should be answered by your research
• "Will I get the job?" — signals desperation
• "Can I work from home?" — save for offer negotiation
• Questions answered in the job description — it signals you did not read it