Good exposure to work in Protocol teams.
We can learn from a lot of people who have been in this area for a long time.
No clear roadmap from management.
Very frequent changes.
Difficult to plan on how to move up.
Also, work needs to be assigned depending on grades.
Avoid too many internal changes, which will impact the engineers.
The interview process included use cases, scenarios, technical interviews, and both phone screens and sit-down reviews that spanned two days. They asked very detailed and penetrating questions. They want to maximize work experience by having player
Not the most difficult of interviews. The questions were at an average level for coding interviews, focusing on fundamental data structures and algorithms. They expect a reasonable level of code quality in the answers. You can't get by writing subpar
I received the interview call a week in advance for a recruitment drive at Cisco for their UCS QA team. I was well received on campus and was escorted by HR to the building where the interview was conducted. I was first briefed by the Director rega
The interview process included use cases, scenarios, technical interviews, and both phone screens and sit-down reviews that spanned two days. They asked very detailed and penetrating questions. They want to maximize work experience by having player
Not the most difficult of interviews. The questions were at an average level for coding interviews, focusing on fundamental data structures and algorithms. They expect a reasonable level of code quality in the answers. You can't get by writing subpar
I received the interview call a week in advance for a recruitment drive at Cisco for their UCS QA team. I was well received on campus and was escorted by HR to the building where the interview was conducted. I was first briefed by the Director rega