Product Manager Jobs at Broadcom

Broadcom PM interview guide

Broadcom's PM loop runs about 2 to 3 weeks (some roles stretch to 4 to 8 weeks across divisions) over roughly 4 to 5 stages: a recruiter screen, a hiring manager behavioral round, then a case study panel with multiple product managers, and for many software PM roles inside the acquired VMware org, a take-home presentation you defend in front of a panel. The one thing that defines it: a panel of working PMs walks you through the full product life cycle on a real domain scenario, so they are testing whether you can actually run a product end to end, not just answer framework questions.

The interview process

1. Recruiter screen (about 30 min). Phone call on your background, skills, and why this role. The recruiter confirms you clear the bar (Broadcom weights real PM experience heavily) and sets expectations on the loop and culture.
2. Hiring manager behavioral round. The reported first interview round is behavioral: standard background and team-collaboration questions to check you have the right experience and would work well across functions. Expect many questions on how you operate with other people.
3. Case study panel (three product managers). The core round: a case study with about three PMs where you walk through various stages of the product life cycle on a given scenario. They probe how you scope, prioritize, and reason through a product from idea to launch, often on a hardware, sensor, or infrastructure domain.
4. Take-home presentation and panel defense (common for VMware-org software PM roles). For many PM roles in the acquired VMware business, you get a use-case scenario, about a week to build a presentation, then defend it to a panel. They assess structured thinking, prioritization, and how clearly you communicate a strategy under questioning.
5. Final manager and team alignment. Closing conversations with team leadership and stakeholders to confirm fit, vision, and ability to influence without authority before the hiring decision.
6. What they're really testing. Three signals carry the most weight: (1) hands-on product life cycle command, can you actually PM a real product from problem to launch, including a domain you may not know; (2) prioritization and data-driven decisions, especially how you rank a backlog and justify trade-offs; (3) cross-functional influence and communication, working with engineers, sales, and customers and articulating a clear strategy without formal authority.

Likely PM interview questions

1. Walk us through a mobile application and how you would build it, from concept to launch.Product sense
2. You have temperature data collected from a field of sensors, and the use case is climate control for crops. Figure out how you would PM your way into building a product for this.Company-specific
3. Walk us through the various stages of the product life cycle for a product you would own here.Execution