Pros: It is a very positive and friendly place to work.

Cons: There are growing pains, and the commute time is long.

Pros: * Autonomy for good work * Scale and user impact * Talented colleagues * Inclusive

Cons: Cultural emphasis is limited by WFH.

Pros: They give you two floating holidays and several mental well-being days off (you'll need them).

Cons: CEO's ego got so bruised during a Q&A that he punched down at an engineer during the company-wide all-hands to avoid answering a highly-upvoted question about why he was requiring his approval as a launch blocker for everything -- even string changes. Many engineers have mentally checked out because of the IPO and are doing the bare minimum to prevent the ship from sinking. Engineers aren't rigorous and don't value testing code they're submitting (manually or via automated tests), leading to broken features that are only discovered weeks or even months later. Company knows that the biggest barrier to profitability is customer service costs, so they hide the phone number and laid off all CS people in high-cost areas, then re-hired customer support agents in Montreal. Middle management and upper management set arbitrary deadlines to appease both the CEO's random requests and marketing pushes for "splashy" launch events. Bus factor is high, with teams usually having one frontend engineer per platform (so one iOS person, one Android person, and one Web person). Little interaction between different product teams, so iOS people are reviewing Android PRs and vice versa. Management's response to engineers leaving (and taking institutional knowledge with them) is to hire external temp contractors to build out company infrastructure. Tech debt is absurdly high, with 5-year-old TODOs masking actual bugs. Engineers don't own their own TODOs and swap teams or leave before fixing them. Getting promoted is hard, so people are constantly launching new frameworks and forcing other teams to migrate to them, leading to too much churn.