O processo levou 1 dia. Fui entrevistado pela Cisco (San Jose, CA) em out. de 2011
Entrevista
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.
Perguntas de entrevista [2]
Pergunta 1
Describe past internships and what you learned from them?
It was nice, informative. One should prepare using all resources. They will judge your understanding based on everything that you ever demonstrated in the process, so be aware of everything you said or mentioned.
It was basically deep dive into resume and some questions on Dsa. The overall experience was good. There were 4 rounds in total. Be familiar with basics of the language that you primarily use.
O processo levou 1 dia. Fiz uma entrevista na empresa Cisco (Bengaluru).
Entrevista
3 rounds. 2 tech and 1 HR. The tech rounds lasted 1 hr 15 means each. HR was just formality for me though some had proper HR rounds. They wanna see how you work out solns with them over the actual one.
Perguntas de entrevista [1]
Pergunta 1
They were curious on knowing why did you do your projects over what you did.