Describe a situation where you led a quality initiative that changed how a team worked.

Senior interviewers want to see organisational influence, not just technical execution. The mark of a strong initiative story is the change persisting after you stopped pushing.

STAR walkthrough — sample answer:

Situation: A previous team I was on (about 25 engineers across three squads) had no shared definition of "ready for QA" or "ready for release." Each squad had drifted into different conventions — one had rigorous staging checks, another shipped on green CI alone, the third had something in between. The result was inconsistent quality and noticeable variance in incident rates between squads.

Task: I was the senior QA across the three squads. The eng manager had asked for "more consistency" but no one had been formally tasked with it. I decided to take it on.

Action: Three phases over about two months.

Phase 1 — listen and synthesise. I spent two weeks shadowing each squad's release process, capturing what each was doing and what they thought was working. Wrote it up as a "current state" document, not as criticism but as a fair description. Shared it with the three squad leads first, who corrected anything I'd misread. That shared baseline was already a useful artefact.

Phase 2 — propose a minimum bar, not the maximum. The instinct was to take the most rigorous squad's process and impose it everywhere. I deliberately didn't. Instead, I pulled together a "definition of release-ready" with five concrete criteria — small enough that even the lightest-process squad could adopt it without disruption. I framed it as a floor that everyone met, with each squad keeping its own additions on top.

Phase 3 — adoption, not enforcement. I took the proposal to each squad's planning meeting. Asked for their perspective, made adjustments based on real concerns ("our service is read-only, criterion 4 doesn't apply" — fine, document the carve-out). Got each lead's verbal commitment in front of their team. Documented it in the eng wiki and added a one-line check to each squad's release template.

Result: Over the next quarter, incident rates converged across squads — the lightest-process squad's incident rate dropped about 40%; the most rigorous squad's didn't change (already meeting the bar). Six months later when I'd moved on to other initiatives, the bar was still active and a new squad lead used it as the basis for their onboarding.

What I learned: durable change doesn't come from authority — it comes from an agreement people made themselves. The process of getting their input was as important as the resulting bar.

Why this works: shows organisational scope (three squads), coalition-building rather than top-down imposition, measured impact, and durability past your direct attention. Strong senior signal.