The interview comprised a telephonic round and an on-site interview. Both included questions related to programming. Intel heavily relies on Microsoft technologies, so knowing them is a plus.
The phone interview consisted of a few verbal technical questions, and then I was asked to code a small program. The time allotted was 15 minutes. The code was judged on thought process, clarity of concepts, and how easy it was to understand for a fellow developer.
The on-site interview comprised 7-8 rounds with a lunch break. It went from 8 am to 5 pm. There was one behavioral round, two problem-solving rounds, and all others were technical coding rounds.
Though the interview process differs from team to team, there is no set pattern. I have seen people get jobs based on a 1-hour on-site interview.
What would you do if you were managing a team and the team was unable to solve a problem technically, with a deadline approaching?
Would you sit down and code it yourself? Be furious at the team? Blame them for failure? Complain to upper management? Etc.
The follow-up was: What would you do if you had two months before your next project started?
Sit and relax? Ramp up team skills? Etc. Etc.
The following metrics were computed from 234 interview experiences for the Intel Software Engineer role in United States.
Intel's interview process for their Software Engineer roles in the United States is on the easier side as most engineers get an offer after going through it.
Candidates reported having very good feelings for Intel's Software Engineer interview process in United States.