I applied online and received a call from a screening recruiter. They then scheduled a remote CoderPad interview with one of their engineers.
The next day, the recruiter called again, stating they wanted to conduct a second, UI-related CoderPad exercise with another engineer.
Soon after, I received a call inviting me for an on-site interview. As far as I was concerned, it went quite well. It included two additional programming exercises, a bug-finding exercise, and a meeting with an engineering manager to discuss goals.
However, the following week, the recruiter informed me they had decided not to proceed with my application. This was highly frustrating, as I believe the first two remote programming exercises should have clearly indicated whether they intended to hire me. If they weren't 80-90% sure by then, they should not have wasted my time (an entire day) by having me come on-site.
Find the minimum value in a dictionary.
Create a UI element/component with built-in input validation.
General stuff, like why Stripe, and what are you looking for?
Find and fix a bug in a third-party library.
The following metrics were computed from 4 interview experiences for the Stripe Full Stack Engineer role in Dublin, Ireland.
Stripe's interview process for their Full Stack Engineer roles in Dublin, Ireland is very selective, failing most engineers who go through it.
Candidates reported having very negative feelings for Stripe's Full Stack Engineer interview process in Dublin, Ireland.