The STAR method, in 30 seconds
Behavioral questions ("Tell me about a time when…") are best answered with STAR: the Situation (context, 1 sentence), the Task (what you needed to achieve), the Action (what you specifically did — the longest part), and the Result (what happened, ideally with a number). Keep each answer under two minutes.
The setup is rarely what costs you the point. Candidates lose ground because they describe the team's work instead of their own, or because the answer stops before the result. A workable balance is roughly one sentence of Situation, one of Task, three or four of Action, and two of Result — and "I" wherever you describe a decision you personally made.
Situation: We were two days from launching a pricing update for about 40 accounts. Task: I owned the final check on the invoice templates. Action: I rebuilt the test file from the original spec instead of reusing last quarter's copy, spot-checked 12 sample accounts, and found that the proration line rounded down for mid-month upgrades. I sent the finance lead two screenshots and a proposed fix the same afternoon. Result: We shipped a day late, but the corrected logic avoided roughly $18K in underbilling in the first month, and the check became a standing item on the launch checklist.
What makes that answer land: a specific stake, a decision that was clearly yours, and a result someone could verify. You do not need a dramatic story. A small incident told precisely beats a vague triumph.
Build a story bank before you practice
Behavioral interviews recycle the same handful of themes. Write six stories once, then reuse each for two or three different questions by shifting the emphasis. Keep them in one document and re-read it the morning of the interview.
- A conflict — a disagreement with a colleague, manager, or client that you resolved without escalating it.
- A failure — a missed deadline, an estimate that was wrong, a launch that underperformed.
- A deadline — a week when everything was due and you had to decide what to cut.
- Leadership without a title — a process you fixed, a new hire you mentored, a project nobody owned.
- Hard feedback — something true that stung, and what changed afterward.
- Fast learning — a tool, domain, or client you had to get up to speed on in days rather than months.
For each story, note the four STAR beats plus one number. If a number genuinely does not exist, note the before-and-after instead: three approval emails per request became one form; two days of manual reconciliation became a scheduled report.
The 15 questions
1. Tell me about yourself.
Not your life story — a 60–90 second professional pitch: present role and one win, key relevant skills, then why this role is the natural next step. Structure it Present → Past → Future.
2. Why do you want to work here?
Show you researched them: reference the mission, a product, or recent news, then connect it to your own goals. Generic praise ("you're a great company") signals a mass application.
3. Why are you leaving your current job?
Stay positive and forward-looking: "I've grown a lot, and I'm ready for a bigger scope that my current team can't offer." Never badmouth a former employer — it's the fastest way to lose an offer.
4. What are your strengths?
Pick one or two strengths relevant to the posting and back each with a quick example. "Strong stakeholder communication — for example, I regularly presented campaign results to non-technical leadership."
5. What is your greatest weakness?
Choose a real, non-fatal weakness and show active improvement: "I used to over-polish deliverables. I now time-box drafting and get feedback early, which has actually improved quality." Avoid humble-brags like "I'm a perfectionist."
6. Tell me about a time you failed.
STAR with emphasis on what you changed afterward. Pick a genuine setback with modest stakes — a missed estimate, a campaign that flopped — and own it clearly.
7. Tell me about a time you handled conflict with a coworker.
Show maturity: you listened first, focused on the shared goal, and resolved it professionally. Never portray the other person as a villain.
8. Describe a time you worked under a tight deadline.
Explain how you prioritized — what you cut, what you communicated, what you delivered. The prioritization reasoning matters more than the heroics.
9. Tell me about a time you showed leadership (without a title).
Great for students and ICs: organizing a process, mentoring a colleague, or stepping up when a project lacked direction. Leadership is behavior, not a job title.
10. Give an example of a time you received tough feedback.
Interviewers test coachability. Describe the feedback without defensiveness, what you changed, and the improvement that followed.
11. Tell me about a time you had to learn something quickly.
Show a concrete learning method — documentation, a course, pairing with an expert — and the outcome. This is especially common for tech and analytics roles.
12. Where do you see yourself in five years?
Keep it plausible and connected to the role: growing expertise, taking on more scope, contributing to bigger projects. Ambition is good; "your job" as a stepping stone is not.
13. What are your salary expectations?
In the U.S., research market rates (Levels.fyi, Glassdoor, BLS data) and give a range you'd genuinely accept, e.g., "Based on my research and experience, I'm targeting $70–80K, but I'm flexible for the right fit." If asked first, you may ask what range is budgeted.
14. Do you have any questions for us?
Always ask 2–3. Good ones: "What does success look like in the first 90 days?" "How does the team handle priorities changing mid-project?" "What do you personally enjoy most about working here?"
15. When can you start?
Be honest about notice periods. If currently employed, "two weeks after accepting an offer" is standard and shows professionalism.
Five more questions that come up
These are less universal than the fifteen above, but they appear often enough in U.S. interviews that they deserve a prepared answer.
16. Tell me about a time you disagreed with your manager.
Show judgment rather than obedience or rebellion. Describe the decision, the evidence you brought, and what happened next. The strongest version ends with you committing once the call was made: "I still thought we should have delayed, but I ran the launch plan as agreed and wrote up the risk for the retrospective."
17. How do you prioritize when everything is urgent?
Name a method instead of a personality trait: impact against effort, hard deadlines against soft ones, and who is blocked downstream. Then describe the communication step — telling stakeholders what will slip and why, rather than quietly working late. One example of a week where you renegotiated a deadline is worth more than a list of productivity tools.
18. Tell me about a process you improved.
Pick something small and measurable: a report that took four hours and now takes forty minutes, a handoff that kept losing requests, a checklist that ended repeat errors. Explain what you noticed, what you changed, and how you confirmed the change stuck. Improvements you made without being asked are strong evidence at senior levels.
19. What do you do when you don't know the answer?
Interviewers are testing honesty and method, not knowledge. Say what you do know, name how you would find the answer, and give a realistic timeframe: "I haven't used that system, but it looks close to one I have. I'd start with the vendor docs, test it in a sandbox this afternoon, and confirm with the platform team." Bluffing is audible to anyone who has done the job.
20. What makes you a strong fit for this role?
Take the three requirements the posting repeats most and give one proof point for each. Mirror their vocabulary — if they say "stakeholder management," do not answer with "I'm a people person." Then say what you would tackle in the first 90 days, which shows you have already pictured doing the job.
Questions to ask the interviewer
You usually get five to ten minutes at the end, and what you ask is weighed almost as heavily as what you answer. Prepare two or three questions about the work rather than the perks, and keep them written down so you do not freeze when the room goes quiet.
- "What does a successful first 90 days look like in this role?"
- "What is the biggest constraint on the team this year — headcount, tooling, or competing priorities?"
- "How are decisions made when the team disagrees?"
- "What happened to the person who held this role before me?"
- "Which parts of the job take the most time in a normal week?"
- "How do you tell whether someone is doing well after the first year?"
Skip anything answered on the careers page, and save compensation, benefits, and time off for the recruiter or the offer stage. If the interviewer seems rushed, ask one question and let them go — a thank-you note is a fine place to add a second.
After the interview
Send a short thank-you note within 24 hours: three sentences, one specific reference to something you discussed, one line restating why you fit. Do not re-attach your resume or write four paragraphs. If you were told a decision would come by a certain date and the date passes, one polite follow-up to the recruiter is appropriate — then wait.
When the next step is an offer, the conversation shifts from proving fit to agreeing on terms. Our salary negotiation guide covers naming a range, countering a lowball, and putting the final agreement in writing.