Working with people
Sponsorship and growing others
Promotion committees look for people you raised, not Slack answers. Track mentee outcomes the way you track projects.
Promotion committees look for evidence you raise the ceiling of people around you — not just that you are pleasant. At SDE3, growing others is often a promotion signal as strong as your own projects.
Concept
Sponsorship is advocacy with skin in the game. Mentors give advice; sponsors give opportunity. See mentors, coaches and sponsors.
Walking through strong vs weak signals
Strong signals:
- Engineers you mentored shipped meaningful work sooner.
- Your reviews and docs became team standards.
- You sponsored others: recommended them for projects, talks or hire loops.
- The team is healthier when you are not in every meeting — because you built capacity.
Weak signals: "I answered Slack questions" with no outcomes; mentoring only people who already look like you; advice without follow-through.
Track mentee outcomes the way you track project outcomes. A line in your brag doc — "Coached two new hires through first on-call month; zero missed pages from process confusion" — is evidence. Vibes are not.
You cannot demand a sponsor, but you can be sponsorable: reliable, low-drama, clear about what you want next. Make it easy for advocates to cite you: crisp launch notes, peer feedback others can forward, a manager who knows your goals.
If you are from a group that gets over-mentored and under-sponsored, be explicit with your manager: "I have plenty of advice. I need stretch visibility and someone to name me in the room."
If you manage no one yet, treat code review and onboarding docs as your mentorship surface. Improving those two artifacts raises everyone who joins after you. Measure yourself by whether the second person through a problem needs you less than the first.
Book one concrete mentoring habit: a recurring 30 minutes with someone junior, or a sharper ask to someone senior with an agenda template. Mentorship compounds slowly and then suddenly — the engineer you unblocked this quarter is the peer who unblocks you next year.
Common mistakes
- Counting Slack answers as growing others.
- Mentoring only people who already look like you.
- Advice without follow-through, and no mentee outcomes in the brag doc.
Check yourself
Which brag-doc line is evidence?
"Coached two new hires through first on-call month; zero missed pages from process confusion" — not "I answered Slack questions."
The team still pages you for every new-hire on-call question. What is missing?
Capacity. Sponsorship and docs should make the team healthier when you are not in the room.
Key takeaways
- Growing others is part of the senior job and part of the promotion case.
- Track mentee outcomes like project outcomes. Vibes are not evidence.
- Be sponsorable, and ask for advocacy when advice is plentiful and opportunity is not.
- Glue that outlives you — reviews, docs, FAQs — is the real multiply.
Further learning
What does sponsorship look like? (Lara Hogan)Illustration by Catt Smalllarahogan.me
Lara Hogan's blogLara Hoganlarahogan.me
Will Larson on why sponsorship is underemphasized relative to mentorship:
Related
Mentorship: getting it and giving it
Distinguish mentors, coaches and sponsors — then ask well, mentor juniors and grow others as an SDE2.
Mentors, coaches and sponsors
Mentors advise, coaches question, sponsors put reputation on the line. You need a mix, not one perfect person.
The path to SDE3 and beyond
What senior engineers do differently: technical leadership, multiplying others and owning ambiguity.