Taro Logo

OS Software Engineer Interview Experience - Folsom, California

February 1, 2019
Negative ExperienceNo Offer

Process

I applied online and received an email to set up a one-hour phone interview. This interview went pretty well; the interviewer was very friendly and helpful. He mentioned on the phone that I should be receiving an onsite request soon. Indeed, I received an onsite request within one to two days. Unfortunately, I received a rejection one week later, after sending a follow-up email.

Phone Interview:

  • A C program for a classical synchronization problem. Solved.
  • How to check the endianness of a system.
  • How to check in which direction the stack is growing.
  • Some other simple C and OS-related questions.
  • Discussion on the team's work and work expectations from the candidate.

Onsite Interview:

Interview 1:

  • Discussion on Project 1.
  • Discussion on macros and inline functions.
  • Explain everything that happens between when a key is pressed and a letter is displayed on the terminal.
  • Discussion on Project 2.
  • Virtual Memory Management.

Interview 2:

This interview was a complete mess. The interviewer didn't seem to have specific questions in mind and appeared to belittle the candidate with every answer. He asked what discussions had taken place in Interview 1, presumably to avoid repetition, which made sense. However, he ended up asking the same questions. He asked about the need for memory management, and the entire interview revolved around this topic for about 50-55 minutes. He then asked about some assembly-level programming. Every time I attempted to answer a question correctly, he would confuse me with a smug expression and declare my answer incorrect. I am rating the entire interview process negatively because of this disappointing interview.

Interview 3:

The interviewer did not show up. They later assigned a new interviewer who also never showed up. I never expected this kind of behavior from Intel.

Interview 4:

This was the lunch interview with the team manager. He was very polite and considerate, informing me about open positions and their candidate requirements. He asked some basic questions about code reviews and code testing.

Interview 5:

This interviewer was exceptionally intelligent. He presented two coding challenges: bit manipulation and number swapping. He asked for the mathematical basis behind the number swapping and for me to reduce the total number of bit manipulation operations from around 250 to 15. He also asked very deep questions about interrupts, system calls, page faults, breakpoints, and so on.

Although the last interview was challenging, I managed to answer correctly. After sending a follow-up email, I received a rejection.

Questions

OS, OS, and OS.

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the Intel OS Software Engineer role in Folsom, California.

Success Rate

0%
Pass Rate

Intel's interview process for their OS Software Engineer roles in Folsom, California is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral0%
Negative100%

Candidates reported having very negative feelings for Intel's OS Software Engineer interview process in Folsom, California.

Intel Work Experiences