Working with people
Mentorship: getting it and giving it
Distinguish mentors, coaches and sponsors — then ask well, mentor juniors and grow others as an SDE2.
Careers compound through other people. Books and docs teach mechanisms; humans teach judgment, warn you about landmines and open doors you cannot see. Early on you mostly receive guidance. By SDE2 you are expected to give it — and by SDE3, growing others is often a promotion signal as strong as your own projects.
Mentorship is not a formal program with matching algorithms. It is a set of relationships you cultivate on purpose.
Concepts in this section
Read them in order. Each one builds on the one before.
| Step | Concept | What it answers |
|---|---|---|
| 1 | Mentors, coaches and sponsors | Who does which job? |
| 2 | Asking for mentorship | How do you make the ask grantable? |
| 3 | Mentoring juniors | How do you onboard, review and coach? |
| 4 | Building a mentor bench | How do you stop depending on one hero? |
| 5 | Sponsorship and growing others | What does a promotion committee actually want? |
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.
A picture of the mix
A mentor can say "you should ask for the migration project." A sponsor says in the staffing meeting "Put Alex on the migration — I'll backstop." One person rarely fills all roles. A small bench of partial relationships beats waiting for a perfect single mentor.
The ask that works is bounded: 30 minutes every other week for two months, agenda in advance, a specific skill, an artifact. The teaching that works is a first-week production win plus questions in review — and a direct answer when the cost of delay is a sev.
Track mentee outcomes the way you track projects. "Coached two new hires through first on-call; zero missed pages from process confusion" is evidence. Slack answers are not. If advice is plentiful and stretch work is not, say so to your manager: you need someone to name you in the room.
Common mistakes
- Waiting for one perfect senior (mentor hoarding).
- Taking notes, never acting, re-asking (advice vampire).
- Solving every junior problem yourself (answer vending machine).
- Lots of coffee chats, no stretch work (invisible sponsorship gap).
- Pushing others to copy your path (clone factory).
Key takeaways
- Mentors advise, coaches question, sponsors advocate; you need a mix, not one perfect person.
- Ask with a bounded cadence, agendas and specific questions tied to artifacts.
- Make yourself sponsorable with visible, reliable work and clear goals; ask your manager for advocacy when advice is plentiful and opportunity is not.
- Mentor juniors through onboarding, pairing and reviews; teach with questions and productive struggle when time allows.
- At senior levels, growing others — including sponsorship — is part of the job and part of the promotion case.
Further learning
What does sponsorship look like? (Lara Hogan)Illustration by Catt Smalllarahogan.me
Lara Hogan's blogLara Hoganlarahogan.me
StaffEng (Will Larson)Staff Engineer: Leadership beyond the management trackStaff Engineer: Leadership beyond the management track
Related
The path to SDE3 and beyond
What senior engineers do differently: technical leadership, multiplying others and owning ambiguity.
Code review
Author small, reviewable PRs and give reviews that improve both the code and the author — design first, tone that teaches, turnaround that unblocks.
One-on-ones, feedback and performance reviews
Run your 1:1s, ask for and act on feedback, and keep a brag document through review cycles.