Software Engineer applicants have rated the interview process at Arista Networks with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 56% positive. To compare, the company-average is 60.3% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 13 days to get hired, when considering 224 user submitted interviews for this role. To compare, the hiring process at Arista Networks overall takes an average of 14 days.
Common stages of the interview process at Arista Networks as a Software Engineer according to 224 Glassdoor interviews include:
One on one interview: 31%
Phone interview: 28%
Skills test: 19%
Presentation: 6%
Group panel interview: 6%
Background check: 3%
IQ intelligence test: 2%
Other: 2%
Drug test: 2%
Personality test: 1%
Here are the most commonly searched roles for interview reports -
I applied online. I interviewed at Arista Networks in Dec 2015
Interview
I was contacted on LinkedIn for a Software Engineer position on network products.
First step was an online coding test on codility.com which was rather simple (I would say even easier than the codility demo task).
The first phone screen was ok. I talked to a technical person and had a nice technical discussion, involving networking and programming questions. He was able to provide more information about the role.
The second phone (actually on a conference tool) interview gave me an extremely negative impression. I think it was with some technical manager (and I think the person from the first interview was also there). I found it really strange (and stupid) that we were using a conferencing tool but without the video (even if video was available) and I had no idea who I was talking to and the communication was suboptimal just by phone.
The person on this second interview seemed to have no interest in actually conducting the interview. He through out some questions, didn't have patience to hear my answer, kept pushing me to write the code on the screen even if I didn't get the change to understand what he was asking, then he was surprised that I was not writing the code that he wanted. He constantly ignored my explanations and have evasive answer on what he actually wanted, then quickly moved to another topic leaving the previous in the air.
Both sessions involved ssh-ing into a sever and using screen to share what you are typing with the other side.
The position itself looked interesting, but that second interview gave me such a negative impression, I wasn't interested in it anymore. I am pretty sure I conducted way more interviews than the guy on the other side so it may be a sign that the company is kind of disorganized when it comes to talent acquisition.
Interview questions [1]
Question 1
programming questions like how to tell if a string is a palindrome and how you sanitize input.
I applied through a recruiter. I interviewed at Arista Networks in Jun 2026
Interview
Pros:
Great initial approach – the recruiter thoroughly checked my GitHub profile and projects before the interview, which is very uncommon and shows they do their homework.
Cons:
A major mismatch between the job description ("Software Engineer C++") and the actual interview reality. The technical stage on CoderPad strictly tests bare-metal C98 skills: raw pointers, manual bitwise operations, and packing bytes into 64-bit integers. If you are accustomed to modern C++ (RAII, templates, safe memory management), this will feel like a massive step backward. Additionally, the time expectations for live low-level bit-shifting were unrealistic, to the point where the interviewer started solving the task themselves.
Interview was kind and not stressful, just minor mismatch of naming
I applied through a recruiter. I interviewed at Arista Networks (Łódź, Lódz) in Jun 2026
Interview
Reached round 3 out of 4 planned, one was coding task, two live coding sessions. Linux development background was highly expected. Performance optimized approach was tested, specially oriented for hardware with lots of resources. I had a problem to properly understand reqruiting person during round 3, voice was not clear for me.
Interview questions [1]
Question 1
List implementation, bits counting, tre traversal.
Pretty good, not too complicated, was comfortable. Mostly LC questions, and was easy enough that you should be able to do it after doing NC150. good luck for the interview!