Stripe relies on a huge range of technology to build the best commerce tools available on the internet. In my roles as a software engineer, that has given me the opportunity to work on machine learning infrastructure, user-facing big data products, and a sophisticated financial backend, among other projects.
The company does worthwhile work. I'm proud that we've helped put hundreds of thousands of folks in business online. And I love that we're powering platforms blazing a trail for creative people to earn a middle-class living online.
There are always bumps along the road for any growing company. The continual changes in infrastructure, tools, documentation, and process can be disorienting at best and frustrating at worst.
Standard SWE interview process: * Recruiter call * Tech screen (60 min DSA problem, not out of LeetCode but probably equivalent to LeetCode Medium) * Final 5-hour loop with pair programming (also DSA), system design, debugging, API integration, and
My experience interviewing at Stripe has surpassed every other company by a wide margin. Every person I spoke and met with was nice, smart, and professional. The recruiters give you just the right amount of preparation material about what the next st
Overall process: * Skype interview: * Started with a generic behavioral interview. * Spent the rest of the time coding two different technical questions in an editor of your choice. * 5-hour onsite: * There were 3 technical in
Standard SWE interview process: * Recruiter call * Tech screen (60 min DSA problem, not out of LeetCode but probably equivalent to LeetCode Medium) * Final 5-hour loop with pair programming (also DSA), system design, debugging, API integration, and
My experience interviewing at Stripe has surpassed every other company by a wide margin. Every person I spoke and met with was nice, smart, and professional. The recruiters give you just the right amount of preparation material about what the next st
Overall process: * Skype interview: * Started with a generic behavioral interview. * Spent the rest of the time coding two different technical questions in an editor of your choice. * 5-hour onsite: * There were 3 technical in