My Journey to Becoming a VMware vExpert: Persistence, Passion & People

 



I’m thrilled to share that I’ve been recognized as a VMware vExpert in 2025—a milestone that means a lot to me both personally and professionally. But this wasn’t an overnight success. In fact, it took a few tries, a lot of reflection, and a solid support system to get here. If you're someone working toward this goal, I hope my journey helps you stay motivated.

🚧 The Early Attempts

Like many, I applied to the vExpert program a few times in the past—each time with hope, and each time facing the sting of not making the cut. It was disheartening, but also humbling. I realized that passion alone isn’t enough—you need strategy, mentorship, and impact-driven contributions.

🔁 What I Did Differently This Time

This year, I changed my approach:

  • Mentorship was key. I reached out to two incredibly generous vExpert Pros & old friends, Arun Nukula and Ravneet Arora, who not only agreed to mentor me but also set up standing meetings to check in on my progress. Their feedback was constructive, honest, and exactly what I needed.

  • I focused on consistent content. I began blogging about topics relevant to VMware technology, customer use cases, and technical tips. I also worked on my coding skills to better contribute to the community from a developer's angle.

💼 My Role as a TAM Helped Shape My Path

As a Technical Adoption Manager (TAM) at VMware by Broadcom, I work closely with Product Managers and engineering teams, helping customers navigate VMware’s evolving product landscape. We conduct workshops, roadmap sessions, and technical enablement that directly impact how customers adopt VMware solutions.

This role gave me a unique vantage point—and I realized I could turn that into community value by sharing insights from the field.

🤝 VMUG: My Longtime Passion

I've always had a soft spot for VMUG. Back in India, I was part of the Bangalore VMUG Steering Committee, where we organized events, supported local users, and spread awareness of VMware technologies. After moving to Sydney, I naturally gravitated toward the Sydney VMUG and continued contributing there.

Community has always been my home base—whether it’s through events, webinars, or simple hallway conversations at meetups.

🏁 The Outcome: My First vExpert in 2025

All these elements—my role, my mentors, and my ongoing community involvement—culminated in what finally became a successful vExpert application. When the acceptance email came in, it was a moment of validation but also one of gratitude.

To Arun and Ravneet—thank you for believing in me. And to the broader VMware community—you are why we do what we do.

Comments

Post a Comment

Popular posts from this blog

Understanding and Customizing ESXi Password Requirements

VMware ESXi enforces strict password policies for access via the Direct Console User Interface (DCUI) , ESXi Shell , SSH , and the VMware Host Client . These rules are designed to improve security by requiring strong, complex passwords. Default ESXi Password Requirements: Character Classes : Passwords must include at least three of the following four character classes: Lowercase letters Uppercase letters Numbers Special characters (e.g., underscore or dash) Password Length : Must be at least seven characters long and no more than 40 characters . Restrictions : Passwords cannot contain dictionary words or parts of them. Passwords cannot include the username or parts of the username. Customizing ESXi Password Restrictions: You can modify the password rules if the default password policy doesn't meet your organisation's needs. VMware allows you to configure custom password policies to match specific s...
Read more

How do you request an NSX 4.2.1.1 download?

How do you request an NSX 4.2.1.1 download? Background: You will notice no downloadable links for this version if you have seen a recent NSX 4.2.1.1 release. This is something we followed to get the download. Step 1: File an SR with VMware Support. Step 2: Request the downloadable link for the NSX 4.2.1.1 release. Please mention your customer's use case and why they need this release.  Please read the below to see if your infra use case needs NSX 4.2.1.1. Release Notes: VMware NSX 4.2.1.1 Release Notes While NSX 4.2.1  brought several improvements, NSX 4.2.1.1  takes things further with targeted fixes and enhancements. Here's a breakdown of what’s worth noting: 1. Security Patches for Critical Vulnerabilities The most significant difference between NSX 4.2.1  and NSX 4.2.1.1  is the resolution of several critical security vulnerabilities . Specifically, NSX 4.2.1.1  addresses: CVE-2024-38818 CVE-2024-38817 CVE-2024-38815 These vulnerabilities were recently...
Read more