Some of the benefits are OK, but they evaporate once you get to understand how disgustingly Stripe treats its own people behind closed doors. It's a sad situation, and nobody in upper management seems to care about it. Why? I think everyone is afraid of being let go by either Patrick or John Collison. That can happen on a whim. Not to mention the recent 1000+ people being laid off.
Initially upon joining, you may see a ton of pros and whatnot, but eventually the pros turn into cons, plus the insane workload and expectations from everyone in the product teams. I've spoken to multiple engineers in other Stripe product teams (than my own), and everyone agrees: the expectations are too high, while CEO Patrick and co-CEO John (I'm not sure what to call him) are nowhere near as overworked as us. It's apparent that they don't put in as much effort as the technical teams. Why? I'm not sure why. Maybe because they think they've already "made it" to the big bucks, and they can rule and be rude to the low-profile engineers in the company? I've never expected this kind of treatment of people at Stripe. Never. While in public, Patrick and John Collison run a narrative of being the good guys, behind the doors, well, they are clearly NOT. It's frustrating and exhausting. I've seen too many of my colleagues getting overworked and frustrated with the instability of decisions from both of the CEOs.
Do not be afraid of the Collison brothers and start fighting for your true beliefs.
Or at least show some principles and character.
I had an initial call with a recruiter where we discussed past experiences and what I was looking for in my next role. The recruiter was pleasant and the conversation was laid-back.
The usual three-step process follows initial calls. This process does not use LeetCode, unlike other big tech companies. Overall, it was a good experience, and I would interview again. System design questions are standard compared to other compani
Pros: * Streamlined scheduling for recruiter and technical interviews. * Screening for multiple locations and teams. Cons: * One hour technical interview was supposed to be 45 minutes for coding, but since the question involved multiple parts (up
I had an initial call with a recruiter where we discussed past experiences and what I was looking for in my next role. The recruiter was pleasant and the conversation was laid-back.
The usual three-step process follows initial calls. This process does not use LeetCode, unlike other big tech companies. Overall, it was a good experience, and I would interview again. System design questions are standard compared to other compani
Pros: * Streamlined scheduling for recruiter and technical interviews. * Screening for multiple locations and teams. Cons: * One hour technical interview was supposed to be 45 minutes for coding, but since the question involved multiple parts (up