I attended a job fair and spoke with the representative handling potential Software Engineer I applicants. This initial screening aimed to ensure I wasn't completely unqualified.
I passed this initial stage at the career fair and was promptly scheduled for an interview at my college career center.
The interview lasted approximately an hour and 15 minutes, with two interviewers present. They asked numerous questions about my academic projects, team experience, and differences between Java and C.
One interviewer was calm and friendly, while the other appeared more severe and judgmental of my responses. Although he likely intended to be intimidating, his demeanor came across as off-putting rather than frightening.
The questions covered topics such as handling team issues and leadership, as well as a detailed comparison of Java and C, including their compilation and interpretation processes.
It was a behavioral question and surprised me the most out of everything.
If you were given only a week to do a project and you knew there was no way you were going to finish it in the time allotted, what do you do?
Basically, you knew you weren't going to finish it in time, but your manager essentially doesn't understand that (not explicitly stated).
The following metrics were computed from 17 interview experiences for the Cisco Software Engineer I role in United States.
Cisco's interview process for their Software Engineer I roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Cisco's Software Engineer I interview process in United States.