I received a message from an Apple recruiter.
It started with the usual HR screen, followed by a quick chat with the hiring manager. That round covered basics in SystemVerilog (SV), UVM phases, and a few light coding questions about arrays and constraints.
Next, I spoke with a couple of managers for team matching and moved ahead with one of them.
Then came the real grind: six rounds over two days. These covered SV, UVM, digital design, coverage, timing diagrams, and even topics like polymorphism and scoreboard design.
One round, for instance, had me sketch out a basic DV architecture, while another focused purely on debugging and constraint logic.
There wasn't a formal behavioral round; most of it involved deep dives into fundamentals and design thinking. Overall, it was pretty technical and intense.
I would advise brushing up on the basics and being ready to defend your design choices. A weak round can be detrimental even if others go well.
Show how to implement a module that yields the dot product of two vectors.
The following metrics were computed from 13 interview experiences for the Apple Design Verification Engineer role in Cupertino, California.
Apple's interview process for their Design Verification Engineer roles in Cupertino, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Apple's Design Verification Engineer interview process in Cupertino, California.