Sponsor, Not Just Mentor — Mentoring Engineers, Part 5
Mentoring Engineers · Part 5
A mid-level engineer has had a mentor for a year. The meetings are good. They've worked on system design, on writing clearer proposals, on how to handle a difficult stakeholder. Then a staff-level project opens up: a rebuild of the team's event pipeline, exactly the kind of work the mentoring was preparing them for. It goes to someone else. Afterwards the engineer learns that the decision was made in a twenty-minute planning conversation. Their mentor wasn't in it. Nobody in the room had seen their recent work, so nobody said their name.
The mentoring wasn't wasted. It made the engineer ready. What it didn't do was get them considered, because readiness only turns into opportunity when someone with standing puts it in front of the people deciding.
That's the difference this part is about. A mentor gives advice in a room you're in. A sponsor uses their credibility for you in rooms you're not in. Sylvia Ann Hewlett's research on sponsorship, collected in The Sponsor Effect (2019), makes the case that sponsorship is what moves careers at the moments that matter, and that it also benefits the sponsor. The method below makes it concrete for an engineering team.
Before you start
List the engineers you mentor. For each, write one opportunity they'd be ready for in the next six months.
List the rooms where those opportunities get decided: planning meetings, promotion calibration, staffing conversations, conference talk selection. Mark which ones you're in.
Ask yourself honestly whose names you've said in those rooms in the last quarter. That list is your current sponsorship, whatever you intended.
Step 1: Tell mentoring and sponsorship apart (10 min)
Mentoring | Sponsorship |
Advice, feedback, skill building | Advocacy, visibility, access to opportunities |
Happens with the person present | Mostly happens when they're absent |
Low risk to the mentor | Spends the sponsor's credibility |
"Here's how to write a good design doc" | "She should lead the pipeline rebuild; her last design doc was the clearest we've had" |
Both matter, and they're done in a sequence: mentoring builds readiness, sponsorship converts it. The common failure is stopping after the first.
Test you can run: for each person you mentor, write down the last thing you did for them when they weren't in the room. If the list is empty, you're mentoring, not sponsoring.
Step 2: Learn the concrete acts (15 min)
Sponsorship sounds grand. Most of it is small and repeatable. Lara Hogan's list, from her 2017 post "What does sponsorship look like?", is still the most practical. In engineering terms:
Recommend them to lead a project, an incident review, a design discussion.
Put them in a visible role, like facilitating a postmortem or presenting at an architecture review.
Forward their work, with a note on why it matters: "This migration plan is the clearest I've seen; worth reading before Thursday."
Credit them by name in the meetings where you'd normally summarise the team's work.
Suggest them for talks and writing, internally or externally.
Say their name in calibration and staffing, with evidence.
Test you can run: pick one act from the list for each person you mentor and do it this week. Notice which ones felt awkward. Those are usually the ones that spend real credibility, which is why they work.
Step 3: Sponsor with evidence, not enthusiasm (10 min)
A sponsor's credibility is the currency. Spend it with specifics. "She's great" persuades nobody in a calibration meeting. "She designed the retry strategy that cut our failed-job pages from weekly to monthly, and she ran the rollout across three teams" does. Keep a short running note of each person's best work so you can be specific without preparing from scratch.
Test you can run: write two sentences recommending one of your mentees for a stretch project, as if you were saying them in a staffing meeting tomorrow. If the sentences contain no specific piece of work, you're not ready to sponsor them yet. Go and find the evidence.
Step 4: Match the opportunity to readiness (10 min)
Sponsoring someone into a role they can't yet do damages them and your credibility. The skill is choosing a stretch that is a real step up but survivable, and making sure they have support once they're in it. Early-career engineers need visibility for good work they've already done. Mid-level engineers need ownership of something with consequences. Senior engineers need access to the cross-team and leadership rooms where staff-level problems are decided.
Test you can run: for the opportunity you have in mind, ask "what's the most likely way this goes wrong, and who catches them if it does?" If you can't answer the second half, line up the support before you put their name forward.
Step 5: Tell them, and ask what they want (10 min)
Sponsorship works better when the person knows. Tell them: "I've suggested you for the pipeline rebuild. If it comes through, here's what I think will be hardest." It lets them prepare, and it stops a surprise opportunity feeling like a test they didn't sign up for. Ask, too, what they want. Sponsoring someone toward a management track when they want to stay technical wastes everyone's credibility.
Test you can run: ask each mentee, "what's one opportunity you'd want me to put your name forward for?" If they can't answer, the next mentoring conversation is about that, before any sponsoring.
Step 6: Audit who you sponsor (10 min)
Sponsorship follows familiarity. People tend to advocate for those whose work they see most and who remind them of themselves. In a distributed enterprise team, that quietly favours the people at headquarters, in your timezone, who talk the way you do. Hewlett's work frames sponsorship as an investment the sponsor chooses deliberately, and the deliberate part is the protection against just backing whoever is closest.
Test you can run: list everyone you've actively sponsored in the past year. Compare it with the team you lead or influence. If the list skews toward one location, background or working style, widen it on purpose, starting with the person whose good work you see least.
Step 7: Get sponsored yourself, and say so (10 min)
Sponsorship runs in chains. The people with the most credibility to spend are usually a level or two above you, and your ability to sponsor others depends partly on someone doing the same for you. Identify who in your organisation could put your name forward, and make their job easy: share your work with a line on why it matters, and tell them what you're aiming for.
There's a second reason to do this openly. Junior engineers often assume opportunities are handed out on merit by some neutral process. Telling them how you got your own stretch projects ("my director suggested me after reading my migration write-up") teaches them that being visible is part of the work, not self-promotion, and shows them how sponsorship actually happens.
Test you can run: name the person who last put your name forward for something. If you can't, finding one is your own next step, and the conversation you have with them is a model for the one your mentees need to have with you.
Worked example: the regional engineer (composite scenario)
An engineering manager at a financial services firm led a team split between a head office and a smaller regional office. A mid-level engineer in the regional office had been mentored for a year by a senior engineer at head office. The mentoring was going well. But in two planning cycles, every stretch project had gone to head-office engineers.
The manager ran the audit from Step 6 and saw the pattern immediately: everyone they'd sponsored that year worked in the same building as them. They asked the mentor to start sponsoring as well as mentoring, and together they did three things. The mentor forwarded the regional engineer's incident write-up, which had found a gap in the alerting, to the architecture group with a note on why it mattered. The manager asked the engineer to present it at the monthly engineering review, which they'd never done before. And when the next stretch project came up, a redesign of the alerting rules, the mentor named the engineer in the planning meeting and cited the write-up.
The engineer got the project. It was hard: they hadn't led cross-office work before, and the mentor held a weekly check-in for the first six weeks. It shipped. The lasting change was in the manager's habits more than the engineer's career. The planning meeting now starts by asking whose work outside head office is ready for something bigger, because the manager had learned that their sponsorship had followed their floor plan.
Trade-offs to make deliberately
Choice | You gain | You risk |
Sponsor early, on potential | Opportunities arrive before others claim them | Your credibility, if they aren't ready yet |
Sponsor late, on proven work | A safe recommendation | They're passed over while you wait for certainty |
Quiet sponsorship (behind the scenes) | Less pressure on them | They can't prepare, and don't learn how to be sponsored |
Open sponsorship (they know) | They prepare; trust grows | A visible failure if it doesn't come through |
Common failure modes
Mentoring without ever sponsoring. They're ready, and nobody in the room knows it.
Enthusiasm without evidence. "She's great" spends credibility and buys nothing.
Sponsoring whoever is closest. It quietly reproduces who already gets opportunities.
Stretch with no safety net. A failed stretch hurts them more than no stretch.
Sponsoring toward a goal they don't have. Ask first.
Final takeaway
Mentoring makes someone ready; sponsorship makes sure the people deciding know they're ready. It's mostly small, repeatable acts done in rooms the person isn't in, backed by specific evidence, aimed at a stretch they can survive, and checked against your own blind spots. Your next action: before your next planning or calibration meeting, write two evidence-backed sentences about one person you mentor, and say them in the room.
Sources
Hewlett, S. A. (2019). The Sponsor Effect: How to Be a Better Leader by Investing in Others. Harvard Business Review Press.
Hogan, L. (2017). What does sponsorship look like? larahogan.me, 14 May 2017.
Continue the Mentoring Engineers path
Previous — Part 4: Help With Stuck
Part of the Mentoring Engineers learning path. Related: Mentoring Without the Ego · Delegate Without Lowering the Bar.


