Behavioral & Negotiation
STAR Method for Engineers
Behavioral interviews are where strong candidates lose offers. Technical skills get you to the final round; behavioral skills get you the offer. The STAR method is your framework for answering every behavioral question.
The STAR Framework
| Component | What It Covers | Time |
|---|---|---|
| Situation | Set the context: project, team, timeline | 15% |
| Task | Your specific responsibility | 10% |
| Action | What YOU did (not the team) | 50% |
| Result | Measurable outcome | 25% |
Example: "Tell me about a time you dealt with a tight deadline."
Situation: "Our team was building a payment processing feature for our e-commerce platform. Three weeks before launch, we discovered the third-party payment API had changed its authentication flow, breaking our integration."
Task: "As the backend lead, I was responsible for fixing the integration and ensuring we still met the launch date."
Action: "I immediately did three things. First, I assessed the scope -- the new auth flow required changes to our token management and webhook handlers. Second, I broke the work into parallel tracks: I took the auth refactor while two teammates handled the webhook updates. Third, I set up daily 15-minute standups specifically for this integration to catch blockers early."
Result: "We completed the integration two days before launch. The payment system processed $2.3M in transactions in the first month with zero auth-related failures. The approach of parallel work tracks became our standard process for critical integrations."
Building Your Story Bank
Prepare 6-8 stories that cover these categories:
| Category | What They're Testing | Example Prompt |
|---|---|---|
| Leadership | Taking initiative, guiding others | "Tell me about a time you led a project" |
| Conflict | Handling disagreement professionally | "Describe a conflict with a coworker" |
| Failure | Self-awareness, learning from mistakes | "Tell me about a time you failed" |
| Ambiguity | Decision-making with incomplete info | "How did you handle an unclear requirement?" |
| Tight Deadline | Prioritization, time management | "Describe a time you had to deliver fast" |
| Cross-team | Communication, influence | "How did you work with another team?" |
| Technical Decision | Engineering judgment | "Describe a difficult technical decision" |
| Impact | Delivering business value | "What's your biggest technical achievement?" |
Pro Tip: Each story can be adapted for multiple categories. A story about a failed project launch can answer questions about failure, tight deadlines, AND conflict.
Company-Specific Behavioral Prep
Amazon (Leadership Principles)
Amazon asks behavioral questions mapped to their 16 Leadership Principles. The most common in SWE interviews:
- Customer Obsession: Start with the customer and work backwards
- Ownership: Think long-term, act on behalf of the company
- Dive Deep: Stay connected to details
- Bias for Action: Speed matters, take calculated risks
- Deliver Results: Focus on key inputs, deliver with quality
Google (Googleyness)
Google evaluates:
- Cognitive ability: Structured thinking
- Role-related knowledge: Technical depth
- Leadership: Effective without authority
- Googleyness: Collaborative, comfortable with ambiguity
Meta (Core Values)
Meta focuses on:
- Move fast: Ship quickly, iterate
- Be bold: Take risks, learn from failure
- Focus on impact: Prioritize high-impact work
- Build social value: Consider broader implications
Common Mistakes
| Mistake | Fix |
|---|---|
| Saying "we" instead of "I" | Focus on YOUR specific contributions |
| Being too vague | Use specific numbers and outcomes |
| Stories that are too long | Keep to 2-3 minutes max |
| Not having enough stories | Prepare 6-8, practice each 3+ times |
| Negative tone about past employers | Frame challenges constructively |
Next, let's cover the most common behavioral questions and how to handle each category. :::