Senior Software Engineer (Ebury Web Platform)

Senior Software Engineer - Founding Team (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.

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. It's your engineering problem - and you'll be solving it directly on the platforms our clients touch every day : the web portal, the mobile apps, the APIs. This isn't back-office plumbing. Every role in this hub builds client-facing products , and the mission is unambiguous: build 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 how you build, 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 product engineers - not employee #400, but one of the first setting how this team builds, what "good" means here, and which product bets are worth making.

Why this role is different

You'll own outcomes, not tickets. A product engineer at Ebury 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. You'll have opinions about what to build and the standing to act on them. If you like being handed a fully-specced ticket and nothing else, this isn't your role. If you want a slice of a product and the trust to make it genuinely good, read on.

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. And finish-and-tidy is part of the work - cutover, decommission, delete the dead code. We reward the engineer who retires a flag, not just the one who ships the feature.

You'll work on the real thing. Client-facing web and mobile channels evolving in parallel; an event-driven, API-first transactional platform on AWS where services own their data and talk only through known contracts; a governed GCP/BigQuery data world. Money-movement discipline - idempotency, deterministic retries, reconciliation - is table stakes, because we're handling businesses' actual cash.

You'll ship fast, and you'll ship AI-native. Deploy continuously, CI/CD with policy-as-code gates, observability as a definition-of-done. AI is woven into both sides of the work: how we build (coding assistants as a real force multiplier, with prompts and guardrails treated as first-class, versioned artefacts) and what we build (client-facing, permission-aware knowledge and summarisation, smart defaults that pre-empt the client's next question). You'll be expected to reach for AI by default, judge where it genuinely improves the client experience, and know where the human-in-the-loop line sits on regulated decisions.

Your work will be measured by client outcomes. Self-service completion, time-to-answer, the reliability and latency of core journeys as the client experiences them - these are first-class engineering metrics here, not an afterthought.

What you'll do in your first year

Days 1-30: ship your first change to production in the first few days (we pre-scope it and pair you with a buddy), learn the domain, own a small feature end to end.

By 90 days: own a defined product area, lead a project with a short design doc, join the on-call rotation for what you build, and start mentoring the next hire.

Across the year: take client problems from ambiguous idea to shipped, measured, iterated product; help set the standards, interview bar, and culture for a hub that's growing around you.

What your responsible for

Provide technical leadership across one or more critical domains, owning the design and evolution of large-scale