Startups

Principal Software Engineer, AMER Payments

Trustly · San Francisco · Remote

← All jobs
About Trustly

Explore Trustly’s Investor Relations hub: financial reports, governance documents, Board & Management details, and regulatory press releases.

About the role

Trustly moves money between consumers, merchants and banks across the US. This is a hands-on engineering role. You'll own, in code, the contracts between our payments systems, bank connectivity and risk decisioning, and you'll build the hardest cross-system changes yourself. Expect to spend about two-thirds of your time building. Write and merge code on the critical path every week: reference implementations, contract tests and the hardest fixes. Found on 1752vc Careers, the job board for startup and VC roles.

What they're looking for

  • Typically 15+ years in software engineering, with principal-level scope across multiple teams, and still writing production code
  • Designed, built and operated payment, banking or ledger systems at scale
  • A record of setting technical direction through code and clear writing, not slides
  • Product judgment: you can make platform trade-offs with business and product leaders, not only engineers
  • Deep distributed systems expertise: consistency, idempotency, concurrency, failure handling
  • Practical, current use of AI in engineering, with clear judgment on its limits in regulated systems
More about this role

Our ambition is to make open banking real for everyone. We're building the network that lets people pay and get paid straight from their bank account, instantly and securely, so more of every payment reaches the people it's meant for. We're a global leader in open banking payments: since 2008 we've connected more than 12,000 banks, and today we process more than $100 billion in payments a year.

Trustly moves money between consumers, merchants and banks across the US. This is a hands-on engineering role. You'll own, in code, the contracts between our payments systems, bank connectivity and risk decisioning, and you'll build the hardest cross-system changes yourself. Expect to spend about two-thirds of your time building.

Write and merge code on the critical path every week: reference implementations, contract tests and the hardest fixes.

Own the contracts between payments, bank connectivity and risk as versioned specs in the repo, with contract tests in CI that fail the build when a contract breaks.

Build the first version of hard cross-domain changes, then hand them to the owning team.

Own our global API specification, with the engineers who own our merchant-facing APIs.

Lead the...

Read the full posting on Trustly's site ↗

Tech

Build your edge while you search

Free tools for founders and investors, plus VC Unfiltered, our take on startups, venture and the people who build them.