Site Reliability Engineer Interview Experience at VMware (Broadcom) – 2026

The recruiter screen covers background and specifically clarifies that the role sits on the Tanzu Kubernetes platform team rather than legacy VMware virtualization infrastructure, since the two tracks reportedly get confused often by candidates applying broadly to 'VMware' roles post-acquisition.

The hiring manager asks about on-call experience specifically, including how large a service the candidate carried a pager for and what the worst production incident was, using the answer to gauge whether the candidate had genuine ownership experience versus only having supported someone else's on-call rotation.

This round opens with a synchronization question — explaining how a mutex is internally implemented and the tradeoffs of a spinlock versus a blocking lock under high contention — then moves into a live coding problem to implement a thread-safe bounded queue supporting concurrent producers and consumers. A condition variable pair (not-full and not-empty) rather than a single condition variable is the expected approach, avoiding unnecessary wakeups. A common follow-up asks candidates to reason through what happens under spurious wakeup, handled by re-checking the queue state in a while loop rather than an if check.

Candidates are asked to design a health-check and auto-remediation system for a fleet of Tanzu-managed Kubernetes clusters spanning multiple customer environments. A hierarchical check model — node-level, cluster-control-plane-level, and cross-cluster fleet-level — is a strong direction, since collapsing all checks into a single dashboard makes it hard to tell whether an issue is isolated or systemic. A common follow-up probes false-positive risk for auto-remediation specifically (e.g. auto-restarting a control-plane component that's actually fine but briefly unresponsive under load) — requiring two consecutive failed checks across a minimum interval before triggering any automated remediation action, with a manual override always available, addresses this well.

This closing behavioral round covers working through Broadcom's post-acquisition changes to team structure and priorities, asking how candidates would handle ambiguity if their team's product roadmap shifted significantly with little notice. Staying focused on the underlying reliability goals of the role rather than getting anchored to a specific tool or project that might change is the strong answer.