Driving Change Across Teams

Topics Covered

What Change Questions Test

Why change questions exist

What the rubric looks for

What interviewers are worried about

Adoption is the outcome

Change is mostly about people

Variants of the question

How change scales with level

Change needs a reason people share

Change takes time

Change needs a sponsor

Change needs a clear finish line

What a strong answer sounds like

Respect the teams you describe

Change stories and your role

Preparing the details

Pick changes that stuck

Change has a cost

Small changes count too

Tell me about a time you drove a change across several teams. Describe a time you introduced a new process or tool. Tell me about a time you changed how your organisation works. Questions about cross team change appear mostly in senior and staff loops, where the job includes improving how many teams work, not just one. This lesson explains what interviewers look for, how to choose and structure a change story, how to build support and adoption, how to handle resistance and how to answer the hardest variants.

Why change questions exist

At senior levels, many of the biggest improvements cross team boundaries: a shared deployment pipeline, a new incident process, a migration to a common platform, a change in how teams plan. None of these can be done by one team alone. Interviewers ask about cross team change to see whether the candidate can make improvements stick across groups they do not control, which is one of the hardest and most valuable skills in engineering.

What the rubric looks for

Change rubrics usually score several behaviors. Did the candidate identify a real problem worth changing? Did they build a case with evidence? Did they involve the affected teams early? Did they design the change so it was easy to adopt? Did they handle resistance constructively? Did they measure adoption and impact? And did the change last after they stepped back? Each is something the interviewer will try to record.

What interviewers are worried about

Interviewers also screen for risks. They worry about candidates who push changes without consulting the people affected, who mistake an announcement for adoption, who declare victory before the change is used, who blame other teams for resisting, or who leave behind a half adopted change that makes things worse. They also worry about change for its own sake, where the candidate wanted a new tool rather than a better outcome.

Adoption is the outcome

The outcome of a change story is adoption and impact, not the launch. Many candidates describe building a new tool or writing a new process and stop there. Strong stories describe how many teams adopted it, how long it took and what improved as a result: eleven of twelve teams moved to the new pipeline within two quarters, and median deploy time fell from forty minutes to eight. Adoption is what the interviewer is scoring.

Change is mostly about people

Cross team change is mostly a people problem. The technical part, building the tool or writing the process, is often the easy part. The hard part is persuading busy teams with their own priorities to change how they work. Strong stories spend most of their time on how the candidate built support, handled concerns and made adoption easy, not on the technical design.

Variants of the question

Change questions take many forms: a time you drove change across teams, a time you introduced a new tool or process, a time you changed a culture or habit, a time you led a migration, a time a change you proposed failed, a time you changed something without authority, how you get teams to adopt standards. Two or three well prepared stories cover most of these.

How change scales with level

Junior engineers improve how their own team works, such as adding a lint rule. Mid-level engineers drive change within a team or with one neighbour, such as a shared testing approach. Senior engineers drive change across several teams, such as a migration or a new on call process. Staff engineers change how a whole organisation works, such as engineering standards, platform strategy or planning practices. Choose stories at the scope you are targeting.

Change needs a reason people share

Teams change when they share the reason, not when they are told to. The strongest change stories start from a problem the affected teams already feel: slow deploys, painful incidents, wasted on call hours. If the teams do not feel the problem, the first job is to make it visible. Stories that start with a solution looking for a problem rarely score well.

Interviewers scored adoption and impact over launch, and most of the effort in successful changes went to people rather than tooling.

Change takes time

Cross team change usually takes months, sometimes years. Interviewers know this, and they are suspicious of stories where twelve teams changed in two weeks. Describe a realistic timeline, with phases: a month of listening and evidence, a quarter of pilots, two quarters of rollout. Realistic timelines make the story believable and show patience and persistence.

Change needs a sponsor

Large changes usually need a sponsor: a director, a principal engineer or an influential team lead who backs the change and helps remove obstacles. Strong stories show how the candidate found and worked with a sponsor without hiding behind them. I showed our director the incident data, and she agreed to make the new process a goal for the quarter, which helped teams prioritise it.

Change needs a clear finish line

A change without a finish line drifts. Strong stories define what done means: every team deploying through the new pipeline, the old system turned off, the process followed in every incident for a quarter. A clear finish line helps teams plan, lets you measure progress and gives you a moment to declare success. Stories that end with mostly adopted suggest the change was never finished.

What a strong answer sounds like

A strong change answer is concrete and people focused. The candidate names the problem and the evidence, explains how they involved the affected teams, describes the change and how it was made easy to adopt, explains how they handled resistance, gives adoption and impact numbers and reflects on what they learned. It avoids heroic narratives, blame of other teams and confusing a launch with adoption.

Respect the teams you describe

Describe other teams with respect. They resisted because they had their own priorities, not because they were stubborn. Prefer language such as the payments team was in the middle of a launch and could not take on a migration that quarter. Interviewers notice how candidates talk about other teams, and respectful language signals that you can work across an organisation.

Change stories and your role

Cross team changes involve many people, so be clear about your role. I proposed the change, wrote the case, ran the pilots and coordinated the rollout, while each team did its own migration with help from our platform team. Clear attribution lets the interviewer score your contribution and avoids the impression that you are claiming credit for work done by others.

Preparing the details

Change stories depend on specifics: the problem and its evidence, the teams involved, the sponsor, the phases and timeline, the resistance and how it was handled, the adoption numbers and the impact. Write these down before the interview. Many candidates remember the launch but not the adoption curve, which is exactly what interviewers probe.

Pick changes that stuck

Choose changes that lasted. A change that was adopted and then quietly abandoned a year later is a weaker story, unless the question is about failure. If you can say the process is still in use two years later, or that new teams adopt it by default, that is strong evidence that the change was well designed and well embedded.

Change has a cost

Every change costs the teams that adopt it: time to migrate, time to learn, risk during the transition. Strong candidates acknowledge this cost and show that the benefit was worth it. The migration cost each team about a week, and saved each team about three hours a week afterwards, so it paid back within two months. Showing that you weighed the cost makes your case far more credible.

Small changes count too

Not every change story has to be a large migration. A smaller change that spread across teams, such as a shared incident template or a common alerting rule, can be a strong story if you show the same skills: a shared problem, evidence, involvement, easy adoption and lasting impact. Small changes are also easier to describe in two minutes, which can make them better interview stories.

Adoption, not announcement

Change questions test whether you find a problem teams share, build a case with evidence, involve the affected teams early, make adoption easy, handle resistance constructively, measure adoption and impact and make the change last. Interviewers are wary of announcements mistaken for adoption, blame of other teams and change for its own sake.