SAP BTP Integration Developer (m/f/d)

Innovation isn't just a value we list somewhere — it's the whole reason SAP Fioneer exists. When we spun out of SAP, the bet was simple: move faster, build better, stay close to the customer. Agility and delivery aren't buzzwords here, they're basically the job description for the whole company.
We've got deep technical roots from our SAP heritage, plus a real understanding of what banks, insurers, and their customers actually need right now. Strip away the mission-statement language and it comes down to this: we build software that helps financial services companies move faster and spend less, using cloud tech and end-to-end solutions across banking and insurance. We're growing fast, we're global, and we've stayed deliberately lean — which honestly makes for a pretty interesting place to work if you like having real impact instead of getting lost in a big org chart.
The role
B2B embedded finance is one of those areas that's quietly becoming a huge deal in financial services, and that's exactly where this role sits. As an SAP BTP Integration Developer, you'll be building cloud-based integrations that actually run real banking processes — not pilot projects that die in a backlog somewhere. If you've got solid SAP chops and you'd rather be building things than sitting in committee meetings about building things, this is probably a good fit.
You'll work closely with customers, product owners, and technical teams to design and deliver integration features on SAP BTP, making sure what you ship is secure, scales properly, and doesn't fall over six months later.
What the job actually involves
You'll work directly with customers and product/solution owners, turning user stories and Jira tickets into real, shipped features. That means owning things end to end — writing the code, testing it, fixing the bugs that inevitably show up, and documenting it well enough that someone else can pick it up later. You'll also help out on the sales side now and then, giving honest effort estimates for new opportunities, and you'll keep people in the loop with regular updates on where things stand — progress, workload, risks, anything that's blocking you. There's also a piece of the role working with the CTO office on BTP and S/4HANA infrastructure, making sure things line up with internal standards rather than becoming a one-off exception.
What we're hoping you bring

5+ years in development, at least 3 of those specifically with SAP
A degree in IT, Computer Science, Physics, Maths, Engineering, or something close enough
Solid, real-world knowledge of SAP BTP architecture and solution design — and the instinct to know how to fix things when they break, not just when they work
Hands-on experience with SAP ERP integration — ALE, IDocs, RFC, Web Services, REST, OData, Process Integration/Orchestration, SAP Integration Suite
Bonus points if you've built new APIs in SAP Integration Suite
Comfortable in SAP UI5, Fiori, Business Application Studio, and the Cloud Application Programming Model
Used to working in Agile setups with Confluence, Jira, and GitHub
Good written and spoken English

Why people stick around
You'd be working with some genuinely sharp people on something that's actually reshaping how financial services work — not a buzzword project, a real one. We've tried to keep the energy of a startup (quick decisions, room to push back on the obvious answer, low tolerance for red tape) while still having the backing of an established company with real customers and a real market presence behind it.
There's space here to think differently and bring ideas that don't necessarily look like what's already on the table. It's a genuinely international team, still growing, and career progression is based on what you actually do rather than how long you've been around.
On the practical side: occupational pension contributions, health and wellbeing support, mobility perks like bike leasing and transport allowances, plus things like celebration bonuses, work-anniversary recognition, and help with relocation if the role requires a move.