Real, anonymous reports from people who interviewed for Software Engineer at Arista Networks, newest first and distilled into what to expect across the loop.
My interview journey started with an online assessment, and then roughly a week later I joined a virtual technical round on a coding platform where I had to write and run everything in the IDE. The questions skewed toward data structures—linked lists and trees came up repeatedly—plus some pointer-style questions. I remember the interviewer being fairly relaxed, which helped, but the structure still felt very “solve and implement,” not a discussion.
My interview started fairly normally: a recruiter call where we talked through my resume in detail. I went over the fields I’d worked in and the projects I’d built, and we discussed different options that fit my background with what the team might need. From there, the technical portion leaned heavily on standard problem-solving.
The interview process typically begins with a recruiter call that focuses on discussing the candidate's resume and fit for the role. Some candidates reported issues with missed calls or abrupt rejections based on perceived fit, leading to a frustrating start.
Candidates generally start with an online assessment that includes coding challenges focused on data structures and algorithms, often using platforms like HackerRank. Success in these assessments is crucial for progressing to the next stages, but some found the format stressful and time-constrained.
The technical interviews often involve live coding sessions where candidates solve algorithmic problems in real-time, with a strong emphasis on data structures like linked lists and trees. The environment is typically structured and performance-driven, leaving little room for discussion or exploration of concepts.
Candidates reported that the evaluation criteria seemed focused on solving specific problems quickly rather than assessing overall experience or understanding. Many expressed confusion over feedback and the disconnect between performing well on tasks and not progressing in the process.
Several candidates noted issues with communication throughout the interview process, including delays in feedback and unclear timelines. This lack of transparency contributed to a feeling of uncertainty and frustration, especially for those who felt they performed well in interviews.
The final rounds often include discussions with higher-level managers that assess both technical skills and cultural fit. Candidates found these discussions to be more conversational, but still challenging, as they required clear communication of thought processes and problem-solving approaches.
