Most Common Interview Questions & How to Answer Them

6 min read·17 questions·Updated Apr 7, 2026

Every interview — whether at a FAANG company, a fast-growing startup, or a Fortune 500 — starts with a predictable set of questions. "Tell me about yourself," "Why this company?", "What's your greatest weakness?" These aren't throwaway small talk; they set the tone for the entire conversation and can quietly make or break a hiring decision. This guide covers the most universally asked interview questions, with frameworks that work across roles, levels, and industries so you never walk in unprepared for the basics.

Self-Introduction

Your opening pitch sets the frame for every question that follows. Get it wrong and you spend the rest of the interview correcting a first impression. Get it right and the interviewer is already rooting for you.

1Tell me about yourself.

Why it's asked

The universal opener. Tests whether you can tell a coherent career story in under 2 minutes and signal why you're a fit for this specific role.

How to answer

Present-Past-Future: start with your current role and a headline accomplishment, briefly explain the path that got you here (2–3 sentences), then pivot to why this role is the logical next step.

Key points to hit

  • Lead with your current title and one quantified achievement
  • Connect the dots between past roles — show intentional growth, not random job hops
  • End by tying your experience directly to the role you're interviewing for
  • Keep it under 90 seconds — this is a highlight reel, not a biography

Rehearse this answer out loud at least 5 times. It's the only question you're guaranteed to get, and stumbling on the opener tanks confidence for the rest of the interview.

2Walk me through your resume.

Why it's asked

Similar to "tell me about yourself" but signals the interviewer wants more chronological detail. They're looking for progression and intentionality.

How to answer

Chronological narrative: start from the earliest relevant role, highlight one key achievement per stop, and explain each transition. End at your current role with the strongest impact statement.

Key points to hit

  • Spend more time on recent roles — 30 seconds each for older roles, 60 seconds for the current one
  • For each transition, explain why you moved (growth, new challenge, not just "the offer was good")
  • Highlight increasing scope or responsibility across roles
  • Skip internships and early roles unless directly relevant
3What do you do in your current role?

Why it's asked

A precision version of "tell me about yourself." They want to understand your day-to-day and whether it maps to the role you're interviewing for.

How to answer

Role → Responsibilities → Results: state your title and team, describe your core responsibilities (not a job description — what you actually spend time on), and cite 2–3 measurable results.

Key points to hit

  • Be specific: "I own the checkout flow" not "I work on the platform"
  • Include cross-functional interactions — who do you collaborate with?
  • Mention scope: team size, revenue impact, user base
  • Close with a recent win that demonstrates your level

Motivation & Fit

These questions test whether you've done your homework and whether your genuine interests align with the company's mission. Generic answers are an instant red flag.

4Why do you want to work here?

Why it's asked

Tests whether you're genuinely interested in this specific company or just spraying applications. Interviewers can tell the difference immediately.

How to answer

Company-Product-You: cite something specific about the company (product, mission, recent news), connect it to a genuine interest or experience of yours, then explain how you'd contribute.

Key points to hit

  • Reference something specific: a product feature, blog post, or company value — not just "I admire your culture"
  • Connect it to your own experience: "I built X which is similar to your approach on Y"
  • Show you've used the product or studied the market
  • Avoid flattery — interviewers value specificity over enthusiasm

Spend 15 minutes before every interview reading the company's latest blog posts, press releases, and product updates. The ROI is enormous.

5Why are you leaving your current job?

Why it's asked

Tests self-awareness and professionalism. They're listening for red flags: bitterness, drama, or running away from problems.

How to answer

Pull, not push: frame your answer around what's pulling you toward the new role (growth, challenge, mission alignment), not what's pushing you away from the old one.

Key points to hit

  • Never badmouth your current employer, manager, or teammates
  • Focus on what you want to move toward: bigger scope, new domain, specific mission
  • If the real reason is negative (layoffs, conflict), reframe honestly but positively
  • Show that you're leaving at a natural inflection point, not fleeing
6Where do you see yourself in 5 years?

Why it's asked

Tests ambition and retention risk. They want to know if this role fits into a coherent career plan — and if you'll stay long enough to deliver impact.

How to answer

Growth within this trajectory: describe the skills you want to develop and the scope you aspire to, connected to what this specific role enables. Be ambitious but realistic.

Key points to hit

  • Show ambition: "leading a team" or "owning a product area" — not "doing the same thing"
  • Tie it to the company's growth: "As the company scales, I'd love to…"
  • Avoid naming specific titles — focus on impact and scope instead
  • Don't say "your job" to the interviewer — it's awkward, not charming
7What motivates you?

Why it's asked

Tests alignment between your intrinsic drivers and the role's daily reality. A mismatch here predicts attrition.

How to answer

Intrinsic driver + proof: name a genuine motivator (solving hard problems, shipping things users love, building teams), then back it up with a specific example from your career.

Key points to hit

  • Be authentic — generic answers ("I love learning") are forgettable
  • Connect your motivator to the role: if you love mentoring, this matters more for EM roles
  • Use a specific story: "When I shipped X and saw users respond, that's what drives me"
  • Avoid purely extrinsic motivators (money, promotion) — save those for negotiation

Strengths & Weaknesses

The classic trap questions. Interviewers aren't looking for perfection — they're assessing self-awareness, honesty, and whether you've done the inner work to understand your own patterns.

8What is your greatest strength?

Why it's asked

Tests self-awareness and relevance. Can you identify what you're genuinely best at — and is it relevant to the role?

How to answer

Strength + evidence + relevance: name a specific strength, prove it with a concrete example, and connect it to why it matters for this role.

Key points to hit

  • Choose a strength that maps directly to the role's core requirements
  • Back it up with numbers: "I reduced deploy time by 40%" not "I'm good at optimising"
  • Avoid clichés: "I'm a hard worker" tells the interviewer nothing
  • One strong, well-evidenced strength beats a list of vague ones
9What is your greatest weakness?

Why it's asked

The most dreaded question in interviewing — and the one that reveals the most about self-awareness. "I'm a perfectionist" is an instant eye-roll.

How to answer

Real weakness + awareness + mitigation: name a genuine area of development (not a disguised strength), explain how it has impacted you, and describe the specific steps you've taken to manage it.

Key points to hit

  • Choose something real but not disqualifying — "I struggle with delegation" not "I can't code"
  • Show the impact: "This caused me to miss a deadline because…"
  • Describe your mitigation strategy: "I now time-box my reviews to 30 minutes"
  • Demonstrate progress: "My manager noticed the improvement in our last review cycle"

The best weakness answers follow a three-act arc: the flaw, the consequence, the growth. Interviewers remember narrative structure.

10What would your manager say about you?

Why it's asked

A back-channel check disguised as a question. Tests whether your self-perception matches external feedback — and whether you're coachable.

How to answer

Quote or paraphrase actual feedback: reference specific feedback from your most recent review cycle. Include one positive and one developmental area to show balance.

Key points to hit

  • Use direct quotes if possible: "In my last review, she said…"
  • Include the developmental feedback — one-sided praise sounds rehearsed
  • Show that you acted on the developmental feedback
  • If you've been at a company with no formal reviews, reference informal 1:1 feedback

Situational & Problem-Solving

These hypothetical questions test your thinking process in real-time. Interviewers care less about the "right" answer and more about how you reason through ambiguity.

11How do you handle pressure or stressful situations?

Why it's asked

Every role involves crunch periods. Interviewers want to know if you crumble, burn out, or have systems to manage stress productively.

How to answer

System + example: describe your approach to managing pressure (prioritisation, communication, time-boxing), then illustrate with a specific story where it worked.

Key points to hit

  • Name your system: "I prioritise ruthlessly and communicate early about trade-offs"
  • Give a concrete example with stakes and outcome
  • Show that you protect your team during pressure, not just yourself
  • Avoid "I thrive under pressure" — it sounds naive to experienced managers
12Describe a time you had to make a difficult decision.

Why it's asked

Tests judgement and decisiveness. Can you weigh trade-offs, commit, and own the outcome?

How to answer

STAR: set the decision context (what was at stake), outline the options and trade-offs you evaluated, explain your decision rationale, and share the result.

Key points to hit

  • Show that you considered multiple options — not just the one you chose
  • Explain your decision framework: data, principles, stakeholder input
  • Own the outcome, whether it was positive or mixed
  • If the decision was wrong, show how you course-corrected
13Tell me about a time you had to prioritise competing tasks.

Why it's asked

Tests your ability to triage and say no. In fast-moving environments, this skill matters as much as execution itself.

How to answer

STAR: describe the competing demands, your prioritisation method (impact, urgency, dependencies), what you chose and what you explicitly deferred, and the result.

Key points to hit

  • Name the stakes: what would happen if you tried to do everything?
  • Show a clear framework: "I ranked by user impact × urgency"
  • Explain what you said no to — and how you communicated that
  • Result: delivered the highest-impact item on time
14How would you deal with a teammate who isn't pulling their weight?

Why it's asked

Tests emotional intelligence and problem-solving. They want to see empathy first, escalation as a last resort.

How to answer

Assume good intent → diagnose → act: explain that you'd first assume there's a reason (burnout, unclear expectations, personal issues), have a private 1:1, offer help, and escalate only if the pattern continues.

Key points to hit

  • Show empathy first: "I'd start by checking in privately"
  • Separate performance from character — focus on specific behaviours
  • Offer concrete help: "Can I pair with you on this?" or "Is something blocking you?"
  • Escalation is a tool, not a threat — explain when and how you'd involve a manager

Closing & Questions to Ask

The end of the interview is your chance to leave a lasting impression and gather critical information for your decision. "No, I think you covered everything" is the wrong answer.

15Do you have any questions for me?

Why it's asked

Tests preparation and genuine interest. The quality of your questions reveals how seriously you've thought about the role and the company.

How to answer

Prepare 3–5 questions in advance, tailored to the interviewer's role. Ask about the team, the challenges, and the decision-making culture — not logistics (save that for the recruiter).

Key points to hit

  • "What's the biggest challenge your team is facing right now?" — shows you're thinking about impact
  • "How do you measure success for this role in the first 6 months?" — shows you're outcome-oriented
  • "What's something you wish candidates understood better about working here?" — disarming and insightful
  • Avoid salary, benefits, or PTO questions in technical/hiring manager rounds

Tailor at least one question to something the interviewer personally said during the conversation. It shows active listening and genuine engagement.

16Is there anything about my background that concerns you?

Why it's asked

You're actually asking this one. It gives you a chance to address objections directly before the interviewer discusses you in a debrief without you present.

How to answer

Ask directly, listen carefully, and address concerns with evidence. This is high-risk, high-reward — only use it if you're comfortable thinking on your feet.

Key points to hit

  • Stay calm if they raise a real concern — this is your chance to reframe it
  • Use specific evidence to counter: "I understand that concern — at my last role, I demonstrated X"
  • Thank them for the honesty regardless of the answer
  • Not all interviewers will answer honestly — that's OK, the signal is still valuable
17What are the next steps in the process?

Why it's asked

A practical closer that shows professionalism and genuine interest. It also sets expectations so you're not anxiously refreshing your email.

How to answer

Ask about timeline, remaining rounds, and who you'd be meeting. Follow up with a brief expression of enthusiasm.

Key points to hit

  • "What does the rest of the interview process look like?" — neutral and professional
  • "When can I expect to hear back?" — direct and appropriate
  • Close with: "I'm really excited about this opportunity — thanks for your time"
  • Send a brief thank-you email within 24 hours

Ready to practise these answers out loud?

Start a mock interview

Frequently Asked Questions

Prepare answers for 15–20 common questions (this guide covers the most important ones), plus 8–10 behavioral stories using the STAR method. You don't need a scripted answer for every possible question — the goal is to build reusable frameworks you can adapt on the fly. Focus on quality over quantity: 15 well-rehearsed answers beat 50 surface-level ones.

No — memorised answers sound robotic and crumble when the interviewer asks a follow-up you didn't anticipate. Instead, memorise your key talking points and practice delivering them in slightly different ways each time. Know your opening line and your closing line; let the middle flow naturally. Record yourself on your phone and listen back — you'll catch filler words and rambling quickly.

Aim for 60–90 seconds for straightforward questions ("Why this company?") and 90 seconds to 2 minutes for behavioral or situational questions. If you're past 2 minutes, you're likely rambling. Practice with a timer until concise answers feel natural. When in doubt, finish your answer and ask: "Would you like me to go deeper on any part of that?"

Yes — every technical interview loop includes behavioral and general questions alongside coding and system design rounds. At Google, Meta, and Amazon, behavioral rounds carry equal weight to technical rounds in the final hiring decision. Engineers who skip preparation for these "soft" questions are making the most common interview mistake in the industry.

It happens to everyone. Take a 5-second pause to collect your thoughts (interviewers respect this). Then use a framework: for behavioral questions, default to STAR. For opinion questions, state your position and give one supporting reason. For questions you genuinely can't answer, say: "I haven't encountered that specifically, but here's how I'd approach it…" Honesty plus a structured thought process beats a bluffed answer every time.

Phone screens are typically shorter (30–45 minutes) and focus on motivation, fit, and basic qualifications — the questions in this guide are exactly what you'll face. On-site interviews dive deeper into behavioral and technical areas. For phone screens, nail your "Tell me about yourself" and "Why this company?" answers — they're almost guaranteed. For on-sites, prepare a wider range of stories and be ready for follow-up questions that probe deeper.

You've read the questions.
Now, practise out loud.

Jump into a live mock interview with an AI interviewer. Get scored feedback on every answer.

No signup needed
Start a mock interview

~30 seconds to set up