Pros: - A *really* great and worthy company mission that is clearly communicated and very motivating. - Ara and Vahe are amazing leaders in my opinion. - Daily work on engineering teams clearly impacts customers' lives in a very positive way. - Able to work at a sustainable pace. - No micromanagement, but strong (and reasonable) expectations of delivery pace. - The compensation and benefits are decent and competitive. - Opportunities to excel and distinguish oneself within team scope.

Cons: - I have absolutely no idea what's going on outside my team besides what I see in official communication channels. - After a year of working remotely (from another state), I still feel very little personal connection with most of my teammates. - The product is *incredibly* vast, and it's all I can do to stay on top of my own team's work. Becoming recognized or even known outside of one's own team is nearly impossible without working at the Staff+ level on a platform or ops team. To have significant cross-team impact, it seems a person has to have what usually amounts to Principal Engineer skills. - As a result of all of the above, building personal connections, even within my own team, has been difficult, and building personal connections with people from other teams has been impossible. For my personality type, it has been hard not to have the sense of motivation that comes from being personally known, trusted, and relied upon by my co-workers. - If you live in the Glendale area or are able to travel there a few times a year (on your own dime), the above problems will be mitigated.

Pros: Reasonable and inspirational management, great compensation, and growth opportunities.

Cons: Not a single con really.

Pros: The people seem nice enough. Space has much potential. Compensation is decent, and benefits are probably OK for most.

Cons: The code-base is under-documented and disorganized, and seemingly small functional changes can easily involve dozens of files. It's also overly engineered, but in areas that aren't conducive to product health and maintainability. Working around crazy tech debt, poor practices, and dicey processes takes up more time than actual problem solving. Unnecessary complexity and tons of runtime feature enable configs used institutionally lead to many, many bugs that are difficult to reproduce. Myopic management fails to recognize it as a problem. Engineer performance criteria are inadequate and heavily favor engineers who have been at the company for many years; you need to be a rock star to break even. Onboarding is wholly inadequate for engineer hires, and it's mostly HR stuff and customer training tutorials focused on one or two product areas. You are at the mercy of tribal knowledge and reverse engineering for the initial several months. The stress of tight deadline expectations means your requests for help often go unanswered. Deadlines are often bumped forward, often cutting time in half. Gaining access to key systems is haphazard, with no list when onboarding and no clear direction on where to obtain access once a need is determined. It is a cheap version of big-name health insurance. My last job was using the same insurance company with a different plan, and non-generics cost me at least 4x more out of pocket than I ever paid previously for them. There is the familiar problem with "unlimited PTO/sick time" which is offered, but use is frowned upon. Trying to find employee resources in the intranet can be annoying because of a lot of outdated material lingering.