Pros
+ mission-driven environment + tangible impact in the form of published research in journals + (mostly) modern development stack + remote-friendly - benefits are/were okay
Cons
Leadership should be ashamed of themselves for creating a toxic environment at a company centered around mental health. The core issue: 1. Feature development was repeatedly prioritized over quality, which led to 2. Too many critical production failures, which led to 3. Leadership forced turbulent process changes to "fix" it, but they still didn't invest in automated quality and alarms 4. Then, engineering leadership eroded trust by repeatedly demonstrating petty interpersonal behavior and not responding to engineer feedback. He thinks he can shove aside emotion and make decisions solely with his mind (or, in his words, his "laser logic sword"). Other cons: - low pay - it's a trope that engineers hate meetings, but too many meetings with pointless "filler" content is nearly unforgivable - SF-based employees are given preferential treatment - required employees to share hotel rooms (and tents) at company on-sites