Tell me about a time you had to adapt to a significant change in technology or tools you were using

In my first full-time role, our team moved from mostly manual testing to an automated testing tool I hadn't used before, right in the middle of a feature I owned. It was a significant change for me because my old approach was to test things by hand and rely on reviewers to catch gaps. I spent a day building a small sample test suite for one simple part of the feature so I could understand the setup, failure messages, and how to run it locally before converting the rest. I also wrote down the commands and patterns I kept forgetting so I wouldn't ask the same questions twice. After that, I was able to add tests for my feature on my own, and my next few reviews had much less feedback around missing coverage. The bigger thing I learned was to start with one safe slice of a new tool and make myself productive there before applying it more broadly.

During a summer internship, the team I was helping on switched from a spreadsheet-based tracking process to a new project management tool partway through a small reporting task I owned. At first I was frustrated because I knew the old spreadsheet well and the new tool changed how we assigned work, checked status, and attached files. I took one afternoon to sit with the project coordinator, watch how they used it, and then recreate my own task list in the new format so I could see the differences side by side. I also asked for one simple rule to follow for updates so I wouldn’t miss anything while learning. After a couple of days, I was able to keep my work organized in the new system and help one other intern get set up too. What I learned was that when tools change, it helps to focus on understanding the team’s new workflow, not just the buttons in the software.