HackerRank test: 90 minutes, including 2 coding questions and 2 multiple-choice questions. (This is based on my memory; the exact numbers might vary slightly, but this reflects the general format.)
Phone interview: This involved SSHing into a recruiting server. It included 3 questions based on definitions (given code, answer the output) and one coding question. I didn't perform as well as I'd hoped and didn't see all the questions. The recruiter was very nice, patient, and kind. I really liked the interview questions, as they tested my experience and thorough understanding of the subject matter. It felt like coding was on the surface, but the interview questions dug deeper into what lies behind the code. For instance, you needed to know why certain code might cause a segmentation error. The coding question involved a basic linked list.
(Before the interview, I wasn't sure what 'SSH into a server' would entail and spent too much time on that aspect. I didn't implement the coding question, but I believe it would primarily require knowledge of coding using Vim through the terminal. For the definition questions, you'll be provided with an account and password to SSH. The questions will then appear on your terminal, so don't worry too much about lacking prior SSH experience, in my opinion.)
HackerRank:
Phone Interview:
The following metrics were computed from 156 interview experiences for the Arista Networks Software Engineer role in United States.
Arista Networks's interview process for their Software Engineer roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Arista Networks's Software Engineer interview process in United States.