A really positive experience through the whole process, which took 5 weeks from the first interview to the offer.
The first interview was a technical phone interview where I remoted in via SSH to work with some files. There were a few C questions, but I don't have much experience with C, so the interviewer let me do the algorithm stuff in Python.
The second interview was a 2-hour onsite where I worked through a whiteboarding problem with an engineering manager for about an hour. Afterward, the CTO joined, and I worked through a couple more questions with him.
Both interviews felt more like an interesting two-way conversation than me being awkwardly put on the spot and judged, which I really appreciated. I'm a new grad, and both of them knew orders of magnitude more than me, but still didn't talk down to me at all. They even left me with a list of 3-4 cool data structures/algorithms to look up when I got home.
Basic questions about C pointers as they relate to Strings.
Evaluate the performance of two simple implementations of popcount().
Given a node in a BST, find the next greater element.
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.