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 — making the case with data and a clear plan, building buy-in, and driving it to a measurable outcome — without being anyone’s manager.
Deep explanation
This tests emergent leadership and the ability to drive across boundaries.
- Situation/Task: A cross-team problem that lacked a clear owner.
- Action: How you created a shared artifact (doc/one-pager), recruited collaborators, used evidence to persuade, and kept teams aligned with lightweight mechanisms (check-ins, a dashboard).
- Result: Quantified impact and what made the alignment durable.
The signal: you move organizations through persuasion and mechanisms, not mandate.
Real-world example
Situation: Three teams duplicated logging code with no owner. Task: drive consolidation as an IC. Action: I prototyped a shared logger, documented the maintenance cost of the status quo, recruited one engineer per team to co-own it, and tracked adoption on a dashboard. Result: logging bugs dropped ~50% and the library became the org standard — adopted on merit and buy-in.
Common mistakes
- - Describing positional authority instead of influence
- - Taking sole credit for a team outcome
- - No mechanism for keeping teams aligned
- - No measurable result
Follow-up questions
- How did you handle a team that wouldn’t engage?
- What mechanism kept everyone aligned?
- What was the hardest stakeholder to win over?