To answer "tell me about a time you mentored someone," describe one person you helped grow, show that you coached them to do the work themselves rather than doing it for them, and end with a measurable change in what they could do on their own. The interviewer is listening for patience, a deliberate approach to teaching, and proof that the other person improved.
This question is narrower than a leadership question. Leading a team is about direction and results across several people; mentoring is about one person's growth. For the team version, see how to answer "tell me about a time you showed leadership". Both sit in our full list of "tell me about a time" questions and answers.
What is the interviewer really testing when they ask about mentoring?
Companies commonly ask this of senior individual contributors and anyone heading toward management, because the ability to grow other people multiplies a team's output. They want to know four things:
- Do you coach, or do you take over? Fixing someone's work for them is faster today and slower forever.
- Do you adapt to the person? A new grad and an experienced hire switching fields need different help.
- Can you show growth? "She got a lot better" is an opinion. "She led the next release on her own" is evidence.
- Do you enjoy it? Reluctant mentoring shows. So does genuine interest in someone else's success.
You do not need a formal mentoring program or a manager title. Onboarding a new teammate, helping an intern, or teaching a colleague from another team a skill all count.
Coaching vs doing: the difference interviewers listen for
The most common weak answer is a story where the "mentor" mostly did the work. Use this table to check your story before you tell it.
| Moment | Doing it for them | Coaching them |
|---|---|---|
| They are stuck on a problem | You write the fix | You ask what they have tried and point to where to look next |
| Their draft is weak | You rewrite it | You name the two biggest issues and let them revise |
| A high-stakes meeting | You present | You rehearse with them, then let them present while you back them up |
| They make a mistake | You quietly fix it | You walk through what happened together and agree on a check for next time |
| Measuring progress | "They seem fine" | A goal you set together, checked on a schedule |
Coaching does not mean never stepping in. If a customer or a production system is at risk, say that you stepped in, and then explain how you turned it into a lesson afterward.
A short answer frame
- Situation: who the person was, where they started, and why the gap mattered.
- Task: the goal you agreed on together, ideally with a time frame.
- Action: your approach, such as regular check-ins, pairing, gradually handing over ownership and feedback. Give two or three specific techniques, not a list of ten.
- Result: what they could do on their own afterward, with a number or a visible milestone, and what you learned about mentoring.
The STAR method guide covers the structure in more depth. Keep the answer to about two minutes.
Three example answers we wrote
These are example answers we wrote to show what a strong response sounds like. Names, details and numbers are invented; use your own experience.
Example answer we wrote: a senior engineer and a new grad
Situation. A new-grad engineer, Dana, joined my team of five. Two months in, she was still asking for help on most tickets and had not yet been added to the on-call rotation, which put extra load on the rest of us.
Task. My manager asked me to mentor her. We agreed on a goal: Dana would join on-call within three months and own a small feature from design to launch.
Action. I set up two 30-minute sessions a week. Instead of answering her questions directly, I asked her to bring her best guess first, then we compared it with how I would approach it. For on-call, she shadowed me for two weeks, then took the lead while I shadowed her. I also had her write a one-page design doc for a rate-limiting feature and review it with me before sharing it with the team.
Result. Dana joined the on-call rotation in ten weeks and handled her first incident without escalating. Her design doc was approved with only minor comments, and she shipped the feature on schedule. Over the quarter, the questions she brought to me dropped from about ten a week to two or three. I learned to ask for her guess before giving mine; it is now how I onboard everyone.
Example answer we wrote: an account manager and a new hire
Situation. I was a senior account manager when a new hire, Leo, took over 30 small accounts. He was strong on relationships but avoided renewal conversations, and four of his first six renewals had stalled.
Task. I offered to mentor him for one quarter, with the aim of getting his renewal rate in line with the team average.
Action. We listened to two of his recorded calls together, and I asked him to point out where the conversation drifted. He spotted it himself: he never asked about budget timing. We wrote a short call plan together, and he role-played it with me twice before using it. I joined his next three renewal calls as a silent listener and gave him feedback within the hour.
Result. By the end of the quarter, he had renewed 13 of his 15 accounts up for renewal, in line with the team average. He later used the same call plan to onboard the next hire, which told me the skill was really his.
Example answer we wrote: a data scientist and an analyst learning to code
Situation. An operations analyst, Aisha, spent about a day each week building the same spreadsheet reports by hand. She wanted to learn SQL and Python but did not know where to start.
Task. I volunteered to mentor her outside my team, and we set a goal: automate her two biggest weekly reports within eight weeks.
Action. We met for an hour every Friday. I gave her small exercises using her own data, not textbook examples, so each lesson solved a real problem. When she got stuck, I asked her to explain the error message to me before I said anything. By week five, I stopped writing any code in our sessions and only reviewed hers.
Result. She automated both reports in seven weeks, saving about six hours a week. A few months later she moved into a junior analytics role. I learned that real work beats practice exercises for adult learners.
Weak vs strong answers
| Weak | Strong |
|---|---|
| "I mentor lots of people." | One person, one goal, one time frame |
| You solved their problems | You asked questions and handed over ownership step by step |
| Growth described as a feeling | A milestone they hit on their own: on-call, a launch, a renewal rate, a promotion |
| The mentee is described as weak or slow | The mentee is described with respect and a clear starting point |
| No lesson for you | A specific thing you now do differently as a mentor |
What follow-up questions should you expect?
- "How did you know it was working?" Name the check-ins and the signals you watched.
- "What did you do when they weren't improving?" Describe how you changed your approach, or a second story where it did not work at first.
- "How did you balance mentoring with your own work?" Be concrete about the time you set aside.
- "How would you mentor someone more senior than you?" Talk about mentoring on a specific skill rather than in general.
- "Have you ever had to give a mentee hard feedback?" Be ready with a story; our guide on giving difficult feedback shows how to tell it.
Mistakes to avoid
- Taking credit for their success. Say "she shipped it," not "we shipped it" or "I shipped it."
- Choosing a story with no measurable change. If you cannot name what they could do afterward, pick another story.
- Making it a story about delegation. Handing someone a task is not mentoring unless you helped them build the skill. If your story is really about handing off work, see how to answer the delegation question.
- Sharing personal details. Keep the mentee's private struggles out of it.
- Going too long. Three techniques are enough. More reads like a training manual.
Practice it
Mentoring stories tend to run long because there is so much to say. Rehearse yours out loud with an AI interview assistant like CoPilot Interview: its Mock Interview builds questions from your résumé and the job description, reads them aloud and scores each spoken answer out of 10 with what to fix, including where you can cut. It is free for 15 minutes a day, with no account. Follow each employer's rules on AI tools, and use AI to prepare beforehand.
Turn your mentoring story into a two-minute answer
Practice behavioral questions out loud, get a score and specific fixes for each answer, and tighten it until it lands.
Try a free AI mock interviewFAQ
What if I have never formally mentored anyone?
Informal mentoring counts. Onboarding a new teammate, helping an intern, teaching a colleague a tool, or tutoring a classmate all work if you can show the person's growth.
Is mentoring the same as leadership in an interview?
They overlap, but mentoring focuses on one person's growth, while leadership questions usually focus on setting direction for a group and delivering a result.
How do I measure a mentee's growth?
Use a milestone they reached on their own, such as joining on-call, leading a launch, hitting a target, taking on bigger work or being promoted. Fewer questions or less rework also count.
Can I talk about mentoring outside work?
Yes, if you have no work example, but a work story is stronger. If you use volunteering or tutoring, keep the same structure and a measurable result.
How long should the answer be?
About two minutes. Spend most of it on your approach and on the mentee's result.
What if the person I mentored did not improve?
You can use it if you explain what you tried, what you learned and what happened next. A story where you adjusted your approach can be stronger than a smooth success.