Common Interview Questions and Answers (STAR Method Guide)

Sit through 20 interviews across different companies and you'll notice something: the questions barely change. A product manager interview at Flipkart and a sales role interview at a Pune-based SaaS startup will both open with some version of "tell me about yourself" and "why do you want to leave your current job." Interviewers aren't being unoriginal — these questions are efficient filters. Here's what each one is actually checking for, and how to structure an answer that doesn't fall apart under a follow-up question.

The STAR method, in 30 seconds

Most "tell me about a time when..." questions want a story, not a philosophy. STAR keeps that story tight and easy to follow:

• Situation — one or two lines of context. Company, team size, the problem.
• Task — what you specifically were responsible for (not your whole team).
• Action — the actual steps you took. This is 60% of your answer.
• Result — a number or concrete outcome. Revenue, time saved, retention, error rate.

Skip STAR and you get a rambling answer that ends with "...and it worked out well." With STAR, the same story ends with "...which cut our average ticket resolution time from 26 hours to 9 hours over the next quarter." One of these gets remembered.

"Tell me about yourself"

This isn't a request for your life story starting from your 10th board exam percentage. It's testing whether you can summarise your professional identity in under 90 seconds without rambling.

How to structure it

• Present: what you do right now and at which company, in one line.
• Past: 1-2 relevant experiences that led here — skip anything unrelated to this role.
• Future: why this specific role and company make sense as the next step.

Example: "I'm currently a business analyst at an Infosys BPM account, handling MIS reporting for a US retail client. Before that I did my MBA in finance from Symbiosis, and interned with a fintech startup building their expense-tracking dashboard. I'm looking to move into a full-time analytics role like this one, where I can work closer to the product instead of just reporting on it."

"Why do you want to leave your current job?"

This tests whether you'll bad-mouth your employer (a red flag for how you'll talk about this company later) and whether your reason for leaving is compatible with what this job actually offers.

• Never criticise your manager or company by name, even if the reason is genuinely bad management.
• Frame it around growth, scope, or skill-fit rather than complaint: "I've hit the ceiling of what my current role can teach me about X."
• If the real reason is compensation, it's fine to say so directly once you're deeper into the process — just don't lead with it.

"What's your biggest weakness?"

The interviewer isn't looking for a confession. They're checking two things: are you self-aware, and have you actually done something about the weakness, or just named it and moved on.

Pick a real weakness that isn't a disguised strength ("I work too hard" fools no one), then show the fix: "I used to avoid pushing back on unrealistic deadlines from stakeholders. After a project slipped by two weeks last year, I started building buffer time into estimates and flagging risks in the first week instead of the last."

"Tell me about a time you handled a conflict or a difficult stakeholder"

This is a pure STAR question, and it's testing your judgment under friction — not whether you avoided conflict entirely.

Example structure: Situation — a client wanted a feature shipped in a sprint your team said was unrealistic. Task — you were the point of contact managing that relationship. Action — you broke the feature into two phases, showed the client a working demo of phase one in week two to buy goodwill, and negotiated phase two into the next sprint. Result — the client renewed the contract for another 6 months and cited responsiveness in the renewal call.

"Where do you see yourself in 5 years?"

This checks two things: whether your ambitions exist within this company's career track at all, and whether you'll leave in 8 months for a 20% hike elsewhere. Anchor your answer to skills and scope, not job titles — "I want to be leading a small analytics team and owning a product line" reads better than "I want your boss's job."

"Why should we hire you?"

This is your chance to directly connect your STAR stories to the job description. Pick the two or three requirements the JD emphasises most and map a concrete result to each one, instead of listing adjectives about yourself.

Before you walk in: a prep checklist

• Write out 5-6 STAR stories from your actual work history — cover a conflict, a failure, a leadership moment, and a big win.
• Time your "tell me about yourself" answer out loud. If it crosses 90 seconds, cut it.
• Re-read the job description and highlight the 3 skills mentioned most — prep a story for each.
• Have your resume numbers memorised cold: percentages, revenue figures, team sizes, timelines.
• Prepare two questions to ask the interviewer that reference something specific about the company, not generic ones like "what's the culture like."