The 25 Most Common Interview Questions and How to Answer Them

Opening questions

1) "Tell me about yourself."

What they're asking: Can you give me a coherent 60-second narrative that maps to this role? Framework: Past → Present → Future, anchored in the JD. Example: "I'm a senior backend engineer with 6 years building payments systems — most recently at Stripe-adjacent infra. I'm currently focused on event-driven microservices, which is exactly why your senior-backend role caught my eye."

2) "Why this company?"

They want to hear specifics — products, recent news, mission — not flattery. Pick one product detail and one strategic detail. "Your Series C focus on enterprise SSO mirrors the auth work I shipped at my last company, and the recent Vault integration is exactly the architecture pattern I want to deepen."

3) "Why are you looking to leave your current role?"

Never criticize. Frame as a forward-looking pull. "My current scope is great but plateaued — I'm looking for a role where I can own a domain end-to-end, which is what this opening offers."

Behavioral questions (use STAR)

4) "Tell me about a time you led a team through a difficult project."

Pick a story with stakes, friction, and a measurable outcome. Spend ~30s on Action — what YOU did — not what the team did.

5) "Tell me about a failure."

Pick a real failure (not a disguised humblebrag). Show: what you owned, what went wrong, what you learned, what you do differently now.

6) "Tell me about a conflict with a coworker."

Stay specific, stay professional, focus on resolution. Avoid trauma-dumping or villainizing.

7) "Describe a time you had to make a decision with incomplete information."

Anchor in what you DID know, the speed/cost tradeoff you made, and how you closed the information gap after the decision.

8) "Tell me about a time you missed a deadline."

Acknowledge it, show how you communicated early, what you did to recover, and what process change came out of it.

9) "Tell me about a time you went above and beyond."

Avoid generic "I worked late" answers. Show a specific instance where you did work that wasn't expected and what changed because of it.

10) "Tell me about a time you received tough feedback."

Show emotional regulation (you didn't get defensive), curiosity (you asked questions), and follow-through (you actually changed).

Situational questions

11) "How would you handle a teammate who isn't pulling their weight?"

Walk through your actual process: gather data quietly, talk to them directly, escalate only if direct conversation fails.

12) "What would you do in your first 90 days here?"

Use a 30-60-90 structure. Days 1-30: learn (people, products, processes). Days 31-60: contribute (ship a small but visible win). Days 61-90: own (take on a named project).

13) "How would you prioritize between feature X and bug Y?"

Show a framework — impact × confidence × effort — and apply it out loud. Interviewers want to see your reasoning, not a single right answer.

Strengths and weaknesses

14) "What's your greatest strength?"

Pick a strength that maps directly to the JD. Anchor in a story. Avoid "I work too hard."

15) "What's your greatest weakness?"

Pick a real weakness, show self-awareness, show concrete steps you're taking. "Public speaking — I joined Toastmasters in January and now lead our team's bi-weekly demo."

16) "Where do you see yourself in 5 years?"

Show ambition rooted in this role's growth path. "I want to grow into a senior IC or tech lead role — both of which this team has clear paths into."

Technical questions

17) "Walk me through how you'd design X."

Use DIRECT: Definition (clarify scope), Implementation (the design), Reasoning (why this design), Examples (where you've seen it work), Constraints (what trade-offs), Tradeoffs (what you'd do differently at 100×).

18) "What's the difference between A and B?"

Define each precisely, give one concrete example of each, then state the tradeoff explicitly.

19) "How would you debug X?"

Show structured process — reproduce, isolate, hypothesize, verify, fix, validate, document.

Closing questions

20) "Why should we hire you?"

Restate the JD's top 3 needs, then map each to a specific accomplishment of yours.

21) "What's your salary expectation?"

Anchor in market data and give a range, not a number. "Based on market data for this role and my experience, I'm targeting $X-$Y."

22) "Do you have any questions for me?"

Always have 3-5 prepared. Best questions: about the role's success metrics, the team's biggest current challenge, and what "good" looks like in 90 days.

Curveball questions

23) "Tell me something not on your resume."

Pick something that signals interest, hustle, or relevant side-skill. Keep it under 30 seconds.

24) "What's your biggest professional regret?"

Pick a real one. Show what you'd do differently. Don't say "I have no regrets."

25) "Why have you changed jobs frequently?"

Acknowledge the pattern, frame each move as forward-looking, and signal that this role is one you'd grow IN, not through.

Pre-interview 48-hour checklist

The 48 hours before an interview are where most prep pays off. Run this checklist:

1. Re-read the JD and write down the 3 outcomes the role exists to produce. You'll reference these in every answer.
2. Pick 4-5 STAR stories from your library that collectively cover leadership, conflict, failure, impact, and technical depth.
3. Research the interviewer on LinkedIn — what's their background, what have they built, what would they care about hearing?
4. Prepare 3-5 thoughtful questions for the interviewer.
5. Set up your environment — clean background, good lighting, headphones, water, notes within reach.