Pros
Company name. Successful success. Interesting engineer culture, salary, stock options, breakfast and lunch, nice location, smiley people, smart everything (almost). Code quality in most cases is decent. Very open company culture, you know all details about the company progress, what is happening, what should be improved and so on. A lot of opportunities to learn and get fun.
Cons
Rapid company growth affects staff quality sometimes. Some managers play strange games and change rules on the fly. Very fast pace, in half of teams you can forget about drinking coffee with colleagues - you don't have time for that. Cross-team communication issues, constantly. Asynchronous culture doesn't work - you may wait for answers forever. To get answer you need to escalate, and for some reason your manager won't do it even if you ask them, so do it yourself. People says you may be asked to shut up and stop highlight problems on the company level. Expectations from your code are completely different from codebase quality (which is sometimes dirty and hacky) and often unclear. Different teams follow own architecture and code styles, so passing pull request review may be a kraken hell. Code monorepo adds, it's often impossible to avoid conflicts in PRs, difficult to push your changes (github locks/outages). Declared values and approaches not always a truth.