Describe a situation where a team member was struggling and what you learned from it

On a project at my last internship, another intern and I were splitting up a small internal tool, and I noticed he had been stuck on his part for a couple of days and had gone pretty quiet in our chat. I asked if he wanted to walk me through what he had tried, and that made it clear he wasn't avoiding the work—he was confused by an older service that barely had any documentation. We paired for a bit, I shared the notes I'd made when I first learned that area, and then we pulled in our mentor to confirm one design choice instead of guessing. After that he was able to finish the task himself, and we still hit our deadline. What I learned was not to assume a lack of progress means a lack of effort; now when someone seems stuck, I try to understand whether they need context, not just answers.

At a small startup where I was the most junior engineer on a three-person team, one of my teammates started missing small deadlines and seemed increasingly frustrated with routine tasks. When I offered to pair for a bit, he showed me that our automated build-and-test system was flaky and took a long time to give feedback, so he was spending hours chasing transient failures instead of actually making progress. I reproduced the problem locally, tracked down a timing bug in a test helper, and fixed the test so it no longer failed intermittently; I also wrote a short script teammates could run quickly before committing and documented the steps. After that he could move forward without the repeated wasted effort and we shipped the feature on time. I learned that not all struggles are about skill—sometimes small, practical improvements to tooling and process unlock a lot of productivity and confidence.