# Behavioral: Proudest Project, Conflict, and Failure This is a standard behavioral round covering three classic prompts in one sitting. The interviewer wants concrete, first-person stories — your specific actions and decisions, the trade-offs you made, and what you learned — not a team narrative or a high-level summary. Answer each part as its own focused story. ### Constraints & Assumptions - Each story should be a real experience you can speak to in depth and defend under follow-up questioning. - Use "I" (your contribution), not "we," when describing actions and decisions. - Keep each story to roughly 2–4 minutes spoken; lead with context, then your actions, then the outcome with concrete results. - Have specifics ready: numbers, timelines, the technical/decision details, and the names of the trade-offs you weighed. ### Clarifying Questions to Ask - How much technical depth do you want — a high-level narrative, or should I go deep on the engineering decisions? - Would you prefer the most recent example or the most impactful one? - Are you most interested in my individual contribution, or how I worked across the team? ### Part 1 — A project you are most proud of Tell me about the project you are most proud of. Explain what it was, why it mattered, what your specific role and contributions were, the hardest problem you personally solved, and the measurable impact. ```hint Structure Use STAR: Situation (context + why it mattered), Task (your specific goal/ownership), Action (the decisions *you* made and trade-offs you weighed), Result (quantified outcome). ``` ```hint Pick for signal, not flash Choose a story where you drove the outcome and faced a real hard decision — pride should come from *your* judgment and impact, not just that the project was large or used trendy tech. ``` #### What This Part Should Cover ```premium-lock What This Part Should Cover ``` ### Part 2 — A conflict Describe a time you had a significant disagreement or conflict with a coworker, manager, or another team. What was the disagreement, how did you handle it, and what was the outcome? ```hint Focus on resolution, not blame The signal is *how* you navigated it: did you seek to understand the other side, use data/user impact to find common ground, disagree-and-commit, and preserve the relationship? ``` #### Clarifying Questions for this Part - Would you like a peer-level technical disagreement, or a conflict across teams / with a manager? #### What This Part Should Cover ```premium-lock What This Part Should Cover ``` ### Part 3 — A failure Tell me about a time you failed — a project, decision, or initiative that did not go as intended. What happened, what was your role in the failure, and what did you do about it? ```hint Own it, then show growth Take genuine personal accountability (not "the requirements were bad"), describe how you mitigated the damage, and end with the concrete change you made so it didn't recur. ``` #### What This Part Should Cover ```premium-lock What This Part Should Cover ``` ### What a Strong Answer Covers ```premium-lock What a Strong Answer Covers ``` ### Follow-up Questions - For the project you're proudest of: if you could redo it, what one decision would you change, and why? - In the conflict, what would you do differently if you faced the same disagreement today — and what if the other person still didn't agree after your best effort? - For the failure: how specifically did the lesson show up in a *later* situation — give a concrete example where you applied it. - Across these stories, what does the pattern say about the kind of work and environment where you do your best?