Tell Me About a Time You Helped a Struggling Teammate
The question: "Tell me about a time you stepped in to help a teammate who was struggling or falling behind on their work."
Also asked as: "Tell me about someone on your team who was falling behind. What did you do?" · "Who have you helped get better at their job, and how do you know they did?" · "Tell me about a senior engineer you helped step up into a bigger role."
Who's asking: an Engineering Director or Senior Engineering Manager, in a behavioral round.
Executive Summary: The director is deciding whether people around you get better, and how you treat someone who's behind. The strongest signal is how that person comes across in your telling: what you noticed, what you checked before you acted, and what they did next on their own. What changes with level is who you're helping and what has to change: one teammate on one ticket, someone you mentor or on your project and how your team works, then a senior engineer stepping up and the managers around them.
What the director is really asking
Underneath the story, the director is answering three questions of their own:
- "Do people around them get better?" Getting someone through a deadline is different from making them better at the job. The evidence is in their next piece of work.
- "How do they treat someone who's behind?" People who are behind are easy to talk about badly. Directors hear it in "slow", "not very strong" and "needed some hand-holding". They also listen for discretion: handing over a colleague's private troubles to make your story better is a red flag, whoever you are.
- "Do they know when to bring in the manager?" Too soon, and escalation stands in for help. Too late, and you've hidden a problem. Usually the person should know first, though a quiet word about someone's wellbeing may not wait.
This question is about someone's work getting better. If you gave something up for a colleague and improving their work wasn't the point, you're answering a different question.
It maps most closely to Amazon's "Hire and Develop the Best"; treat that as approximate. Three ladder dimensions do most of the work: people (who you're expected to grow), how you treat people, and escalation hygiene.
Level fit at a glance
| SDE | Senior SDE | Staff | Principal | |
|---|---|---|---|---|
| Asked at this level? | Common | Core | Common | Not asked |
| Story scope they expect | A peer on your team, one ticket or pull request | Someone you mentor or on a project you own, and how you helped | A senior engineer stepping up to lead across teams, or how several teams develop people | Not this question: leaders and culture across an org |
| The bar in one line | Notice, ask, help without taking over, and show what they did next | Find the cause before you choose the help, help over time or change how the team works, and say where they are now | Grow a senior engineer into a bigger role, or change how several teams develop people, through managers you don't run; say what you got wrong and what really happened | Judged on the leaders you built and the culture you set |
| Instant down-level | "I took it over and we hit the date", or "I told my lead" and nothing else | "He lacked the skills, so I mentored him", with no check of the cause | A junior you mentored on your own team, or "he wasn't cut out for it" | One senior engineer you coached, with nothing that reached beyond them |
It's Core at Senior because mentoring and raising the team's bar are the job. At SDE and Staff it comes up, but other questions carry more of the signal.
Quick test: swap the names. If they told this story about you, would you feel helped, or handled?
SDE: notice, ask, and keep your hands off their keyboard
What meets the bar
- You noticed something specific, and you can describe it with no judgment attached.
- You asked before you helped. If you didn't, you can say so plainly and say what it cost them.
- They did the work themselves in the end, and you can show how their next piece of work went.
- You knew when to involve your lead, and you didn't speak for your teammate when you did.
- There's a result you can point to, and you can say what the help cost.
Model answer
"Our team ran the weekly order cutoff at a meal-kit subscription company, the deadline when customers can still skip or change a box. A teammate who'd moved over from mobile three months earlier was on day nine of a three-day ticket. Her standup updates had got shorter, and my ticket was waiting on hers.
On a Thursday night, with a release on Monday, I pulled her branch and rewrote most of it. I opened a new pull request and told her it was there to help. She said thanks and closed hers. The next week she stopped asking questions in our channel, and when the next cutoff ticket came up, she said I should probably take it.
That bothered me enough to ask her about it over coffee. She said it had felt like being corrected in front of the team, and she still didn't know why her tests had kept failing. I hadn't thought about either. I told her I'd still raise it if a date was at risk, but with her first, before I touched anything. I asked if she'd take that next ticket, the holiday-week skip handling, and let me sit beside her while she typed. When our lead asked how she was doing, I told him to ask her, and that I'd rewritten her first one without asking.
We did about an hour a day for eight days. She worked out what had been tripping her: our test helper froze the clock in UTC, so correct code failed. I'd been working around that for a year without thinking, which is why my rewrite passed, and I'd never written it down. She fixed the helper herself.
It was slower. A five-day ticket took eleven, the PM had wanted it a week sooner, and my own ticket slipped two days. Complaints about missed skips that holiday week were 12, against about 70 the year before. Her next ticket, sized at four days, took four, with one round of review. She asked me nothing, and she was asking questions in our channel again.
When I help with someone's work, they type and the commit is theirs. I'll sit there as long as they want."
Why this lands at SDE
- "I asked if she'd take that next ticket", and "let me sit beside her while she typed": the level beat. A peer asks another peer, about one ticket, with no authority to assign anything.
- "She said it had felt like being corrected in front of the team": the harm, told from her side, with no argument.
- "I'd still raise it if a date was at risk" and "I told him to ask her": a fair point kept after the apology, and a lead answered without speaking for her.
- "Her next ticket, sized at four days, took four": evidence that she got better, beside a stated cost that disappointed the PM.
Follow-ups to expect
- "Did she ask for your help?": tests whether you helped or imposed → no, not the first time. Say so, and what you asked before the second.
- "How did you decide when to bring in your lead?": tests judgment → "On that Thursday the date was at risk, and I should have raised it, with her first. I didn't." Then what you'd raise now.
- "On her next ticket, when you weren't helping, what happened?": the most dangerous one → the days, the review rounds, and that she was asking the channel, not you.
- "What would she say about you?": tests whether the repair held → what she actually told you, including that the rewrite stung.
Red flags
- ❌ "She couldn't handle it, so I fixed it." It's the rescue story, with contempt on top.
- ❌ Going to your lead before you've said a word to your teammate.
- ❌ "She was so grateful." Thanks isn't evidence. People thank you for rewrites too.
Senior SDE: find the cause before you choose the help
What meets the bar
- The person is someone you mentor, or on a project you own, so you answer for how it goes.
- You checked the cause before you chose the help: load, clarity, tools, confidence, skill, or something that's none of your business.
- You helped them over time, or changed how the team works (plan, reviews, on-call), and you can say what it cost.
- If your manager needed to know, they heard early, and the person knew what you'd say.
- You can say where they are now, honestly. Good and not a triumph is fine.
Model answer
"On a six-person team at an email-delivery service, I led the rebuild of bounce processing, which decides whether a failed send means we stop mailing an address. The engineer who owned bounce classification had three years on the team, and his two-week milestone was in its third week. I'd never seen him do streaming work, so I decided that was the gap. I paired him with a senior engineer twice a week and sent him reading.
Three weeks on it still wasn't done, and he'd got quieter in reviews. The senior engineer told me he knew streaming better than she did. I'd spent three weeks teaching someone what he already knew, in front of a colleague. I told him that and apologised. He said it had been embarrassing. I asked him to walk me through last Tuesday, hour by hour.
He'd had about three focused hours. The rest went on my pairing and on support escalations for the old pipeline, by direct message, about 14 hours a week. I was the one who'd told support to go to him. He mentioned something outside work that had taken the evenings he used to catch up in. That part's his, and he told our manager himself. I told him what I'd say, then told our manager I was moving support's requests off him, and why.
I held one thing. Weeks of 'nearly there' with no flag was a problem, and I needed to hear at the first slip. He agreed, not warmly.
The deal I struck with the PM was no sender-reputation dashboard that half and a launch three weeks later. Escalations went on a rota of the other five, me included, about three hours each. One engineer told me she hadn't joined to do support. He wrote the runbook, which cut the total to about 8 hours a week, and his classifier took wrongly suppressed addresses from 6.1 percent of bounces to 1.4.
He's still on the team and shipped his next two workstreams on time. He hasn't put himself up for senior, and that's his call. He still brings me bad news later than I'd like, and I think those three weeks are part of why."
Why this lands at Senior SDE
- "The deal I struck with the PM was no sender-reputation dashboard that half": the level beat. A tech lead spends their own team's plan and changes a team practice. One team and support, no managers realigned, so no Staff moves.
- "I'd spent three weeks teaching someone what he already knew": the wrong diagnosis, told as something done to a person.
- "That part's his": the discretion a director listens for, in three words.
- "Later than I'd like": no transformation claimed. Directors believe this ending.
Follow-ups to expect
- "What was going on outside work?": tests discretion → "That's his to tell. It mattered because it took away his catch-up time." Then stop.
- "How did your manager see it?": tests escalation hygiene → what they said about the three weeks, that he knew first what you'd say, and that he spoke for himself.
- "Who did you grow on this?": tests whether you overclaim → he isn't a junior, so don't claim you grew him. He wrote the runbook and shipped the classifier, you changed his load, and the late flagging hasn't changed. If they want a mentee, have a junior story ready.
- "What did you give up?": tests trade-offs → the dashboard, three weeks, and a rota one engineer disliked.
Red flags
- ❌ "He needed mentoring, so I mentored him." A fix with no check of the cause.
- ❌ Describing a colleague's health, family or finances in detail. The director wonders what you'd say about them.
- ❌ "He's my best engineer now, thanks to me." Too clean, and the credit's in the wrong place.
Quick check before moving on:
Staff: grow senior engineers through managers you don't run
What meets the bar
- The person is a senior engineer stepping up, or the problem is how several teams develop people. A junior on your own team is Senior scope.
- People stepping up hear what their managers are saying while they can still act on it, as specifically as those managers would say it.
- You align managers you don't run: what the role decides, and who tells the person what.
- You own your part and credit them for what they did. A change of role they chose can be an honest ending.
- Something outlives this one case, in how those teams work.
Model answer
"At a satellite-imagery company, a picture took about seven hours from downlink to customer, across three teams. I proposed an 18-month program to bring it under three, and put forward a senior engineer from ingest as tech lead, his first time across teams. I managed none of the three, and offered to coach him.
The plan was sound, but two teams stopped coming to his review, their leads brought decisions to me, and I answered them. Their managers told me they were losing confidence. He asked me three times how he was doing. I said 'you're getting there', and I told his manager he was growing into it. I'd put him forward, I liked him, and I didn't want to be wrong about him.
At month seven we were a quarter behind. The delivery manager, with a customer date at stake, said she wanted a new lead that week. He said, 'You told me it was going fine.' I had.
That afternoon I gave him what I owed him five months earlier: what each manager had said: that he reopened settled decisions and raised risks only once they'd landed. I told the three managers the soft reports had come from me, not him, and he was owed six weeks with an honest picture. The delivery manager agreed, unhappily, once I said I'd back her call if it wasn't working by week six. I got all three to write down what the tech lead decides, and I sent their leads back to him.
It partly worked. He ran those six weeks himself. One team came back; the other kept checking with me. Then he said he could do the job and didn't want it, and moved to a deep technical role. Another engineer took over, and the teams landed it five months late at 2.8 hours. The slip took 8 percent off a $4 million-a-year renewal. He says he'd have made that call six months sooner if I'd been straight.
The three teams still use that write-up for new tech leads. Next time I'd pass on what managers say the week I hear it. And I wouldn't be the only coach for someone I'd put forward, because I had a stake in hearing he was fine."
Why this lands at Staff
- "I told the three managers the soft reports had come from me, not him": the level beat. Three managers, authority over none, and the candidate spends their own credibility on a senior engineer's growth. "I'd back her call" is what buys the six weeks.
- "I didn't want to be wrong about him": softened feedback, with the personal reason attached and no process language.
- "He could do the job and didn't want it": his decision, his dignity, and no story about him failing.
- "The slip took 8 percent off a $4 million-a-year renewal": about $320,000 a year, an org-level price for the kindness.
Follow-ups to expect
- "Why didn't you tell him sooner?": tests honesty → the personal reason, and what you now do the week you hear something.
- "How did you get the managers to give him six weeks?": tests influence → what you offered the delivery manager: a fixed date, and your backing if it failed.
- "How did his manager take it when you said your reports had been soft?": tests how you handle your own miss with a peer → what they said, what it cost your standing, and how you report on people now.
- "What would he say about you, and how's his work now?": tests whether you'd oversell → that you cost him six months. Say it before they ask, then how he's doing in the role he chose.
Red flags
- ❌ "I mentored a junior on my team." Senior scope, told by a Staff candidate.
- ❌ "He wasn't cut out for it." Contempt, and it skips what you withheld from him.
- ❌ "It worked out for everyone." A move like this has a cost.
Principal: not this question, because they'll ask who you built
Why this isn't a Principal question
At Principal, the ladder's people dimension is building leaders and shaping org-wide engineering culture. Helping one person is worth doing at any level. It says little about either, though how you treat that person still counts.
What they'll ask instead
- "Tell me about a leader you developed. What can they run now that they couldn't before?": whether you build leaders (staff engineers count, not only managers), and whether it lasted once you moved on.
- "What have you changed about how your org develops its engineers, and how do you know it stuck?": whether you shape culture through a mechanism other leaders keep using.
- "Tell me about a senior leader who wasn't working out in a role you'd backed them for. What was your part?": how you treat someone who's behind when the stakes and the embarrassment are both higher.
If it comes up anyway
Answer at your altitude, with your own details: "The example I'd pick is a staff engineer I'd backed to lead across two orgs, who was losing the directors. I told them early what I was hearing, and they [what they did]. It changed how our org prepares people for that jump: [mechanism], which cost [X], and [Y] still isn't working."
Quick check before moving on:
One story, four altitudes
| SDE | Senior SDE | Staff | Principal | |
|---|---|---|---|---|
| Situation | A teammate on day nine of a three-day ticket | A colleague's milestone running weeks late on my project | A senior engineer's first cross-team lead, with two teams drifting away | Not asked. Asked instead: a leader you developed |
| Your role | Peer on the same team | Tech lead of a six-person team | Staff engineer across three teams, managing none | A sponsor of leaders, not one person's helper |
| The key move | Stopped taking over; sat beside her while she typed | Walked through his week; gave up a dashboard for a rota | Told him and three managers the truth, including my part | A practice that grows leaders beyond your own reach |
| Result | Complaints about 70 to 12; next ticket on estimate, unaided | Wrongly suppressed 6.1% to 1.4%; launch three weeks late | 2.8 hours, five months late; he chose a different role | Leaders running scopes they couldn't run before |
| Reflection | They type, and the commit is theirs | He still brings me bad news late; part of that's mine | Pass on what managers say that week; don't be the only coach | What the culture still gets wrong |
Draft your answer
Step 1: Pick the right story
Run each candidate story through the test for your target level:
- SDE: Was it one teammate and a piece of their work, did you ask before you helped (or can you own that you didn't), and can you say how their next piece of work went?
- Senior SDE: Was it someone you mentor or on a project you own, did you check the cause before you chose the help, did you help them over time or change how the team works (plan, reviews, on-call), and can you say where they are now?
- Staff: Did a senior engineer step up with your help, or did several teams change how they develop people, and did managers you don't run agree to something because of you?
- Principal: Don't draft this one. Prepare a story about a leader (a staff engineer counts) now running a scope you developed them for, or a practice other leaders kept using.
Then check that it passes all of these:
- It's from the last two or three years, and you were central to it.
- They'd recognise your version, and you'd be comfortable if they heard it.
- You can tell it without anything private about them.
- There's something observable about their next piece of work, and a number for the work itself.
- Their work getting better was the point, and you know what it cost.
If you're a new grad. A fellow intern, a lab-mate or someone in your project group counts if they were a peer on shared work and you helped them do their part instead of doing it for them. The director expects one person and one assignment, but still wants what you asked first, what they did themselves and how their next task went: "The other intern was three days into a one-day ticket, and hadn't mentioned it in standup."
Aiming a level above your current title? A Senior aiming at Staff can tell the cross-team version only if a senior person was really stepping up, and managers you don't run really agreed to something. If what you have is a junior you mentored well, tell it at its real altitude and show you see the next one: "If I did it now, I'd get their managers to agree what the new role decides before they start." That beats an inflated story that falls apart at "How did the other managers see them?". A Staff aiming at Principal shouldn't stretch this story; bring the leader-building one.
Step 2: Fill the skeleton
SITUATION (15s) — Your scope, who they were (role only), and what was
at stake: ______
NOTICED (10s) — What you actually saw, with no judgment in it: ______
THE CAUSE (20s) — What you checked, what they told you, and how far you
can say it without anything private: ______
YOUR MISTAKE (15s) — What you got wrong, stated as a decision. Include one
thing you'd still insist on, such as hearing about a
slip sooner: ______
ACTIONS (35s) — 2–3 moves, each "I …, because …". What they did
themselves. If your manager came in, when, and whether
they knew first: ______
LEVEL BEAT (inside ACTIONS) — the line only your level could say.
SDE: how you helped on one piece of work while they
kept the keyboard. Senior: how you helped over time,
or what you changed in how the team works, and what
it cost. Staff: what managers you don't run agreed
to, and what it cost you to get it.
RESULT (15s) — One number for the work, what it cost, and who wasn't
happy about it: ______
WHERE THEY ARE (10s) — Their next piece of work, an honest state of things,
and what you do differently now: ______
Aim for about two minutes, two and a half at most, with a 30-second cut ready (what you noticed, the cause, what they did, how their next piece of work went).
Step 3: Calibrate it
| If your answer says… | It reads as… | Fix |
|---|---|---|
| "He was slow", or "she just needed confidence" | Contempt, or a guess presented as a finding | What you saw, what you checked, what they told you |
| "I took it over and we hit the date" | Heroics, and nobody got better | What they did themselves, and how their next piece of work went |
| "I told my manager, and they handled it" | The action was escalation; below the bar at any level, unless the story is about learning when to escalate | Who you spoke to first, and whether they knew |
| A colleague's health, family or money, in detail | Indiscretion, a red flag at any level | "Something outside work", and stop |
| "She's a star now, thanks to me" | A saviour story, and too clean | Their credit, and where they honestly are |
| A junior you mentored, told at Staff | Senior | A senior person stepping up, or a practice across teams, with managers |
| One senior engineer you coached, with nothing that reached beyond them, told at Principal | Staff or below | The leaders you built, or the culture you shaped |
Step 4: Rehearse the follow-ups
Prepare these five, and say each answer out loud once:
- "On their next piece of work, when you weren't helping, what happened?" The most dangerous one. Say what they shipped and how you know. If they didn't improve, say so.
- "Did they want your help?" Whether they asked, and what you asked them first. If you imposed it, own that.
- "What would they say about it?" What they told you, including what stung.
- "How did your manager see it?" When they came in, what they said, and whether the person knew first.
- "What did you give up?" Your own work, a date or a feature, and who was unhappy about it.
Common mistakes
- Telling a rescue. You're not the hero of someone else's bad month. Say what they did themselves, and credit it.
- Oversharing their troubles. Private detail makes a story vivid and makes you sound unsafe. Say why it mattered to the work, and stop there.
- Claiming you grew a peer. "I grew" is a fair claim about a junior and a condescending one about a peer. Say what you changed, and what they did.
Key takeaways
- It tests whether people around you get better, and how you treat someone who's behind.
- Find the cause first, and say what they did themselves.
- The level shows in who you helped and what you had to change to do it.
- You don't need a triumph, only proof of how their next piece of work went.
Test yourself on this question's key ideas: