As a Staff Engineer in the Business Spend segment, you shape the architecture of how companies model, process, and pay for spend. You’ll own critical parts of supplier data and invoicing flows while coordinating across product, design, and compliance. You’ll drive cross-team technical decisions, raise the capability of teammates through pairing and clear documentation, and help scale a legacy-to-modern migration. This role offers visibility into customer impact and a chance to tackle hard problems in a fast-growing fintech environment.
Pay / Benefits
Your own Pleo card
Lunch provided or allowance
Comprehensive private healthcare
25 days of annual leave + holidays
Hybrid or remote options
Mental health and well-being support
Responsibilities
Own the architecture of the Business Spend domain and align multiple teams around it
Lead supplier data migration, decoupling legacy services into dedicated per-customer components with minimal downtime
Improve reliability of invoice payment flows to reduce failed payments and customer friction
Transform vendor data model to ensure consistency across cards, invoices, and accounting
Foster cross-team technical decisions via design docs, code reviews, and architecture discussions
Mentor teammates through pairing, documentation, and knowledge transfer across time zones
Work on roadmap items: supplier management extraction, ISO 20022 payment requirements, and supplier/vendor modeling across Business Spend
Collaborate with counts and compliance teams to ensure security, scalability, and governance
Key requirements
Deep backend engineering experience in a modern statically typed language (Java, Kotlin, or TypeScript) on production-scale systems
Technical lead experience for a multi-country/time-zone team
Experience migrating within legacy systems, not just target-state design
Ability to drive technical direction across teams you don’t own
Proven ability to produce actionable design documents, migration plans, and decision records
Background in payments, fintech, accounts payable, ERP, or B2B SaaS
Experience with event-driven systems and Kafka; strong observability practices
Experience architecting services across multiple domains (e.g., invoicing, subscription cards)
We use essential cookies to make this site work. With your permission we would also like to use the optional cookies below. Nothing optional is set until you choose, and you can change your mind at any time from "Cookie settings" at the bottom of every page. Cookie policy.
Essential — keep the site working and secure, and remember the choice you make here. Always on.