Pros
It's one of the more demanding, rewarding, and genuinely interesting places I've worked. If you show up ready to own your work and grow fast, you'll thrive. If you need a lot of structure and a clearly paved road, you'll struggle.
The AI-first commitment is real. This isn't a company slapping "AI" on a slide deck and calling it a strategy. There's actual investment in helping team members build AI skills, learn new tools, and work smarter. It's one of the more forward-thinking things the company does for its people, and it shows up in how work actually gets done day to day.
The people are the other big one. Across almost five years, I've consistently worked with sharp, collaborative, motivated people who actually care about doing good work. The kind of colleagues who raise your game just by being in the room. That's not something every company can say, and it's worth a lot.
Autonomy is real here too. You're trusted to own your space, make decisions, and drive outcomes without someone looking over your shoulder. That's a gift if you know how to use it. And the expectations aren't just about volume of work, they're about the quality, the speed, and the ownership behind it. You're expected to bring solutions, not just surface problems. To move fast and think ahead. To operate with a level of maturity and self-direction that some environments don't ask for until you're several levels up. That can be energizing, but it can also feel relentless if you don't have a strong sense of your own boundaries and capacity.
The collaboration across teams is genuinely strong. People here work together, not around each other.
Cons
The company asks a lot. A lot. The workload is real, the expectations are high, and the pace doesn't really let up. For some people, that's the whole point. For others, it's a slow burn. I'd say it's the single biggest thing to be honest with yourself about before joining. It's not a culture where you can quietly cruise.
The autonomy that shows up in the pros cuts both ways. Sometimes "you own it" means there isn't a lot of infrastructure or guidance underneath you. You figure things out as you go, which builds capability but can also mean navigating ambiguity that could've been resolved upstream.