4 exercises — promotion readiness, surfacing unspoken concerns, delivering hard news, and coaching career ambiguity.
0 / 4 completed
1 / 4
A senior engineer asks you, their manager, "What would it take for me to get promoted to staff?" You believe they have real potential but aren't there yet. How do you respond?
Option C is a well-structured promotion readiness conversation:
Structure: 1. Defines the bar concretely — "consistently driving technical direction beyond your own team" — not a vague feeling, an operational definition specific to the level 2. Acknowledges current strength with evidence — "strong on execution; the checkout migration" — grounds the conversation in real work, not generic praise 3. Names the specific gap — "cross-team influence" — the actual missing dimension, not "needs to be more senior" 4. Gives concrete examples of what the gap looks like closed — "leading a design doc other teams adopt" — makes an abstract competency observable 5. Proposes a specific vehicle — "own the RFC for the event-bus redesign" — turns the conversation into an actionable plan, not just feedback 6. Sets a review cadence — "monthly check-ins" — promotion becomes a tracked project, not a one-time conversation
Why "just keep doing what you're doing" fails: It implies the current trajectory alone leads to promotion, which is rarely true — most promotion gaps are about a specific missing dimension (scope, influence, ambiguity) that requires deliberately different work, not more of the same work.
The "operational definition" principle: Every engineering level should be translatable into observable behaviors and artifacts. If you can't point to a specific example of what "staff-level influence" looks like, the engineer can't aim for it.
2 / 4
An engineer on your team is clearly unhappy with their level and salary, but hasn't raised it directly — you've noticed it through indirect comments and lower engagement. How do you open the conversation?
Option C shows how to proactively surface an unspoken career concern:
Structure: 1. Names the observation directly but non-accusingly — "I've picked up on a few comments" — signals attentiveness without making them feel surveilled 2. States a preference for directness — "I'd rather talk about it directly than have it sit unspoken" — sets the tone for the relationship going forward, not just this conversation 3. Invites confirmation, doesn't assume — "is that something on your mind?" — avoids putting words in their mouth 4. Offers an honest, evidence-based assessment — "here's my honest assessment... what's solid, what's missing" — respects them enough to be candid rather than vague reassurance 5. Separates the underlying drivers — "recognition, money, or growth pace" — these require different responses; a manager who treats them as interchangeable will likely solve the wrong problem
Why waiting for them to raise it formally is risky: By the time frustration becomes a formal conversation, it has often already cost engagement or led them to start interviewing elsewhere. A good manager reads the signals and opens the door first.
Why deflecting to HR damages trust: Career and compensation conversations are core manager responsibilities. Deflecting them signals the manager doesn't see career growth as part of the job — which is exactly the perception that drives people to leave.
3 / 4
You need to tell an engineer their promotion case was not approved this cycle, despite them putting in real effort toward it. What is the most constructive way to deliver this news?
Option C is a model for delivering a promotion denial constructively:
Structure: 1. Delivers the news directly, without burying it — "wasn't approved this cycle" stated plainly in the first sentence — respects the person enough not to soften it into ambiguity 2. Acknowledges the emotional reality — "I know that's disappointing, especially given the work you put in" — validates without being maudlin 3. Gives specific, actionable committee feedback — "wants to see the pattern repeat, not a single example" — concrete enough to plan around, unlike "not quite there yet" 4. Shares their own position transparently — "I disagree with parts of that read, and I said so" — builds trust by showing they advocated, without undermining the committee's legitimacy 5. Immediately pivots to a forward plan — "here's what gets you there clearly next cycle" — prevents the conversation from ending on pure disappointment 6. Reframes the setback — "I don't want this to feel like starting over — you're close" — accurate reassurance grounded in the specific feedback, not empty comfort
Why vague news ("just be patient") backfires: Ambiguity about why a promotion didn't happen is one of the top drivers of engineers leaving. Specific, actionable feedback — even when disappointing — preserves trust and gives them something to work toward.
The manager's dual role here: Being simultaneously honest about the outcome and an advocate for the engineer's growth are not contradictory — the best career conversations do both.
4 / 4
During a career conversation, an engineer says: "I don't really know what I want — staff engineer track, or management, or just staying where I am." How do you help them think it through in English?
Option C demonstrates coaching an engineer through career ambiguity rather than pushing them toward a track:
Structure: 1. Normalizes uncertainty — "most people aren't sure at this stage" — removes the pressure to have a polished answer 2. Breaks an abstract question into concrete, answerable ones — "what energizes you day to day" and a specific comparison ("mentoring Alex" vs. "the API redesign") — abstract self-knowledge questions are hard; specific recent-experience questions are answerable 3. Explicitly validates staying put — "staying at your current level while you explore is a legitimate choice" — counters the implicit assumption that career conversations must produce upward momentum 4. Proposes low-stakes experiments — "leading a small design review" and "informally mentoring one junior" — gives them data before a commitment, rather than asking them to choose blind 5. Frames it as an ongoing conversation — "we can talk about what each one felt like" — removes the pressure of a single deciding moment
Why "management is the natural path" is poor career guidance: It reflects an outdated assumption that management is the only form of advancement, and it can nudge naturally strong ICs into a track that doesn't suit them — a common source of both bad managers and lost strong engineers.
The "experiment before commit" principle: Career decisions made from real experience (a trial mentoring relationship, a trial tech-lead assignment) are far more reliable than decisions made from imagining what a role might feel like.
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.