Low Contribution Teammate
Last Updated: June 4, 2026
Medium Priority
8 min read
AI Mock Interview
Practice this question in a realistic, spoken behavioral interview.
Question
Tell me about a time a teammate was not contributing enough or pulling their weight. How did you handle it?
A useful version of this story sounds like peer support before it sounds like performance management. Pick a moment where the teammate's contribution issue was visible in the work itself, not just in your frustration. Walk through the pattern you noticed, the private question you opened with, the concrete help you offered, and the threshold where you would have brought a manager into the conversation.
What the Peer Support Needs to Show
The answer should sound like peer support before performance management:
- Start with curiosity: Low contribution often has a cause: unclear scope, skill gap, personal issue, overload, or blocked dependency.
- Keep the first conversation private: Public callouts damage trust and rarely improve performance.
- Offer concrete help: Pairing, unblocking, clarifying scope, sharing context, or splitting work beats vague encouragement.
- Treat it as a team delivery risk: Frame the issue around the work and the team's commitments, not the person's worth.
- Know when it becomes a manager issue: Peer support has limits. Explain where you would escalate if the pattern continued.
Where This Answer Usually Goes Wrong
This question scores against Earn Trust, Has Backbone, and Builds Awesome Teams. The common ways candidates lose points:
- Manager-first escalation: "I went to my manager and explained the situation" as the opening move signals that you cannot resolve peer-level issues yourself. At L5+, this almost always downgrades the Influence and Earn Trust signals. Save escalation for after you have a story of peer-level effort.
- The "I worked around them" story: "I just picked up their tickets and got the project done myself" sounds heroic but counts as poor judgment, because it enables the underperformer instead of addressing the situation. It burns you out, hides the problem from leadership, and leaves the team in a worse place.
- The public callout: "In our team standup, I pointed out that his tickets were still not done" comes across as toxic. Even when the underlying point is correct, the delivery is the disqualifier. Behavioral committees flag this as a Builds Awesome Teams concern.
- No curiosity about the cause: Strong answers consider the possibility that the teammate was overwhelmed, blocked, dealing with something personal, or working from unclear scope. Stories where the candidate assumed laziness from the start downgrade the Empathy and Earn Trust signals.
- Only modeling the easy case: The default sample is "a junior engineer needed pairing." A good answer is ready for the harder variants too: a senior engineer who is checked out, a long-tenured favorite who underperforms, a teammate whose situation did not improve after your help. Follow-up questions tend to push toward exactly these.
- The clean resolution every time: A story where the teammate responded to one conversation and turned it around feels implausible. Real performance issues often take months or never fully resolve. A small admission that the change was partial, slow, or eventually needed a manager makes the story more believable than a fairytale arc.
- Confusing peer support with peer evaluation: Telling the teammate "you're not pulling your weight" in a private conversation is not the same as offering help. The first is feedback (which is your manager's job in most companies); the second is collaboration. Strong answers stay on the help side of that line.
How to Approach the Teammate
The Action section should start with curiosity and stay close to the work. Show the private conversation before any formal escalation.
- Assume positive intent and observe: Start from the assumption that your colleague is not lazy or malicious. They are likely struggling with something. Observe the specific behaviors.
- Ask privately and with curiosity: Initiate a private, informal, one-on-one conversation. Tone should be concern, not accusation. Use "I" statements and focus on observable facts.
- Offer specific, actionable help: Based on the conversation, offer concrete support. This is the step that turns a potential conflict into a collaborative solution.