Founding Engineering Manager (Ebury Web Platform)

Ebury helps ambitious businesses unlock global growth, and we take the same approach with our people. We encourage innovation and movement, collaboration and problem-solving, and foster an environment where everyone can feel they belong, are valued, supported and empowered to succeed. If you’re a collaborator who wants to help transform how businesses operate globally, get in touch - we’d love to discuss how Ebury can accelerate your career so you can shape the future.

Engineering Manager - Founding Team (Ebury Web Platform) Valencia Office - Hybrid: 4 days in the office, 1 day working from home Build the banking experience the world's businesses deserve Ebury is a global fintech, headquartered in London. We help businesses move money across borders — FX, payments, and lending — in 140+ currencies, sending payments to 160+ countries across 30+ regulated markets, delivered by 2,000+ experts in 40+ offices worldwide and backed by the stability of majority-owner Santander. That's a bank's reach and reliability with the pace of a product team.

And we've set ourselves a deliberately hard bar: beat the best digital-first experience in our market, not merely match the incumbents. That bar is an engineering problem — and increasingly, a leadership problem. Great systems don't ship themselves; teams ship them.

As a founding Engineering Manager in our new Valencia hub, your job is to build and lead the team that solves it, directly on the platforms our clients touch every day: the web portal, the mobile apps, the APIs. This isn't back-office plumbing, and it isn't a coordinator role. Every team in this hub builds client-facing products, and your mission is unambiguous: build a team that builds the best banking-and-payments experience in the market.

We also expect you to be AI-native. Not "curious about AI" — fluent. You use AI coding tools as a genuine force multiplier in your own work, you know how to help a team adopt them well, and you know how to design AI into the product so clients get answers and outcomes instead of forms and waiting.

We're opening a new engineering hub in Valencia, and you'd be one of its founding Engineering Managers — not the manager of team #40, but one of the first people setting how this hub hires, how it builds, what "good" means here, and which product bets are worth making. Why this role is different You'll build the team, not inherit it. As a founding EM you'll hire your first engineers, set the interview bar, and shape the culture from an empty room.

The people you bring in and the standards you set in the first six months will echo for years. If you want to walk into a fully-formed team and keep it running, this isn't your role. If you want to decide what this team is , read on.

You'll own outcomes through your team, not tickets. Your team takes a real client problem — "businesses can't see why a payment is held" — and owns it end to end: the experience, the services and APIs behind it, the data, the measurement, and the iteration after launch. Your job is to make that ownership real: give the team the context, the trust, and the room to make product calls, then hold the bar on quality and delivery.

You'll have opinions about what to build and the standing to act on them. You'll be a player-coach early, a leader always. At founding stage the team is small and you'll stay close to the code — pairing, reviewing, unblocking, and shipping the occasional change yourself to keep your judgement sharp and your credibility earned.

As the team grows, your leverage shifts from your own commits to the people and systems you've built. You're comfortable with both modes and know which one the moment calls for. You'll build platforms, not one-offs.

Our third principle is blunt: never build for one client, region, or deal — generalise before committing, or decline. New currencies and payment rails are onboarded as configuration and adapters, not bespoke branches.