Handle conflict and missed delivery deadlines

### How to structure answers (use STAR + reflection) Use **STAR** (Situation, Task, Action, Result) plus a final **Reflection** section. - Keep **Situation/Task** to ~20–30%. - Spend most time on **Action**: decisions, trade-offs, communication. - End with **Result** (measurable if possible) and **Reflection** (what you’d do differently). --- ## 1) Conflict: what interviewers look for They want evidence you can: - disagree without being toxic, - separate people from problems, - use data and shared goals, - escalate appropriately, - preserve trust. ### Strong outline **Situation:** Cross-team disagreement (API contract, performance target, oncall ownership, roadmap priority). **Actions (good signals):** 1. **Diagnosed the conflict type** - Misaligned goals? ambiguous ownership? lack of data? communication style? 2. **Aligned on the shared objective** - “We both want X (reliability, latency, launch date). Let’s define success metrics.” 3. **Brought data / proposed experiments** - Benchmark, load test, prototype, or small A/B. 4. **Presented options + trade-offs** - “Option A hits deadline but increases ops risk; Option B delays 1 week but reduces incidents.” 5. **Closed the loop** - Documented decision (RFC/ADR), owners, next steps. **Result:** Decision made, relationship intact (or improved), project moved forward. **Pitfalls to avoid:** - Blaming language (“they were wrong”), - pretending there was no conflict, - escalating too early or never escalating. --- ## 2) Hard relationship: how to show maturity Hard relationships are often about **trust** and **predictability**. ### Strong outline - **Situation:** Partner team repeatedly misses requirements; teammate dismisses feedback; PM changes scope frequently. - **Actions:** 1. **1:1 conversation** to understand constraints/incentives. 2. **Make expectations explicit** (definition of done, response time, review SLA). 3. **Change the collaboration mechanism** - weekly sync, shared doc, ticket templates, decision log. 4. **Give specific feedback** (behavior → impact → request). 5. **Find quick wins** to rebuild trust. - **Result:** fewer escalations, smoother delivery, better morale. **Good reflection:** what you learned about communication styles, incentives, and setting boundaries. --- ## 3) Missed deadline: what “good” looks like Missing a deadline can be acceptable if you show: - early risk detection, - proactive communication, - mitigation and scope control, - learning and process improvement. ### Strong outline **Situation/Task:** A feature with external dependency, unclear requirements, or underestimated complexity. **Actions (must-hit points):** 1. **Detected risk early** - call out when you first knew the date was at risk (don’t wait until the deadline). 2. **Communicated with options, not just problems** - “We can ship MVP by date with X removed,” - “or keep scope and move date by 2 weeks,” - “or add 1 engineer and accept integration risk.” 3. **Controlled scope** - explicitly cut non-critical work (nice-to-haves), freeze requirements. 4. **Protected quality** - avoid shipping something unsafe; add feature flags, staged rollout. 5. **Post-mortem + prevention** - better estimation (spikes), earlier integration tests, dependency contracts, milestone checkpoints. **Results:** even if date slipped, highlight positive outcomes: - reduced incident rate, - successful phased launch, - improved delivery process. --- ### Common follow-up questions (prepare concise answers) - What did you personally own? - What would you do differently next time? - How did you handle disagreement after escalation? - How did you quantify impact (latency, cost, revenue, customer experience)? ### A reusable sentence template - “Given X constraint, I proposed A/B options with trade-offs, aligned stakeholders on success metrics, executed a risk-mitigated plan (flags/rollout), and documented the decision and learnings.”