In short
Founding engineer (second hire) at an early-stage startup building lending infrastructure that lets payment providers run underwriting, offers, payouts and repayments themselves. You'll build the lending engine in Java on GCP with Docker and Postgres, hybrid in London (3 days onsite, 2 from home), with equity.
About the role
Founding engineer. London. One of the first.
Bit of a novel, this one. Please read it, though.
You know that point in a job where you’re the one people come to, quietly running a chunk of the system, but the big decisions still get made three meetings above you?
This gets you out of that.
I’m working with a small team building lending infrastructure for payment providers. Both founders came out of Adyen’s lending team. The technical co-founder built Adyen’s capital product from day zero, watched it grow into a core part of the business, and then left to do it again with his own company.
Here’s the problem they’re solving. Pretty much every payment provider in Europe now wants to offer financing to the merchants it already serves.
Most of them do it through a partner lender.
The lender controls the underwriting, the PSP keeps a small slice, and the merchant often ends up qualifying for less and paying more.
This team gives PSPs the tech to run lending themselves: underwriting rules, offers, payouts, repayments, the lot. No 12-month build, and they don’t have to become a lender.
The money comes from banks and funding partners. This lot build the engine.
So it’s not a bank. It’s a proper engineering problem with real merchants on the other end.
Funding in, and a good old runway.
They’re hiring their second engineer in London. You’d work alongside one of the best; he's very, very good, and you’d take on more of the product and architecture as you go.
I’m honestly less bothered about years of experience on this one. If I’m honest, I get the feeling it would suit someone in their second engineering job, who’s got a bit to prove and an entrepreneurial streak.
Maybe you’re building something on the side, running a small business, or doing something completely unrelated to engineering that you care about. That said, I’ve met engineers 15 years in with exactly the same hunger. It just shows up differently.
So what I’m really looking for is a bit of evidence. Have you pushed back on a technical decision, and can you tell me how it played out? Have you built something from nothing, or picked up a problem nobody asked you to? Do you have opinions about the stuff you’ve worked on?
The stack is Java on GCP, with Docker and Postgres. That’s it. Boring on purpose. Anything new gets added when a real problem needs it, and you’d be part of deciding that.
They take AI seriously too. Write a proper spec, use the tools, check what comes out and stay responsible for it.
I'm not saying you have to be the loudest person in the room either. Some of the people with the most conviction are the quiet ones.
Probably not for you if you want a big team and a big roadmap to settle into, or if you need the brief fully written before you start.
£75–85k plus equity. Three days a week in London, two at home. It’s early stage, so expect early-stage energy and early-stage upside.
If this feels like the move, get in touch.