I was contacted by a recruiter and spoke for five minutes about general topics, including my interests, the position itself, and the team at Intel. A week later, I was notified that they would like me for an on-site interview in another week.
At the on-site interview, I met with seven people during one morning, from 8 a.m. to 12 p.m.
As this is a Software Engineering position, I expected at least some technical questions, but I received none. The only technical question was a casual "Can you code?" to which I replied, "Yes, of course."
Every interviewer asked me about my PhD work, and we generally discussed my research. It seems the most important thing for them was to determine whether I would be a good fit, considering my vision, interests, and prior experience. Personality is definitely something they look for, even if it's not immediately apparent.
People in this group seemed quite young and open-minded, especially the group leader. The position itself wasn't a "code in the trenches" type of role; it offers considerable flexibility and requires creativity and novel approaches. Perhaps that's why they were more interested in vision and interests than direct coding ability.
Why would you be a good fit for this group?
Questions about my PhD work, where I had to justify my decisions. They were difficult because the questions came from a different perspective than I would typically encounter in academia.
The following metrics were computed from 24 interview experiences for the Intel Software Engineer role in Santa Clara, California.
Intel's interview process for their Software Engineer roles in Santa Clara, California 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 Software Engineer interview process in Santa Clara, California.