Tell me about a time you convinced a resistant team to adopt something new.
What they are really testing: Influence without authority, which is most of a platform role. They want to hear that you took the resistance seriously rather than treating it as ignorance to be overcome.
A real interview question
Tell me about a time you convinced a resistant team to adopt something new.
What most people say
drag me
“I demonstrated the benefits in a presentation and management made it a requirement.”
That is a mandate, not persuasion. Teams comply minimally with mandates and keep their old approach alongside, so the outcome is usually two systems and quiet resentment rather than adoption.
The follow-ups they ask next
What if you had found their objection was simply correct?
Then say so and change or abandon the plan. Being seen to drop a proposal on good evidence buys enormous credibility for the next one.
How do you scale that to 15 teams without doing every migration yourself?
Do the first few personally, then use those teams as references and let their engineers help peers. Documentation plus a working example from a respected team beats a mandate.
What the interviewer is listening for
- Investigates the real reason for resistance
- Makes trying cheap and reversible
- Changed their own design based on feedback
What sinks the answer
- Escalates to a mandate
- Treats resistance as ignorance
- Story where they were entirely right
If you genuinely do not know
Say this instead of freezing. Reasoning out loud from what you do know beats silence every single time, and a good interviewer is listening for exactly that.
“They resisted [X]. I asked why, and the real reason was [a past cost, often a trust problem]. So I [made the first step small and owned the risk myself], proved it on [their own service, not a toy example], and [changed my design based on their feedback]. Then [their success recruited the next teams].”
Keep going with behavioural
Mid
Tell me about a time you broke production. What happened and what did you do?
Mid
Tell me about a time you disagreed with a developer about how something should be deployed.
Mid
Tell me about a time you were on call and it went badly.
Mid
Tell me about a mistake that cost the company money.
Mid
Walk me through a time you inherited a system nobody understood. Where did you start?
Mid
Tell me about something repetitive you automated. How did you decide it was worth it?
Knowing the answer is not the same as recalling it under pressure
Sign in to send the questions you fumble to spaced recall, so they come back right before you would forget them, and learn the concepts behind them with hands-on labs.
Start free