{"id":3347,"date":"2020-05-09T09:38:33","date_gmt":"2020-05-09T13:38:33","guid":{"rendered":"https:\/\/blog-alexis.monville.com\/en\/?p=3347"},"modified":"2026-01-25T10:48:52","modified_gmt":"2026-01-25T15:48:52","slug":"grow-your-software-engineering-career-with-emilien","status":"publish","type":"post","link":"https:\/\/blog-alexis.monville.com\/en\/2020\/05\/09\/grow-your-software-engineering-career-with-emilien\/","title":{"rendered":"Growing as a Software Engineer: Learning, Sharing, and Impact"},"content":{"rendered":"\n

Career growth in software engineering is often described as a matter of accumulating technical skills, mastering new tools, or moving into more complex systems.<\/p>\n\n\n\n

In reality, the journey is more nuanced.<\/p>\n\n\n\n

In this episode of Le Podcast on Emerging Leadership<\/em>, I had the pleasure of welcoming Emilien Macchi<\/strong>, Senior Principal Software Engineer at Red Hat, to discuss how learning and sharing have shaped his career.<\/p>\n\n\n\n

Learning as a continuous practice<\/h2>\n\n\n\n

Emilien is a long-time contributor to OpenStack<\/strong>, having been involved nearly since the inception of the project. Originally from France and now based in Canada, he has built his career in distributed, open-source environments.<\/p>\n\n\n\n

A recurring theme in our conversation is that learning never stops<\/strong>. And more importantly, learning rarely happens alone.<\/p>\n\n\n\n

We discuss how practices such as:<\/p>\n\n\n\n

    \n
  • peer reviews<\/li>\n\n\n\n
  • pair programming<\/li>\n\n\n\n
  • open discussions<\/li>\n\n\n\n
  • and shared problem-solving<\/li>\n<\/ul>\n\n\n\n

    contribute not only to better code, but to better engineers.<\/p>\n\n\n\n

    Collaboration, including remote work<\/h2>\n\n\n\n

    Emilien shares a perspective that may surprise some: he believes that collaboration can be easier and better in remote contexts<\/strong>.<\/p>\n\n\n\n

    We explore why remote work, when supported by the right practices, can:<\/p>\n\n\n\n

      \n
    • improve focus<\/li>\n\n\n\n
    • encourage clearer communication<\/li>\n\n\n\n
    • and create more inclusive collaboration<\/li>\n<\/ul>\n\n\n\n

      This naturally connects with earlier conversations on distributed teams and asynchronous work.<\/p>\n\n\n\n

      Growing beyond technical skills<\/h2>\n\n\n\n

      Of course, I also asked Emilien what he believes are the most important things to develop as a software engineer.<\/p>\n\n\n\n

      The answer goes beyond technical skills.<\/p>\n\n\n\n

      We talk about:<\/p>\n\n\n\n

        \n
      • communication<\/li>\n\n\n\n
      • curiosity<\/li>\n\n\n\n
      • responsibility<\/li>\n\n\n\n
      • and the ability to learn with others<\/li>\n<\/ul>\n\n\n\n

        These capabilities shape long-term impact far more than any specific technology.<\/p>\n\n\n\n

        A reflection on practitioner leadership<\/h2>\n\n\n\n

        As Emilien was also one of the first people to leave a written review on Goodreads, I asked him what he thought of I am a Software Engineer and I am in Charge<\/em>.<\/p>\n\n\n\n

        This led to a broader reflection on responsibility, ownership, and how engineers can increase both their impact and satisfaction at work.<\/p>\n\n\n\n

        A final thought<\/h2>\n\n\n\n

        If you are a software engineer wondering how to grow without chasing titles or hype, this episode offers a grounded and inspiring perspective.<\/p>\n\n\n\n

        Growth, as Emilien shows, is less about standing out and more about learning, sharing, and contributing over time<\/strong>.<\/p>\n\n\n\n