Becoming a Microsoft MVP (Most Valuable Professional) is a goal for many in the technical community. It represents a bridge between professional expertise and community advocacy. Recently, I was honored to receive this award for my work with Azure Kubernetes Service (AKS). However, the road to getting that trophy wasn’t a straight line. It involved a high-volume content schedule, a very painful rejection, and a deep focus on a specific niche.
How the MVP Process Actually Works
The MVP award isn’t something you can simply “sign up” for; it is a recognition of community contributions made over the previous 12 months. These contributions can take many forms:
- Content Creation: YouTube videos, blog posts, or technical articles.
- Public Speaking: Presenting at local meetups or large-scale conferences.
- Open Source: Contributing to GitHub repositories or Microsoft documentation.
- Community Leadership: Organizing events or helping others in forums like Reddit.
To start the process, you must be nominated by an existing MVP or a full-time Microsoft employee. Once nominated, you submit a summary of up to 24 contributions. This part is critical—the impact of these contributions is what matters. Speaking to 10,000 people has a different weight than speaking to five, but every bit of consistent community help counts toward your case.
The Benefits: Beyond the Trophy
While the physical trophy and the “date disks” for each year in the program are great, the real value lies in the access.
- Networking: You gain access to a global network of experts via a private Microsoft Teams environment.
- Product Insights: MVPs often get a “behind the curtain” look at upcoming features and can provide direct feedback to Microsoft product groups under NDA.
- Software & Tools: The program provides licenses for Visual Studio Enterprise, Office 365, and third-party learning platforms like Pluralsight.
The “Lows”: Handling Rejection
Many people only share the success story, but my first attempt in 2022 ended in failure. Despite publishing 52 long-form blog posts and having a GitHub repository with hundreds of stars, I was rejected.
The most difficult part wasn’t the rejection itself, but the delivery. I received a surprisingly unprofessional email that questioned why I had even accepted the nomination. It was a discouraging moment that could have easily led to quitting community work altogether. The lesson here is that the process is subjective and sometimes timing is everything. If you are doing community work because you love the technology, a rejection is just a speed bump, not a dead end.
Tips for Aspiring MVPs
If you are looking to earn the award, here are three pieces of advice:
- Don’t do it for the award: If creating content feels like a chore, you won’t be able to sustain it. Do it because you enjoy sharing know-how.
- Focus on a Niche: You need to show expertise in a specific category (like AKS or DevOps). If your 24 contributions are scattered across five different categories, you may not have enough “weight” in any single one to qualify.
- Polish your Application: Filling out the contribution form can take 15–20 hours. Treat it like a professional portfolio.
The Person Behind the Screen: Sim Racing
I often get questions about the steering wheels seen in the background of my videos. They aren’t just for show—sim racing is my primary hobby outside of the cloud. I use a full sim rig with a triple-monitor setup to race in iRacing, mostly focusing on high-downforce cars like Formula 3 and LMP2. The different wheels on the wall are swapped out depending on whether I’m racing open-wheelers, trucks, or NASCAR.
The Future of the Channel
After 15 months of a grueling weekly upload schedule, I am moving to a bi-weekly release schedule. This change allows me to dive deeper into niche AKS topics and cover new features with the quality they deserve. You can still expect regular content on Azure, security, and architecture, but with a bit more breathing room between sessions.
Thank you for being part of this journey. Whether you are here for the Kubernetes deep dives or the career tips, I appreciate the support.
You can find all the code sample on GitHub.
This post was AI-generated based on the transcript of the video “My Journey to Microsoft MVP - The Highs, the Lows, and the Lessons”.
Comments powered by Disqus.