Guide

People use these words interchangeably. They are different jobs. Careers compound through other people: books teach mechanisms; humans teach judgment, warn you about landmines and open doors you cannot see.

RoleWhat they doWhat you get
MentorShares experience, patterns, war stories; helps you thinkPerspective, shortcuts, "here's how I'd approach it"
CoachAsks questions; helps you find your answerClarity, ownership of decisions, skill at reflection
SponsorPuts their reputation on the line for youOpportunities, visibility, advocacy in rooms you are not in
ManagerOwns your outcomes, feedback, staffing and reviewsClarity of expectations, resources, performance narrative

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." Lara Hogan's framing is the industry default: mentors give advice; sponsors give opportunity. Will Larson's staff-engineer writing pushes the same point — moderate mentorship plus more sponsorship is how senior ICs multiply others.

The big idea

Concept

Sponsorship is advocacy with skin in the game: recommending you for a stretch assignment, citing your work in calibration, introducing you to a hiring manager. It is not the same as being friendly or giving tips over coffee.

You need different people for different gaps. One person rarely fills all roles. A "Manager Voltron" (Hogan's joke) of several partial relationships beats waiting for a perfect single mentor.

If you are from a group that gets over-mentored and under-sponsored (a consistent research finding for many minoritized engineers), be explicit with your manager: "I have plenty of advice. I need stretch visibility and someone to name me in the room."

Ask mentors for judgment. For sponsorship, do excellent visible work and make it easy for advocates to cite you: crisp launch notes, peer feedback others can forward, a manager who knows your goals. You cannot demand a sponsor, but you can be sponsorable — reliable, low-drama, clear about what you want next.

Walking through a mix

You want to own a multi-week migration.

  • Mentor: reviews how you would scope it, warns you about dual-write landmines.
  • Coach: asks "what would make this a credible SDE2 packet?" until you can answer.
  • Sponsor: names you in the staffing meeting.
  • Manager: makes the assignment real in the review narrative.

Coffee chats without that mix feel like progress and leave your scope unchanged.

Common mistakes

  • Waiting for one perfect senior to be mentor, coach, sponsor and manager.
  • Collecting advice and never asking anyone to name you in the room.
  • Treating friendliness as sponsorship.

Check yourself

Someone gives you career tips over coffee. Are they a sponsor?

Not unless they put reputation on the line — a stretch assignment, a calibration cite, an intro with skin in the game.

You have plenty of advice and no stretch work. What do you tell your manager?

"I have plenty of advice. I need stretch visibility and someone to name me in the room."

Key takeaways

  • Mentors advise, coaches question, sponsors advocate, managers own outcomes.
  • You need a mix, not one perfect person.
  • Sponsorship has skin in the game. Friendliness is not it.
  • Be sponsorable: visible, reliable, clear about what you want next.

Further learning

Next, how to ask without a vague contract: asking for mentorship.

What does sponsorship look like? (Lara Hogan)Illustration by Catt Smalllarahogan.me