My first interview was a phone interview via a Lync meeting. The interviewer was low-key and asked questions that started easy but became progressively harder.
The in-person interview was out of state, so I was flown in. I had a five-person interview, one after the other. While some of the interviews were certainly more personality-focused, every interviewer (except for the lunch interview) had me write code on the board. I am an EE major, and I had to study extensively for the interview, but it paid off.
My number one piece of advice is to study the basics you learned a long time ago. It's the fundamentals (for students fresh out of university) that they want to see.
Put only things on your resume that you can talk about in great detail.
Bit checking a 32-bit number. Recursive searching of binary trees. Writing unit tests for simple code algorithms. After writing code, was asked to optimize it. All questions were C.
Also, they wanted details about my Sr. project, which was firmware for an embedded system.
The following metrics were computed from 1 interview experience for the Intel Firmware Engineer role in Longmont, Colorado.
Intel's interview process for their Firmware Engineer roles in Longmont, Colorado is incredibly easy as the vast majority of engineers get an offer after going through it.
Candidates reported having very good feelings for Intel's Firmware Engineer interview process in Longmont, Colorado.