Tell me about leading through conflict
Company: Snapchat
Role: Technical Program Manager
Category: Behavioral & Leadership
Difficulty: medium
Interview Round: Onsite
For an onsite TPM interview, prepare to **present a project you led end-to-end** and answer behavioral follow-ups such as: **Tell me about a time you worked with a difficult stakeholder**, and **share a counterintuitive lesson you learned**. Your answer should demonstrate leadership, communication, ownership, and reflection.
Quick Answer: This question evaluates leadership, stakeholder management, communication, ownership, and reflective learning in the context of technical program management and is categorized under Behavioral & Leadership.
Solution
**Model STAR answer**
**Situation / Task:** In my last role, I led a cross-functional effort to migrate our ML training pipeline to a shared platform. The goal was to reduce model launch time and improve reliability for multiple teams. One senior data scientist strongly resisted the migration because he believed the shared platform would slow experimentation and reduce his team’s autonomy. My job was to align engineering, data science, and infra teams and still hit a hard launch deadline.
**Action:** I started by separating the person from the problem. Instead of escalating immediately, I ran a working session to understand his specific concerns: experiment speed, feature flexibility, and rollback risk. I translated those concerns into measurable requirements and updated the project plan. We launched a pilot with one model, added a fast-path for experimentation, and created a decision document with clear owners, success metrics, and a rollback plan. For the onsite-style presentation, I framed the project as: business context, why it mattered, key decisions, tradeoffs, results, and what I would do differently.
**Result:** The pilot succeeded, and we expanded the platform to three teams. Training time dropped by 35%, deployment incidents fell by 40%, and we saved roughly $800K annually through better resource utilization. Just as importantly, the previously skeptical stakeholder became one of the project’s strongest advocates because his concerns were reflected in the final design.
**Counterintuitive lesson:** The biggest lesson was that slowing down early can speed up delivery overall. My initial instinct was to push harder for alignment after executive approval, but I learned that investing time upfront in shared definitions, success metrics, and stakeholder trust prevents rework and resistance later. Interviewers want to hear that you can lead through ambiguity without becoming defensive or overly political.
**What interviewers look for / pitfalls:** They look for ownership, influence without authority, conflict resolution, and self-awareness. Avoid vague stories, blaming difficult partners, or presenting yourself as the lone hero. The best answers are specific, measurable, and reflective.