Staff Software Engineer, Payments Orchestration: Customer, Merchant & Configuration Data

Trustly•San Francisco, CA

10d•Hybrid

About The Position

Trustly moves money between consumers, merchants and banks across the US. We are building our US engineering hubs in San Francisco and New York, starting with a small group of staff engineers who will take technical ownership of our most critical systems. You will own Payments Orchestration: Customer, Merchant and Configuration Data end to end: its architecture, its reliability, its operation in production, and where it goes next. You'll own the records and configuration every payment depends on: customer records and their uniqueness guarantees, merchant records and settings, the rules configuration for our gaming and enterprise verticals, and the shared configuration and merchant notification services. You'll start by learning a mature, business-critical codebase fast, using AI tools to map it and writing the documentation others will build from. Within your first year, you'll help hire and lead the team that owns it with you.

Requirements

Typically 10+ years building and operating production software systems, including several years owning systems at staff level or equivalent.
Hands-on experience with payments, banking or other financial systems where correctness, auditability and uptime matter most.
You have carried the pager for systems you built, and improved them because of it.
A track record of taking over an unfamiliar, business-critical codebase and becoming its owner.
Daily use of AI coding tools (such as Claude Code, Cursor or Copilot), with clear views on where they help and where human review has to hold.
Strong distributed systems design: data consistency, idempotency, concurrency.
Clear writing. Your design docs and incident write-ups are the ones other people reuse.
Production experience with Java or a comparable backend language.
Experience owning core entity data and configuration services where duplicate or inconsistent records have direct financial impact.

Nice To Haves

Experience with ACH, RTP, FedNow or open banking.
Experience helping build a new engineering hub or leading a major platform transition.

Responsibilities

Own the architecture, service contracts and production health of Payments Orchestration: Customer, Merchant and Configuration Data.
Own the operation of your services: on-call, SLAs, incident response and root-cause fixes. There is no separate operations team; the team that builds the service runs it.
Meet the observability standards set for every service, and make the service measurably better each quarter.
Use AI tools to understand existing code quickly, then turn what you learn into design docs, interface definitions and runbooks that engineers and AI agents can work from.
Partner with the engineers who run these systems today, across the Americas and Europe, to transfer knowledge.
Direct AI-assisted implementation: write and close implementation plans, review output against requirements, and own integration testing.
Help hire and shape the team that will own this domain.