Leadership & Influence

Intermediate · 14 min read · Question Bank by Theme, Working With People

Leading without authority: aligning people, driving a decision, raising the bar.

"Leadership" in an engineering interview rarely means managing people. It means making things happen through others when you don't have authority: aligning a team on a design, getting another team to change their API, raising the quality bar, stepping up when something is drifting.

The question in its many forms

What they're scoring

Influence techniques worth naming in your story

Weak vs strong

Weak: "I noticed our deployments were slow, so I told everyone we should move to a new CI system. People were resistant at first, but eventually they agreed and we migrated. Deployment time went down."

Scaling the story to your level

See Signals by Level.

At senior and staff level

At these levels, leadership stories are about setting direction for several teams, changing how the organisation works, and growing other leaders. Expect to explain how you chose what to lead, not only how you led it.

Follow-ups to expect

Key takeaways

Engineering leadership usually means influence without authority, which Google calls emergent leadership.
Show initiative, a clear why, influence through data and examples, execution and credit given to others.
Name your techniques: a shared goal, a prototype, a written doc, an early ally, a lower cost of saying yes.
Match the scope to your level.

Previous: Conflict & Disagreement · Next: Collaboration & Mentoring