|
|
|
|
|
by ss3000
2072 days ago
|
|
Exactly, it's clearly not a lack of resources, but explicitly not prioritizating candidate experience for candidates you're not actively pursuing. Which, by the way I think is a totally valid decision to make, but let's not kid around and make it sound like your hands were tied. |
|
(1) The practical reality that a lot of people will have a suboptimal experience until we (both "we Stripe" and "we the industry") figure out more scalable ways to assess people. We'll do the best we can to identify promising people but a lot of people will get something somewhat functionally equivalent to a form rejection. You could argue that this is merely a prioritization decision -- we could keep hiring recruiters until everyone could be individually assessed -- but doing so would require a recruiting team of comparable magnitude to the rest of the Stripe organization and so the current state is an unfortunate compromise given the current constraints and given the decision to have an open application form (which is, I think, on net better for everyone).
(2) Cases where people at Stripe mishandled the process. I know for a fact that some of the anecdotes shared in the thread are from many years ago, and I know that our process has improved since then (we have empirical data to this effect), but we're also acutely aware that we continue to make mistakes -- recruiting is a high-stakes and complex process with a lot of fallible moving parts. For whatever it's worth, we issue CSAT surveys to every candidate who interviews (about 6,000 onsite interviews in 2019), and track the results both at the aggregate Stripe level and at the individual recruiter level. And I get why some people here sound so annoyed -- what might be "another entry in a database" to a recruiter or hiring manager is "the future of my career" to someone on the other side. While it's always hard to know what to make of a set of anecdotes, and while our referral rate among Stripe employees is very high today, I'm nonetheless bothered by the number of cases shared here, and we're going to be digging in. (Specific anecdotes with more concrete dates or data are welcome at patrick@stripe.com.)