vExpert Application – Tips and Tricks

Currently the whole VMware vExpert & Advocacy team and vExpert Pros are voting on the second half 2019 vExpert applications. When going through the application you can see awesome, good, ok, bad and worst applications. So I thought I will take some time to do a quick tips and tricks post on how your application should probably look like to have a good chance to be selected as vExpert.

But first of all, as usual, what is the vExpert program.

The VMware vExpert program is VMware’s global evangelism and advocacy program. The program is designed to put VMware’s marketing resources towards your advocacy efforts. Promotion of your articles, exposure at our global events, co-op advertising, traffic analysis, and early access to beta programs and VMware’s roadmap.

Each year, we bring together in the vExpert Program the people who have made some of the most important contributions to the VMware community. These are the bloggers, book authors, VMUG leaders, speakers, tool builders, community leaders and general enthusiasts.

When applying for the vExpert program there are 3 tracks you can choose from.

Evangelist Path
The Evangelist Path includes book authors, bloggers, tool builders, public speakers, VMTN contributors, and other IT professionals who share their knowledge and passion with others with the leverage of a personal public platform to reach many people. Employees of VMware can also apply via the Evangelist path. A VMware employee reference is recommended if your activities weren’t all in public or were in a language other than English.

Customer Path
The Customer Path is for leaders from VMware customer organizations. They have been internal champions in their organizations, or worked with VMware to build success stories, act as customer references, given public interviews, spoken at conferences, or were VMUG leaders. A VMware employee reference is recommended if your activities weren’t all in public.

VPN (VMware Partner Network) Path
The VPN Path is for employees of our partner companies who lead with passion and by example, who are committed to continuous learning through accreditations and certifications and to making their technical knowledge and expertise available to many. This can take shape of event participation, video, IP generation, as well as public speaking engagements. A VMware employee reference is required for VPN Path candidates.

There is also the VCDX path. So if you are a VCDX you are automatically a vExpert. The only requirement you have to do is to APPLY.

From my experience the VPN path is the most challenging path because most of the people’s content, who are applying for the VPN path is maybe not public available. This is the reason why a VMware employee reference is required.

So most of the people applying for vExpert are in the Evangelist path. Here are some tips and tricks for this path you should consider when filling out your vExpert application.

  • Make sure that your content is about VMware. If you are writing most of the time about Veeam, Microsoft or what ever, chances are good that you won’t be selected as vExpert. For this content other community programs are available like Microsoft MVP or Veeam Vanguards. So personally I would say that 50% or more should be about VMware.
  • Be honest in your vExpert application, content and path. Voters are also looking at your content provided in the application and also checking the VCDX directory if you applied for the VCDX path. If you have chosen the wrong path because you are e.g. no VCDX it’s up to the voter and the remaining content if you are still getting selected.
  • Don’t use a syndicate blog in your application. This content is not your own and voters can’t give you credit for that.
  • If you fill out the VMTN field please provide the correct VMTN username. You can find your VMTN username if you login to VMTN and select “View my profile”. This will create an URL similar to this one “” where the red marked part is your VMTN username.
  • Just fill out your VMTN username if you actually helping people there. If you are just a lurker and your last post is ages ago don’t fill out the VMTN part because we can’t give you credit for that.
  • If you are mentioning speaking engagements (VMworld, VMUG, etc.), please provide the necessary references for that (links, agenda, etc.). Otherwise it won’t count towards the final scoring.
  • First half vExpert applications normally taking content from last year into account (e.g. vExpert 2019 -> content from 2018), whereas second half vExpert applications normally taking June to June timelines into account (second half 2019 -> content from June 2018 to June 2019). Keep this in mind when you are providing content links.
  • If you are a blogger, please date your posts in whatever way suits you. If we can’t verify that the content is from the required time period we also can’t give you credit for that.
  • If you are a VMUG leader it would be great if you are mentioning your meetings and have a link to it. Would save time for the voters who doesn’t need to search for it.
  • Please mention only content or activities which were created or done outside of your daily job business. E.g. if you’re a Vendor SE and you’re doing presentations for your customers, then this is part of your job. But if you’re speaking at VMUGs or VMworld then this is voluntary and would count towards the vExpert criteria .

I hope some of this tips and tricks will help people who will apply for the vExpert program in the near future or such people who get’s denied in their first try. Also if you need help for preparing your application you can always reach out to your local vExpert Pro which can be found in the vExpert Directory. If there is no vExpert Pro in your country or region you can either contact me or one of the other Pros in the directory. I think everyone of them will be happy to help with the application or giving some advice for “how to apply”.

Source: Information about the vExpert program and wording was taken from the VMware vExpert Blog site.

Leave a Reply

Your email address will not be published. Required fields are marked *