Leading Without Authority

Topics Covered

What Influence Questions Test

Why influence matters for engineers

What the rubric looks for

What interviewers are worried about

Influence is not manipulation

Sources of influence

Variants of the question

How influence scales with level

Compliance versus commitment

What a strong answer sounds like

Influence in other stories

Influence and seniority

Preparing the details

Choosing which story to lead with

Influence without a project title

Influence measured by what others did

Be clear about your formal position

Influence stories and humility

Tell me about a time you led a project without being the manager of anyone involved. Describe a time you had to convince people who did not report to you. How did you get another team to change their plans? Leading without authority is central to senior and staff engineering, where most important work depends on people you cannot direct. This lesson explains what interviewers look for, how to build the credibility that makes influence possible, how to persuade and align people, how to lead a cross team effort day to day and how to handle the hardest variants.

Why influence matters for engineers

As engineers grow, the work that matters most spans more people than any one manager controls. A migration touches ten teams, a reliability goal depends on services owned by others and a new standard only works if everyone adopts it. None of those people report to the engineer driving the work. The ability to get things done through influence rather than authority is therefore one of the clearest signals of senior and staff level.

What the rubric looks for

Influence rubrics usually score several behaviors. Did the candidate build a shared understanding of the problem? Did they adapt their case to what each stakeholder cared about? Did they listen to objections and change the plan where appropriate? Did they create clear structure, such as owners, milestones and a decision process? Did they keep momentum without authority? And did the effort reach a real outcome? Interviewers try to record evidence for each.

What interviewers are worried about

Interviewers also screen for risks. They worry about candidates who rely on escalation instead of persuasion, who push their own solution without listening, who confuse being loud with being influential, or who give up when people say no. At senior levels, they also worry about candidates who achieve compliance but not commitment, where teams agree in a meeting and then quietly do nothing.

Influence is not manipulation

Influence in a healthy organisation means helping people see a problem clearly and choose a good solution together. It does not mean manipulation, pressure or politics. Interviewers want stories where people were persuaded by evidence and shared goals, and where the candidate was open to being persuaded in return. Stories that sound like outmanoeuvring colleagues raise concerns about trust.

Sources of influence

Engineers without authority draw influence from several sources: expertise, a track record of delivering, relationships built over time, clear data, a well framed shared goal and the willingness to do the unglamorous work themselves. Strong stories show the candidate using several of these, rather than relying on seniority or a manager endorsement alone.

Variants of the question

Influence questions take many forms: leading a project without being the manager, getting buy in for an idea, convincing a skeptical team, driving adoption of a tool or standard, aligning teams with conflicting goals, influencing a decision above your level. Some overlap with conflict and change questions. Two or three strong stories cover most of them, with different emphasis for each.

How influence scales with level

Junior engineers influence their own team, for example by proposing a better testing approach. Mid-level engineers influence adjacent teams, such as agreeing an interface with a partner team. Senior engineers lead cross team projects and influence their organisation technical direction. Staff engineers influence across organisations, shaping strategy and standards that many teams adopt. Match your story to the level you are targeting.

Interviewers scored shared understanding, tailored persuasion, listening and structure, and watched for escalation and compliance without commitment.

Compliance versus commitment

A crucial distinction is between compliance, where people agree because they feel they must, and commitment, where they agree because they believe in the goal. Compliance often fades as soon as attention moves elsewhere. Commitment survives setbacks. Strong stories show how the candidate earned commitment, for example by involving teams in shaping the plan, and how that commitment showed when things got hard.

What a strong answer sounds like

A strong influence answer names the goal, the people whose help was needed and why they did not have to help. It shows how the candidate built a shared view of the problem, tailored the case to each group, listened to objections and changed the plan, set up structure and kept momentum. It ends with a measurable outcome and a note about the relationships afterwards, such as the teams choosing to work together again.

Influence evidence appears across the loop. Conflict stories show influence when the candidate persuaded someone. Ownership stories show it when the candidate rallied others to fix an unowned problem. Prioritization stories show it when the candidate got stakeholders to accept a trade off. Interviewers often record influence signals across several answers, so tell every multi team story with a clear account of how you got people on board.

Influence and seniority

Some candidates have influenced people more senior than themselves, such as convincing a director to change a plan. These stories can be powerful, but they need care. Show that you respected the decision maker, brought evidence and accepted the decision if it went the other way. Avoid framing the story as you proving a senior person wrong, which can sound arrogant.

Preparing the details

Influence stories depend on specifics: who the stakeholders were, what each cared about, what objections they raised, what you changed in response, how decisions were made and what the outcome was. Write these down before the interview. Many candidates remember the result but forget the objections, which are often the most interesting part to interviewers, because they show how the candidate listened.

Choosing which story to lead with

If you have several influence stories, lead with the one where the people involved had the least reason to help you and the outcome mattered most. A story about persuading a skeptical team with their own priorities is more convincing than one about rallying willing colleagues. Keep the easier stories for follow ups or for questions about collaboration.

Influence without a project title

Some candidates assume influence stories require a formal role such as project lead. They do not. Many of the best stories involve an engineer with no title at all who noticed a cross team problem and organised people around it. If you were the de facto lead without the title, say so plainly: nobody had been asked to lead this, so I offered to coordinate. Interviewers often find these stories more convincing than ones where the role was assigned.

Influence measured by what others did

The evidence of influence is what other people did differently because of you. A story full of your own actions but with no change in anyone else behavior is an execution story. Make the change in others explicit: four teams changed their roadmaps, two adopted the library and one started running the same review. Counting what others did is the simplest way to show the interviewer your influence was real.

Be clear about your formal position

Interviewers need to know what authority you did or did not have. State it early: I was a senior engineer on the payments team, and none of the four teams reported to me or my manager. This one sentence frames the whole story. Without it, the interviewer may assume you had more authority than you did and give you less credit for the influence you used.

Influence stories and humility

Influence stories can easily sound self congratulatory, because they describe getting others to do what you wanted. Balance this with genuine credit for others, honest acknowledgment of what you changed in response to them and recognition that the outcome was shared. A story told with humility is far more persuasive than one that casts the candidate as the only clear thinker in the room.

Persuade, listen, structure, deliver

Influence questions test whether you can build a shared view of a problem, tailor your case to each stakeholder, listen and adapt, create structure and keep momentum without authority, and reach a real outcome. Interviewers are wary of escalation instead of persuasion, pushing without listening and compliance without commitment.