The first round was onsite and consisted of standard questions:
argc and argv).Coding was done directly in the terminal.
The second round comprised two one-hour interviews.
At the start of the first interview, the interviewer stated upfront that there would not be a second round if things didn't go well. The interviewer then asked me to design a stack API for a generic stack, using a dynamic array for implementation. (For details, you can search for "programming paradigms Stanford generic stack" online, which includes a YouTube video).
Questions were also asked about the implementation of memcpy and memmove. Additionally, I was queried on how free memory is managed in the heap and the number of push/extra copy operations required when resizing the dynamic array for storing the stack by doubling its capacity each time it becomes full.
At the end of the first hour, the interviewer said, "Sorry, this doesn't seem to be a good fit." I was quite shocked, as I felt I had answered all the questions adequately and didn't truly grasp the interviewer's expectations.
This experience suggests a strong emphasis on skills related to Stanford or Cisco. While I wouldn't go so far as to claim bias, I received a mixed impression. It's worth giving it a shot.
Stack API
Delete nodes from linked list
Size of structure
Code to debug
The following metrics were computed from 20 interview experiences for the Arista Networks Software Engineer role in Santa Clara, California.
Arista Networks's interview process for their Software Engineer roles in Santa Clara, California is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for Arista Networks's Software Engineer interview process in Santa Clara, California.