Tell me about a time when you had to lead a team or project

In my last internship, I was asked to add a small admin page for support agents, and near the end I realized the work was getting stuck because the requirements were split across messages from design, my mentor, and support. I pulled the open questions into one document, proposed my best understanding of each one, and set up a short meeting with the two people involved so we could resolve them quickly. After that, I broke the remaining work into a few clear steps, coordinated testing with another intern, and kept my mentor updated on anything that could affect the deadline. We found one issue late in testing, so I shifted my time to fix the core problem first and moved a lower-priority polish item out of scope. We launched on time, and the support team started using it that week. That experience taught me that even as a junior engineer, leadership can mean creating clarity and momentum when a small project starts to drift.

At my last job at a small nonprofit, I was asked to help coordinate a volunteer website update for an upcoming fundraiser, and our team was very part-time, so nothing was moving unless someone kept it organized. I took the lead on keeping the schedule together by making a simple task list, checking in with the designer and the content writer twice a week, and making sure everyone knew what depended on what. When our event date got moved up, I spoke with the staff member in charge of donations and helped narrow the update to the most important pieces so we could finish on time. I also tested the pages myself and flagged a few broken links before launch, which saved us from confusing visitors. The site went live the day before the event, and the team told me it made a big difference in how smoothly things ran. That project showed me I’m good at being the person who keeps a small team focused and moving, even when everyone is balancing other responsibilities.