Tell me about a time you drove change beyond your own team.

Question

Accepted Answer

At senior level, impact crosses team boundaries. This tests whether you can **drive organizational change** through influence, coalition-building, and persistence — not authority.

## How to approach it

```text
1. Frame the problem in terms leadership cares about (cost, risk, velocity)
2. Build a coalition of allied teams and sponsors
3. Start with a pilot that proves value
4. Make adoption easy — tooling, docs, support
5. Measure and broadcast the wins
```

## Worked example

```text
S: Each team built its own auth differently — inconsistent and a security risk.
T: I wanted a shared, secure auth standard across six teams, with no authority
   over any of them.
A: I quantified the duplicated effort and risk, got a staff sponsor, piloted a
   shared library with one willing team, then ran office hours and migration
   guides for the rest.
R: Five of six teams adopted it within two quarters; a class of auth bugs
   disappeared from incident reports.
```

## Good vs weak

```text
✓ Coalition + pilot + easy adoption + metrics
✗ Mandating change by decree
✗ A great idea that never left a doc
```

## Why it matters

Org-wide change rarely succeeds by mandate; it spreads through proof, allies, and momentum.

A pilot de-risks the change and gives skeptics evidence instead of promises.

This kind of cross-team impact is the core differentiator for senior and staff roles.