Cisco has no technology religion. We thirst for innovation and continue to adopt new technologies and development processes. We learn from the very best in the industry, and we are willing to change. You will find disruptive patterns everywhere while working at Cisco, whether in technical areas or process-related areas. You will not get bored because everything is continuously on the go. Those who are resistant to change or are uncomfortable with trying new things should not apply.
There is a lot of pressure on individual contributors to get "visible" because of the annual ranking process. The process has a limited quota for top performers, so every year, management fights with each other to promote their own team, and individual contributors step on each other to get ahead. Ironically, Cisco greatly promotes teamwork and collaboration. However, with this limited quota ranking system, teamwork is just a slogan. Only the naive will believe and practice it.
Be more fair to judge individual performance, not relying on what they talk about, but on what they do and how they do it.
Get more technical so you can fairly judge the performance of individual contributors.
This was my first software engineer interview, so I just used it as practice. It started with an online assessment that featured medium-level LeetCode questions. I did not know how to solve the last question, so I was rejected from there, I guess.
Nice people, but hard questions. One phone interview and one onsite interview with four people. All technical questions were asked, with no behavioral questions. It took more than half a day. All questions were coding skill questions.
The recruiter set up a phone screen. This was an hour long, and the interviewer asked me about OS, Data Structures, OOPS, and gave me a problem to solve. Then, there was an onsite round, which consisted of more DS and algorithm problems, varying fro
This was my first software engineer interview, so I just used it as practice. It started with an online assessment that featured medium-level LeetCode questions. I did not know how to solve the last question, so I was rejected from there, I guess.
Nice people, but hard questions. One phone interview and one onsite interview with four people. All technical questions were asked, with no behavioral questions. It took more than half a day. All questions were coding skill questions.
The recruiter set up a phone screen. This was an hour long, and the interviewer asked me about OS, Data Structures, OOPS, and gave me a problem to solve. Then, there was an onsite round, which consisted of more DS and algorithm problems, varying fro