Behavioral interviews assess how you've handled situations in the past to predict future performance. At FAANG and top companies, behavioral questions can make up 50% of your interview evaluation. This guide covers the STAR method, common questions, and how to structure winning answers.
Technical Skills + Behavioral Skills = Great Hire
50% 50%
Companies assess:
├── Leadership potential
├── Collaboration ability
├── Problem-solving approach
├── Communication skills
├── Cultural fit
└── Growth mindset
┌─────────────────────────────────────────────────────────────┐
│ STAR Method │
├─────────────────────────────────────────────────────────────┤
│ │
│ S - Situation (10-15%) │
│ ├── Set the context │
│ ├── When and where │
│ └── Who was involved │
│ │
│ T - Task (10-15%) │
│ ├── Your responsibility │
│ ├── What needed to be done │
│ └── What was at stake │
│ │
│ A - Action (60-70%) │
│ ├── What YOU specifically did │
│ ├── Step by step approach │
│ ├── Skills and tools used │
│ └── How you overcame obstacles │
│ │
│ R - Result (15-20%) │
│ ├── Quantifiable outcomes │
│ ├── What you learned │
│ └── What you'd do differently │
│ │
└─────────────────────────────────────────────────────────────┘
Question: "Tell me about a time you had to deal with a difficult technical problem under pressure."
SITUATION:
"During Black Friday at my previous company, our payment processing
system started failing at 3x normal traffic. I was the on-call
DevOps engineer when alerts started firing at 2 AM."
TASK:
"I needed to identify the root cause and restore service quickly.
Every minute of downtime was costing approximately $50,000 in
lost revenue, and the team was depending on me to lead the response."
ACTION:
"First, I established a war room and pulled in the payment team lead
and database engineer. I quickly triaged by checking our monitoring
dashboards and identified that our database connection pool was
exhausted.
Rather than just increasing the pool size, I dug deeper and found
that a recent code deployment had a connection leak. I made the call
to roll back to the previous version while we fixed the bug.
I communicated status updates every 15 minutes to stakeholders and
documented everything in our incident channel. After rollback, I
worked with the dev team to identify the exact code causing the leak."
RESULT:
"We restored service within 45 minutes, limiting revenue loss to
approximately $35,000 instead of the potential $200,000+ if we'd
taken longer. I then led a blameless postmortem that resulted in
three key improvements: automated connection pool monitoring,
mandatory load testing before Black Friday deployments, and a
runbook specifically for high-traffic events.
The following year, we handled 5x traffic with zero incidents."
1. "Tell me about a time you led a project or initiative."
Good Answer Elements:
- Clear ownership and accountability
- How you motivated the team
- Obstacles you overcame
- Measurable outcomes
Sample Response Structure:
SITUATION: "Our deployment process took 4 hours and required manual
steps. This was causing delays and errors."
TASK: "I proposed and got approval to lead a CI/CD modernization
project, managing a team of 3 engineers."
ACTION: "I started by documenting our current state and identifying
the biggest pain points through developer surveys. Then I:
1. Created a phased roadmap with clear milestones
2. Set up weekly demos to maintain momentum and get feedback
3. Paired with skeptical team members to address their concerns
4. Built automated testing into each stage
5. Created documentation and training materials"
RESULT: "We reduced deployment time from 4 hours to 15 minutes and
eliminated manual errors. Developer satisfaction with deployments
increased from 3/10 to 8/10. This project was later adopted by
three other teams."2. "Describe a time when you went above and beyond your job responsibilities."
3. "Tell me about a time you identified a problem before it became critical."
4. "Give an example of when you took ownership of something outside your area."
5. "Tell me about a disagreement you had with a coworker. How did you handle it?"
Good Answer Elements:
- Show emotional intelligence
- Focus on the issue, not the person
- Demonstrate compromise or resolution
- Maintain professionalism
Sample Response Structure:
SITUATION: "My team lead wanted to use a proprietary monitoring
solution, while I advocated for Prometheus/Grafana."
TASK: "I needed to express my technical concerns while respecting
their experience and maintaining our working relationship."
ACTION: "Instead of debating in meetings, I asked for a 1-on-1 to
understand their reasoning. They had valid concerns about support
and integration.
I proposed a proof-of-concept: we'd evaluate both solutions for
two weeks using the same criteria. I created an objective scoring
rubric covering cost, scalability, team expertise, and support.
I also acknowledged that my preference might be influenced by my
familiarity with open-source tools and committed to being objective."
RESULT: "The evaluation showed the open-source stack was 60% cheaper
with comparable features. My lead appreciated the data-driven approach
and agreed to my recommendation. More importantly, this established a
pattern for how we make technical decisions as a team. We now use
proof-of-concepts for all major technical choices."6. "How do you handle working with someone who isn't pulling their weight?"
7. "Describe a time you had to work with a difficult stakeholder."
8. "Tell me about a time you had to convince someone to change their mind."
9. "Describe the most challenging technical problem you've solved."
Good Answer Elements:
- Technical depth without jargon overload
- Systematic problem-solving approach
- Collaboration with others
- Learning from the experience
Sample Response Structure:
SITUATION: "Our Kubernetes cluster was experiencing random pod
evictions during peak hours, causing service disruptions. The
issue had persisted for three weeks and multiple engineers had
attempted fixes."
TASK: "As the senior DevOps engineer, I took ownership of finding
the root cause and implementing a permanent fix."
ACTION: "I started by gathering data: pod events, node metrics,
and application logs. I noticed evictions correlated with memory
pressure on specific nodes.
My investigation revealed:
1. Our resource requests were based on average usage, not peaks
2. One application had a memory leak that slowly consumed headroom
3. Node-level memory was hitting OOM killer thresholds
I implemented a multi-part solution:
1. Added memory limits based on P99 usage plus 20% buffer
2. Deployed Vertical Pod Autoscaler in recommendation mode
3. Created dashboards to track resource headroom per node
4. Set up alerts for approaching memory pressure
5. Worked with the app team to fix the memory leak"
RESULT: "Pod evictions dropped from 50+ per week to zero. Application
reliability improved from 99.5% to 99.95%. I documented the debugging
process as a runbook, which has since helped resolve similar issues
in other teams within hours instead of weeks."10. "Tell me about a time you made a mistake. What happened and what did you learn?"
Key Elements:
- Own the mistake completely
- Show self-awareness
- Focus on learning and prevention
- Don't blame others
Sample Response:
"Early in my career, I ran a database migration script on production
instead of staging. I had the terminal windows side by side and
executed in the wrong one.
The script corrupted about 5% of user records. I immediately notified
my manager, documented what happened, and worked with the DBA to
restore from backup. We recovered within 2 hours with minimal data loss.
What I learned was invaluable: I now use visual differentiation
(different terminal colors for prod), always verify with 'hostname'
before running commands, and advocate for infrastructure as code
where changes go through PR review.
I also implemented a policy on my team that production changes
require two-person verification. This mistake made me a much more
careful engineer and a better advocate for safety practices."11. "Describe a time when you had to make a decision with incomplete information."
12. "Tell me about a time you had to learn something new quickly."
13. "Tell me about a project that failed. What happened?"
Good Answer Elements:
- Honest about the failure
- Show accountability
- Focus on learning
- Describe how you've applied lessons
Sample Response:
SITUATION: "I led a migration from our monolith to microservices
that we had to abandon after six months of work."
TASK: "I was responsible for the technical architecture and
leading a team of four engineers through the migration."
ACTION: "In hindsight, I made several mistakes:
1. Underestimated the complexity of our data dependencies
2. Didn't get enough buy-in from the teams who'd maintain it
3. Tried to do too much at once instead of incremental migration
4. Didn't set clear success metrics upfront
When we realized we were stuck, I made the difficult decision to
recommend stopping the project. I prepared a presentation for
leadership explaining what went wrong, what we learned, and how
the investment wasn't entirely lost."
RESULT: "While the project 'failed,' we learned a lot. Six months
later, we started a more modest decomposition, extracting one
service at a time. We successfully migrated three critical services
using the lessons from the failed project.
I now always start with a clear 'definition of done,' get stakeholder
buy-in early, and prefer incremental approaches. That failure made
me a much better technical leader."14. "How do you handle high-pressure situations?"
15. "Describe a time when you received critical feedback."
16. "Tell me about a time you improved the experience for end users or developers."
17. "Describe a situation where you had to balance technical debt with new features."
18. "Tell me about a time you had to say no to a request."
19. "What's the most important thing you've learned in your career?"
20. "Tell me about a skill you developed in the last year."
21. "Describe how you stay current with technology."
Amazon asks behavioral questions aligned with their 16 Leadership Principles:
Customer Obsession:
Question: "Tell me about a time you went above and beyond for a customer."
Focus: Customer needs first, working backwards
Ownership:
Question: "Describe a time you took on something outside your area."
Focus: Act on behalf of the entire company, long-term thinking
Invent and Simplify:
Question: "Tell me about a time you found a simple solution to a complex problem."
Focus: Innovation, simplification, external awareness
Are Right, A Lot:
Question: "Describe a time you made a decision with ambiguous data."
Focus: Good judgment, seeking diverse perspectives
Learn and Be Curious:
Question: "Tell me about something you learned recently."
Focus: Continuous learning, exploring new possibilities
Hire and Develop the Best:
Question: "Tell me about a time you mentored someone."
Focus: Developing others, recognizing talent
Insist on the Highest Standards:
Question: "Describe a time you refused to compromise on quality."
Focus: High standards, continuously raising the bar
Think Big:
Question: "Tell me about a bold idea you proposed."
Focus: Creating and communicating bold direction
Bias for Action:
Question: "Describe a time you made a decision without complete information."
Focus: Speed matters, calculated risk-taking
Frugality:
Question: "Tell me about a time you accomplished more with less."
Focus: Resourcefulness, constraints breed innovation
Earn Trust:
Question: "Tell me about a time you built trust with a difficult stakeholder."
Focus: Listening, speaking candidly, treating others respectfully
Dive Deep:
Question: "Describe a time you had to get into the details to solve a problem."
Focus: Operating at all levels, staying connected to details
Have Backbone; Disagree and Commit:
Question: "Tell me about a time you disagreed with a decision."
Focus: Respectfully challenging, committing wholly once decided
Deliver Results:
Question: "Tell me about your most significant accomplishment."
Focus: Key inputs, delivering with quality and timelinessGeneral Cognitive Ability:
- Problem-solving approach
- Learning from experience
- Thinking on your feet
Leadership:
- Emergent leadership (stepping up when needed)
- Leading without authority
- Growing others
Googleyness:
- Intellectual humility
- Comfortable with ambiguity
- Collaborative mindset
- Taking action
Role-Related Knowledge:
- Technical depth
- Practical experience
- Applied skillsCore Values:
Move Fast:
"Tell me about a time you had to make a quick decision."
Be Bold:
"Describe a time you proposed a risky solution."
Focus on Impact:
"What's the most impactful project you've worked on?"
Be Open:
"Tell me about a time you gave or received difficult feedback."
Build Social Value:
"How have you improved developer or user experience?"Preparation:
1. Prepare 8-10 stories covering different situations
2. Practice telling each story in 2-3 minutes
3. Research the company's values and culture
4. Review your resume for talking points
5. Prepare questions to ask them
Story Bank:
Categories to cover:
- Technical challenge overcome
- Leadership/initiative example
- Conflict resolution
- Failure and learning
- Going above and beyond
- Working with difficult people
- Time management/prioritization
- Customer/user focusDo:
- Listen carefully to the question
- Ask clarifying questions if needed
- Use specific examples, not hypotheticals
- Quantify results when possible
- Show self-awareness
- Be concise (2-3 minutes per answer)
Don't:
- Use "we" when you mean "I"
- Badmouth previous employers
- Give generic or hypothetical answers
- Ramble or go off-topic
- Claim you've never failed
- Be defensive about weaknessesGood Closers:
- "Would you like me to go deeper on any part of that?"
- "That experience taught me [key lesson]."
- "Is there a specific aspect you'd like to hear more about?"
Self-Check:
- Did I answer the question asked?
- Did I use a specific example?
- Did I focus on MY actions?
- Did I include measurable results?
- Did I show what I learned?Question Types: Achievement, problem-solving, innovation
SITUATION:
"At [Company], we were facing [specific technical challenge]
that was causing [business impact]."
TASK:
"As the [role], I was responsible for [specific responsibility].
This was critical because [stakes]."
ACTION:
"I approached this by:
1. First, [analysis/research step]
2. Then, [planning/design step]
3. I implemented [specific technical solution]
4. I validated by [testing approach]
5. I collaborated with [teams/people] on [specific collaboration]"
RESULT:
"This resulted in [quantified improvement]. Additionally,
[secondary benefits]. I learned [key lesson] which I've
applied to [subsequent work]."Question Types: Disagreement, difficult coworker, stakeholder management
SITUATION:
"I was working with [person/team] on [project]. We had a
disagreement about [specific issue]."
TASK:
"I needed to [goal] while maintaining [relationship/timeline/quality].
This was important because [stakes]."
ACTION:
"Rather than [wrong approach], I:
1. Sought to understand their perspective by [specific action]
2. Found common ground around [shared goal]
3. Proposed [compromise/solution]
4. Followed up by [reinforcing action]"
RESULT:
"We reached [resolution]. The relationship [outcome].
I learned [insight about working with others]."Question Types: Failure, mistake, learning experience
SITUATION:
"When I was [role], I [specific mistake/failure that happened]."
TASK:
"I was responsible for [what you were trying to accomplish].
The impact was [consequences]."
ACTION:
"I immediately:
1. [Took responsibility]
2. [Addressed immediate impact]
3. [Communicated with stakeholders]
4. [Implemented fix/mitigation]
5. [Put preventive measures in place]"
RESULT:
"The immediate impact was [outcome]. More importantly,
I learned [key lesson]. Since then, I've [applied lesson],
which has [positive outcome]. I now [changed behavior]."- Understand STAR method thoroughly
- Prepare 8-10 diverse stories
- Practice each story out loud
- Research target company values
- Prepare specific Amazon LP stories (if applicable)
- Quantify results in each story
- Practice concise delivery (2-3 min)
- Prepare questions to ask interviewer
- Review and refine after mock interviews
- Build confidence through repetition
Remember: Behavioral interviews test WHO you are, not just WHAT you know. Be authentic, specific, and show growth. The best answers demonstrate self-awareness, ownership, and learning.
Key Principles:
- Use specific examples, never hypotheticals
- Focus on YOUR actions and impact
- Own your mistakes and show learning
- Quantify results whenever possible
- Practice makes perfect