TL;DR

The next wave of stablecoin adoption is payments. We are building a stablecoin clearinghouse to make stablecoins move like money, not a trading asset. We need a backend engineer who can own the systems that move real value: mint and burn flows, reserve accounting, reconciliation, settlement, integrations, and the APIs built on top of all of it.

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 Do

• Design, build, and operate core backend services behind mint/burn flows, reserve accounting, reconciliation, and settlement pipelines.
• Integrate with banks, custody providers, stablecoin issuers, blockchains, and partner APIs, and make those dependencies safe enough for money movement.
• Build durable reconciliation and audit trails so the team always knows where money is, what happened, and whether state matches reality.
• Design secure API surfaces and own monitoring, alerting, runbooks, and incident response for services that move real value.
• Contribute to the payments API and internal/admin surfaces where backend ownership meets customer or operations workflows.
• Identify and pursue improvements that make the core product more robust, without waiting for a fully specified ticket.

What We’re Looking For

• 5-12 years of production backend engineering experience, with services you have designed, shipped, and operated in production. Our stack is TypeScript on Node.js, PostgreSQL, and GCP.
• Experience with high-value transactional systems: payments, banking integrations, fintech infrastructure, trading or exchange infrastructure, ledgering, or stablecoin/crypto infrastructure.
• A working command of distributed systems fundamentals: consistency, eventing, idempotency, retries, durable reconciliation, ordering, partial failure, and observability.
• Judgment for integrating with unreliable external systems: banks, payment rails, custody providers, issuers, or similar partner APIs.
• Experience designing secure APIs, handling secrets and access control, instrumenting services, and writing runbooks for infrastructure that moves real value.