←back to thread

1703 points danrocks | 4 comments | | HN request time: 0.001s | source

Recently I interviewed with Stripe for an engineering MoM (Manager of Managers) for one of their teams. I interview regularly, so I am used to many types of processes, feedback mechanisms, and so on. I won't go into details about the questions because there's nothing special about them, but I wanted to share some details of my experience for people thinking of interviewing there.

1) About 35-40% of the interviewers started their questioning by saying "I will only need 20 minutes for this", while emphasizing it is an important leadership position that they are hiring for. So 20 minutes is all needed to identify "important, critical leaders"? What a strange thing to say - also a GREAT way to make candidates feel important and wanted!

2) There is significant shuffling of interviewers and schedules. One almost has to be on-call to be able to react quickly.

3) For an engineering manager position, I only interviewed with only technical person. To me it hints that Engineering MoM is not a very technical position.

4) Of all the people I spoke to, the hiring manager was the one I spoke the least with. The phone screen was one of the "I only need 20 minutes for this" calls. The other one was quite amusing, and is described below.

5) After the loop was done, the recruiter called me to congratulate me on passing, and started discussing details of the offer, including sending me a document described the equity program. Recruiter mentioned that the hiring manager would be calling me to discuss the position next.

6) SURPRISE INTERVIEW! I get a call from the hiring manager, he congratulates me on passing the loop, then as I prepare to ask questions about the role, he again says "I need to ask you two questions and need 20 minutes for this". Then proceeds to ask two random questions about platforms and process enforcement, then hangs up the call after I answer. Tells me he'd be calling in a week to discuss the position.

7) I get asked for references.

8) After passing the loop, have the recruiter discuss some details of the offer, have the hiring manager tell me they'd be calling me after a week, I get ghosted for about 3.5 weeks. References are contacted and feedback is confirmed positive.

9) I ping the recruiter to see when the offer is coming - it's not coming. They chose another candidate. I am fine with it, even after being offered verbally, but the ghosting part after wasting so much of my time seems almost intentional.

10) I call up a senior leader in the office I applied to, an acquaintance of mine. His answer: "don't come. It's a mess and a revolving door of people". I was shocked with the response.

11) I get called by the recruiter saying that another director saw my feedback and is very interested in talking to me and do an interview loop.

Guess I'm not joining, then.

I am ok with passing loops, being rejected, I've seen it all. But being ghosted after acceptance is a first. What a bizarre place this is.

Show context
pc ◴[] No.29388148[source]
I'm sorry; that's bad. Can you email me with details so that we can investigate what happened? (patrick@stripe.com; others welcome to do so too.)

More than 10,000 people have interviewed at Stripe so far this year, so "several sigma bad" still happens to an unfortunate number of people. That said, we want those who interact with Stripe to come away having been treated professionally and respectfully, and our recruiting team cares about fixing our process failures. On behalf of Stripe, I apologize.

replies(9): >>29388290 #>>29388370 #>>29388459 #>>29388723 #>>29388864 #>>29389302 #>>29389310 #>>29389807 #>>29392020 #
lmilcin ◴[] No.29388290[source]
Only some of this could be explained by "several sigma" of bad luck. The rest is either the candidate misunderstanding/distorting the process or a structural hiring problem.

I interview a lot of candidates. I just can't imagine to make a hiring decision for a dev, let alone a manager that manages other managers, based on 20 minute discussion.

replies(4): >>29388352 #>>29388368 #>>29388662 #>>29391311 #
hogFeast ◴[] No.29388352[source]
Describing your recruiting process as a random variable...wut? Does the hiring manager make decisions randomly? Someone calls up, the hiring manager gets out the lucky 8-ball, and it comes out "give a 29th percentile recruiting interview", and the manager just straps on the Biggles goggles to bomb the candidate. Why even say that to someone who is pissed off with your recruiting process? Just don't say anything.

As you say, it is very hard to attribute a bad recruiting process to something that is non-structural...no matter how many thousands of people you hire.

replies(1): >>29388592 #
1. perl4ever ◴[] No.29388592{3}[source]
>Describing your recruiting process as a random variable

Anyone who can do anything with zero variation should definitely drop what they are doing now and make it their new business.

replies(2): >>29388717 #>>29396045 #
2. sombremesa ◴[] No.29388717[source]
I think what GP is trying to say is that your hiring process is within your control (especially this far in the pipeline), so even the worst candidate experience should fall above some baseline. You don't get much sympathy if you say "that baseline turns out to be absolute gobshite at the first percentile, sorry."
3. hogFeast ◴[] No.29396045[source]
The other reply explained this but imagine you bought a soda, and you drank it and it turned out to be rat piss. You call up the company: my soda was full of rat piss. Their reply: "Oh yes, we sell lots of sodas, you couldn't possibly understand how much soda we sell so rat piss soda is a seven sigma event...bye".

If you are in software, recruiting is your business. You have no other real assets. So categorising your hiring process as a random variable makes no sense. You should have processes in place that ensure non-randomness...again, is Coca-Cola out there selling tons of rat piss, and just saying: "Tough luck guys, this is a hard business"...no. If you don't have processes to ensure that outcomes in the core parts of your business are not random, you don't have a business (I used to work as an equity analyst, I have heard this kind of thing from CEOs over and over...I never recommended investing in such business, I have never seen a company that was run that way succeed).

replies(1): >>29400924 #
4. perl4ever ◴[] No.29400924[source]
People report even more clear cut events regarding food products than your example, even. You know, like rat parts. Sometimes they may be hoaxes or urban legends. Not necessarily all the time.

I've seen odd things first hand with processed food from the grocery store. I've bought sealed packages of food that were all dried out and stale. Or that looked fine but gave me...indigestion. The weirdest thing I've seen recently were some mints where some of them randomly were solid chocolate, no filling. Oh, and a frozen dessert had a sealed cardboard box, but the plastic covering inside was open.

How does that sort of variation happen? I'd imagine that the better your process is, and the less variation you have, the larger proportion of your failures will be "unknown unknowns" that are just weird.

I acknowledge the conclusion that the interview process is f-ed up could well be correct.