Being a Microsoft MVP with a focus on the PowerShell contribution area has been a really groovy ride because the program is so open to its members. From NDA briefings, product feedback sessions, and working along side fellow MVPs on various community projects, I have really enjoyed how much investment Microsoft has made into the program. I also love how diverse the program is when considering race, gender, and nationality. That’s a huge plus, since much of the technology world seems to be a bro-fest, sadly.
Having recently returned from attending my second annual Microsoft MVP Summit, I thought it fitting to offer up some ideas on how to participate and said as much on Twitter.
Still A Newbie
I joined the Microsoft MVP program two years back in 2016. It seemed like a logical goal to reach towards because I have spent the better part of a decade working with PowerShell. The last few years, I have specifically been trying to foster a sense of community by creating various open source projects – such as Vester, Rubrik’s PowerShell Module, and VMware NSX functions – along with touring VMworld and VMware User Groups (VMUGs) to educate and promote the use of infrastructure as code using frameworks like PowerShell.
The official MVP Twitter handle has been nice enough to share some of the work, which is cool.
Picking a Category and Contribution Area
The MVP program has a ton of award categories to choose from. If you’re looking to join the program, start by reviewing the list of categories and seeing which ones strike your interest. Each category has a number of contribution areas. In my case, I’m in the Cloud and Datacenter Management category and the PowerShell contribution area. While it is possible to choose multiple contribution areas for the MVP, I think it’s best to narrow your focus when pursuing the MVP, since creating enough content to satisfy multiple contribution areas sounds daunting.