Founding Engineer at Sava in New York, NY

Job description

Sava is a chartered trust company that builds its own software. We hold the Nevada trust charter, act as the fiduciary of record, and write every line of the system that runs it. Most of this industry rents its regulated core from someone else and inherits the limits that come with it. We're live with real clients. We've raised $10M from Gradient Ventures, Max Mullen (Instacart), SV Angel and others. Where this is going Trust administration has barely changed in decades: paper and a trust officer's inbox. We're building the version where software and AI agents do most of the fiduciary work and people stay accountable for every decision that matters. Today that means running trusts for families on a platform we wrote ourselves. The engineers who join now write the ledger and the agents that take it from there. What you'd do Own domains end to end, from schema to screen: the onboarding pipeline, custodian and bank integrations, the AI layer. Build agentic workflows that do real fiduciary work: document extraction, compliance monitoring, distribution analysis, drafting. They reach client data through authorized, audited tools, never raw SQL. Every consequential action requires human approval. None of it is a chatbot. Extend an immutable, double-entry fiduciary ledger that must be correct. Make complex legal and financial structures understandable to non-experts. Trusts are a 500-year-old interface problem. Raise the bar on all of it. The foundation is solid but it isn't finished. What you'd build on The platform that runs the trust company today is ours, and a few choices define it: Go, Postgres and sqlc backend. The schema is the source of truth, every query is SQL we wrote and CI fails if the migrations and the schema ever disagree. Types cross the wire. OpenAPI is generated from the Go handlers and TypeScript from the OpenAPI, so the Next.js frontend can't drift from the backend. There is more test code than application code. Integration tests are the default, against a real Postgres, with the race detector on. Correctness is structural, not cultural. Row-level security lives in the database, client SSNs sit under envelope encryption with one decrypt path, and the audit row is written before the decrypt. Who we're looking for You've been a founder, an early engineer, or a tech lead at a strong company, and you care about getting things right, because in this business a wrong number has real consequences. You have product and UI taste and can be trusted to make interface decisions on your own. You build with AI and have strong opinions about how; we build this way and expect you to push it further. You want to be measured by what shipped. No trust or finance background is needed. The domain is learnable; judgment isn't. The team We work in person in NYC, 5 days a week. You'd report to Dylan and work most closely with: Nimit Maru, CEO: 2x YC founder, two exits to public acquirers, most recently Fullstack Academy Rush Sadiwala, COO: serial founder, deep financial and operational background Dylan Richardson, Head of Engineering: previously WhatsApp, Meta and Google Reporting to Dylan means, in practice, that you ship to production in your first week. Code review is a conversation, and nobody waits on it. You'll talk to Nimit, clients, and the trust officers who use what you build, directly and often.