50+ Common Interview Questions and How to Answer Them
Knowing the questions that might come up in a job interview is useful. But simply collecting questions is not enough.
The real challenge is understanding why the interviewer is asking the question, what they are trying to assess, and how to give an answer that is specific, concise, and directly relevant to the role.
For a complete overarching prep strategy, check out our complete step-by-step interview preparation guide. In this guide, we cover more than 50 common interview questions across nine major categories:
- Introductory questions
- Motivation questions
- Strengths and weaknesses
- Behavioral questions (with links to our behavioral interview guide)
- Problem-solving questions
- Career questions
- Situational questions
- Role-specific questions
- Difficult interview questions
For each question, you will learn what the interviewer is evaluating and how to approach your answer without sounding scripted.
Part 1: Introductory Interview Questions
1. Tell me about yourself.
What they want: A concise summary of your professional background and why it is relevant to this specific role. Use the Present → Past → Future framework. Do not spend five minutes reciting your resume chronologically.
2. Walk me through your resume.
What they evaluate: Whether you can explain your career transitions logically. Focus on major decision points, key accomplishments, expanding scope, and increasing responsibility.
3. Tell me something that isn't on your resume.
What they evaluate: A chance to demonstrate personality, intellectual curiosity, self-directed learning, or an additional skill. Pick something professionally relevant.
4. What are you currently working on?
What they evaluate: Current engagement and execution. Connect your day-to-day responsibilities to skills needed in the target role.
5. How would you describe yourself?
What they evaluate: Self-awareness. Avoid generic adjectives like "I'm hardworking and passionate." Give evidence: "I tend to be highly structured when solving ambiguous problems. In my current role, I break complex client requirements into phased workstreams before proposing architecture."
Part 2: Motivation Questions
6. Why do you want this job?
A strong answer connects three elements: Your relevant experience + What this specific role requires + Where you want to grow next.
7. Why do you want to work here?
Avoid generic praise like "Because you are an industry leader." Explain what genuinely attracts you about their product, technology stack, business model, or engineering culture.
8. Why are you leaving your current job?
Keep your response positive and future-oriented. Focus on career growth, scope, new challenges, and learning. Avoid complaining about compensation, coworkers, or management.
9. Why should we hire you?
This is your core value proposition. Formula: Target skill from JD + Concrete evidence from your track record + Immediate impact you can deliver.
10. Why are you interested in this industry?
Demonstrate that you understand the macro challenges, unit economics, or user dynamics of the industry rather than simply saying you find it exciting.
11. What are you looking for in your next role?
Be specific about responsibilities, technical complexity, autonomy, team collaboration, and problem scale.
Part 3: Strengths and Weaknesses
12. What are your greatest strengths?
Select 2–3 strengths directly relevant to the target position. Follow each immediately with a concrete example proving it.
13. What is your biggest weakness?
Avoid cliché humblebrags like "I'm a perfectionist" or "I work too hard." Use this formula: Real professional limitation → Honest business impact → Active system or habit you've implemented to manage it.
14. What skill are you currently trying to improve?
Choose a real technical or leadership skill. Explain the courses, projects, or mentors you are leveraging to build competence.
15. What would your manager say you need to improve?
Demonstrate self-awareness. Refer back to constructive feedback received during performance reviews and show how you've addressed it.
Part 4: Behavioral Interview Questions
For in-depth strategies and frameworks for these questions, see our comprehensive guide on 30 behavioral interview questions and STAR examples.
16. Tell me about a time you faced a difficult challenge.
Use the STAR format: set the context, your objective, the specific actions you drove, and the quantifiable outcome.
17. Tell me about a time you failed.
Do not hide the mistake or shift blame. Explain what went wrong, own your part, explain the immediate remediation, and describe the systematic change you instituted afterward.
18. Tell me about a conflict with a coworker.
Demonstrate professional empathy. Show that you can debate technical or business approaches without taking disagreements personally.
19. Tell me about a time you disagreed with your manager.
Explain how you gathered data to present an alternative perspective respectfully, and how you committed fully once a final decision was reached.
20. Tell me about a difficult stakeholder.
Focus on understanding their underlying incentives, adapting your communication cadence, and aligning on shared milestones.
21. Tell me about a time you influenced someone without authority.
Detail your approach: initial resistance, data and prototypes used, stakeholder alignment, and ultimate consensus.
22. Tell me about a time you worked with a difficult team.
Focus on procedural actions: clarifying roles, improving documentation, introducing retrospectives, not interpersonal complaints.
23. Tell me about a time you had to work with incomplete information.
Tests decision velocity and risk judgment. Explain how you framed assumptions, established reversible rollback mechanisms, and moved forward.
24. Tell me about a time you made a difficult decision.
Walk the interviewer through the explicit trade-offs you weighed and why you picked the chosen path.
25. Tell me about a time you had competing priorities.
Demonstrate a systematic framework for prioritization (e.g., business impact vs. engineering effort) and stakeholder communication.
Part 5: Problem-Solving Questions
26. How would you approach a problem you've never seen before?
Provide a structured mental framework: Clarify requirements → Break into workstreams → Formulate testable hypotheses → Validate with data → Implement & monitor.
27. Tell me about a time you solved a difficult problem.
Highlight your analytical rigor and provide a measurable outcome (e.g. latency reduced by 40%, churn lowered by 15%).
28. How do you make decisions when you don't have enough data?
Show that you can separate reversible two-way doors from irreversible one-way doors, consult domain experts, and test small pilots.
29. How do you prioritize your work?
Explain how you balance urgent operational requests against high-leverage strategic initiatives.
30. What would you do if you disagreed with project direction?
Demonstrate structured disagreement backed by evidence, followed by full commitment once leadership decides.
Part 6: Career Questions
31. Where do you see yourself in five years?
Avoid rigid job title forecasts. Focus on the depth of technical expertise, level of ownership, and mentoring responsibilities you aim to achieve.
32. What is your biggest career achievement?
Pick an accomplishment where you overcame significant obstacles to deliver clear business impact.
33. What accomplishment are you most proud of?
Pick something that reveals your professional values, whether it was mentoring junior team members or rescuing a mission-critical project.
34. What motivates you?
Be genuine: solving complex problems, building software users love, collaborating with high-performing peers, or seeing direct business results.
35. What type of manager do you work best with?
Describe an environment in which you thrive (e.g., clear goals with autonomy over execution, regular constructive feedback).
Part 7: Situational Questions
36. What would you do if you received an unrealistic deadline?
Explain how you scope the problem: clarify core vs. secondary requirements, identify trade-offs, and negotiate a phased delivery plan.
37. What would you do if a teammate wasn't contributing?
Do not immediately escalate to management. First check in 1-on-1 to understand blockers, clarify role expectations, and offer support.
38. What would you do if you made a serious mistake in production?
Immediate sequence: Mitigate impact → Alert stakeholders → Roll back or hotfix → Conduct blameless post-mortem → Implement permanent guardrails.
39. What would you do if a client or stakeholder rejected your proposal?
Listen actively without getting defensive, identify their underlying objections, and iterate collaboratively on a compromise.
40. What would you do if company priorities changed halfway through a project?
Demonstrate emotional agility: quickly archive current work cleanly, align team on new objectives, and redirect momentum.
Part 8: Role-Specific Questions
41. What technical skill are you strongest in?
Anchor your answer in production experience: scale handled, trade-offs navigated, and architectural decisions made.
42. What technical skill are you weakest in?
State the area cleanly, why it matters, and what you are doing to close the knowledge gap.
43. How do you keep your skills and industry knowledge current?
Name concrete publications, open-source repositories, technical newsletters, or personal sandbox projects you maintain.
44. How do you explain complex technical topics to non-technical stakeholders?
Avoid jargon. Anchor explanations in business outcomes, concrete analogies, and visual architectural diagrams.
45. How do you validate the quality of your work?
Discuss your quality standards: automated unit testing, peer code reviews, user testing, monitoring, and telemetry.
Part 9: Difficult Interview Questions
46. Why should we choose you over another qualified candidate?
Do not speculate about other candidates. Focus on your unique combination of skills, domain background, and commitment to driving results.
47. What salary are you expecting?
Know your market value based on industry benchmarks. Offer a competitive target range based on total compensation and role scope.
48. Why were you unemployed for a period?
Be honest, transparent, and concise. Then pivot immediately to how you stayed sharp, learned new skills, or prepared for your next step.
49. Why have you changed jobs frequently?
Frame transitions around expanding scope, company restructuring, or deliberate career progression without sounding defensive.
50. Do you have any questions for us?
Always prepare 3–5 strategic questions (explore our curated list in 25 best questions to ask at the end of an interview).
5 Questions Candidates Often Underrate
The questions that seem simplest can be the most dangerous:
- “Tell me about yourself.” — Because candidates ramble without focusing on what the employer actually needs.
- “Why should we hire you?” — Because candidates list personal traits rather than business value.
- “What is your weakness?” — Because candidates deliver transparent humblebrags instead of genuine self-awareness.
- “Tell me about a failure.” — Because candidates try to sanitize the story instead of showing accountability and reflection.
- “Do you have any questions?” — Because candidates treat the interview as a one-way interrogation instead of a peer evaluation.
Don't Memorize These Answers
A common interview mistake is searching "Best answer to tell me about yourself" and memorizing a paragraph. That creates a fragile illusion of preparation.
Interviewers don't just accept canned responses. They probe with follow-ups: "Why did you choose that?", "What did you personally do?", "What failed?", "What would you change?"
Your preparation must survive the live conversational pressure of an interviewer pushing into the details.
Turn These 50 Questions Into a Mock Interview
You can use this article as a preparation checklist. But reading questions is only the first step. To build true conversational fluency, practice answering them aloud under pressure against your target job description.
Ready to put this into practice?
Reading the answer isn't enough. Say it out loud and practice the conversation with Mockly's JD-matched voice interview simulator.
Start Free Trial →Frequently Asked Questions
What are the most common job interview questions?
Questions about your background ('Tell me about yourself'), motivation ('Why do you want this job?'), strengths and weaknesses, behavioral situations ('Tell me about a time you failed'), problem solving, and why you want to join the company are the most universal categories.
Should I prepare answers to every interview question?
No. Instead of memorizing dozens of static scripts, prepare a structured story bank of 8–12 versatile professional experiences and flexible frameworks (like STAR) that can adapt to hundreds of question variations.
How long should an interview answer be?
Most answers should land between 60 and 120 seconds. This is long enough to provide context, concrete action, and quantifiable results without losing the interviewer's attention.
How can I practice common interview questions?
Answer them aloud, record yourself, use a timer to keep answers concise, and practice with an interactive mock interviewer that asks spontaneous follow-up questions.