Senior Software Engineer (Ebury Web Platform)

About this role

<div class="content-intro"><p>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.</p> <p>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.</p></div><p><strong>Senior Software Engineer - Founding Team (Ebury Web Platform)</strong></p> <p><strong>Valencia Office - Hybrid: 4 days in the office, 1 day working from home</strong></p> <h2>Build the banking experience the world's businesses deserve</h2> <p>Ebury is a <strong>global fintech, headquartered in London.</strong> We help businesses move money across borders — FX, payments, and lending — in <strong>140+ currencies</strong>, sending payments to <strong>160+ countries</strong> across <strong>30+ regulated markets</strong>, delivered by <strong>2,000+ experts</strong> in <strong>40+ offices worldwide</strong> and backed by the stability of majority-owner <strong>Santander</strong>. That's a bank's reach and reliability with the pace of a product team. And we've set ourselves a deliberately hard bar: <strong>beat the best digital-first experience in our market, not merely match the incumbents.</strong> </p> <p>That bar is an engineering problem. It's <em>your</em> engineering problem — and you'll be solving it <strong>directly on the platforms our clients touch every day</strong>: the web portal, the mobile apps, the APIs. This isn't back-office plumbing. Every role in this hub builds <strong>client-facing products</strong>, and the mission is unambiguous: <strong>build the best banking-and-payments experience in the market.</strong></p> <p>We also expect you to be <strong>AI-native.</strong> 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 <em>into the product</em> — so clients get answers and outcomes instead of forms and waiting.</p> <p>We're opening a <strong>new engineering hub in Valencia </strong>, and you'd be one of its <strong>founding product engineers</strong> — not employee #400, but one of the first setting how this team builds, what "good" means here, and which product bets are worth making.</p> <h2>Why this role is different</h2> <p><strong>You'll own outcomes, not tickets.</strong> 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 <em>what</em> 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.</p> <p><strong>You'll build platforms, not one-offs.</strong> Our third principle is blunt: <em>never build for one client, region, or deal — generalise before committing, or decline.</em> New currencies and payment rails are onboarded as configuration and adapters, not bespoke branches. And <strong>finish-and-tidy is part of the work</strong> — cutover, decommission, delete the dead code. We reward the engineer who retires a flag, not just the one who ships the feature.</p> <p><strong>You'll work on the real thing.</strong> 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.</p> <p><strong>You'll ship fast, and you'll ship AI-native.</strong> Deploy continuously, CI/CD with policy-as-code gates, observability as a definition-of-done. AI is woven into both sides of the work: <strong>how we build</strong> (coding assistants as a real force multiplier, with prompts and guardrails treated as first-class, versioned artefacts) and <strong>what we build</strong> (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.</p> <p><strong>Your work will be measured by client outcomes.</strong> Self-service completion, time-to-answer, the reliability and latency of core journeys as the <em>client</em> experiences them — these are first-class engineering metrics here, not an afterthought.</p> <h2>What you'll do in your first year</h2> <ul> <li><strong>Days 1–30:</strong> 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.</li> <li><strong>By 90 days:</strong> own a defined product area, lead a project with a short design doc, join the on-call rotation for what…