The process took 1 week. I interviewed at Cisco in Nov 2009
Interview
I met the person who later became my manager at the career fair in my school. She liked my resume and scheduled me for 1:1 interview in my school. The interview went well. Some questions were technical and some were behavioral. They called me one week later to schedule a phone interview. The phone interview was like an orientation and some simple technical questions. One week later, I was offered the job
Interview questions [1]
Question 1
what is the difference between a router and a switch
I applied online. The process took 1 day. I interviewed at Cisco in Feb 2011
Interview
The manager was very positive and upbeat. It was a fairly routine interview with many "deep dives" into my past accomplishments and how that would translate and benefit Cisco. I found common ground with the interviewer in order to make a connection to better explain my skill set as well as the skills I was acquiring at school. I did not feel as if this were a high pressure interview or as if the interviewer thought they were superior. The interviewer was very receptive to my questions and answered thoroughly.
Interview questions [1]
Question 1
Ironically, I didn't feel that there were any unexpected questions during this interview. It was much more of a conversation about my skills, expectations of my internship experience and the standard questions like "walk me through your resume" or "how will Cisco benefit from your skills" or "what is unique to you"...
The process took 1 day. I interviewed at Cisco (San Jose, CA) in Oct 2011
Interview
Recruiting at my local university. Met with the division manager that was hiring. Accepted my resume. Called me to schedule an interview on location. Once arrived was interviewed by 3 people individually, all engineers i'd be working with. First person asked me general questions about my past projects in electrical engineering and past internship experiences and how that helped me or what I learned. next one asked me about metastability and also about past projects. Last one asked me about c++ coding structures and how I would design a loop to go over an array of some sort. I can't remember too well. He also asked about Design verification generalities as to how I would check for errors on a basic calculator that was giving a wrong answer. Was thrown off by the simplicity of it but if you think about it he was looking at how I would go about the process, he didn't expect me to really know how to fix a simple calculator. He was trying to see how my thought process was in design verification mostly. Interesting interview process to say the least. It wasn't difficult but it wasn't the easiest either.
Interview questions [2]
Question 1
Describe past internships and what you learned from them?