When an interviewer asks you to describe a time you mentored someone, they are rarely checking whether you held the title “mentor”. They want evidence that you can make another person better at their job, and that you know the difference between doing the work for them and helping them learn to do it.
This guide explains what the question tests, then walks through four annotated examples at different career levels. Every example is illustrative: written to show the moves that score well, not a script to memorise.
What the interviewer is listening for
Mentoring has a fairly specific meaning in HR practice. The CIPD’s coaching and mentoring factsheet describes it as “a relationship in which a more experienced colleague shares their greater knowledge to support the development of an inexperienced individual”. It adds that mentoring relationships “tend to be longer term than coaching arrangements”, and that good mentors use “the skills of questioning, listening, clarifying and reframing that are associated with coaching”.
That gives you three things to show:
- Knowledge transfer: you had something worth passing on, and you passed it on deliberately.
- Method: you asked and listened, rather than only telling.
- Development over time: the person could do something at the end that they could not do at the start.
Employers’ published frameworks point the same way. The UK Civil Service behaviour framework, under “Developing Self and Others”, asks staff at middle grades (HEO and SEO) to “take time to coach, mentor and develop other colleagues to support succession planning”. At the most junior grades the expectation is lighter: to “share knowledge and skills learnt with colleagues to contribute to the learning and development of the whole team”. Amazon’s “Hire and Develop the Best” principle states that “Leaders develop leaders and take seriously their role in coaching others.”
That junior-grade line matters if you are early in your career. You do not need a formal mentoring scheme behind you. Showing a new starter the ropes, or helping a classmate through a module you found easier, counts if you can describe it properly.
A structure that fits mentoring stories
The STAR method (Situation, Task, Action, Result) works here with one adjustment. In a mentoring story the result has two layers: what the other person achieved, and what changed in how they work. Most of your answer should be the action, and for mentoring that means time spent on how you taught, not on the problems the mentee had.
Run through this checklist before you speak:
- Who was the person, and what gap did they have? One or two sentences, kept respectful.
- Why were you the one helping them?
- What did you do, in order, and why that approach?
- How did you step back as they improved?
- What could they do afterwards, and what shows it?
- What did you learn about mentoring?
Example 1: Onboarding a new team member (early career)
Illustrative example. Customer support associate with about two years’ experience.
“When a new colleague joined our support team, my manager asked me to buddy him for his first month because I had the best quality scores on billing tickets. He was confident on the phone but kept escalating billing questions he could have solved, which slowed the queue.
In the first week he sat with me on live tickets and told me what he would do before I did it. In the second week we swapped: he handled the tickets and I listened, and we spent ten minutes at the end of each day on the ones he found hardest. I also wrote up the five billing scenarios that caused most escalations as a one-page guide, which the team still uses.
By the end of the month his escalation rate on billing tickets was around the team average, and he had started answering other new joiners’ questions in our team chat. What I learned was that he did not need more information. He needed permission to make the call, and practice making it while someone was there to catch mistakes.”
Why it works:
- The gap is specific (unnecessary billing escalations), not a vague “he was struggling”.
- The method changes over time: watch, then do with support, then do alone. That shows the mentor stepping back.
- The one-page guide shows the help outlasted the relationship.
- The result is measured against something real, the team average, and is not overstated.
- The closing insight is about the colleague’s confidence, which signals attention to the person, not just the task.
Watch out for: if you quote a figure, be ready to say where it came from. “Around the team average, from our weekly dashboard” is fine. An invented percentage is not, and a good interviewer will probe it.
Example 2: A formal mentoring relationship (mid-career)
Illustrative example. Site engineer on a construction project.
“Our company runs a mentoring scheme for graduate engineers, and I was paired with a graduate in her first year. At our first meeting I asked what she wanted from the year. She said she wanted to pass her professional review, but as we talked it became clear the real worry was speaking up with clients and contractors.
We agreed to meet every two weeks for six months. Rather than giving her answers, I asked her to bring one situation each time where she had held back in a meeting. We worked out what she could have said, and she picked one thing to try before our next session. I also arranged for her to present the weekly progress update to the contractor, with me in the room for the first three and then on her own.
By month five she was leading the update without me, and she used two of those situations in her professional review submission. What I changed in my own approach was to stop jumping in. The first time she stalled in a meeting I wanted to rescue her, and I had to accept that letting her recover was more useful.”
Why it works:
- The candidate finds the real goal by asking, which matches the CIPD’s emphasis on questioning and listening.
- An agreed rhythm (every two weeks for six months) signals a genuine relationship, not a single favour.
- The mentee chooses what to try, so she owns her development.
- The reflection is honest about the mentor’s own instinct to take over.
Watch out for: do not claim the mentee’s achievements. “She used two of those situations in her review” gives her the credit and still shows your contribution.
Example 3: When the mentoring did not work at first
Illustrative example. Senior accountant.
“I mentored a junior accountant who was making repeated errors in month-end reconciliations. I assumed it was a knowledge gap, so I spent two sessions walking him through our process. The errors continued.
In the third session I asked him to talk me through his last reconciliation step by step. He understood the process perfectly well; he was working from an old version of the checklist saved on his desktop. Once he switched to the shared version, most of the errors stopped. The remaining ones were in intercompany balances, where he did have a gap, so we used our remaining sessions on that.
He has not had a reconciliation returned for rework in the last quarter. The lesson for me was to diagnose before teaching. I spent two sessions explaining things he already knew, and it probably felt patronising.”
Why it works:
- A story with a misstep is often more credible than a clean success. It shows judgement developing.
- “Talk me through it” is a concrete diagnostic technique the interviewer can picture you using again.
- The candidate separates the process problem from the real skill gap.
- The reflection names the cost of the mistake, including how it may have felt to the other person.
Watch out for: keep the misstep small and resolved within the story. The error is the turning point, not the ending.
Example 4: No formal role at all (student or career changer)
Illustrative example. Final-year student applying for a graduate scheme.
“In my second year I volunteered as a peer tutor for first-year students on our statistics module, which I had found hard myself. One student came to every session but kept failing the weekly quizzes.
I asked her to solve a problem out loud and noticed she could do the calculations but could not decide which test to use. So we built a simple decision flowchart together, using the questions she kept asking, and practised it on past quiz questions until she could choose without looking at it.
She passed the end-of-term exam, and the module leader asked if the flowchart could be shared with the next cohort. I learned that having struggled with the subject was an advantage, because I remembered exactly where I had got stuck.”
Why it works:
- It shows that mentoring does not require seniority, which suits graduate and entry-level applications.
- The tool is built with the student, from her own questions.
- “Until she could choose without looking at it” shows the support was designed to be removed.
Five mistakes that weaken a mentoring answer
- Describing the mentee as a problem. Interviewers notice when someone talks down a colleague. Describe the gap, not the person’s failings.
- Telling a delegation story. Handing someone a task is not mentoring unless you supported their learning while they did it.
- Ending on your own achievement. The result should be what the other person could now do.
- Being vague about method. “I gave her guidance and support” says nothing. Name what you actually did in the sessions.
- Sharing confidential details. Leave out names and anything personal the person told you.
Follow-up questions to prepare for
The National Careers Service advises candidates to “be prepared to answer follow-up questions about the examples you give”. For a coaching or mentoring example, likely follow-ups include:
- How did you know what the person needed?
- What would you have done if they had not improved?
- How did you fit mentoring around your own workload?
- Have you been mentored yourself? What did you take from it?
- How would you mentor someone older or more senior than you?
The last one deserves a sentence of preparation. The CIPD notes that an effective mentoring relationship is one “where there are learning opportunities for both participants”, so it is reasonable to talk about what you learned from the other person as well as what you taught.
Put it on your CV as well
If developing people is a real part of your record, it belongs on your CV, not only in the interview. One line under the relevant role is enough, for example: “Mentored two graduate engineers through their first year; both now lead client progress updates.” You can draft and format that line under the right job in the resumebuilder.ae/ resume builder, and the resume examples library shows how people-development achievements read in different roles.
FAQ
What if I have never formally mentored anyone?
Use an informal example: onboarding a new colleague, peer tutoring, training a volunteer or helping a teammate learn a system. The Civil Service framework expects junior staff to share knowledge with colleagues, not to run mentoring schemes, so an informal example is a fair answer at that level.
Is coaching the same as mentoring for this question?
Not quite. The CIPD describes coaching as “essentially a non-directive form of development” focused on performance, while mentoring involves a more experienced person sharing knowledge, usually over a longer period. Most interviewers will accept either, but use the word that fits your story honestly.
Can I use an example from outside work?
Yes. The National Careers Service says examples “could be from work, home or volunteering”. Pick the one that best shows a deliberate teaching method and a clear change in the other person.
Sources
- Coaching and mentoring factsheet, CIPD
- Success Profiles: Civil Service Behaviours, UK Government (GOV.UK)
- Our Leadership Principles, Amazon
- The STAR method, National Careers Service