{"id":905,"date":"2026-10-26T17:55:00","date_gmt":"2026-10-26T16:55:00","guid":{"rendered":"https:\/\/grindloop.ai\/blog\/?p=905"},"modified":"2026-10-26T09:12:28","modified_gmt":"2026-10-26T08:12:28","slug":"teammate-not-pulling-their-weight-interview","status":"publish","type":"post","link":"https:\/\/grindloop.ai\/blog\/teammate-not-pulling-their-weight-interview\/","title":{"rendered":"Teammate Not Pulling Their Weight Interview Question: Cover for Them or Tell Your Lead?"},"content":{"rendered":"<p>Asked about a teammate not pulling their weight, interviewers want to know when the risk surfaced. They also want to know who you told. The answer that scores has three moves in a fixed order. First, you talked to the teammate directly and asked what was blocking them. Second, you agreed on a date and a small next step. Third, when the date slipped, you raised it with your lead. You did that openly, with the teammate aware of it. You framed it as a risk to the release. Two answers lose points. One is quietly doing their work for weeks, because your lead never learned the plan was off. The other is going to your lead before you spoke to the teammate. End on what happened to the work and what you changed afterward. Leave the teammate&#8217;s private reasons out. Those details belong to them.<\/p>\n<h2>The teammate not pulling their weight question asks when your lead found out<\/h2>\n<p>Most candidates prepare this as a conflict question. The scoring also turns on dependability and timing. Google&#8217;s re:Work guide to team effectiveness dates from 2015. It lists dependability as one of five dynamics of strong teams. <a href=\"https:\/\/rework.withgoogle.com\/intl\/en\/guides\/understand-team-effectiveness\" target=\"_blank\" rel=\"noopener\">It defines dependable teams<\/a> as ones whose members &#8220;reliably complete quality work on time.&#8221; A teammate who misses dates breaks that. Your story shows what you do when it breaks.<\/p>\n<p>So the interviewer listens for three things. Did you speak to the person first? Did the people who plan the work learn about the slip while there was still time to act? And what happened to the work in the end? Candidates usually prepare the private conversation. They tend to skip the second point. That is where answers lose ground.<\/p>\n<p>We&#8217;ll use one story through this post. Sofia is an Android engineer building a new checkout screen. Her teammate Ben owns the migration of the app&#8217;s payments module to a new billing API. Her screen calls his new purchase methods. The release is six weeks out. Two sprints in, Ben&#8217;s pull request still isn&#8217;t open. At standup he says it&#8217;s almost done.<\/p>\n<h2>Quietly doing their work hides a delivery risk from your lead<\/h2>\n<p>Sofia&#8217;s first move was the common one. She wrote a temporary adapter so her screen could run without Ben&#8217;s code. She also fixed two of his failing tests in her own pull request. Her work stayed on track. The sprint board still showed the migration as on schedule.<\/p>\n<p>Covering feels like being a team player. Meanwhile your lead keeps planning around a date that is no longer real. <a href=\"https:\/\/handbook.gitlab.com\/handbook\/leadership\/underperformance\/\" target=\"_blank\" rel=\"noopener\">GitLab&#8217;s public handbook page on underperformance<\/a> names this pattern. Its list of warning signs includes other team members starting to work around the person. It also stresses addressing problems early. A week of silent workarounds delays the moment anyone can act.<\/p>\n<p>If your honest story includes a stretch of covering, keep it in. Say how long it lasted and what made you stop. Sofia stopped when she saw the board. Her adapter had made a late migration look on time. Say that in the interview. It shows you noticed what your workaround cost the team.<\/p>\n<h2>Going to your lead first skips the one conversation you owned<\/h2>\n<p>The opposite mistake is escalating straight away. It can sound efficient. Usually it reads as avoiding a hard conversation. It also puts your manager in the middle of something two peers could sort out. And you never learned why the work was late.<\/p>\n<p>The why matters, because the fix depends on it. GitLab&#8217;s handbook gives managers a simple split. Skill-based underperformance means the person doesn&#8217;t know how to do the task. Will-based underperformance means low motivation. A peer can&#8217;t diagnose that alone. But a peer can ask a plain question and listen.<\/p>\n<p>Sofia sent Ben a message and then called him. She was specific about dates. His pull request had been due on the 3rd. Her screen needed his purchase methods by the 17th to make the release. Then she asked what was blocking him. Ben said he was stuck on how refunds should map to the new API. He hadn&#8217;t wanted to ask, because he thought he should already know.<\/p>\n<p>In GitLab&#8217;s terms, that was a skill problem. So they paired for an hour on the refund mapping. They also split his change into two pull requests. Ben agreed to open the first by Thursday.<\/p>\n<h2>Raise the slipped date with your lead, with the teammate in the loop<\/h2>\n<p>Ben opened the first pull request on Thursday. The refund part slipped past the following Monday. At this point a second private chat is not enough. The date now affects the release, so your lead needs to hear it.<\/p>\n<p>How you raise it is what the interviewer is scoring. Sofia told Ben first that she would bring the date to their lead, Ana. She asked whether he wanted to raise it himself at standup. He did. Sofia followed up with Ana in writing that afternoon. Her note had the dates, the dependency and two options. Refunds could move to the next release. Or Sofia could take the refund flow herself.<\/p>\n<p>The note has no judgment of Ben&#8217;s effort. It describes a project risk and gives the person who owns the plan something to decide. Performance itself stays with the manager. GitLab&#8217;s handbook assigns that job to managers, through coaching and private feedback.<\/p>\n<h2>Leave the teammate&#8217;s personal reasons out of your answer<\/h2>\n<p>Sometimes the real cause is outside work. A sick parent, a new baby or a health problem can all slow someone down. Some candidates mention it to show empathy. It usually backfires. The interviewer hears a colleague&#8217;s private life shared with a stranger.<\/p>\n<p>GitLab&#8217;s handbook sets a useful bar here. It asks team members to tell their manager when life circumstances affect their work. It also says they don&#8217;t have to give details. If someone may withhold details from their own manager, you shouldn&#8217;t share them in an interview. One neutral clause is enough. Sofia&#8217;s version says Ben had things going on outside work that aren&#8217;t hers to share.<\/p>\n<h2>Sofia&#8217;s checkout story, start to finish<\/h2>\n<p>Sofia and Ben are invented for this post. The release, the dates and the API details are illustrative, so swap in your own. Spoken at a normal pace, this runs about two minutes.<\/p>\n<blockquote>\n<p>I was building a new checkout screen in our Android app. My teammate Ben owned migrating our payments module to a new billing API. My screen depended on his purchase methods. The release was six weeks out.<\/p>\n<p>Two sprints in, his pull request still wasn&#8217;t open. For about a week I worked around it. I built a temporary adapter and fixed two of his tests myself. Then I looked at the sprint board. It still showed the migration on time. My workaround was hiding a real risk, so I stopped.<\/p>\n<p>I messaged Ben and then called him. I gave him the dates. His change had been due on the 3rd. I needed it by the 17th. Then I asked what was blocking him. He was stuck on how refunds should map to the new API. He also had things going on outside work. Those aren&#8217;t mine to share. We paired for an hour on refunds and split his change into two pull requests. He opened the first one on Thursday, as agreed.<\/p>\n<p>The refund part slipped again. I let Ben know I&#8217;d raise the date with our lead, Ana. I asked if he wanted to bring it up himself. He raised it at standup. That afternoon I sent Ana a short note with the dates and two options. We could move refunds to the next release, or I could take that flow.<\/p>\n<p>Ana moved in-app refunds to the next release. Checkout shipped on the original date. For one release, refunds went through the web. Ben finished refunds the following sprint. I also changed one habit. If I work around someone&#8217;s late piece now, I post it in the team channel that day.<\/p>\n<\/blockquote>\n<p>The covering week stays in the second paragraph on purpose. It makes the later escalation believable. If you never covered, your story can skip that part. The conversation itself gets more depth in our post on <a href=\"https:\/\/grindloop.ai\/blog\/difficult-feedback-to-a-peer-interview\/\">difficult feedback to a peer<\/a>. For the related &#8220;whose job was it?&#8221; probe, see our post on the <a href=\"https:\/\/grindloop.ai\/blog\/ownership-interview-question-whose-job\/\">ownership interview question<\/a>.<\/p>\n<h2>If the teammate was later let go, end on the work<\/h2>\n<p>Some honest versions of this story end with the teammate leaving or being fired. That changes the ending. Don&#8217;t present the exit as your result. An interviewer may hear that you got someone removed. That can overshadow everything before it.<\/p>\n<p>Give the exit one neutral sentence, placed after the work outcome. Something like &#8220;Ben later moved on from the team&#8221; is enough. Never guess at the manager&#8217;s reasons. Never say you saw it coming. Then end on what you changed in your own habits. Sofia&#8217;s channel rule still works as the last line. If the follow-up asks whether you agreed with the decision, say it wasn&#8217;t yours to make. Then say what you did report and when. Sofia raised two dates and two options with Ana. She never discussed Ben&#8217;s performance with anyone.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Teammate not pulling their weight? Talk to them first, raise the slipped date with your lead in the open and keep their private reasons out. Full sample.<\/p>\n","protected":false},"author":4,"featured_media":906,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rank_math_title":"Teammate Not Pulling Their Weight Interview Question: Cover for Them or Tell Your Lead?","rank_math_description":"Teammate not pulling their weight? Talk to them first, raise the slipped date with your lead in the open and keep their private reasons out. Full sample.","rank_math_focus_keyword":"teammate not pulling their weight","footnotes":""},"categories":[10],"tags":[35,75,16,19,18],"class_list":["post-905","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-behavioral","tag-behavioral-interview","tag-conflict-resolution","tag-interview-prep","tag-soft-skills","tag-star-method"],"_links":{"self":[{"href":"https:\/\/grindloop.ai\/blog\/wp-json\/wp\/v2\/posts\/905","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/grindloop.ai\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/grindloop.ai\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/grindloop.ai\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/grindloop.ai\/blog\/wp-json\/wp\/v2\/comments?post=905"}],"version-history":[{"count":1,"href":"https:\/\/grindloop.ai\/blog\/wp-json\/wp\/v2\/posts\/905\/revisions"}],"predecessor-version":[{"id":907,"href":"https:\/\/grindloop.ai\/blog\/wp-json\/wp\/v2\/posts\/905\/revisions\/907"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/grindloop.ai\/blog\/wp-json\/wp\/v2\/media\/906"}],"wp:attachment":[{"href":"https:\/\/grindloop.ai\/blog\/wp-json\/wp\/v2\/media?parent=905"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/grindloop.ai\/blog\/wp-json\/wp\/v2\/categories?post=905"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/grindloop.ai\/blog\/wp-json\/wp\/v2\/tags?post=905"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}