From Researcher to Developer: Learning to Work as a Team

It’s Amy here. I am a software developer based in the Netherlands. 

Today, I am blessed with the beautiful spot Karlingse Bos, the largest city park in Rotterdam. So, I would like to share something insightful with you.

I have a very long education history in the medical field, but now, working as a software developer feels surreal to me.

I just realized an essential difference between these two careers: medical scientist vs software developer. If you are interested in this topic, please continue to read this blog.

---

Transitioning from scientific research to my first job as a developer has been an eye-opening experience. Before this, I was a medical researcher and doctor, accustomed to diving deep into challenges independently. In research, it wasn’t unusual to spend weeks reading hundreds of papers just to complete a single study. I relished figuring things out independently, rarely asking for help unless I had exhausted every possible avenue.

However, working as a developer in an Agile team has taught me the value of collaboration and a completely different approach to problem-solving.

---

Adjusting to Agile and Teamwork

As a developer, tasks are broken down into smaller, manageable pieces within short sprint cycles, typically lasting two weeks. Each task has a defined scope and time frame, and the expectation is to deliver work quickly and iteratively. Unlike research, where I had weeks to tackle a problem, here, I often have just a few hours or days to complete a task.

Initially, I struggled with this fast-paced environment. My instinct was to isolate myself, quietly grappling with challenges on my own, just as I had done in research. But this approach didn’t work well in a team setting. When I spent too much time stuck on a problem, it impacted the entire team’s progress.

---

The Importance of Asking for Help

One of my biggest lessons is that it’s okay to ask for help—and to ask early. Some problems that took me hours to solve could have been resolved in minutes by a more experienced teammate. The fear of appearing incapable or unskilled often held me back, but I’ve realized that collaboration is key in software development.

Now, I focus on these principles:

• Limit Struggling Periods: If I’m stuck for more than a reasonable amount of time, I reach out for help instead of letting the task drag on.
• Open Communication: During daily stand-ups, I share my progress honestly, even if it’s just to say, “I’m stuck on this task.” This keeps the team informed and encourages support.
• Team Transparency: Isolating myself doesn’t help anyone. By being open about challenges, I can benefit from the team’s collective knowledge.

---

Overcoming the Fear of Judgment

At first, it was intimidating to admit I couldn’t solve something. But I’ve learned that struggling with a task doesn’t mean I’m incapable. Sometimes, what seems impossible to me is a simple fix for a more experienced engineer. And that’s okay—learning from those moments is part of growing as a developer.

---

Final Thoughts

Working in an Agile environment has completely shifted how I approach challenges. It’s not just about solving problems—it’s about solving them together as a team. I’ve learned to embrace collaboration, ask for help, and focus on progress rather than perfection.

While the transition from research to development has had its hurdles, it’s been gratifying to grow in this new role. For anyone making a similar shift, remember teamwork and communication are just as important as technical skills. Don’t be afraid to ask for help—your team is there to support you.