Tell me about a time developers pushed back on a tool or process your team introduced. How did you handle it, and what changed?

What the interviewer is looking for

• This question tests collaboration with developers. Gives examples of listening to developer pain, explaining changes, and adjusting tools based on feedback rather than mandating them.
• What to bring out: Listened to concerns, separated real problems from resistance to change, adjusted the approach, and communicated the reasons clearly.
• Expect a follow-up like: Looking back, what would you do differently from the start?

Another way it may be asked: Think of a time you rolled out something new and developers did not like it. What did you do next?

A structure to follow: STAR, with the weight on Action and Result

1. Step 1

   Situation

   One or two sentences: where, when and what was at stake. Pick a real example you were close to.

2. Step 2

   Task

   What you personally were responsible for. Say "I", not only "we", so the collaboration with developers you showed is visible.

3. Step 3

   Action

   The two or three things you did and why you chose them over the alternatives. This should be about half your answer.

4. Step 4

   Result

   What changed, in your own measure of it, and what you would do differently. Only use numbers you can stand behind.

This is guidance on shape, not a script. Use your own real experience and facts; never invent details to fill a gap. See the STAR guide and answer frameworks.

Common slips

• Describing what the team did without saying what you did.
• Choosing an example with no clear outcome, or one you cannot answer detailed questions about.
• Ending on the action and skipping the result and what you learned.

How to practise it

Write two bullet points for each STAR letter, then say the answer aloud in about two minutes.

Related questions

• Walk me through what happens, step by step, between a developer pushing code and that code running in production, on a pipeline you would set up.
• Why would a team define its infrastructure in code instead of clicking through a cloud console, and what problems does that solve?
• In plain terms, what is a container, and how is it different from running an app directly on a virtual machine?
• A pod in Kubernetes keeps restarting in a crash loop right after a deploy. How do you work out what is wrong?
• Tell me about a time you set up monitoring or alerting that caught a problem before users noticed. What did you measure?

Browse all questions