The process began with a standard phone screen, followed by an onsite interview. It took approximately two weeks from the initial recruiter call to the onsite interview. However, the result took a very long time, likely due to bureaucracy. Cisco appears to have a deep hierarchy, and it's unclear if all layers are synchronized during the interview process. It felt haphazard. They seemed unprepared for the interview, with a significant delay in starting (25 minutes!) and uncertainty about who would interview next. To top it off, they didn't even know if there would be anyone else to interview me afterward.
Although five rounds were scheduled, after four, they stated they were finished and that I had performed well. This was confusing.
A week later, I heard back from the hiring manager, who assured me an offer would be extended soon. However, this never materialized. Despite multiple follow-ups, there has been no response from Cisco.
This is unacceptable. Candidates dedicate more than half a day to interviews and expect clear communication and a definitive result. I am surprised by this unethical approach to managing candidates and cannot picture myself working here.
Kernel-level questions, some standard string, array, and linked list questions. A lot of current experience-related questions. System design questions.
The following metrics were computed from 125 interview experiences for the Cisco Software Engineer role in San Jose, California.
Cisco's interview process for their Software Engineer roles in San Jose, California is on the easier side as most engineers get an offer after going through it.
Candidates reported having very good feelings for Cisco's Software Engineer interview process in San Jose, California.