The everyday people you interact with at Stripe are world-class. As you go up the management chain, however, this becomes less and less so.
Important decisions are kept hidden but they promote "transparency". They're constantly behind on projects. There's a large hierarchy of managers of managers of managers. Re-orgs happen every few months. Getting up a level is a pain, and it's no longer worth it because RSUs stay the same. New joiner L4s are earning less than L1s. The largest con is that the work weeks are > 70 hours, and everyone's always online but never responding when you need them.
Scale down, cut Muda, focus on core products. Large internal projects keep getting delayed. Think about why.
Phone Screen, a typical Stripe interview question which is really easy but long, contains three parts. You can find them on the website. It'll take you a very long time to finish if you use Java.
Online assessment, then a technical phone call with one question, then a battery of rounds on Superday with various coding portions, then a hiring manager behavioral interview. Standard fare, to be perfectly honest.
The phone screen is ridiculous. The question is simple, but very time-consuming if coding with Java. The interviewer will give questions one by one, and they are all related. However, the implementation may not be optimal if not given all questions t
Phone Screen, a typical Stripe interview question which is really easy but long, contains three parts. You can find them on the website. It'll take you a very long time to finish if you use Java.
Online assessment, then a technical phone call with one question, then a battery of rounds on Superday with various coding portions, then a hiring manager behavioral interview. Standard fare, to be perfectly honest.
The phone screen is ridiculous. The question is simple, but very time-consuming if coding with Java. The interviewer will give questions one by one, and they are all related. However, the implementation may not be optimal if not given all questions t