Good benefits and pay. Definitely a cool company to work for resume-wise. A good IPO will be a big payday to employees, but if you don't care much about money, maybe other companies can be more challenging and better for your career.
Engineering management is really bad. Managers do not pay attention to career growth, given that the career ladder is taboo inside the company. Nobody talks about or knows their position, so don't expect your manager to advise you much about how to go from level A to level B, C, etc.
When people get bored in their current position, they either switch teams or branch out into management (lateral moves), which feeds back into the problem where management focuses on reporting green numbers to upper management.
Invest more in training managers to focus on people and their careers, less on project and risk management.
A recruiter contacted me through LinkedIn. This experience was particularly disappointing because the recruiter painted a picture of an engineering culture that was the opposite of what it turned out to be. I had the impression that they cared more
Restrictions for planning an interview are really tight; you essentially can't reschedule after you've made the plans. It's a typical and straightforward interview, though, where you just go right into a coding question.
The interview process was fairly typical: * 20-30 minute call with a recruiter to discuss the role and next steps. * 45-minute phone call with an engineer. For my interview, this wasn't typical coding trivia. Instead, we went over a practical co
A recruiter contacted me through LinkedIn. This experience was particularly disappointing because the recruiter painted a picture of an engineering culture that was the opposite of what it turned out to be. I had the impression that they cared more
Restrictions for planning an interview are really tight; you essentially can't reschedule after you've made the plans. It's a typical and straightforward interview, though, where you just go right into a coding question.
The interview process was fairly typical: * 20-30 minute call with a recruiter to discuss the role and next steps. * 45-minute phone call with an engineer. For my interview, this wasn't typical coding trivia. Instead, we went over a practical co