Transcript
A (0:00)
You hear me through your headphones, I assume?
B (0:03)
Yep.
A (0:04)
So can you tell me who you are and what you do?
B (0:07)
Yes. I'm John De la Motte and yeah, I have for the last about 10 years or so, I've been a software engineer. I've worked kind of all around and done a lot of platform type work, so stuff where I'm supporting other engineers at companies and working on the tools that they used.
A (0:26)
And like, I usually like to tell people before we start what my thoughts are about the episode, but I maybe we. You need to help me figure out what yours is.
B (0:37)
I think it is kind of a story of like putting my hope in something and then realizing like, it was very misplaced.
A (0:49)
Hello and welcome to CO Recursive and welcome to 2025. I'm Adam Gordon Bell. Today's story is about career change in John's trying to get a job at Stripe. Working at Stripe, eventually leaving. And it's super fascinating. It's a very candid look into identity and relationships and performance reviews, culture, relationships. I don't even know how to set it up. You won't be able to predict where the spawn is going, I promise you that. But yeah, it all starts with John trying to get a job.
B (1:27)
I had, I had a few friends who had worked with me at my previous company and they worked at Stripe and they were like, hey, you should come get a job over here. I thought Stripe was the coolest company. I was really actually particularly interested in it because they did sort of financial infrastructure. My dad was an entrepreneur and he honestly, from the age of about like maybe, yeah, 12 or so, he kind of had groomed me to almost take over for him in his business, in finance. And so until I was about maybe 25 or so, my life trajectory was I'm going to go get a job in software engineering and I'm going to work here for a while and then I'm going to like take all this, this stuff that I learned over here and then I'm going to go work with my dad. And so when Stripe came along, I was like, oh, this is perfect. It's a company I really respect. They have really high engineering standards. It's got people I really like that are working there and like it. I could go like, actually see what it's like to work in a real company that does like real like financial money movement stuff. So it kind of ticked all the boxes for me. And I applied at Stripe and yeah, I remember that was super nerve wracking. I was like way overprepared for the interview. I was like, I'd been writing typescript at the time for, I don't know, maybe like six months or something. And so I had this impression of like, oh, strike. Such craftsmanship, such quality. Like, I got to make sure that I, like, show up in the interview super well and present myself. Like, I really care about craftsmanship. And so I had my ide all set up. I was like, I was so focused on making sure that like, I had the testing and the types all right, that I actually ended up like sucking on the question. So that was tough. It was tough to swallow, like the failure there. I got turned down. And then I tried again six months later because they were like, hey, you can re interview in six months. And then that time around, I made sure I did a bunch of practice interviewing beforehand. So I was like, okay. And I talked to some other people who worked in big tech and they're like, yeah, it's not really about demonstrating super high quality. It's about solving the problem. So I like, I allowed myself to lower my standards the next time to just be like, okay, I got to just like, I got to solve the thing and then I can iterate and make it better if I have time left in the interview. But really I got to optimize for finishing the thing. Stripe is, they have several headquarters. They've got their mainly San Francisco and actually Ireland. They got a big Seattle office and several others. But I joined in 2020. They had actually just established a remote hub. So they had made, they'd made like remote a part of their, like official kind of like you could be hired into the remote hub and you could stay remote. So I made it to Stripe and I actually had a choice. When I was joining Stripe, they. They were like, hey, we're spinning up a brand new JS infra team. When a language gets a certain level of usage at the company, they typically form a team to support that language and kind of all the tooling and stuff around it. And they asked me, are you interested in being the first hire onto the team? And I was actually planning on joining the team that my friends at the company were on. They had an opening on their team and so I kind of had to make the decision, like, do I want to take the riskier, like more difficult route of like trying to help spin up a brand new team or do I kind of want to go the safer route and just be on it? And I took the riskier route. Cause I was like, what the heck? Why not? Let's Try it. And so, yeah, I joined the JS Infra team and it was. The first year was pretty difficult, actually. I was. I had a hard time with the team, like, getting our feet underneath us and like, almost saying the words is difficult for me, but I'll say it anyway. Demonstrating business value, the phrase was difficult.
