Careers
Small team, unusually specific problem
Private markets run on snapshots — a PDF, a data room, a mark. We are building the memory underneath: what a company reported, when, and what happened next. The work sits where accounting rules, distributed systems and a user who cannot afford to be wrong all meet.
How we work
Small teams, long attention spans, and written decisions. We would rather ship one correct thing per week than five plausible ones. Nobody here is a resource on a plan — the person who builds a surface owns it, including what it does when things go wrong.
- Written first
- Decisions get a document. Meetings resolve documents rather than replace them.
- Own the edges
- Empty, loading, error and permission states are the job, not a follow-up ticket.
- Real users early
- Everyone talks to customers — the companies that report and the lenders and investors who rely on that reporting. Nobody is insulated from them.
How to apply
Pick the role closest to your work, or write to us if none fits. Tell us which problem here you would want to own, and why.
Roles
Who we want to hear from
- Express interest
Senior product engineer
Own the reporting workflow companies use, end to end — pulling from their accounting systems, checking against the Sureshake Financial Reporting Standard, publishing. Deep TypeScript, opinions about correctness.
Engineering
- Express interest
Accounting systems engineer
Map real ledgers to the Sureshake Financial Reporting Standard. For someone who has closed books and can also write code.
Engineering
- Express interest
Design engineer
Build the interfaces finance teams, lenders and investors work in, and hold the line on the design system while doing it.
Design
- Express interest
Pilot lead
Take companies from first contact to their first published reporting period. Part sales, part implementation, all follow-through.
Go to market
Tell us what you would build.
The best applications we get are two paragraphs about the problem, not a cover letter about the company.