Behavioral interview questions follow a predictable pattern: "Tell me about a time you…" They are answered with the STAR method — Situation, Task, Action, Result — one of the most-studied structured interviewing techniques in industrial-organizational psychology research (Levashina et al., 2014, Personnel Psychology). Below are all 50 questions across five categories. The first question in each category includes a full sample answer you can adapt; the remaining 45 include a targeted answer tip. For role-specific prep, see the FAANG software engineer interview guide.
The STAR Method
Situation
Set the scene with context
Task
Your specific responsibility
Action
Exactly what you did
Result
The measurable outcome
5 Sample Answers in Full
One detailed STAR answer per category — adapt the structure to your own experience.
Tell me about a time you led a team through a difficult project.
Our team was mid-way through a product launch when a key engineer left unexpectedly.
As tech lead, I had to redistribute ownership and maintain the timeline without overloading the remaining engineers.
I ran a scope triage session, cut two non-essential features with stakeholder sign-off, re-assigned ownership with clear documentation, and implemented daily standups for the sprint.
We shipped on time. The cut features were delivered in the following sprint and the team morale held — two engineers specifically mentioned the clarity it gave them.
Describe a disagreement with a colleague and how you resolved it.
A senior colleague and I disagreed on the database architecture for a new microservice — they wanted PostgreSQL, I advocated for DynamoDB.
We needed to align before sprint planning the following day.
I proposed we each write up a one-page trade-off doc and share it asynchronously. I focused on the read pattern and cost at scale. We then had a 30-minute structured discussion on the docs rather than a debate.
We landed on a hybrid approach — DynamoDB for the hot path, Postgres for reporting queries. The decision got buy-in from the whole team because the trade-offs were documented.
Tell me about a time you failed. What did you learn?
I shipped a feature that caused a 15-minute outage on a Black Friday equivalent traffic day.
The post-incident review was my responsibility as the feature's owner.
I ran the review without blame, identified the root cause (a missing circuit breaker), documented the contributing factors, and proposed a pre-deploy checklist for high-risk releases.
The checklist was adopted team-wide. The same failure mode hasn't recurred in 18 months. Personally, I developed a strong habit of load-testing in staging before any high-traffic deployment.
Give an example of a time you worked well in a cross-functional team.
A product redesign required close collaboration between engineering, design, and customer success — three teams that rarely worked together directly.
I was the engineering representative and responsible for translating technical constraints into design requirements.
I set up a shared Figma channel where engineers could annotate feasibility notes directly on designs, ran bi-weekly sync sessions, and created a living document of constraints and trade-offs accessible to all three teams.
The redesign launched with zero cross-functional blockers and became a model for how we structure multi-team projects. Customer success rated it the smoothest collaboration they had been part of.
Tell me about a time you identified a problem before being asked to.
Our support ticket volume was growing 30% month-on-month but we had no visibility into which features were driving it.
This was not in my remit — I was on the platform team — but I could see the data.
I spent two evenings building a simple dashboard that tagged tickets by feature area using keyword matching. I shared it with the support and product leads with a prioritized list of the top 10 friction points.
The product team used the dashboard to reprioritise their backlog. Two of the top issues were addressed in the next sprint, and ticket volume dropped 18% the following month.
All 50 Questions
Grouped by category. Each includes a tip on what interviewers are really looking for.
Leadership
Tell me about a time you led a team through a difficult project.
Tip: Full STAR example above — reference it.
Describe a time you had to make a decision with incomplete information.
Tip: Show your reasoning process. Explain what data you had, what you assumed, and how you validated post-decision.
Tell me about a time you had to influence someone without direct authority.
Tip: Focus on relationship-building and logic. Avoid "I just convinced them" — walk through the specific argument.
Give an example of a time you set a vision for a team.
Tip: Quantify the before/after. What changed because of the vision you set?
Tell me about a time you had to deliver difficult feedback.
Tip: Show empathy and specificity. Describe what you said, how the person responded, and the outcome.
Describe a time you had to motivate a disengaged team member.
Tip: Diagnose before prescribing. Show that you understood the root cause before acting.
Tell me about a time you had to change direction mid-project.
Tip: Explain what triggered the pivot, how you communicated it, and how you minimized disruption.
Describe a time you held your team to a high standard under pressure.
Tip: Show that you balanced quality with humanity — you pushed for the bar without burning people out.
Tell me about a time you developed someone on your team.
Tip: Be specific about what you coached, how the person grew, and the measurable impact.
Give an example of when you had to escalate a decision upward.
Tip: Show good judgment. Explain what you had tried first and why escalation was the right call.
Conflict
Describe a disagreement with a colleague and how you resolved it.
Tip: Full STAR example above — reference it.
Tell me about a time you disagreed with your manager.
Tip: Show respect and assertiveness. You can disagree and commit — explain how you did both.
Describe a time you had to navigate a politically sensitive situation.
Tip: Avoid vague diplomacy. Show the specific actions you took and why.
Tell me about a time a colleague was not pulling their weight.
Tip: Show that you addressed it directly and professionally before escalating.
Describe a conflict between two team members you had to resolve.
Tip: As a mediator, show impartiality. Describe how you got both parties to a shared understanding.
Tell me about a time you pushed back on a requirement from a stakeholder.
Tip: Frame pushback as serving the stakeholder's real goal, not just your preference.
Describe a time when your priorities conflicted with a colleague's.
Tip: Explain the trade-offs you surfaced and how you reached alignment.
Tell me about a time you had to give feedback that someone resisted.
Tip: Stay on the outcome, not the emotion. What happened after they resisted?
Describe a time you were wrong and had to admit it.
Tip: Own it cleanly. The strongest answers show what you did after admitting the mistake.
Tell me about a time you had to represent your team's interest against another team's.
Tip: Show you advocated firmly but without damaging the relationship.
Failure & Resilience
Tell me about a time you failed. What did you learn?
Tip: Full STAR example above — reference it.
Describe a time a project you owned did not meet expectations.
Tip: Own it. Show the root cause analysis and the systemic fix, not just a personal lesson.
Tell me about a time you missed a deadline.
Tip: Show early communication. Did you flag the risk before the miss or only after?
Describe a time you received critical feedback. How did you respond?
Tip: Show that you separated your ego from the feedback. What specifically changed in your behavior?
Tell me about a time you worked on something that got cancelled.
Tip: Show maturity. Focus on what you learned and how you handled the disappointment.
Describe a time when you overcommitted.
Tip: Show that you diagnosed the cause — not just "I was too busy" — and changed how you scope work.
Tell me about a time you had to recover from a mistake in front of customers.
Tip: Speed of acknowledgment matters. Show how you communicated, fixed, and followed up.
Describe a time you underestimated the complexity of a task.
Tip: Show improved estimation practices. What changed in your planning process after?
Tell me about a time you had to start over from scratch.
Tip: Show resilience without drama. Focus on the systematic approach you took the second time.
Describe a time you disagreed with a decision but it turned out to be right.
Tip: Show intellectual honesty. What updated your view and how did you update it?
Teamwork & Collaboration
Give an example of a time you worked well in a cross-functional team.
Tip: Full STAR example above — reference it.
Tell me about a time you had to rely on a colleague you had not worked with before.
Tip: Show how you built trust quickly and established clear ownership.
Describe a time you had to adapt your communication style for a different audience.
Tip: Be specific about what you changed and why.
Tell me about a time you helped a colleague who was struggling.
Tip: Show judgment — you helped without doing their work for them.
Describe a time you went above and beyond for your team.
Tip: Keep it concrete. "Above and beyond" should have a measurable outcome.
Tell me about a time you had to coordinate across time zones or remote teams.
Tip: Show structural thinking. What systems did you put in place to compensate for async gaps?
Describe a time you shared credit with your team.
Tip: Show genuine generosity. Mention specific colleagues and their contributions.
Tell me about a time you onboarded a new team member.
Tip: Show investment in the person. What did you put in place to set them up for success quickly?
Describe a time you had to represent a team decision you personally disagreed with.
Tip: "Disagree and commit" is a senior skill. Show that you committed without undermining the decision.
Tell me about a time you contributed to improving your team's process.
Tip: Quantify the improvement. Time saved, errors reduced, velocity increased.
Initiative & Ownership
Tell me about a time you identified a problem before being asked to.
Tip: Full STAR example above — reference it.
Describe a time you took on a project outside your job description.
Tip: Show strategic judgment — you did it because it mattered, not just to look good.
Tell me about a time you proposed and drove a significant change.
Tip: Show the full arc: problem → proposal → buy-in → execution → result.
Describe a time you saw an opportunity others missed.
Tip: Be specific about what you noticed and why others might have missed it.
Tell me about a time you improved a process no one asked you to fix.
Tip: Quantify the improvement. Show you validated the problem before jumping to the solution.
Describe a time you had to learn something new quickly to do your job.
Tip: Show your learning method, not just that you learned it.
Tell me about a time you took a risk that paid off.
Tip: Show calculated risk — what did you assess before deciding, and what was the upside/downside?
Describe a time you set a goal and exceeded it.
Tip: Explain how you set the original goal and what you did differently to exceed it.
Tell me about a time you built something from zero.
Tip: Show the ambiguity you navigated. Starting from scratch means dealing with undefined requirements.
Describe a time you made a process more efficient.
Tip: Before/after metrics make this answer. Without numbers it sounds like a guess.
Practice these with Amigo's AI copilot
Run mock behavioral interviews and get <BlogLink to="/blog/real-time-interview-assistance-explained">real-time STAR-structured answers</BlogLink> tailored to your resume. Free to start.
Try Amigo free →Frequently Asked Questions
What is the STAR method?
STAR = Situation, Task, Action, Result. A structured framework for answering behavioral questions with a clear narrative arc and measurable outcome.
How long should a behavioral answer be?
Aim for 90 seconds to 2 minutes. Cover all four STAR elements with specifics. If the interviewer wants more detail, they will ask.
Should I memorise specific answers?
Memorise your key stories, not word-for-word answers. Know 5–8 strong examples from your career well enough to fit them to different question angles. Don't script — interviewers can tell.
What if I don't have a relevant example?
Use the closest thing you have and frame it honestly. 'I haven't faced exactly this, but the most relevant situation I can think of is...' is always better than making something up.
Found this useful?
Share it with someone preparing for an interview.