Behavioral Interview: Tell Me About a Time You Coached a Teammate Through a Skill Gap

Prompt and context

Tell me about a time a teammate had a skill gap on an important task. How did you diagnose it, design coaching, create practice opportunities, and prove that the teammate could deliver independently?

This tests coaching, feedback, delegation, and accountability for outcomes. Amazon's “Hire and Develop the Best” asks leaders to take coaching seriously and create mechanisms for development; Google re:Work describes learning as a process requiring motivation, practice opportunities, and continuous feedback. Your answer should show capability transfer rather than you completing the task for someone else.

What the interviewer is testing

• Separating a knowledge gap, confidence issue, process blocker, and unclear ownership.
• Asking about the person's goal before designing individualized, practice-based support.
• Giving timely, specific, respectful feedback while increasing the person's ownership.
• Proving growth with independent delivery, quality, time, or a reusable mechanism rather than gratitude alone.

Questions to clarify first

• What task, customer commitment, or team goal did the gap affect?
• What was your relationship and authorization boundary, and had the person asked for help?
• Was the gap knowledge, tooling, judgment, communication, or process? How did you verify it?
• What could be measured without exposing private information, and who owned the work afterward?

A 30-second answer

I would describe the task and impact, diagnose the real gap through questions, observation, and a small exercise, then agree on a goal and time box. I would use demonstration, paired practice, short feedback, and staged delegation so the teammate completed the next step rather than I doing it. Finally, I would have the teammate deliver a real but controlled outcome and use quality, rework, time, or reuse evidence to show the change. I would also explain how I turned the lesson into a team mechanism.

Step-by-step deep dive

Choose a real, bounded situation

Use an example with a clear task, impact, and time window. Do not turn “I trained a new hire” into a course description; explain how the gap blocked delivery, who held final accountability, and why your involvement was appropriate. Remove personal details while preserving verifiable outcome facts.

Diagnose before giving answers

Use open questions, work-sample observation, and teach-back to distinguish “cannot do,” “has not done,” missing context, fear of mistakes, and an environmental blocker. Restate your diagnosis and ask the teammate to confirm it so your preference is not mistaken for the standard.

Turn the goal into practiceable behavior

Break the large task into an observable skill such as writing a query plan, adding tests to a change, leading a drill, or explaining a risk. Define a completion condition and checkpoints; keep the scope small enough for a short practice cycle and feedback.

Use demonstration, practice, and feedback loops

Demonstrate one reasoning pass, then let the teammate teach it back or complete an adjacent task. Describe behavior, impact, and next action; avoid personality labels such as “not proactive.” Google re:Work recommends personalized one-to-one coaching and continuous feedback to improve learning.

Increase ownership instead of becoming a permanent fallback

Pair on the first round, let the teammate lead while you observe on the second, and have them deliver independently on the third with agreed checkpoints. Make approvals and escalation triggers explicit so coaching does not create a hidden single point of dependency.

Verify growth and build a mechanism

Have the teammate complete a real task independently and compare quality, rework, delivery time, help requests, or customer outcomes. If the result is stable, put the checklist, example, office hour, or peer-learning mechanism into the team workflow; if the gap remains, adjust the goal instead of declaring failure.

{
  "goal": {"skill": "independently lead a release drill", "checkpoints": 3},
  "evidence": {"reworkRateBefore": 0.3, "reworkRateAfter": 0.1, "owner": "teammate"}
}

Example of a strong answer

During a cross-service release, a teammate was unfamiliar with rollback drills, causing repeated rework in preparation. I asked them to explain the current process and walk through a small sample; that showed the gap was risk ordering and check sequencing, not missing access. We agreed that they would independently lead a drill within two weeks. I demonstrated how to list prerequisites and stop conditions, then had them lead the next drill while I asked questions only at checkpoints and gave same-day feedback. They led the third drill independently, rework fell from 30% to 10%, and they checked the runbook into the team repository. That result showed capability transfer and turned one-off help into a reusable mechanism.

Common mistakes

• Saying “I completed the task for them” without showing practice or independent delivery.
• Recommending a course or document without diagnosing the gap or verifying learning.
• Using labels such as “bad attitude” or “not smart enough” instead of behavior evidence.
• Turning coaching into public embarrassment or forced demonstration and ignoring psychological safety.
• Reporting thanks but not quality, time, rework, or ownership transfer.
• Failing to explain how you changed scope, escalated risk, or protected delivery when coaching did not work.

Follow-ups and responses

What if the teammate does not want your coaching?

Ask about their goal, concerns, and preferred learning style, then explain the task impact and available support choices. Start with a short exercise and let them choose the time and topic. If delivery risk is already material, clarify ownership and support boundaries with the manager rather than disguising control as help.

What if feedback does not lead to improvement?

Return to diagnosis: was the goal too large, was the feedback specific, and were practice opportunities, access, or context missing? Narrow the task, add observation points, or change the teaching method. If the role expectation and current responsibility do not match, escalate early and adjust delivery plans.

How do you avoid making the team dependent on you?

Use staged-delegation checkpoints, let the teammate lead real work, and put checklists, examples, and decision rules in a shared location. Track help requests, independent delivery, and whether the person can coach someone else to confirm the knowledge left your personal memory.

How do you handle sensitive performance information during coaching?

Share only what is needed to complete the task, discuss personal feedback privately, and record observable behavior rather than labels. Follow company processes for formal performance, health, or privacy matters and involve only necessary managers; never expose the person in a public forum.