Me postulé a través de una facultad o universidad. El proceso tomó 1 día. Acudí a una entrevista en Cisco (Bengaluru) en jul 2018
Entrevista
Horrible interview process and experience. The interview was a mere formality. They made me wait from 10:30 to 3:30 for my interview. Out of 30 candidates, I was the 27th they called. Cisco had already made up their mind on who to select. While I was waiting for my first round, others were already finished with their second interview. Even though I answered everything correctly (as the technical interview was just based on my resume) I got rejected. Sheer waste of time.
Me postulé a través de una facultad o universidad. El proceso tomó 1 día. Acudí a una entrevista en Cisco (Bengaluru) en ago 2016
Entrevista
one written test , one technical interview , one manegerial interview , one hr interview . Process was simple , started with a writtent test which was aptitude test. 50 questions in 1 hour. Followed by 3 interviews.
Me postulé a través de una recomendación de un empleado. El proceso tomó 4 meses. Acudí a una entrevista en Cisco
Entrevista
Interviewed with them over four months, over these four months had three different WebEx/Skype interviews. I am a recent college grad, the interview process began in my final semester of university.
Preguntas de entrevista [1]
Pregunta 1
Joke of an interview process, or atleast very easy. This may have been since the position was in IT and not Engineering, although the position was application development. They take extremely long, and seem to drag the process out substantially. My first interview was way back in October 2013, and I had not even been invited onsite by January 2014 time frame. Its too bad because Cisco was a company I always wanted to work for, but the speed of the interview process was a huge turnoff. I decided to accept a better role at a company that moved faster on me as a candidate. My advice would be too have Cisco maybe as a last resort in the interview process. Also, the fact that the interviews were so simple may indicate the level/challenge of work you will be doing if hired. Most technical interviews should atleast be somewhat challenging, this one was not at all.