The process took 1 day. I interviewed at Cisco in Oct 2010
Interview
I interned with Cisco for 2 summers and then moved to another company to broaden my experience. The interview below was for a full-time position. There was supposedly only one round, after which you either got an offer or you didn't.
1) I spoke with a recruiter at a campus recruiting event. On looking at my resume, he was immediately sour (and even rude) at the fact I chose not to do a 3rd consecutive internship with Cisco. Nonetheless, he invited me to a 1:1 interview the next day.
2) The interview was with the same recruiter I spoke to the day before. All questions were behavioral ("tell me about a time when..."), except for one where he told me to give him a sample SQL statement. He kept mentioning that his boss told him to come back with an "unlimited number of candidates to give offers to".
3) A few days later, I got an email saying "thank you for applying, but Cisco is not interested".
Overall a very negative experience, but mostly a function of the arrogant and unprofessional recruiter I happened to get paired with. Probably could have gone quite differently depending on the interviewer.
Interview questions [2]
Question 1
What is the harshest, but best piece of criticism you ever received?
I applied through an employee referral. The process took 2 days. I interviewed at Cisco (Bengaluru) in Jun 2008
Interview
I got the call for the interview through a referral from my friend working there. The call was immediate (if I remember well, its just the day after I submitted my resume).
I was in contact with the hiring manager right from the start, I had a initial overview of the team and the product for which I was supposed to be working if offered the job, after the hiring manager was convinced that I would take up the job if I got through the interviews, I was called for interviews on the next day.
Day 1 of the interviews: Had to go through 5 rounds of 1:1 interviews , each spanning for about a hour. Mainly technical interviews , about the previous work-ex, the skills required for the job, the basics of the engineering degree.
Day 2 of the interviews: 3 rounds of Phone interview and again, each spanning for about a hour. Again all of those included technical questions, some tests involving the skills for the job.
After day 2 , I had a feeling that I will get through and as expected got the offer within 3-4 days and I was asked to fill some online forms for the background checks.
The people and the work culture in the office looked pretty relaxed and way better than those in my previous job. Had a great feeling and a sense of excitement for the new role. Even during the interview process, never felt any exam like environment and was pretty relaxed and informal to an extent.
Advice to other candidates if you are a fresher or have a work-ex in a diff. domain , please be prepared for the basics of the networking. That was some area where I could have fared better , nevertheless I could get through.
On the whole, it was a good experience now that I was offered the job.
Interview questions [1]
Question 1
What is the reason for job change and what if those reasons re-occur in the new job that would be offered?
I applied through an employee referral. The process took 2 weeks. I interviewed at Cisco (San Jose, CA) in Aug 2007
Interview
1 hour phone interview. Topics were on Network concepts, Resume, projects, Operating system basics, Data structures, Algorithms and others. Overall understanding of network concepts would be helpful to clear the phone interview. Onsite interview would be all day long with 5-6 individual 1 hour interviews.
Interview questions [2]
Question 1
How would you find size of structure without using sizeof operator?
How would you reverse a single linked list?
How would you define bit fields in C?
What are the common IPC techniques in UNIX?
What is the difference between micro-kernel and macro-kernel?
Briefly explain the need for memory protection
Why do we need POSIX standards?
Thread synchronization and critical sections
Instruction pipelining
TCP connection establishment and tear down process
MIPS architecture and need for RISC processors in Embedded environment
C questions to check familiarity with pointer arithmetic.