Career path to success - Ep.5: Exclusive interview with Antoine Radiguet

Today, we’re shining a light on Antoine Radiguet and a career journey that perfectly illustrates how growth often comes from curiosity more than from planning. From Software Engineer to Scrum Master, and now Transformation Manager, Antoine has followed opportunities as they appeared, driven by a love for problem-solving, a passion for collaboration, and a constant desire to improve the way teams work together. In this episode, he shares the key moments that shaped his path, what stepping into a broader scope really changed for him, and the mindset that helped him turn a shift in role into a real step forward.

[Sonia Jagourel] You started your career as Software Engineer then Scrum Master and are now a Transformation Manager. Can you walk us through your journey?

I didn’t plan any of it. I genuinely didn’t know where I was going. I became a developer because during my studies I realized I loved problem-solving and algorithms.

Antoine Radiguet

[Antoine Radiguet] I discovered Agile later, a few years into my career, after mostly working solo on projects. Then I joined a mission with Scrum Masters and it was a real turning point. I’ve always enjoyed collaboration and asking the right questions to improve the way we work together. At some point, I had the opportunity to fill in for the Scrum Master in my team, I facilitated my first retrospective, and that threw me straight into the deep end. I also liked the fact that in tech, you can evolve into new roles without being locked into one path forever. So I took my first Scrum Master opportunity and switched roles mid-mission, knowing it wouldn’t stop me from going back to development if I wanted. When I joined Believe, two years ago, discussions about scaling agility came up very quickly, and I was naturally offered a Transformation Manager role moving from one team to an organization-wide scope. It was a complete discovery, and I ended up really enjoying it.

[Sonia Jagourel] What motivated you to take on this Transformation Manager role?

[Antoine Radiguet]I’ve always loved exploring topics, digging deeper, and asking myself: how could this work not only in my team, but across other teams too? At Believe, we operate in tribes, so it feels natural to apply good practices in one tribe and help them spread. It’s very rewarding because the work impacts more people. But it’s also a different scale of challenges, so it requires more reflection and a different mindset. I also really enjoy meeting people with different expertise, this role is very cross-functional and allows me to work with many business and domain experts.

[Sonia Jagourel] How did the transition, Scrum Master to Transformation Manager, process go for you?

[Antoine Radiguet] The transition process itself was smooth, but the real shift was in posture. As a Scrum Master, everything is structured, paced by rituals, and highly organized. As a Transformation Manager, the rhythm feels closer to what I experienced as a developer: you have projects, tasks to complete, and you deliver progressively over time. The difference is that I’m much more autonomous in how I organize my work and approach topics. But I still have Jira and assigned tickets, so in a way it felt like going “back to the past”, just with a completely different scope.

[Sonia Jagourel] Looking back, what were your biggest challenges and how did you overcome them?

[Antoine Radiguet] The biggest challenge was learning to step back. As a Scrum Master, you’re immersed in the daily life of a team and its day-to-day problems. As a Transformation Manager, you have to think further ahead about the timeline changes because you’re trying to build deep, long-term organizational changes. Everything becomes bigger: you need time to explain expectations clearly, be pedagogical, and convince people to commit to the journey. You also need to introduce topics gently, without being too abrupt, so people can build long-term advocacy rather than short-term compliance. As a Scrum Master, there’s more flexibility to test and learn quickly. As a Transformation Manager, you still have the right to make mistakes, but because the timeframe is longer, the impact of failure can be much larger, so you have to bring meaning, strategy, and structure to what you do.

[Sonia Jagourel] Have there been any standout moments or accomplishments you’re particularly proud of?

[Antoine Radiguet] I’m proud that I quickly felt I could be useful to my multidisciplinary team. I felt in the right place, and confident I could bring something personal and valuable. I’m also proud of a project where I introduced a full philosophy around habits during an internal conference, turning it into a talk and an advocacy moment for that mindset. And I’m proud of being recognized by other teams and building strong relationships across the organization.

[Sonia Jagourel] What are you most excited to learn or contribute to this new role?

[Antoine Radiguet] The topics I can work on are much broader than what I covered as a Scrum Master. My impact can be much wider, and there are so many subjects I’ll be able to explore. I’m genuinely excited about what comes next.

[Sonia Jagourel] How does this move align with your career goals?

[Antoine Radiguet] In one of my previous experiences, there wasn’t a strict distinction between Agile Coach and Scrum Master, so I naturally moved into a more “trainer” posture, supporting product teams and broader engineering teams. I really loved that role. I also worked on project framing, which was something I found very motivating. With this internal move, I feel like I can reconnect with that same energy, and it’s exactly the direction I wanted to go in.

[Sonia Jagourel] What advice would you give to colleagues considering an internal move?

[Antoine Radiguet] Prove what you’re capable of before even starting the conversation. If I look back at my move from developer to Scrum Master, I was already doing Scrum-related tasks while I was still a dev. And when I became a Scrum Master at Believe, I naturally stepped beyond my team scope and started thinking about the broader organization. I became interested in how different teams interact, and I didn’t hesitate to share my ideas and observations with my manager, especially around scaling agility inside the tribe. That’s how I was identified for a Transformation Manager role, and that’s what triggered my move. So, my advice is simple: don’t limit yourself to the bullet points of your job description, think bigger!

Back to home +

Career path to success - Ep.5: Exclusive interview with Antoine Radiguet

Similar content