Platform Engineer
Posted 8 Jul 2026
Advertised as “Senior Platform Engineer (Money Movement Systems)”
BranchFactor Summary
The original posting with the fluff stripped out
- Management level
- Individual contributor
- Employment
- On-Site
- Contract
- Full-time
No salary listed for this role.
TL;DR
The next wave of stablecoin adoption is payments. We're building a stablecoin clearinghouse to make stablecoins move like money, not a trading asset. Payments don't run on trading, but stablecoins currently do, this is unacceptable for traditional payments companies. We're looking for a Senior Platform Engineer who obsesses over correctness/efficiency and likes to get involved across backend/distributed systems. Help us build the systems that help us build faster with confidence by owning and building internal tools, dev infrastructure, and automation.
About Us
We believe stablecoins are better money and will be the backbone of better payments. We see key structural problems hindering stablecoin adoption, and we're going to fix them – starting with building a clearinghouse. We're a small, scrappy team (~10 people) based in NYC, we've raised $10M from a16z crypto and other excellent partners, and we're going to bring better money to the world.
What You'll Own
-
Correctness of money movement. The invariants, tests, and failure-mode coverage for our ledger, netting, routing, and payment ordering. This includes a reliability layer for the banks, custodians, exchanges, and issuers we depend on: shared clients, rate-limit budgets, retries that respect idempotency, and failure tests for each provider.
-
The trust layer for AI-assisted development. We work with coding agents every day, with automated review and automated incident analysis in place. You will extend it: verification of agent-written changes, guardrails on credentials and sandboxes, cost and quality telemetry, and evals that show whether the agents are improving. You will also keep a fast-growing codebase easy to read and trust.
-
Observability that catches problems first. Alerts the team trusts, service-level targets on the flow of funds, and telemetry around the integration edges we do not control. Our monitors live in the repo as code, and we want more of that thinking.
-
Load and performance. The load tests, the cadence for running them, and a capacity model we believe. This area is open for you to own outright.
-
Internal tools. The admin surfaces and automation that make a small team feel much larger. You will have strong opinions here. Bring them.
-
The path to production. CI/CD, environments, deploys, and rollback, built to be fast, safe, and repeatable.