Good pay, good benefits, usually good work-life balance, and a generally helpful engineering culture.
Very metrics-focused in evaluations, claims not to be. You'll never meet or interact with most of the people evaluating you. They rarely promote people. If they promote you, that means you've been doing the promoted job already for at least a year without matching pay.
Location (in San Francisco) isn't very good. Teams don't always have clear purposes or missions, and they change often.
Every team everywhere is at full bandwidth all the time, usually with months of roadmap. If you need code written in some other team's area, the best you'll get is them advising you while you write it.
Engineering support members (design, research, product, etc.) occasionally change at random with no notice or reason. Biggest con is that they've been fighting various fires non-stop for months. I wouldn't be shocked if they're out of business in a year or two.
Get your employees in the room when people are evaluating them, at least sometimes. It doesn't feel good hearing second-hand from your manager about your performance.
Also, consolidate some of these teams and resources. It's not always clear why a team is needed in whatever area. It sometimes feels like the teams are needed because you have so many managers who need things to manage.
Overall, I would give this interview process a 'meh'. I have conducted numerous interviews over my 10+ years of industry experience, including at companies of this size. The process is long, and you will likely feel strung along. To preface this, ev
1. Call with recruiter to verify I have the relevant skills. 2. Take-home project to create a component with an existing scaffold. I would recommend spending twice the time they recommend to move forward. They will quiz you on what your functions do
Applied online and was contacted by the Tech Lead. It was an hour of live online coding using a tool like Collabedit.
Overall, I would give this interview process a 'meh'. I have conducted numerous interviews over my 10+ years of industry experience, including at companies of this size. The process is long, and you will likely feel strung along. To preface this, ev
1. Call with recruiter to verify I have the relevant skills. 2. Take-home project to create a component with an existing scaffold. I would recommend spending twice the time they recommend to move forward. They will quiz you on what your functions do
Applied online and was contacted by the Tech Lead. It was an hour of live online coding using a tool like Collabedit.