I had two general phone interviews.
Then, I had an on-site interview with six to seven people, all in one-on-one sessions.
The first interview involved a tour of the building, followed by a practical session in the lab where I was asked to characterize a two-port filter. I found this quite interesting.
The only interview that didn't go well focused entirely on computer architecture, including topics like cache organization and RAM operation. Unfortunately, I was not well-prepared for that one.
The programming interview was straightforward. I was asked to write Python code on a whiteboard, as the company now uses Python for everything. This included tasks related to string operations, sets, lists versus tuples, and regular expressions.
The next interview was a detailed discussion about I/O characterization, covering QPI, PCIe, and similar technologies.
Finally, there was an interview on digital and analog design, including topics like FSMs and DACs.
Overall, pretty standard, but I didn't remember cache organization.
The following metrics were computed from 1 interview experience for the Intel Product Engineer role in Hudson, Massachusetts.
Intel's interview process for their Product Engineer roles in Hudson, Massachusetts is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Intel's Product Engineer interview process in Hudson, Massachusetts.