My MVP Story: From Software Engineer to Microsoft MVP
When I started my career in 2018 as a Software Engineer in Bangladesh, I never imagined that one day I would become a Microsoft Most Valuable Professional. My journey didn't begin with that goal. It began with something much simpler: I loved technology, I loved learning, and I loved helping other people learn. Where My Journey Started I began my professional career in 2018. Early on, I started working with Microsoft technologies, particularly Power Platform, Dynamics 365, Power Apps, Power Automate, and Dataverse. Like many developers, my focus at first was mostly technical. I wanted to understand how things worked, solve real business problems, and become a better developer. But there was another part of me that had been there long before I entered the tech industry: I loved teaching. Teaching Was Always Part of Me Growing up in Bangladesh, I spent a lot of time tutoring students. There was something rewarding about watching someone struggle with a topic, explaining it a different way, and then seeing the moment they finally understood it. That feeling never left me. Even after becoming a software professional, I didn't want to keep what I learned to myself. Whenever I picked up something useful, I wanted to explain it to someone else. That instinct eventually pointed me toward one of my career goals: becoming a Microsoft Certified Trainer (MCT). Teaching Was Always Part of Me Growing up in Bangladesh, I spent a lot of time tutoring students. There was something rewarding about watching someone struggle with a topic, explaining it a different way, and then seeing the moment they finally understood it. That feeling never left me. Even after becoming a software professional, I didn't want to keep what I learned to myself. Whenever I picked up something useful, I wanted to explain it to someone else. That instinct eventually pointed me toward one of my career goals: becoming a Microsoft Certified Trainer (MCT). Starting a New Chapter in Canada In April 2024, I moved from Bangladesh to Canada, a major transition, both personally and professionally. As I adjusted to a new environment, the organization I worked with also gave me room to explore new technologies and ideas. My work gradually expanded from Power Platform and Dynamics 365 into AI, Microsoft Copilot Studio, intelligent automation, and AI agents. And eventually, I achieved something I'd wanted for a long time: I became a Microsoft Certified Trainer. It was meaningful because it connected two parts of my life: my technical career and my love of teaching. From Learning to Sharing Becoming an MCT wasn't the finish line, it was a launchpad. I started writing technical blogs and articles, sharing tutorials, organizing free community sessions, and building hands-on demos to explain complex Microsoft technologies in ways beginners could actually follow. The more I shared, the more I learned. That became one of the most important lessons of this journey: teaching is one of the best ways to learn. When you prepare to teach someone else, you can't stop at knowing which button to click. You need to understand why something works, when to use it, what can go wrong, and how to explain it clearly. My community work increasingly centered on Copilot Studio, Power Platform, Dynamics 365, Power Automate, Dataverse, AI agents, and practical AI automation. My articles and tutorials became another way to give back to the wider Microsoft community. The Person Who Helped Me Understand the MVP Journey An important turning point came when I met Frank Falvey. Frank helped me understand something I hadn't fully grasped before: becoming an MVP isn't simply about being technically strong. It's about community contribution. He guided me on how to contribute meaningfully and encouraged me to keep sharing what I knew. I followed that guidance. I kept writing. I kept teaching. I kept running community sessions and creating content. And most importantly, I kept trying to help people learn. Eventually, Frank nominated me for the Microsoft MVP award. I'm deeply grateful for his mentorship, encouragement, and belief in me, and equally grateful to Mushi Bhuiyan, whose support has meant so much throughout this journey. The Email I Will Always Remember Then came a moment I'll never forget: I received the acceptance email. I had been awarded the Microsoft Most Valuable Professional award in Copilot Studio. For a few moments, it was hard to believe. I thought about the journey from Bangladesh to Canada. I thought about starting as a Software Engineer in 2018, the evenings spent learning new technologies, becoming an MCT, and every blog post, tutorial, free session, demo, and conversation along the way. Suddenly, all those small steps connected. The MVP recognition wasn't the result of one big achievement. It was the result of learning, sharing, teaching, and contributing, consistently, over time. MVP Is Not the Destination Receiving the Microsoft MVP award is one of the proudest moments of my professional journey. But I don't see it as a finish line. I see it as a starting point. It gives me even more motivation and responsibility to keep learning and contributing. Technology is changing incredibly fast, especially with AI and AI agents. There will always be another technology to learn, another problem to solve, another article to write, another session to deliver, and another person who needs help getting started. That's what excites me about what comes next. My goal is to keep building practical solutions with Microsoft Copilot Studio, Power Platform, Dynamics 365, AI, and automation, while sharing what I learn along the way. I want to help more people move from "I don't know how to do this" to "I built it." What This Journey Taught Me If there's one lesson I'd share with someone who wants to become an MVP someday, it's this: Don't start by chasing the award. Start by helping people. Learn something. Build something. Share what you learned. Write an article. Create a tutorial. Answer someone's question. Deliver a community session. Help a beginner build their first solution. Then do it again. You don't have to know everything before you start contributing, I certainly didn't. You just need to be willing to share what you know today, while continuing to learn what you don't know yet. For me, becoming a Microsoft MVP is an achievement. But more importantly, it's a new beginning. My journey continues: Learn. Build. Teach. Share. Empower. And I'm excited to see where it takes me next.
