Rivet

Design, build, and maintain full-stack features and collaborate with clients to translate needs into software. | 5+ years shipping full-stack web applications with production proficiency in Go and React, comfortable with end-to-end feature ownership in a fast-paced environment. | ABOUT RIVET Rivet is an AI-native accounting firm. In less than 3 years, we've built a T500 firm in the US, combining corporate and personal income tax, sales tax, R&D credits, and bookkeeping into a single, all-inclusive experience that eliminates the worst parts of tax season for real businesses and the people who run them. Our platform is designed to feel invisible: it guides clients through their tax to-dos, automates the drudgery for preparers, and gets out of the way when it's not needed. We measure success in time saved and returns completed, not vanity usage metrics. We run Rivet (the firm) on Rivet (the platform) because owning the stack makes it possible to deeply embed AI into every step of our workflows, far more than our competition will ever be able to relying on third-party/off-the-shelf tooling. Our team of 50 supports more than 1,000 of the most innovative companies in the US — including Cursor, Cognition, and ModRetro — and their executives, investors, and employees. And while we may have just gotten started a little over two years ago, this isn't our first rodeo: * Nick Abouzeid (cofounder & CEO) comes from Ramp, where he ran three of their Growth teams from $100M → $600M in ARR * Kyle Christenson (cofounder & Head of Tax) comes from the IRS, where he spent six years as an auditor before leaving to start his own firm over a decade ago We're well-funded, growing quickly, and sustainable. We've raised over $7M to date, from investors like XYZ Ventures, Susa Ventures, Haystack Ventures, and 40+ executives from Ramp, Anduril, Physical Intelligence, & more. WHY THIS ROLE IS DIFFERENT At six engineers, features don't stop at an API boundary. The person who designs the schema is the person who ships the screen and the person who hears about it when a preparer can't find the button. * Ownership from first commit to production. Engineers design, build, ship, and maintain their work — no handoffs, no middle-management mazes. * Decisions happen at the edge. Engineers talk to clients and tax preparers directly. We optimize for speed and context, not committee consensus. * Clear is kind. We surface problems early, talk about tradeoffs openly, and don't sugarcoat. We're kind by being honest, not by being vague. * Pragmatic stacks. We pick tools that solve real problems. If it doesn't help us ship faster, safer, or better, we don't use it. * Skin in the game. We ship things we'd be proud to put our name on — and if something breaks, we own it and fix it fast. OUR STACK Six engineers today, five languages. You'd work across the first two: * Platform: Go, as a modular monolith — Connect RPC over protobuf, Go Fx for wiring, sqlc and goose against Postgres, River Pro for background jobs, Watermill for pub-sub over RabbitMQ. * Frontend: React and TanStack, deployed to Cloudflare Workers. * AI and eval: Python, in their own repos — ModelBridge (a gRPC service for AI building blocks) and TaxBench, our internal eval suite. * Legacy integration: a C# Windows agent that drives Drake, one of the tax platforms our industry never built APIs for. * Infrastructure: AWS — ECS Fargate, Amazon MQ, AMP, Loki, Tempo — provisioned by Pulumi, itself written in Go. * Around the edges: Buildkite for CI, OpenTelemetry throughout, Doppler for secrets, Linear for tracking. WHAT YOU'LL DO * Ship features end to end — Postgres schema, Go service, protobuf contract, React screen, and the alert that pages you when it breaks. * Move where the quarter needs you. Client portal in the fall, preparer workspace before January, platform work when filing season quiets down. This role is for someone who finds that energizing rather than scattered. * Take AI from prototype to product. Plenty of things demo well here. Deciding what graduates into a workflow preparers depend on, and hardening it so it can be, is the job. * Talk to preparers and clients directly, then go build the thing they actually needed. * Leave the codebase better than you found it. We have five languages and six engineers. Some of that is deliberate; some of it isn't, and we want opinions about which is which. We're fully distributed — but if you want an office, we'll help you find one through our investor network. WHAT MAKES YOU A FIT * 5+ years shipping full-stack web applications, with production experience in both Go and React * Have owned features end to end on a small team, where there was nobody to hand the other half to * Comfortable choosing where the complexity should live — in the schema, the service, or the UI — and defending the call * Know how to prototype fast and then decide, honestly, what it takes to make it real * Comfortable operating in a fast-changing, early-stage environment * Excellent verbal and written communication skills NICE TO HAVES * Were the first or second engineer on a product that made it to real users * Connect RPC, gRPC, or protobuf-first API design, and generated typed clients * TanStack in production, or edge deployment on Cloudflare Workers * Shipped LLM systems into production paths and evaluated them properly, not as prototypes * Built tax-adjacent software — fund administration, payroll, accounting platforms, filing systems * Started a company yourself, however small WHAT WE OFFER * Benefits and meaningful equity * A fully remote team, plus twice-yearly company offsites * A well-funded, fast-moving environment with minimal layers of management * A world-class client base that values your time and pays for the premium experience * The chance to build production-grade software your teammates use and love every day We encourage you to apply even if you don't meet every qualification. Strong candidates rarely check every box.

Own end-to-end development of client-facing and internal portals ensuring high performance and clarity. | 4+ years building production React web applications with backend capability and strong communication skills. | ABOUT RIVET Rivet is an AI-native accounting firm. In less than 3 years, we've built a T500 firm in the US, combining corporate and personal income tax, sales tax, R&D credits, and bookkeeping into a single, all-inclusive experience that eliminates the worst parts of tax season for real businesses and the people who run them. Our platform is designed to feel invisible: it guides clients through their tax to-dos, automates the drudgery for preparers, and gets out of the way when it's not needed. We measure success in time saved and returns completed, not vanity usage metrics. We run Rivet (the firm) on Rivet (the platform) because owning the stack makes it possible to deeply embed AI into every step of our workflows, far more than our competition will ever be able to relying on third-party/off-the-shelf tooling. Our team of 50 supports more than 1,000 of the most innovative companies in the US — including Cursor, Cognition, and ModRetro — and their executives, investors, and employees. And while we may have just gotten started a little over two years ago, this isn't our first rodeo: * Nick Abouzeid (cofounder & CEO) comes from Ramp, where he ran three of their Growth teams from $100M → $600M in ARR * Kyle Christenson (cofounder & Head of Tax) comes from the IRS, where he spent six years as an auditor before leaving to start his own firm over a decade ago We're well-funded, growing quickly, and sustainable. We've raised over $7M to date, from investors like XYZ Ventures, Susa Ventures, Haystack Ventures, and 40+ executives from Ramp, Anduril, Physical Intelligence, & more. WHY THIS ROLE IS DIFFERENT The product is the only part of tax season most of our clients ever see, and it runs through one design engineer today. Every module's back-end owner pairs with him on the UI, which makes him the shared dependency for every screen we ship. You'd be the second, and the two of you would split it. * Ownership from first commit to production. Engineers design, build, ship, and maintain their work — no handoffs, no middle-management mazes. * Decisions happen at the edge. Engineers talk to clients and tax preparers directly. We optimize for speed and context, not committee consensus. * Clear is kind. We surface problems early, talk about tradeoffs openly, and don't sugarcoat. We're kind by being honest, not by being vague. * Pragmatic stacks. We pick tools that solve real problems. If it doesn't help us ship faster, safer, or better, we don't use it. * Skin in the game. We ship things we'd be proud to put our name on — and if something breaks, we own it and fix it fast. OUR STACK Six engineers today, five languages. You'd live mostly in the first two: * Frontend: React and TanStack, deployed to Cloudflare Workers. Typed clients generated from protobuf. * Platform: Go, as a modular monolith — Connect RPC over protobuf, Go Fx for wiring, sqlc and goose against Postgres, River Pro for background jobs, Watermill for pub-sub over RabbitMQ. * AI and eval: Python, in their own repos — ModelBridge (a gRPC service for AI building blocks) and TaxBench, our internal eval suite. * Legacy integration: a C# Windows agent that drives Drake, one of the tax platforms our industry never built APIs for. * Infrastructure: AWS — ECS Fargate, Amazon MQ, AMP, Loki, Tempo — provisioned by Pulumi, itself written in Go. * Around the edges: Buildkite for CI, OpenTelemetry throughout, Doppler for secrets, Linear for tracking. WHAT YOU'LL DO * Own client-facing surface area end to end — the portal where clients hand over documents, answer questions, and watch a return move toward filed. Design, build, ship, and keep it working. * Build the workspace our preparers live in all day. Roughly 40 people use our internal tooling for eight hours a day, four months a year. Speed and clarity are the whole product for them. * Pair with Anton, our design engineer. You two split the surface and set the standards — component patterns, testing, performance budgets, accessibility — because nobody has written them yet. * Ship AI into the interface, not around it. Extraction, review, and suggestion flows only work if the UI makes it obvious what the model did and where a human needs to look. * Talk to the people using it. Preparers are on Slack; clients are one call away. Watch someone use what you built before you decide it's done. We're fully distributed — but if you want an office, we'll help you find one through our investor network. WHAT MAKES YOU A FIT * 4+ years building production web applications, primarily in React * Have owned a product surface end to end, including the parts after launch * Can read and write enough backend code to unblock yourself rather than filing a ticket and waiting * Care about the unglamorous parts — loading states, error handling, what happens on a bad connection with a 40MB PDF * Comfortable operating in a fast-changing, early-stage environment * Excellent verbal and written communication skills NICE TO HAVES * Production experience with TanStack (Query, Router, Table) * Deployed to the edge — Cloudflare Workers or similar * Worked with generated clients from protobuf, gRPC, or Connect RPC * Built document-heavy or upload-heavy interfaces, where files are large, messy, and occasionally encrypted * Strong design sense, especially if you've shipped without a dedicated designer * Built internal tools for operators who sit close enough to tell you what's broken * Built tax-adjacent software — fund administration, payroll, accounting platforms, filing systems, anywhere a wrong number has consequences WHAT WE OFFER * Benefits and meaningful equity * A fully remote team, plus twice-yearly company offsites * A well-funded, fast-moving environment with minimal layers of management * A world-class client base that values your time and pays for the premium experience * The chance to build production-grade software your teammates use and love every day We encourage you to apply even if you don't meet every qualification. Strong candidates rarely check every box.

Develop and maintain backend infrastructure and systems using Rust and TypeScript in a distributed environment. | Requires 5+ years backend or infrastructure experience, distributed systems knowledge, Rust or similar systems language proficiency, and TypeScript familiarity. | Senior Software Engineer About Rivet Rivet is infrastructure for AI agents. The primitive is the actor: a durable, stateful process for every agent, session, and user, living in a standard Node.js or Bun backend. Everything else builds on it: agentOS (a computer for every agent, with filesystem, networking, bash, Python, and Node), Workflows (durable automation that sleeps, retries, and survives restarts), and Dynamic Apps (deploy the backends agents generate, 22 MB per app, scaling to zero and to millions). A library in development, a platform in production: Rivet Cloud, self-hosted (Apache 2.0), or fully air-gapped in your VPC. Code at github.com/rivet-dev/rivet. The work The Rust engine: actor orchestration (Pegboard) durable execution (Gasoline) traffic routing (Guard) multi-region KV on EPaxos (Epoxy) SQLite engine The TypeScript SDK (RivetKit) and its bindings into the Rust core agentOS, the computer agents run on inside an actor Rivet Cloud: multi-tenancy, edge routing, autoscaling, observability Almost everything you write will be public. Stack: Rust, TypeScript, FoundationDB, Postgres, ClickHouse, NATS, SQLite. Our AI Policy we break down our codebase in rivet in to: core engine: no/limited ai for mission critical + “off rails” code sdks + frontend: reviewed ai for routine + “on rails” code website: just test the output Requirements 5+ years on backend or infrastructure systems Distributed systems experience in production Rust, or a strong systems background in another language like C++ or Go Working knowledge of TypeScript Stack: Rust, TypeScript, FoundationDB, Postgres, ClickHouse, NATS, SQLite. Benefits - Health, dental, and vision insurance - 401(k) - Unlimited PTO