Four rounds of interviews. The first two rounds focused on technical aspects; the later two were a mix of technical and managerial.
The interview process was very smooth, and I enjoyed the conversation with each interviewer. I learned a thing or two. It was a detailed kind of discussion where we discussed each point back and forth, rather than ticking answers on an MCQ.
The HR/TA was lost and confused me more than facilitating the interview process. They had poor scheduling, a "my way or the highway" attitude, and intimidation at a late stage.
What is the difference between normal stock Linux and real-time Linux?
Why is normal Linux not real-time?
An application (a large single binary) is running very slowly. How will you diagnose this issue?
Write a C macro to flip the i-th bit of a 32-bit value. Write unit tests to test this macro. Why did you choose these tests?
volatile. What does the compiler do? Why is it needed? Will we need volatile if we had no caches? What is the downside of using volatile? When will you use it? What will happen if you forget to use it when you should have?
What is the most common scheduler used in Linux, and what is its scheduling policy?
What is the most interesting project you have worked on, and what did you like about it?
The following metrics were computed from 378 interview experiences for the Cisco Software Engineer role in India.
Cisco's interview process for their Software Engineer roles in India is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for Cisco's Software Engineer interview process in India.