Arista has a good work-life balance with flexible hours, and they just started matching 401k contributions. The products are more reliable than their competitors', and Arista employs a comprehensive automatic unit-testing system that is unlike anything the competition has.
During interviews, Arista proudly touts that every employee is afforded time to do interesting work, with teams employing rotating job schedules in which every employee takes turns at the interesting aspects of software engineering and the not-so-interesting aspects of software engineering.
What actually happens is that team managers come up with multiple ways to describe bug-fixing and rotate the same two to three employees through different "projects" that are all the same maintenance work. If you're not one of these two to three employees, you might enjoy working on interesting projects and learning new things.
At Arista, bonuses and raises are determined by the "A-review/peer-bonus" system, in which every employee rates their colleagues based on their perceived contributions to the company. Naturally, this tends to favor the same employees who are getting the interesting projects, since nobody cares about fixing bugs. If you don't get a good A-review, then you aren't getting any bonuses or raises that year.
So, you can waste your life away by working hard and cleaning up other people's bugs, and maybe after a couple of years, you might get slotted into a project visible enough that your coworkers might notice what you're doing and you might get a peer-bonus or something. Alternatively, you can fill out a job application at one of Arista's many competitors and get a much larger pay-hike now.
Not all of us were here before the IPO. You need to give newer employees a reason to stay instead of taking them for granted.
The inane review/peer-bonus system might have worked out well enough 5 years ago when everybody was grateful to have a job at a startup with a bright future and a big payout imminent. Those of us who weren't here before the IPO need a real reason to stay, especially when other companies are giving us good incentives to leave.
I received the initial interview offer fairly quickly after submitting my resume at a career fair. The first technical interview was straightforward, presenting a medium-difficulty question. It required a solid understanding of the material, and the
This was for a new grad position. The process involved a phone screen with basic technical questions. This was followed by a phone interview coding test where you SSH into the interviewer's laptop and solve a few coding problems (around LeetCode eas
The interview is conducted over the phone. I need to access their remote server using SSH and answer prepared questions. The interview lasts for an hour. I also need to implement an algorithm using Java.
I received the initial interview offer fairly quickly after submitting my resume at a career fair. The first technical interview was straightforward, presenting a medium-difficulty question. It required a solid understanding of the material, and the
This was for a new grad position. The process involved a phone screen with basic technical questions. This was followed by a phone interview coding test where you SSH into the interviewer's laptop and solve a few coding problems (around LeetCode eas
The interview is conducted over the phone. I need to access their remote server using SSH and answer prepared questions. The interview lasts for an hour. I also need to implement an algorithm using Java.