The "Social Capital" Bank Account
Most engineers are promoted into authority — they become a manager and suddenly people report to them. Staff Engineers get a different deal: they are expected to lead, but they have no direct reports, no hiring/firing power, and no ability to mandate anything. This is called leading without authority, and it is one of the hardest skills to develop because it requires a completely different toolkit than technical expertise.
Think of it like being a trusted advisor versus being a boss. A boss can say "do this." An advisor has to make you want to do it.
How influence is actually generated:
- Technical Competence: People listen to you because you have been right before. This is the baseline — without it, nothing else works. But it is not sufficient on its own.
- Empathy: You understand the other person's constraints, pressures, and goals. You do not just push your agenda; you ask "what does success look like for you?" before proposing a solution.
- Sponsorship: You actively use your platform and visibility to highlight other people's wins. When you make others look good, they trust you.
- Consistency: You do what you say you will do. Reliability is a form of trust-building that compounds over time.
The Bank Account Metaphor:
Social capital works exactly like a bank account. Every interaction either deposits or withdraws from your balance with a given person.
| Action | Effect |
|---|---|
| Help someone debug a nasty production issue | Deposit |
| Publicly credit someone for their idea | Deposit |
| Deliver on a commitment you made | Deposit |
| Ask someone to refactor code they're proud of | Withdrawal |
| Escalate a disagreement over their head | Large withdrawal |
| Ask for a roadmap change that creates work for them | Withdrawal |
The critical insight: you cannot make withdrawals from an empty account. If you have not invested in a relationship, you have no standing to ask for anything. Engineers who skip the relationship-building phase and go straight to demanding changes are consistently the least effective at driving organizational change, regardless of how technically correct they are.
A common Staff+ interview question is: "Describe a time you influenced a decision without having formal authority." Interviewers are looking for a specific structure: (1) you identified a stakeholder's underlying concern, not just their stated position; (2) you addressed that concern directly; (3) you built a coalition rather than trying to win a one-on-one argument. Answers that describe "I just showed them the data and they agreed" miss the point — the question is about navigating resistance, not about being obviously correct.