Pros
+ Tons of upside and fast career mobility + Get to work with some of the brightest minds in the valley, both internally and externally + Lots of room for the company to grow, and tons of foundational work to be done. Just because we're a unicorn doesn't mean things are slowing down. + Trust is assumed and ownership is given quickly. You will not be pigeon-holed, especially if you communicate and are proactive. It's hard to believe some of the engineering posts here are from actual Scale engineers. To say we aren't a real tech company, these other reviewers must have not spent much time with many of our product systems. There are many operationally intense tech companies (AWS, Uber, etc) and yes, we are one of them. If you want a 9-5 or a place where you're given lax timelines where it really isn't make a big deal if your code is pushed tomorrow or several weeks from now, Scale is probably not the place for you. Scale is a place where you get what you make of it. Proactivity is your best friend. If you think things should be done differently, say something. If you think there's high impact work that is not being done, bring it up or just go do it. There's so much opportunity to stand out and do really impactful work, and Scale will recognize and reward you for it. If you do end up joining Scale, I highly advise you to try and deeply understand how the business works. Being able to drive product direction with context is one of the most direct ways to become invaluable here. You'll have a pretty different experience if your only input is from ticket descriptions.
Cons
- Hours can be long (as a result of big ownership & growth pains) - Owning big outcomes can be stressful - With how fast things are moving, it can be hard to make the trade-off to always build things the right way the first time - It can be hard to standout among such a talented team - There have been some issues with culture, but once leadership heard and understood the issues, they've been very active in figuring out how to solve it. They certainly aren't all solved, but we're making good progress