Jeff Wallace
Aug 14, 2013
(3 votes)

EPiServer Most Valuable Professional Program


The EPiServer Most Valued Professional Program, more commonly known as the EMVP Program, is designed to promote professionals within the EPiServer developer community who are contributing with high class content (e.g. blogs, forums posts, code samples, etc.). It is the highest rank a developer can get in the community.

The current members, at the time of authoring this blog, total 16 people out of the 20,000+ member community. The EMVP names should look familiar to most as they truly represent key contributors and provide great information and assistance to many here on EPiServer World.

  • Alexander Haneng
  • Anders Hattestad
  • Anders Nordby
  • Arild Henrichsen
  • Daniel Berg
  • David Knipe
  • Deane Barker
  • Erik Nordin
  • Frederik Vig
  • Fredrik Haglund
  • Joel Abrahamsson
  • Lee Crowe
  • Mark Everard
  • Mathias Kunto
  • Stefan Forsberg
  • Ted Nyberg


EMVP Benefits

  • Partners can use EMVP logo in their marketing (see the logo at the top of this blog)
  • EMVPs can use EMVP logo in their personal marketing
  • EMVP logo is displayed next to name in EPiServer World content (blogs, forums, comments, etc.)
  • Access to private discussion groups and forums
  • Invitations to special developer meetings and webinars where feedback is welcome
  • Automatic access to all future early adopter programs (e.g. TAP)
  • Free EPiServer license to be used on personal site
  • Speaking slots at some EPiServer events
  • VIP treatment at some EPiServer events
  • And on occasion, EMVPs might receive some interesting EPiServer goodies


EMVP Requirements

It is important to note that reaching this status is entirely based on personal achievements not the partner company achievements. Each EMVP being considered must have demonstrated high skills in EPiServer solution development. They must leverage this personal expertise to assist others. This includes, but is not limited to, contributing to the EPiServer World community via blogs, forums posts, code samples, Add-ons, organizing meet ups, speaking at events, and more.


EMVP Process

The EMVP board consists of a number of senior EPiServer employees with Allan Thraen heading things up as the chairman of the board. The board monitors contributions throughout the year and schedules regular meetings quarterly to review this activity. In cases where community members are closely tracking towards EMVP status they may be notified via email to incent them to continue their good work. In January of each year the board meets to review contributions from the previous year. New EMVP prospects are approved or disapproved by the board at this time. Existing EMVP status is also reviewed at the same time. The expectation is that once an individual has achieved EMVP status they will continue to contribute in a similar manner to what earned them this status in the first place. Anyone at risk of losing EMVP status is notified with enough advance warning to allow them to take the appropriate measures to maintain status. Each year new EMVPs are announced on EPiServer World. An example of this can be seen here. You’ll find similar posts for many years past if you search.


Future Considerations

Below are a few examples of additional items being *considered* for EMVPs:

  • Global EMVP Summit
  • Special EMVP section on EPiServer World
  • The number of EMVPs a given partner has noted on their partner page (similar to the number of certified developers which is already present)

Note, the above are considerations subject to change.


How to Become an EMVP?

As noted in the “EMVP Process” section the board meets regularly to discuss key contributors. If you are doing all of the things in the “EMVP Requirements” section at a level comparable to other EMVPs this is a great start. While the board monitors activity regularly, if you believe you have a good candidate on your team, you are always welcome to submit the candidate for consideration to your preferred contact at EPiServer. Please do this by December of the year in which you believe they should be considered.

Aug 14, 2013


Please login to comment.
Latest blogs
Vulnerability in CMS 12 shell module configuration

Introduction A potential security vulnerability has been identified in Optimizely CMS 12, triggered by a certain shell module configuration. To be...

Magnus Rahl | Sep 28, 2023

AI-Assistant: The 'Change Tone' Shortcut

The AI-Assistant for Optimizely is constantly evolving, adjusting, and transforming to meet your digital needs, providing a cutting-edge advantage...

Luc Gosso (MVP) | Sep 27, 2023 | Syndicated blog

How to fix scheduled job 'Remove Abandoned BLOBs' if it keeps failing

Optimizely inlcudes a job named 'Remove Abandoned BLOBs'. This post will help you fix it if it's no longer working.

Henning Sjørbotten | Sep 26, 2023 | Syndicated blog

Optimizely Web Experimentation Metrics

Within the domain of Optimizely Web Experimentation Metrics, the emphasis is on objective key performance indicators (KPIs) selected to assess an...

Matthew Dunn | Sep 23, 2023 | Syndicated blog