Pros: Roblox is a very comfortable place to work at. All usual stuff that you may see at other successful companies are present: snacks, paid meals, flexible/unlimited vacation, 401K matching etc. Personally I chose Roblox over facebook and google not only because I got a better (or matching) offer from Roblox, but also because I felt that I'd be lost in a huge army of Facebook/Google employees possibly working on something not so important. At Roblox I work now on something that instantly affects entire platform and tens of millions of players and I like that. At google/facebook I'd be getting shares that can be sold for cash any moment, however their value is unlikely to increase tenfold over 4 years. With the way Roblox grows I'm fairly confident value of my options will increase more than 10-x over 4 years of vesting period. Yes, Roblox is not a public company, but it's on a good trajectory to become one: we grow consistently over multiple years in revenue, in user count and retention; Roblox just started to expand worldwide and we have a good CEO and top leadership team. I've been at Roblox just a bit less that 2 years and I'm happy that I chose Roblox over all other options when I decided to move to SF Bay area.

Cons: Perhaps our release cycle isn't something that I'm happy to deal with, or our versioning system. Some senior managers are afraid or not willing to try some ideas. For example, Roblox is not a small, agile startup anymore. So, join us and help us make it better!

Pros: Free lunch, great benefits, and interesting work.

Cons: Still early days for engineering practices.

Pros: Corporate culture of cultivating the strengths of every employee, putting the employee's growth ahead of company growth. Everyone working here is intelligent, thoughtful, friendly, and helpful. Every day is an opportunity to solve challenges no other company has faced. Work goes towards systems for a platform that empowers anyone with an internet connection to follow their ambitions.

Cons: Learning the ropes and onboarding takes some time, and documentation on systems is often lacking. Team structures change rapidly, making it hard to keep track of who owns what.