Founding Platform Engineer

BOB is a free finance employee for businesses. Bob does the books, pays vendors, chases invoices, and answers any money question you throw at him.

He works through regulated financial partners, with the controls and approvals needed to move real money safely. Our whole philosophy is that Bob is real. When work comes up, we ask one question: why not just give it to Bob?

We believe AI agents are becoming economic actors. Done right, that gives every founder and business more leverage-not less control. We're building the financial infrastructure that makes that future useful, safe, and available to anyone with a business to build.

We're backed by Circle Ventures and founders of PayPal, Zynga, and Plaid-including Peter Thiel, Mark Pincus, and Zach Perret., You're an early full-stack engineer, but infrastructure is your home base. You can ship the product end to end. Your center of gravity is the machinery underneath it: money movement, provider integrations, the ledger, and the production systems that have to work when things get weird.

This is not a narrow DevOps job. You'll write product code, touch the dashboard, design APIs, debug financial workflows, and own infrastructure in the same week.

You'll own:

• Go and PostgreSQL systems that execute and track money movement.
• Payment lifecycles: approvals, idempotency, retries, webhooks, reconciliation, and durable events.
• The ledger and treasury primitives behind balances, holds, settlements, and reversals.
• Financial-provider integrations and the isolation boundary around payment execution.
• AWS infrastructure: ECS/Fargate, RDS, networking, secrets, observability, and deploys.
• Full-stack product work when the job calls for it-from the data model and API to the Next.js interface.
• The tools and runbooks that let a small team understand what happened and fix it fast.

• High agency. No layer of the stack is beneath you. You find the problem, cross the boundary, and own it through production.

You're a full-stack builder with platform instincts: pragmatic enough to ship and rigorous enough to protect the infrastructure underneath it.

You stay calm when systems fail. You can follow an ambiguous problem across the UI, API, database, provider, and AWS account without throwing it over the wall.

You're deeply fluent in Go, strong with PostgreSQL, and comfortable in React, Next.js, and TypeScript. You understand concurrency, idempotency, failure recovery, and why "probably executed" is a real state when money moves.

Payments, ledgers, financial infrastructure, or another high-trust system is a big plus. Perseverance is not optional. A lot of the important work is the last unglamorous 10%.