I was referred by an acquaintance to the Windows OS team at Folsom. The overall interview process lasted about 3-4 weeks. I had an initial phone interview which concentrated on general operating system concepts.
I was invited for an onsite interview at Folsom, CA. It was the worst experience I have had in an interview. I felt that the decision regarding hiring was made well before I was even interviewed. There were 7 rounds of technical interviews.
The first round was good, with a general discussion about my projects and operating system concepts. The second round was with an engineer who lacked proper communication skills. He was rude and unwilling to listen to my approach to problems. This was supposed to be an x86 coding round, even though I had not listed that anywhere on my resume.
Most of the rounds primarily concentrated on computer architecture, an area where I have very limited knowledge. The interviewers seemed very inconsiderate of the fact that I am a computer science student, not a computer engineering student.
The lunch interview was a pain. Right from the moment we left the meeting room until we returned, the interviewer constantly asked questions, giving me very limited time to even eat my food. I was expected to code on paper even during the lunch interview round, which seemed pretty insane to me.
The worst part was that the same team at Hillsborough asked no computer engineering questions at all while interviewing candidates.
What is the difference between a Pentium 4 pipeline and a RISC pipeline?
What is the first instruction that the CPU executes?
Write the PIN diagram of the 8086 processor.
The following metrics were computed from 20 interview experiences for the Intel Software Engineer role in Folsom, California.
Intel's interview process for their Software Engineer roles in Folsom, California 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 Folsom, California.