If you’re working with Kentico, here’s what you need to know about the MVP path — straight from someone who’s achieved it.
We sat down with Dmitry Bastron, our Head of Development, to learn about his journey to becoming a Kentico MVP and what it really takes to earn the title.
1. 𝗛𝗼𝘄 𝗱𝗶𝗱 𝘆𝗼𝘂𝗿 𝗞𝗲𝗻𝘁𝗶𝗰𝗼 𝗷𝗼𝘂𝗿𝗻𝗲𝘆 𝗯𝗲𝗴𝗶𝗻?
Kentico was the first CMS I worked with. I learned a lot through DevNet’s Q&A section and, over time, started contributing back. That’s how my path to MVP started.
2. 𝗪𝗵𝘆 𝗯𝗲𝗰𝗼𝗺𝗲 𝗮 𝗞𝗲𝗻𝘁𝗶𝗰𝗼 𝗠𝗩𝗣?
For me, the real value was direct collaboration with the product team: sharing feedback, shaping features, and seeing ideas turn into improvements.
3. 𝗜𝘀 𝗶𝘁 𝗵𝗮𝗿𝗱 𝘁𝗼 𝗯𝗲𝗰𝗼𝗺𝗲 𝗮 𝗞𝗲𝗻𝘁𝗶𝗰𝗼 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿?
The entry barrier is lower than people may think. Good documentation helps a lot, but you still need a foundation in web development. Experience with other CMSs is a plus, but not a must.
4. 𝗪𝗵𝗮𝘁 𝗱𝗼 𝗞𝗲𝗻𝘁𝗶𝗰𝗼 𝗠𝗩𝗣𝘀 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝗱𝗼?
They answer community questions, share knowledge, give feedback to the product team, and promote Kentico more broadly. In short: they amplify the community.
5. 𝗛𝗼𝘄 𝗺𝘂𝗰𝗵 𝘁𝗶𝗺𝗲 𝗮𝗻𝗱 𝗲𝗳𝗳𝗼𝗿𝘁 𝗱𝗼𝗲𝘀 𝗶𝘁 𝘁𝗮𝗸𝗲?
Consistency matters more than volume. Write posts, speak at events, publish extensions, or support the community. MVP is about ongoing, genuine contribution.
6. 𝗪𝗵𝗮𝘁 𝗮𝗿𝗲 𝘁𝗵𝗲 𝗯𝗲𝗻𝗲𝗳𝗶𝘁𝘀?
Early access to features, roadmap insights, MVP summits, free tickets to Kentico Connection if you present, and direct contact with the product team.
7. 𝗛𝗼𝘄 𝗽𝗼𝗽𝘂𝗹𝗮𝗿 𝗶𝘀 𝗞𝗲𝗻𝘁𝗶𝗰𝗼 𝘁𝗼𝗱𝗮𝘆?
Kentico Xperience is steadily growing. With new features rolling out monthly, it’s becoming a strong career choice for developers and marketers alike.
8. 𝗔𝗻𝘆 𝗮𝗱𝘃𝗶𝗰𝗲 𝗳𝗼𝗿 𝗳𝘂𝘁𝘂𝗿𝗲 𝗠𝗩𝗣𝘀?
Be active in the community, share what you know, and do it because you enjoy it. The Kentico MVP group is small, close-knit, and full of passionate professionals.
A big thanks to the Kentico community — and to all this year’s MVPs — for making it such a supportive and inspiring place to grow!
Check out the full interview on our blog, where Dmitry shares more about his personal journey, lessons learned, and practical advice for anyone considering the MVP path. Link in the comments. 👇