Latest / The Career Change Podcast with Fexingo: Switching Fields, Bootcamps, and Reskilling / How Bootcamp Grads Can Break Into Fintech Payments
Transcript
- Lucas: So Luna, I was digging into job postings for fintech payments roles the other day, and one thing jumped out. Almost every posting for a junior engineer or solutions engineer at a payments company mentions 'knowledge of payment flows' as a plus. But they rarely tell you what that actually means. Luna: Right, it's this black box. You see 'payments experience preferred' and if you're a bootcamp grad, you're thinking, well, I've never worked at Visa. Lucas: Exactly. And that's the gap I want to close today. Because the reality is, you don't need years at a bank to break in. You need a specific set of technical skills plus a working understanding of how money moves. And I've got a real example to anchor this. A friend of a friend — let's call him Marcus — he was a barista for six years, did a full-stack bootcamp in 2024, and this year he landed a job as a integration engineer at a payments startup. Luna: Oh nice, that's a great story. What did he build in his portfolio that got him noticed? Lucas: That's the thing. He didn't build another to-do app or a weather dashboard. He built a mock merchant integration tool. He simulated a small e-commerce storefront that could accept payments through a test gateway — think Stripe's test mode. He documented how he handled webhooks, idempotency keys, and refunds. And he put that on GitHub with a thorough README. Luna: Idempotency keys — that's a fancy term. For someone listening who hasn't heard it, can you break that down? Lucas: Yeah, so idempotency means that if you send the same request twice, the system only processes it once. In payments, that's critical. Imagine a customer clicks 'pay' and the network times out, so they click again. Without idempotency, you might charge them twice. Marcus built his tool to handle that with a unique key for each payment attempt. Luna: That's such a concrete skill. And it shows he understands the real-world messiness of payments, not just the happy path. Lucas: Exactly. And that's what hiring managers in payments care about. They don't expect a bootcamp grad to know every nuance of settlement cycles, but they do expect you to show curiosity about them. Marcus taught himself how card settlement works — you know, that when you swipe a card, the money doesn't hit the merchant's account instantly. It goes through an authorization, then a capture, then a settlement process that can take a couple of days. Luna: So how did he actually learn that? Did he just read blog posts? Lucas: Mix of things. He read the docs from Stripe and Adyen — those are public and really detailed. He also listened to a few podcasts on payments — actually, I think he mentioned this one, but whatever. And he built a simple simulation. He had a mock bank account balance in his app that only updated after his simulated settlement delay. That kind of hands-on tinkering is gold. Luna: That's a smart way to internalize it. So beyond the technical skills, what about the domain knowledge? Like PCI compliance — how much does a bootcamp grad need to know? Lucas: You don't need to be an expert, but you need to know what pci dss is — that's the Payment Card Industry Data Security Standard. And you should understand why it matters. In an interview, if you can mention that you'd never store raw card numbers on your server, and that you'd use a tokenization service instead, that instantly sets you apart. Luna: That's such a good point. I've seen job descriptions that mention 3-D Secure too. That's the extra authentication step, right? Lucas: Yeah, the 'verified by Visa' thing. It's actually a protocol for authenticating card not present transactions. Knowing the basics — that it reduces fraud and shifts liability — shows you're not just a coder, you're someone who thinks about the business context. Luna: So if someone's listening and they're a bootcamp grad, what's the one project they should build to mimic Marcus's success? Lucas: I'd say build a simple checkout flow with a test payment gateway. Focus on these three things. One, handle webhooks correctly — that's how the payment processor tells your server about events like a successful charge or a dispute. Two, implement idempotency. And three, simulate a refund flow, including partial refunds. Document every decision in your README. Luna: And what about the interview itself? How did Marcus talk about his project without sounding like a hobbyist? Lucas: He framed it in business terms. He didn't just say 'I built a checkout page.' He said, 'I built a system that helps merchants accept payments reliably, with automatic retries and a clear way to handle failures.' He talked about the user experience — how a failed payment feels to a customer — and what that means for the merchant's revenue. Luna: That's a great shift in perspective. It's not just about code, it's about the impact. Lucas: Exactly. And that's what I want listeners to take away. If you can combine solid coding fundamentals with a genuine interest in how payments work, you don't need to have fintech on your resume already. You just need to demonstrate that you've done your homework and built something real. Luna: So for someone who's just starting out, what's a good first step today? Should they just read Stripe's docs? Lucas: Yeah, that's a great starting point. Stripe's docs are incredibly well-written, and they have a 'getting started' guide that walks you through a basic integration. But I'd also recommend watching a few talks from conferences like the ones from the professional developer community. Just to hear how people talk about payments in production. Luna: And if they want to go deeper, are there any books or courses you'd point them to? Lucas: There's a great free ebook called 'The Payments Primer' that a few companies have put out. It's not too long, covers the basics of card networks, bank transfers, and alternative methods. Also, the developer blog at Adyen has some good posts on the psychology of checkout. But I'd say the most important thing is to actually build something. Luna: Yeah, building is the best teacher. And Marcus's story is proof. He went from pulling espresso shots to writing integration code in under two years. Lucas: And he told me the job search wasn't easy. He applied to maybe forty roles, got four interviews, and two offers. But what got him through was that he had a specific story to tell. He wasn't just another bootcamp grad with a generic portfolio. He had a niche. Luna: That's a powerful reminder. It's not about applying to everything; it's about finding that angle that makes you memorable. Lucas: Right. And I think payments is a fantastic angle for bootcamp grads right now, because the industry is growing, and there's a real shortage of people who understand both code and the payment flow. Plus, it's a domain where you can learn the business side quickly. Luna: I'm curious — what about the salary range? I don't want to get too into the weeds, but is it competitive? Lucas: It's competitive, definitely. Entry-level integration engineers at payments companies are typically seeing salaries in the low six figures in major tech hubs. That's on par with general software engineering roles, sometimes a bit higher because of the specialized knowledge. Luna: That's encouraging. And it's not just the money, it's the career trajectory. Payments is a skill that's transferable across so many industries. Lucas: Absolutely. Whether you're at a startup, a bank, or a giant tech company, understanding how money moves is a superpower. And it's one that bootcamp grads can definitely acquire. Luna: Before we wrap up, I want to echo something you said earlier. If this episode gave you a concrete idea for your next project, or even just a new way to think about your job search, that's exactly what we're aiming for. Lucas: And if that's the case, the way we keep delivering this without ads is through listener support. So if you found this useful, you can buy me a coffee dot com slash fexingo. It's a small gesture, but it truly keeps us going. Luna: Yeah, every little bit helps us keep the lights on. And it means we can keep bringing you episodes like this one. Lucas: So, to bring it back to Marcus. He's been in the role for about six months now, and he says the learning curve is steep but exciting. He's now comfortable with API design, he's diving into fraud detection, and he's even mentoring new hires. It's a reminder that the first step is often the hardest, but it's worth it. Luna: That's a great note to end on. If you're a bootcamp grad on the fence about fintech, I hope this episode gives you the push to go for it. Lucas: Thanks for listening, and we'll catch you next time.