Me postulé a través de una facultad o universidad. El proceso tomó 3 semanas. Acudí a una entrevista en Arista Networks (Santa Clara, CA) en ene 2011
Entrevista
3-part interview consisting of a phone screen, and then 2 (back-to-back) interviews with a manager and then a founder. The screen was on programming basics over a shared ssh screen session (data-structures, memory management, basic C stuff, general algorithmic questions, etc). The interviews consisted mostly of more coding and design questions (designing a generic data collection's interface) with only a cursory discussion of my resume.
Preguntas de entrevista [1]
Pregunta 1
Oh, operating systems was your favorite class? Well, how do you feel about the way [such and such OS] lays out their virtual memory in [such and such a manor]. Oh, you don't know that? Let me explain it to you, and let's analyze the design tradeoffs they made.
Me postulé a través de un reclutador. Acudí a una entrevista en Arista Networks en jun 2026
Entrevista
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
Acudí a una entrevista en Arista Networks (Vancouver, BC)
Entrevista
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!
Starts with online test, then three rounds of technical interviews follow.
Not a lot of discussion, just go straight to the technical challenges which have to be solved in time