0 day streak

BEHAVIORAL · GROWING OTHERS

Tell me about someone you mentored. What changed for them?: sample answer

Whether you can see what someone specifically needs, help them grow without doing the work for them, and point to a concrete change in what they can do. The focus should be on their growth, not on how helpful you were.

Also asked as

  • Tell me about a time you helped a teammate succeed.
  • Tell me about someone you mentored. What changed for them?
  • Describe how you assess or help hire a new team member.

The short version: Show a specific person you helped grow and what changed for them.

Sample STAR answer

An invented example from typical software engineering work, about 250 words, around two minutes spoken. Use the structure, not the story: yours should be real.

Situation A new graduate engineer joined my team and was struggling. Their pull requests were large, often over a thousand lines, so reviews took days and came back with dozens of comments. They had started to go quiet in team meetings.

Task My manager asked me to be their mentor for their first six months. My goal was for them to ship independently and feel confident in the team.

Action In our first one-to-one I asked what felt hardest, rather than telling them what I had seen. They said they waited until a change felt "finished" so reviewers would not think badly of them. So the first thing I worked on was splitting work. We took their next feature and planned it together as five small pull requests, each one reviewable in fifteen minutes. I reviewed their first few the same day so the faster cycle felt rewarding. I paired with them for an hour a week on whatever they chose, and I stopped giving answers after the first month; instead I asked what they would try first. After three months I suggested they own a small internal service end to end, including its on-call runbook, and I stayed in the background.

Result Within two months their average pull request was under 200 lines and reviews took less than a day. By month five they led a small feature with two other engineers and presented it at our team demo. They now mentor the next new graduate, using the same small pull request approach.

Weak answer vs strong answer

Weak

"I have mentored many junior engineers. I always make time to answer their questions and help them when they are stuck, and they have all grown a lot."

Why it scores low: It is general and about you being available, not about one person's growth. There is no diagnosis of what they needed, no approach, and no specific change in their work.

Strong

A specific situation, an action you took yourself, the reasoning behind it, and a result with a number. Show a specific person you helped grow and what changed for them.

How the story changes with level

SDE 1

At SDE 1, helping an intern or new joiner get set up, or teaching a teammate a tool you know well, is a fair answer. Keep it specific.

Senior and staff

At senior or staff level, show that you grew someone into a role, such as a project lead, and that you built mentoring into the team, for example an onboarding plan or a review guide others use.

SDE 1 interviews · Senior interviews · Staff interviews

Follow-up questions interviewers ask

  1. How did you know what they needed?Show you asked and listened before giving advice.
  2. How did you avoid doing the work for them?Describe moving from answers to questions as they grew.
  3. Tell me about a time mentoring did not work.Be honest about a mismatch and what you changed or who you involved.
  4. How do you give difficult feedback to someone you mentor?Specific, private, soon after the event, with a clear next step.

Amazon Leadership Principles that test this

Hire and Develop the Best · Tell me about a time you helped improve hiring or developed someone on your team.

Raise the level of talent with every hire and promotion, spot strong people, and take developing others seriously.

Situation Our team was hiring four engineers. Interviewers each asked their own favourite questions, and debriefs often ended in arguments because people had judged different things.

Task I was one of the regular interviewers, and I wanted our decisions to be fairer and better at predicting how people would do on the job.

Action I collected the questions from our last twenty interviews and grouped them by what they tested. We were asking a lot of puzzle-style questions and almost nothing about debugging or reading existing code, which was most of our real work. I proposed two changes: a debugging exercise using a small, realistic codebase, and a written rubric for each round that described what weak, good and strong looked like. I ran a practice session where five interviewers scored the same recorded mock interview, and we adjusted the rubric until our scores were close. I also offered to shadow and coach two newer interviewers.

Result Debriefs became shorter and more focused on evidence. Of the four engineers we hired that half-year, all were rated as meeting or exceeding expectations at their first review, and the two newer interviewers became fully independent within a month.

Tip: Show you raised the bar with a system, such as a rubric or a coaching plan, not just that you interviewed people.

All 16 Amazon Leadership Principles with sample answers

Companies that test this

Prepare your own

Write your story in the story bank and tag it "Growing others"; it will show up against every company value that tests this theme.

Related: Collaboration and inclusion · High standards

All behavioral themes · How the behavioral round is scored