Broadcom, headquartered in Palo Alto, designs semiconductors such as network switch chips and Wi-Fi and broadband silicon, and also runs a large infrastructure software business that includes VMware, acquired in November 2023. Interviews depend heavily on the division: chip and firmware teams test C, embedded systems and operating-system fundamentals. This page covers what Broadcom builds and who it hires, the process candidates commonly report, the technical depth the teams care about, representative problem types, what interviewers score, and a three-week prep plan.
What Broadcom builds and who it hires
On the semiconductor side, software engineers write SDKs and drivers for switch chips such as the Tomahawk and Jericho families, firmware for wireless and broadband devices, and bring-up and validation tools for new silicon. On the software side, divisions such as VMware build virtualization and cloud infrastructure, and their interviews look more like those at other enterprise software companies.
- Firmware and embedded engineers: C on microcontrollers and real-time operating systems.
- SDK and driver engineers: Linux drivers and switch-chip software development kits.
- Silicon validation engineers: testing and bringing up new chips.
- Infrastructure software engineers: VMware and other software divisions.
What the process tends to look like
| Stage | What happens | How to prepare |
|---|---|---|
| Recruiter or hiring-manager call | Background, a résumé deep dive and team match | Know every project on your résumé down to the registers |
| Technical phone screen | C fundamentals, bit operations and embedded or OS questions | Answer C questions precisely and write small functions aloud |
| Final loop | Several back-to-back technical interviews; candidates report sessions of three to four hours or five to six interviewers, covering C, RTOS, OS concepts and past work | C, embedded concepts and one system you built, explained end to end |
Processes differ by team, level and office and change over time, so treat this as the common shape candidates report and confirm the specifics with your recruiter.
C, embedded systems and the hardware boundary
C fundamentals. Reported questions include the difference between static and automatic variables, the volatile keyword, pointer arithmetic, and why recursion is risky on a device with little memory. Our C programming interview questions cover these.
Embedded and RTOS. Know interrupts and what is safe inside an interrupt handler, RTOS tasks and priorities, priority inversion, and buses such as I2C, SPI and UART. Our embedded software engineer questions go further.
Memory and hardware. Expect to read and write memory-mapped registers with bit masks, and to explain how you would test a block of memory for faulty bits.
Linux and OS. SDK and driver roles probe race conditions, processes versus threads, locking and Linux kernel basics. Review our operating system questions.
Representative problem types
These are the kinds of problems candidates describe, not a leaked question list. Practice the category, not the exact question.
- Set, clear and toggle bits in a memory-mapped register.
- Write a memory test that walks ones and zeros through a region.
- Implement a circular buffer shared by an interrupt handler and a task.
- Explain and fix a race condition between two threads.
- Reverse the bits or the byte order of a 32-bit integer.
- Implement a linked list or hash table in C without the standard library.
- Explain the costs of recursion and dynamic allocation in firmware.
What interviewers score
- Correct C: code that compiles, frees what it allocates and handles empty lists, null pointers and boundary values.
- Understanding of the machine: what your code does to memory, the stack and the CPU, and why.
- Debugging discipline: how you find a fault with prints, assertions or a debugger instead of guessing.
- Clear reasoning about systems: explaining a networking, OS or hardware trade-off in plain words.
The behavioral side
Technical rounds decide most outcomes, but every Broadcom loop also asks about how you work. Prepare a short story for each of these, with a result and what you learned:
- Something you shipped end to end. Cover the user problem, your decisions, what you measured and what you would change.
- A disagreement with a teammate. Show how you made the decision on evidence and kept the relationship.
- Why this company? Connect its product and engineering problems to the work you want to do next.
Structures and sample answers for the common questions are in our software engineer behavioral answers guide.
A three-week prep plan
- Week 1: C precision: storage classes, volatile, const, pointer arithmetic and bit operations, plus a linked list, a hash table and a circular buffer written without the standard library. Our C++ interview questions help if the team also uses C++.
- Week 2: embedded concepts: interrupts, RTOS scheduling and priority inversion, memory-mapped registers, I2C, SPI and UART, and a memory test written from scratch, using our embedded software engineer questions as a checklist.
- Week 3: operating systems and your own work: race conditions, locks, processes versus threads and Linux driver basics, then rehearse a walkthrough of each project on your résumé and do two mock interviews.
For practice lists, use LeetCode company-tagged questions and the NeetCode 150 roadmap; for design rounds, read system design building blocks; and compare the practical style of Datadog.
Where CoPilot Interview fits
Most of a Broadcom loop is spoken: you explain an approach, defend a trade-off and talk through your past work. CoPilot Interview is an AI interview assistant whose free AI mock interview builds technical and behavioral questions from your résumé and the job description, reads them aloud and scores each spoken answer out of ten, so you can rehearse the explanation as well as the code. The free plan gives 15 minutes a day of live help in sessions of up to 15 minutes, with AI mock interviews included. Online assessments and many coding rounds forbid outside help, so practice beforehand and follow your employer's rules on the day.
Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly.
Frequently asked questions
What programming language should I use in a Broadcom interview?
C for firmware, drivers and SDKs, with some C++ and Python for tools; VMware and other software divisions use languages such as Java, Go and Python. Follow the job description.
Does Broadcom send an online assessment?
Reports from chip and firmware teams mostly describe a phone screen followed by a virtual or on-site loop rather than an online assessment, though campus hiring may differ. Many public reports are several years old, so confirm the current process with your recruiter.
Is a Broadcom interview different for VMware roles?
Usually, yes. Semiconductor teams focus on C, embedded systems and the hardware boundary, while software divisions such as VMware run interviews closer to other enterprise software companies, with data structures, system design and behavioral rounds. Read the job description and ask your recruiter.
How should I prepare for Broadcom coding questions?
For chip and firmware teams, drill C fundamentals and bit operations until the answers are precise, then cover interrupts, RTOS scheduling, memory-mapped registers and common buses, and be ready to explain every project on your résumé in detail. For software divisions such as VMware, prepare like any enterprise software loop.
Can I use AI tools in a Broadcom interview?
Only if the instructions you receive say so. Online assessments and live coding rounds generally forbid outside help, and some companies now state their AI policy in the invitation. Use AI to practice beforehand, and follow your employer's rules.
Practice this interview before the real one
The AI mock interview builds questions from your resume and the job description, reads them aloud and scores each spoken answer out of 10. Included on the free plan.
Start a mock interview