Tell me about a time you led a cross-functional project without formal authority

Updated May 18, 2026

Short answer

Use STAR and lead with influence, not authority. Pick a project where you aligned several teams toward a shared goal, made the case with data and a clear plan, and drove it to a measurable outcome — emphasizing how you built buy-in rather than issued orders.

Deep explanation

Google evaluates Leadership and Googleyness here — specifically emergent leadership: stepping up without being told to.

Situation/Task: Frame a cross-team problem that lacked a clear owner.
Action: Show how you created a shared artifact (a one-pager or doc), recruited collaborators, and used evidence to persuade. Highlight how you navigated competing priorities.
Result: Quantify impact and note what made the alignment durable.

Avoid "I told people what to do." Influence-without-authority is the entire point.

Real-world example

Three teams duplicated logging code with no shared owner. As an IC, I prototyped a shared logger, documented the maintenance cost of the status quo, and recruited one engineer from each team to co-own it. The result: logging bugs dropped ~50% and the library became the org standard — adopted purely on merit and buy-in.

Common mistakes

- Claiming credit for a team outcome without showing *your* specific contribution
- Describing positional authority ("as the manager...") when the question is about *not* having it
- No measurable result
- Skipping how you handled disagreement or competing priorities

Follow-up questions

How did you handle a stakeholder who disagreed with the direction?
What would you do differently if you ran it again?
How did you keep momentum once the project lost novelty?