Pros: - There's opportunity to contribute across technologies and throughout the stack. - There's an unreal level of transparency in terms of business health and management outlook that truly makes you feel like the owner you are. - The noticeably high level of business awareness & eagerness to achieve customer happiness regardless of role is really motivating; the sense of ownership is palpable. - The excitement of a startup & quick iteration with the stability & resources of a company backed by big players.

Cons: Some groups are faced with demands that exceed available bandwidth for the team size, affecting work/life balance; management has acknowledged this and is making sincere efforts to rectify.

Pros: Great culture! Engineering teams are small enough for lots of ownership and not so big that everyone is siloed off from each other.

Cons: There is a possibility for growing pains in the near future.

Pros: There are catered lunches, friendly people, pretty good benefits, and various technologies used in different places.

Cons: Few years ago company had great culture and great values. Nowadays, the values are just mentioned time from time while nobody is really following them anymore. For instance, company constantly advocates itself as being completely open about everything. While at the same time a whole project and respective team was disbanded with 1 day notice, being a surprise even to the team itself. New projects are being announced with extremely short deadlines, and without even consulting about resource availability with teams in advance. There were cases of "secret" projects, that nobody in the company knew about but the team working on them. And even though company has a "Town Hall" type of meetings, most of the really difficult questions are answered with non-answers like "isn't this a great problem to have? this means we are growing!". Amounts of tech debt is staggering. Whenever there's a choice of doing something good for short-term vs something good long-term, short-term always wins and long-term problems will be solved when they become fires. A lot of services still do not have proper tracing/monitoring after literal years of raising this issue. Technical direction is provided by design-by-committee or in other words - there's no technical direction. Either nobody cares about an issue, or everyone discusses it into the ground for few weeks, then gets tired and forgets about it.