How Do You Drive a Change When You're Not the Lead?

This is a seniority signal. Junior engineers wait to be told what to do. Senior engineers spot a problem and get the team to fix it, even with no authority to order anyone around. The interviewer wants proof you can do the second thing.

What they're really asking

Can you build a case and bring people along, instead of just complaining in standup? Do you understand that influence comes from trust, data, and good timing rather than from a title? They want to know you can change how a team works without being the one in charge of it.

How to structure your answer

Use STAR but treat the Action as a sequence of moves. Situation: the problem you saw. Task: why it mattered and why it fell to you even though it wasn't your call. Action: how you built support, who you talked to first, what evidence you gathered, how you made it easy to say yes. Result: what actually changed and how it stuck. The strongest answers show you started small and let a quick win do the persuading.

A sample answer

Our team kept shipping bugs that better tests would have caught, but we had almost no frontend test coverage and nobody owned changing that. I wasn't the lead, so I couldn't mandate it. I started by measuring: I pulled three months of bug tickets and tagged which ones a unit or integration test would have prevented. It was a little over half.

I didn't open with a big proposal. I picked the flakiest part of the app, our form validation, and wrote tests for it on a quiet Friday. The next time someone touched that code, the tests caught a regression before review. I mentioned it casually in standup and let that land.

Then I brought the bug data to our retro and proposed one rule: any bug fix ships with a test that reproduces it. Small, no big upfront cost. People agreed because they'd seen it work. Over the next quarter, coverage on our core flows went from near zero to about 60%, and escaped bugs in those areas dropped noticeably. I never had the authority to require any of it. The numbers and the early win did the convincing.

What to avoid

• Describing influence as nagging or going over people's heads to a manager.
• Having no concrete result, just "I convinced everyone it was a good idea."
• Trying to boil the ocean. A giant proposal with no quick win rarely lands.
• Taking sole credit when it was a team effort. Acknowledge who you brought along.