How to use this guide
Most interviews reuse the same 30 to 50 questions across every industry. Memorising scripts makes you sound robotic. Instead, build a story bank of 6 to 8 concrete projects and learn to map any question to one. This guide groups 100 questions into 8 buckets so you can rehearse by theme, not rote.
Interviewers are checking three things: can you do the job, will you work well with the team, and do you want this role specifically. Every answer you give should nudge at least one of those three. If your answer does not land somewhere on that map, cut it.
10 behavioural questions (the warm-ups)
These show up in the first 15 minutes of almost every interview. Nail these and you buy room to breathe in the harder rounds.
Q. Tell me about yourself.
A. 60 to 90 seconds. Present-past-future: one line on what you do today, two on the most relevant past wins, one on why this role now. No childhood bio, no full resume read-back.
Q. Why do you want this role?
A. Name one specific thing about the company (product, team, strategy) plus one bridge to your strengths. Generic answers ("great culture") get filtered.
Q. Why are you leaving your current job?
A. Forward-looking and neutral. "Looking for bigger scope in X" beats "my manager is..." Never bash a past employer.
Q. What is your greatest strength?
A. Pick one strength relevant to the role plus a 30-second story that proves it. Range + depth, not a list.
Q. What is your greatest weakness?
A. Real and in-progress, not humble-brag. "I under-communicate status on long tasks; I fixed it by shipping weekly written updates to my manager." Shows self-awareness + action.
Q. Where do you see yourself in 5 years?
A. Direction, not a title. "Deep expertise in X with growing ownership of Y" beats "your job". Leaves room for the interviewer to see a path.
Q. Why should we hire you?
A. Three sentences. One line on the biggest problem they hire this role for. One line on your closest past win. One line on the compounding you will create.
Q. Describe a time you failed.
A. Pick a real failure with a clear lesson. STAR: Situation, Task, Action, Result + Learned. The learning is the whole point.
Q. Tell me about a conflict with a coworker.
A. Pick a substantive, resolved conflict. Describe the disagreement factually, what you did to understand their view, how you resolved it, what you would do differently.
Q. Describe a time you led without authority.
A. Cross-functional project or peer initiative. Focus on influence: how you got buy-in, handled pushback, kept momentum.
5 situational questions
"How would you handle..." or "What would you do if...". they test judgment on scenarios you have not faced yet. Structure beats polish.
Q. How do you prioritise when everything is urgent?
A. Frame: impact x reversibility x deadline. Walk through how you cut 10 asks to 3 and communicated the trade-offs up.
Q. How do you handle tight deadlines?
A. Scope cut first, team help second, overtime last. Concrete example of each lever.
Q. How do you handle a disagreement with your manager?
A. Disagree-and-commit. State view in writing, hear theirs, commit if decision stands; revisit with data if outcome proves it wrong.
Q. How would you handle an underperforming team member?
A. Clarify expectations, specific feedback, agree PIP, weekly 1:1s, clear outcomes at 30/60/90. Document throughout.
Q. How do you handle ambiguity?
A. Break into what you know, what you can find in a day, what needs a decision. Ship the smallest version first.
6 technical questions (role-agnostic frames)
Exact questions vary by stack. The frames below work for software, data, design, PM, ops. any craft role.
Q. Walk me through a recent project.
A. Problem, constraints, key trade-off, outcome with a metric. 2 minutes. End by offering to go deeper on any part.
Q. How do you debug a production outage?
A. Stabilise (rollback/feature-flag) first, root-cause second. Logs, traces, last-known-good commit. Post-mortem with blameless review + action items.
Q. What is the hardest technical decision you made?
A. Build vs buy, migration, architecture. Focus on the trade-offs you evaluated and the cost of the option you did NOT pick.
Q. How do you stay current?
A. Source the answer: one newsletter, one podcast, one hands-on project. Names and specifics, not "I read a lot".
Q. How do you design [system X]?
A. Requirements first, read-vs-write path next, data model, scale assumptions, bottlenecks, trade-offs. Use 4 quadrants; stop and check scope every 2 mins.
Q. Explain [concept] to a non-technical person.
A. Analogy + one concrete example + why it matters. Skip the jargon. Interviewer is testing communication range.
4 leadership / management questions
Q. Describe your management style.
A. High context, high autonomy. Example of how you set a team North Star and how often you step in on execution.
Q. How do you give hard feedback?
A. Specific, private, within 48 hours. SBI (Situation-Behaviour-Impact). End on a clear ask, not a rant.
Q. How do you hire?
A. Rubric first. Panel with diverse views. Paid or scoped take-home for senior roles. Debrief independently, then together, before vote.
Q. Tell me about a time you had to let someone go.
A. Factual: what was communicated, what PIP looked like, when decision was made, how transition was handled. No bitter tone.
7 culture fit questions
Q. Do you prefer working alone or in a team?
A. Both, with examples. Deep solo focus for craft work, team for architecture calls and reviews. Healthy oscillation.
Q. How do you handle stress?
A. Systems, not willpower. Named habits (end-of-day shutdown, weekly review). One real example of a high-stress period and what you did.
Q. What motivates you?
A. Impact, craft, growth. Pick the one closest to your real driver and a 30-second story.
Q. What are you passionate about outside work?
A. Real, specific, 1 sentence. Not "Netflix". Something that shows depth or curiosity. No red flags (extreme views).
Q. Describe your ideal work environment.
A. Match it to the company you are interviewing at. If they are remote-first, say remote-first with specifics on async habits.
Q. How do you handle criticism?
A. Pause, clarify, thank, act. Example of feedback you received that changed how you work.
Q. What is your proudest professional accomplishment?
A. Something that required stretch and had measurable impact. Skip the trophy story; tell a shipping story.
6 tricky questions (gaps, layoffs, salary, job-hopping)
Handle these badly and you lose the offer in 30 seconds. Practise these out loud, not just in your head.
Q. Why is there a gap in your resume?
A. Direct and brief. Caregiving, health, learning, layoff. Name it, one sentence on what you did during, pivot back to what you bring now.
Q. Why were you laid off?
A. Business context (role/team/company cuts), not performance. Transition to what you are focused on now.
Q. Why are you job-hopping?
A. Pattern + reason + stability plan. "2 short stints were at failing startups; looking for a 5+ year home at a profitable company."
Q. You are overqualified for this role.
A. Acknowledge + deflect. "I stepped down in scope deliberately for [reason]; here is how I will bring outsized value without being bored."
Q. What are your salary expectations?
A. Give a researched range + offer flexibility on structure. Deflect if too early: "I would like to understand the role better first; can you share the band?"
Q. Will you take a counter-offer from your current employer?
A. No (if true). Explain reason for leaving is not pay. Counters rarely fix real issues.
4 questions you will face at the end
Q. Do you have any questions for us?
A. Always yes. Three prepared: one about the role (what does success look like in 6 months), one about the team (biggest recent challenge), one about the company (bet you are most excited about).
Q. What other companies are you interviewing with?
A. Honest but vague. "A few similar-stage companies in fintech." Do not name them unless you are late-stage and leveraging.
Q. How soon can you start?
A. Give real notice period. 30 days is standard for senior IC in India; 60 for US. Do not over-promise to win the offer.
Q. Is there anything else you would like us to know?
A. One sentence that reinforces your strongest signal for the role. Not a redo of your resume.
The STAR method in 60 seconds
Every behavioural answer fits in 90 seconds if you respect the proportions. Candidates who ramble on Situation for 2 minutes never get to Result and lose the question.
Top 10 interview mistakes
- Rehearsing answers so tight they sound scripted. Leave room to breathe.
- Answering for the team ("we did...") instead of yourself ("I...").
- Over-describing Situation. Interviewer wants Action and Result.
- No numbers. Every project story needs at least one metric.
- Bashing a previous employer. Instant red flag.
- Asking zero thoughtful questions at the end.
- Not researching the company enough to name one specific thing.
- Giving fake weaknesses ("I work too hard").
- Interrupting the interviewer. Let them finish.
- Arriving un-slept. Sleep beats one more hour of prep the night before.
The 48-hour prep plan
Day 1 (2 hours)
- Re-read the JD. Highlight 5 key requirements.
- Pick 6 stories from your past 3 roles that cover those 5 plus one failure.
- Write each as STAR bullets (not scripts).
- Research company: last 2 earnings / blog posts / recent news.
Day 2 (1.5 hours)
- Mock-interview out loud (phone voice recorder). Play back.
- Time each story. Anything over 2 minutes, cut.
- Prepare 3 questions for the interviewer.
- Lay out outfit, test the video/audio setup, write down the interviewer names.
External references
Further reading on this topic from independent sources. All external links open in a new tab.
Frequently asked questions
Should I memorise answers word-for-word?+
How long should my answers be?+
Is it OK to say "I do not know"?+
Should I take notes during the interview?+
Should I ask about salary in the first round?+
How do I answer when I do not have the exact experience they want?+
What if I bomb one question?+
Get your resume interview-ready
Every answer above is easier to tell when your resume already has the story bank. Build one in 10 minutes, free.