4 exercises — the mentor/sponsor distinction, advocacy in calibration meetings, IC-level sponsorship, and raising sponsorship with your manager.
0 / 4 completed
1 / 4
A junior engineer asks you: "What's the actual difference between a mentor and a sponsor? People keep using the words interchangeably." How do you explain it accurately?
Option C gives an accurate, well-structured explanation of the mentorship vs. sponsorship distinction:
Why it's accurate: 1. Anchors the distinction on presence — "when you're in the room" vs. "when you're not in the room" — this is the cleanest, most memorable way to distinguish the two concepts 2. Gives concrete examples of each — mentorship: "reviewing your code, talking through a career decision"; sponsorship: "putting your name forward," "pushing back in a calibration meeting," "you should talk to Alex" — turns an abstract HR term into observable behavior 3. States the underlying purpose of each — "development" vs. "visibility and opportunities" — this is the deeper reason the distinction matters 4. Notes they're independent, not sequential or redundant — "a great mentor who never sponsors you, and a sponsor who barely mentors you" — corrects the common misconception that sponsorship is just "advanced mentoring"
Why this distinction matters practically: Research on career advancement (particularly for underrepresented groups) consistently shows that sponsorship — advocacy in rooms the person isn't in — has an outsized effect on promotion and opportunity access, distinct from the skill-building effect of mentorship. Someone can be excellent at their job and well-mentored but still get passed over if no one is advocating for them where decisions are made.
Why "basically the same thing" is a meaningfully wrong answer: Conflating the two leads engineers to assume that having a good mentor is sufficient for career advancement, when in many organizations, sponsorship is the more decisive factor for promotions and high-visibility opportunities.
2 / 4
You are in a promotion calibration meeting where a strong engineer on your team is being discussed, but other managers don't know their work well and are underrating them. What does effective sponsorship language sound like in this meeting?
Option C is a strong example of sponsorship language in a calibration/decision-making meeting — advocacy happening precisely when the person being discussed isn't present:
Structure: 1. States the reason for speaking up — "I don't think it's visible from the doc alone" — frames the intervention as filling an information gap, not just cheerleading 2. Provides specific, firsthand, verifiable evidence — "the payments migration... critical blocker in week two... the fix other three teams adopted" — this is what separates sponsorship from vague praise; it's testimony a sponsor is uniquely positioned to give because they witnessed it directly 3. Explains why the evidence might otherwise be missed — "not in their self-review because they don't tend to highlight their own impact" — many strong engineers underreport their own impact, and a sponsor exists partly to correct for that gap 4. Takes an explicit position, not a neutral one — "I'd push back on rating this as borderline... this is a clear yes" — sponsorship requires actually using social capital to advocate, not just providing balanced information and staying neutral
Why "I'll defer to the group's judgment" fails as sponsorship: Deferring when you have unique, decisive information the room lacks isn't neutrality — it's a missed opportunity to correct an information gap that will materially affect someone's career, which is exactly the moment sponsorship is supposed to happen.
Why worrying about "seeming biased" often misses the point: Advocating with specific, verifiable evidence isn't bias — it's providing information the calibration process needs to be accurate; the actual risk of unfairness usually runs the other way, when strong engineers are underrated simply because no one who witnessed their impact firsthand spoke up for them.
3 / 4
A senior engineer says to you: "I try to mentor junior engineers, but I never seem to actually sponsor anyone — I don't really know what that would even look like day-to-day." How do you explain concrete sponsorship actions they could start doing?
Option C gives concrete, actionable examples of sponsorship behavior available to individual contributors, not just managers:
Why the examples are effective: 1. "Suggest a specific junior by name to lead a piece of a high-visibility project" — actively creates an opportunity rather than passively waiting for one; this is a core sponsorship act, distinct from just being encouraging 2. "I think that was [Name]'s point — can we go back to it?" — a small, repeatable, low-cost intervention that corrects a very common pattern (ideas being talked over or misattributed, disproportionately affecting junior and underrepresented voices) 3. Giving a specific, evidence-backed recommendation rather than generic praise — "solid" carries little weight in a hiring or staffing decision; a specific example does 4. "Say something" when someone is underestimated in a conversation they're not in — this is the essential definition of sponsorship restated as an action item — advocacy in absentia
Corrects two common misconceptions the other options represent: • That sponsorship is one big generic gesture ("tell people they're good") — in reality it's many small, specific, repeated actions • That sponsorship requires managerial authority — in reality, ICs sponsor each other constantly through recommendations, project nominations, and correcting misattribution, and this peer-level sponsorship is often invisible but highly impactful
Why "you need to be in management" is a meaningfully wrong answer: It would discourage senior ICs — who often have significant informal influence and visibility — from using it, when in practice IC-to-IC sponsorship is one of the more underused levers for improving equity in who gets opportunities.
4 / 4
You want to sponsor a talented but quiet engineer on your team who tends to be overlooked for high-visibility opportunities. How do you raise this with your own manager, using advocacy language?
Option C is a strong example of proactive sponsorship language directed at your own manager — advocacy for someone who isn't in the room:
Structure: 1. Names a specific opportunity, not a vague ask — "the upcoming platform initiative" — sponsorship works best attached to a concrete opening, not a general request to "think of them sometime" 2. Gives specific, evidence-rich proof of capability — "led the migration... handling an unplanned outage during the cutover... documented the recovery" — three distinct, verifiable data points, not a single vague compliment 3. Names the exact structural problem being corrected — "they don't self-promote, so I don't think their name would naturally come up... which is exactly why I want to make sure it does" — this is the precise mechanism sponsorship exists to counteract: quiet excellence being systematically overlooked in favor of louder self-promotion 4. Makes a direct, specific ask — "put them forward as a lead candidate... how to make that happen" — moves from information-sharing to a concrete action request, which is the difference between sponsorship and simply mentioning someone favorably
Why "keep an eye out for opportunities" is too weak: It's a passive, generic request that puts no real weight behind the recommendation and gives the manager nothing specific to act on — it's the sponsorship equivalent of a form letter.
Why "it's not fair" framing is less effective than it seems: Appeals to fairness alone, without concrete evidence of capability and a specific opportunity attached, are much less likely to move a decision-maker to action than a specific, evidence-based case tied to a real opening — sponsorship is most effective when it does the decision-maker's evaluative work for them.
What will I practise in "Sponsorship vs. Mentorship"?
This module focuses on Mentoring & Feedback — real workplace phrasing you'll use on the job. It contains 4 scenario-based multiple-choice questions with instant feedback.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account or sign-up required.
How many questions does this exercise have?
This module includes 4 questions. Each one gives an immediate right/wrong result plus a full explanation of the correct phrasing.
What happens if I answer a question incorrectly?
You'll see the correct answer highlighted straight away, along with a plain-English explanation of why it's right and why the other options don't fit — mistakes are part of the learning here.
Can I retry the exercise if I want a better score?
Yes — use the 'Try again' button on the results screen to reset your score and go through the questions again. There's no limit on attempts.
Who is this Mentoring & Feedback exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around mentoring & feedback — useful whether you're preparing for real conversations at work or just building confidence with the vocabulary.
Do I need an account to track my progress?
No account is needed. Your progress through the exercise is tracked locally in your browser for the current session, and you can replay the module at any time.
How is this different from reading a blog article?
This exercise is an interactive drill that tests and reinforces specific phrasing through multiple-choice questions with instant feedback, while blog articles explain concepts and vocabulary in prose. The two work well together.
Where can I find more Mentoring & Feedback exercises?
See the Mentoring & Feedback hub for more modules like this one, or browse the full Exercises page for other IT-English topics.
Can I complete this exercise on my phone?
Yes — every exercise on CoderSlingo is fully responsive and works on phones and tablets, so you can practise anywhere.