I applied through a recruiter. The process took 3 weeks. I interviewed at Arista Networks (Santa Clara, CA) in Aug 2016
Interview
Applied online, recruiter mailed next day. 1st round phone interview. 2nd round onsite.
Phone interview is exactly what the other interviewee's say. For the onsite, I wouldn't say the interview questions itself were difficult, but it was difficult to get what the interviewer asked. Rather than giving hints, the interviewer just gave away the answers. Doesn't test your thinking process. Really flawed way of conducting interivews.
Anyway, here are some tips:
1. Be cautious about function arguments. Use const, pass by reference when appropriate.
2. Average and worst case Running time analysis (which is very common)
3. Leetcode doesn't help much for onsite, but helps for phone interview
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!