Great name recognition on your resume. Typically smart and competent coworkers. Wide market deployment for Cisco hardware, good exposure to customers. Stable company. Attention to good development practices like code review, unit tests, etc. Good benefits.
Big companies mean a lot of momentum, so change happens slowly.
Support and maintenance for existing/legacy software can be frustrating.
Some managers have no personal lives and expect you to behave similarly, often with the expectation of constant availability by email and working on weekends.
Too much process slows down the pace of development.
In many ways, the problems at Cisco are because of the company's success.
Now, Cisco is extremely large and change happens slowly.
New ideas take a long time to adopt, and even that requires constant driving.
The solution to every problem is not always additional process. More decision-making should be left to engineering expertise, not a one-size-fits-all process that can be applied universally.
I interviewed at Cisco after being laid off from another big company where I worked for over three years. All the interviewing went well. I had at least 13-14 interviews over the phone, as the team was geographically distributed. I felt I did "except
I was referred by an employee and received an immediate call from the recruiter to discuss my interest. The hiring manager then called to have a brief discussion about my background and qualifications. After that, I was invited for an on-site inter
The recruiter called to check basics. I had one phone screen for 30 minutes, followed by an on-site interview with six team members. There were no hard questions compared to expectations. Only one engineer asked a question on linked lists. They seeme
I interviewed at Cisco after being laid off from another big company where I worked for over three years. All the interviewing went well. I had at least 13-14 interviews over the phone, as the team was geographically distributed. I felt I did "except
I was referred by an employee and received an immediate call from the recruiter to discuss my interest. The hiring manager then called to have a brief discussion about my background and qualifications. After that, I was invited for an on-site inter
The recruiter called to check basics. I had one phone screen for 30 minutes, followed by an on-site interview with six team members. There were no hard questions compared to expectations. Only one engineer asked a question on linked lists. They seeme