Solicité el puesto a través de la escuela superior o la universidad. Acudí a una entrevista en Cisco en feb 2017
Entrevista
Met the recruiter at the career fair, got invited to an interview the following day. The interview was easy, all behavioral questions, they wanted to know how well you work with teams. The interviewer was very nice and the whole interview was very relaxed. After the interview, the interviewer introduced me to another recruiter from Cisco next door and she asked me some brief questions about my skill (what programming languages do I write, what are my interests).
The interviewer said he'd email me later the same day, but never did. A week later, I received an email from him asking for another talk on the phone, but he never replied after I sent him my available times. Neither the interviewer nor the other recruiters replied to follow-up emails, and I got the rejection letter almost a month later.
Overall, interview process and interviewer were all very nice. But not replying to any emails afterwards was kind of frustrating.
It's a one hour long panel interview with two to four engineers. The interview contained behavioural questions, resume walk through, python and c implementation, c trivia questions, os concepts, debugging.
Solicité el puesto a través de un captador. Acudí a una entrevista en Cisco en feb 2026
Entrevista
Applied 1/14, prescreening with recruiter 1/29, interview with hiring manager 2/9, offer 2/13
Very easy interview and manager was super nice! Mostly was just asked about the projects on my resume with a couple problem-solving questions surrounding my projects.
Preguntas de entrevista [1]
Pregunta 1
How would you prove your product's safety to the user? (Essentially asking my testing process)
Envié una solicitud electrónica. Acudí a una entrevista en Cisco (San Jose, CA)
Entrevista
The interview has two rounds:
Round 1 focuses on solving DSA problems within 45 minutes, testing logic, efficiency, and coding skills.
Round 2 involves resume screening and project discussion, where you explain your contributions, technical decisions, challenges faced, and overall understanding of your work.