In this article
Before you start
This page is one question in the behavioral interview guide.
Why interviewers ask this
The question separates engineers who raise their own output from engineers who raise a team's. Candidates report mentoring prompts in senior and staff loops, for example at LinkedIn and Anthropic; these are candidate reports, not company statements. Some companies publish the expectation: Amazon's leadership principles say "Leaders develop leaders and take seriously their role in coaching others" (Amazon, read October 2026), and the Amazon leadership principles page covers the rest. Many career ladders list mentorship as a requirement; Will Larson of StaffEng notes that people sometimes "see a requirement for mentorship in their career ladder and try to mechanically check that box" (StaffEng).
A weak answer lists habits: "I answer questions when juniors ask." A strong answer describes one person, what you did and what changed for them. A Staff-level answer adds the cost to your own time and what you did once the person no longer needed you.
Mentoring as an IC from first principles
- IC mentoring
- IC mentoring is a relationship in which an engineer with no management authority shares knowledge, advice and judgment with a colleague over time, so the colleague can do work they could not do alone before. The mentor does not have to be in management, and the relationship builds over weeks or months, not in one conversation.
- Coaching
- Coaching is a way of helping someone reach their own goals by asking questions instead of giving answers. The coach's job is to help the person think, not to supply the solution; the best coaches, as Jacob Kaplan-Moss writes, help their clients come up with the answers themselves.
- Sponsorship
- Sponsorship is the use of your power, influence and networks to advance another person's career, for example by putting their name forward for a project or a promotion. A sponsor acts on someone's behalf, while a mentor shares knowledge. Sponsorship can grow out of a mentoring relationship.
In plain words
Think of teaching a friend to cook. You can hand over a recipe. You can ask what they would try next. You can recommend them to a restaurant that is hiring. Those are three different jobs. The analogy breaks in one place: at work the jobs overlap, and one person can do all three.
Janice Omadeke, writing in Harvard Business Review (2021), defines mentorship as a relationship between someone sharing knowledge and providing guidance and someone learning from that person's experience and example. She adds that a mentor does not have to be somebody in management. So IC mentoring is knowledge and judgment, shared over time, with no authority over the other person's pay or promotion.
Step 1: Pick one person and one gap
A strong answer starts with one specific person and one specific gap in their work, not with a list of habits. Choose someone you helped for weeks, because Will Larson of StaffEng writes that "Sharing your experience and advice, along with building an ongoing relationship to understand the recipient's context, is high impact work."
Pick a gap an outsider can picture. Take a newer engineer whose pull request (PR), a proposed code change that teammates review before it is merged, needed many review rounds because they did not know the service's failure modes. Candidates report being asked for concrete evidence that they improved another engineer's autonomy or judgment, so choose a gap about judgment, not trivia.
Input: your memory of one project. Output: one sentence in the form "A newer engineer struggled with X because Y." Use no real names; "a newer engineer on my team" is enough.
Step 2: Prove the other person became more independent
Proof of independence is what the other person did differently after your help, stated so the interviewer can check it. It can be a number or an observed behavior. Both work, but never invent a number in a real answer.
Here is an invented story, labeled illustrative. Over the first five pull requests the newer engineer needed 4, 5, 4, 3 and 4 review rounds. After weekly sessions on past incidents, the last five needed 2, 1, 2, 1 and 2. In the illustrative story, mean review rounds per pull request fell from 4.0 to 1.6.1 The engineer also began flagging risky migrations in design review without being asked, which is the judgment evidence.
| Quantity | Value (illustrative, computed) |
|---|---|
| Mean review rounds, first five pull requests | 4.0 |
| Mean review rounds, last five pull requests | 1.6 |
| Drop in review rounds | 2.4 |
| Drop as a share of the starting mean | 60% |
Text description of the diagram
- In the illustrative story, mean review rounds per pull request fell from 4.0 to 1.6.
- In the illustrative story, review rounds per pull request fell by 2.4 rounds, a drop of 60%.
Step 3: Say which role you played
Mentoring, coaching and sponsorship are different tools, and naming yours shows range. Jacob Kaplan-Moss (2024) separates the tools by purpose: mentorship is about knowledge transfer, and coaching is about achieving goals. Mentoring sounds like "I think you should…"; coaching sounds like "What are your next steps?" Herminia Ibarra (2022) says a sponsor is somebody who has power and will use it for you, and one person can play both roles.
Sponsorship often follows trust. Ibarra (2022) says you cannot start off expecting sponsorship. In the story above, the sponsorship step is recommending the engineer to lead a design review once they were ready.
Text description of the diagram
- Mentorship is about knowledge transfer, but coaching is about achieving goals.
- A sponsor is somebody who has power and will use it for you.
The whole answer follows one path. A strong answer starts with one specific person and one specific gap. The result is evidence that the other person became more independent. Then you say whether you shared knowledge, asked questions or used your influence for them.
Step-by-step description
- Start with one specific person and gap.
- Show the person became more independent.
- Say if you mentored, coached or sponsored.
- A strong answer starts with one specific person and one specific gap.
- The result is evidence that the other person became more independent.
Knowing it is half the job. Saying it is the other half.
Interview Clozo is an AI interview copilot for real interview rounds: it hears the question and puts a strong answer on your screen, and you say it in your own words. See the features or how it works.
Start Free Trial →The Staff-level answer
Tell me about a time you helped another engineer grow.
A newer engineer on my team needed about four review rounds per pull request, mostly because they did not know our service's failure modes. Once a week we walked through a past incident, and I asked them to predict the review comments before I gave mine. A few weeks later most of their pull requests passed in one or two rounds, and they started flagging risky migrations unprompted. It cost me about an hour a week, and I stopped writing their fixes. Once they were ready, I put them forward to lead a design review.
The numbers in this answer are illustrative. What makes it staff-level: it proves independence, names the cost to your own time, and ends with sponsorship, not just advice. Say the setup, then the method, then the result, then the cost. If you find your voice drifting into a life story, the guide to telling your story in an interview shows how to stay short.
The rubric
| Dimension | Weak answer | Strong answer | Staff answer |
|---|---|---|---|
| Evidence | Says "I help juniors when they ask." | One anonymized situation with what you did. | Shows an observable change in the other person's independence. |
| Method | Gives answers and fixes the code. | Explains context and gives reasons in review. | Picks mentoring, coaching or sponsorship to fit the person, and says why. |
| Trade-offs | Mentions only benefits. | Mentions the time it cost. | Weighs your time against team output and names what you stopped doing. |
| Communication | Rambles through years of examples. | Tells one story with a clear order. | Opens with the result, then the method, and invites a follow-up. |
| Follow-up readiness | Cannot say what happened afterwards. | Knows how the person is doing now. | Describes what the person now teaches others. |
This rubric is our own guide to what a strong answer shows. It is not any company's scoring sheet.
Three variants of this question
What are your principles of mentorship?
Give context before answers, ask what they would try first, and let them own decisions you can reverse. Step back as they grow, and move from advice toward sponsorship once trust exists. Candidates report this prompt in staff-level loops at LinkedIn.
How do you handle technical and non-technical mentoring?
Technical mentoring transfers specific knowledge such as design trade-offs, review habits and debugging. Non-technical mentoring covers communication, scoping and asking for help, and the interpersonal communication guide covers that side. This split is a common framing, not a formal definition.
Describe a project with many junior engineers where quality stayed high.
Write the standards down, pair on the first few pull requests, and check outcomes instead of only effort. Say what you stopped doing yourself so the team could grow, and tie it to the independence evidence of Step 2.
Common mistakes
- "I mentor by telling people what to do." (wrong) Mentors share experience and recommend, and coaching is the mode that asks questions. (right) "I share what I know, then ask what they would try."
- "Mentoring is on my career ladder, so I do it." (wrong) Larson calls mechanically ticking the mentorship box a shame, because it is one of the most valuable activities in a Staff-plus role. (right) "I mentor because the person's gap was slowing the team."
- "I have not mentored because I am not a manager." (wrong) A mentor does not have to be in management. (right) "I have no reports, but I mentored a teammate."
- "I started mentoring, so sponsorship came automatically." (wrong) Sponsorship is a separate step that uses your influence, and it usually follows trust in the person's work. (right) "Once their work showed they were ready, I put their name forward."
- "I fixed their code myself." (wrong) That shows your skill, not their independence. (right) "I explained why, and they fixed the next one alone."
Follow-up questions
What is the difference between a mentor and a sponsor?
A mentor has knowledge and shares it; a sponsor has power and uses it for you. Digital.gov quotes Hewlett: "Mentors proffer friendly advice. Sponsors pull you up to the next level."
Do you have to be a manager to mentor someone?
No. Janice Omadeke, writing in Harvard Business Review (2021), states that a mentor does not have to be somebody in management, and Digital.gov notes mentors are typically in the same field and roles as their mentees.
How do you know your mentoring worked?
Look for the other person doing alone what they needed help with before: fewer review rounds, a decision made without asking, or a teammate they now help. The common interview questions guide covers how to state results like these.
How do you find time to mentor while delivering your own work?
Cap it, schedule it, and choose the sessions that remove your recurring interruptions. The prioritising under pressure guide covers the trade-off.
Is mentoring different from coaching?
Yes. Mentoring transfers knowledge and sounds like "I think you should…". Coaching asks questions such as "What are your next steps?" so the person finds their own answer.
- Mentoring as an IC is sharing knowledge and judgment over time without managing the person.
- Tell one story about one person and one gap, never a list of habits.
- End with proof the person became more independent, and never invent a number.
- Name your role: mentoring shares knowledge, coaching asks questions, sponsorship uses influence.
- Mention the time cost and what you stopped doing.
Sources
- What do Staff engineers actually do? — StaffEng (Will Larson); page undated, read 2026-10-26, 26 Oct 2026
- What's the Difference Between a Mentor and a Sponsor? — Harvard Business Review (Janice Omadeke), 20 Oct 2021
- What We Still Misunderstand About Mentorship and Sponsorship — Harvard Business Review podcast (Herminia Ibarra), 1 Nov 2022
- Mentorship, coaching, sponsorship: three different tools for developing talent — Jacob Kaplan-Moss, 1 Apr 2024
- Go Beyond Coaching and Mentorship and Get Started as a Sponsor — Digital.gov (US General Services Administration), 13 Mar 2019
- Leadership Principles — Amazon; page undated, read 2026-10-26, 26 Oct 2026
