I went through the VMware TPM interview process for a senior TPM role focused on their cloud infrastructure releases. Here's the full breakdown because TPM interviews are genuinely different from SWE interviews and there's not much written about VMware's specifically.
Recruiter screen (30 min). Standard. Background, why VMware, rough sense of your scale and scope (how many engineers you've coordinated, what kind of releases you've run).
Technical screen with a hiring manager (1 hour). This was half 'walk me through a program you ran' and half light technical discussion. For the technical part: they asked how I'd track dependencies across five parallel engineering workstreams, what I do when a critical path item slips, and how I communicate risk to senior leadership. Nothing deeply technical on the engineering side, but they tested whether I understood the engineering constraints I'd be working with. If you don't know the basics of how CI/CD pipelines work, what a release branch strategy is, or how containerization affects deployment complexity, study up. You don't need to be an engineer, but you need to talk fluently with them.
Onsite (4 rounds, virtual).
Round 1: Program execution deep dive. Walk me through your most complex cross-functional program. They had detailed follow-up questions: how did you handle a dependency that blocked multiple teams, how did you scope the program initially, what did your status reporting look like. I had a specific 18-month program I walked through and they drilled into it for the full 45 minutes.
Round 2: Technical judgment. They gave me a scenario: a major infrastructure release is planned for Q3 but engineering is estimating 20% behind schedule at the midpoint. Walk me through how you'd handle it. They wanted to see a structured approach: triage critical path vs. nice-to-have, communicate early, understand the technical blockers, think about phased release options. It's not a test of engineering knowledge, it's a test of structured thinking under ambiguity.
Round 3: Stakeholder management. All behavioral, focused on how you navigate competing priorities from different leaders, how you push back when scope creep threatens a deadline, how you build relationships with engineering leads vs. product leaders vs. exec sponsors.
Round 4: Leadership and culture. More senior questions: how you grow other PMs or TPMs, how you influence without authority, what you look for in a healthy team.
The compensation for senior TPM was in the 170-195k total comp range depending on experience level and negotiation. The role genuinely does involve real technical depth on the infrastructure side, so it's not a coordination-only position.
Overall the process was well-organized. They took about 2.5 weeks from onsite to offer.