I met a recruiter at a campus career fair. He asked broad questions, like "Why do you want to be an engineer?", to get to know my personality. He was very friendly and wanted me to succeed.
A few days later, I had a phone interview. The questions weren't supposed to be difficult, but they focused more on embedded design, whereas my studies focused on analog circuits.
I thought I did pretty poorly, and the interviewer confirmed that I wasn't proceeding in the interview process. However, about three weeks later, they flew me down to Arizona for an on-site interview.
The process consisted of five one-on-one, hour-long interviews. Each person asked about something different, such as behavioral questions, programming skills, or digital logic.
I had to use the whiteboard often to draw schematics or show my ideas and my thought process. I got along well with most of the interviewers, but I think the actual hiring manager didn't like me.
A few days later, I received an email saying that I did not get the job.
I pointed out my lack of digital experience several times, so I was surprised I still made it that far through the interview process.
Given this circuit, how can you redesign it to use fewer logic gates?
The following metrics were computed from 3 interview experiences for the Intel Validation Engineer role in Chandler, Arizona.
Intel's interview process for their Validation Engineer roles in Chandler, Arizona 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 Validation Engineer interview process in Chandler, Arizona.