[pololee]

I was in a small company working on payments team as fullstack engineer. Given the big volume, stripe would be too expensive for us. So we built our own credit card processing service. We integrated with FirstData directly. While I was working on payments, I kept following news about stripe. I love their design and appreciate the deep care they put in their product, even the documentation. I like Patrick and John's inspiring stories and love watching their interviews. After 3 years, I was looking for a new opportunity. Stripe is my dream company. I was lucky to get a phone interview. The conversation went fine. The coding problem was easy. But I could tell the interviewer was not impressed. I couldn't figure out what and why. I was depressed when I got the rejection email. I'll definitely want to try again. Anyone advice or suggestions Stripe folks could offer would be greatly appreciated!

[yitchelle]

Did they give a plausible reason for their rejection? I am just interested if the trend for job rejection reasons is moving towards a more transparent model. In the past and present, it is extremely difficult/frustrating to get the real answers for being rejected.

[pololee]

They didn't give me any specific reasons. The recruiter called me one day after my video interview. She only told me they didn't think I was a good fit. In the interview, I finished the coding questions in 30 mins. Then I just had a chat with the interviewer. The conversation went fine. He told me he was full-stack eng and worked on frontend. I asked him whether he worked with Benjamin De Cock, a stripe designer I admire and if he could share some stories. He said yes but didn't want to share stories.

[rajasimon]

Same here. Done coding challenge and got the interview call but finally, they turned me down.