Careers
Small team, unusually specific problem
We are eleven people building a proof layer for private financial reporting. The work sits where accounting rules, distributed systems and a user who cannot afford to be wrong all meet — which makes it narrow, and much more interesting than it sounds.
- Team
- 11
- Growing to about 18 this year
- Where
- Cleveland + remote
- US time zones
- Pay
- Posted in range
- No negotiation games
- Process
- Three conversations
- Plus one paid work session
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 operators. Nobody is insulated from the people using this.
Hiring process
Three conversations and one paid work session, usually inside two weeks. The work session is a real problem from our backlog, scoped to about four hours, and we pay for it whether or not we make an offer. No whiteboard algorithms, no panel of nine.
What we pay
Open roles
Four roles open now
- Apply
Senior product engineer
Own the reporter workflow end to end — acquisition, schema validation, publishing. Deep TypeScript, opinions about correctness.
EngineeringCleveland or remoteFull time
- Apply
Accounting systems engineer
Map real ledgers to the reporting standard. For someone who has closed books and can also write code.
EngineeringRemote (US)Full time
- Apply
Design engineer
Build the interfaces operators live in, and hold the line on the design system while doing it.
DesignRemote (US)Full time
- Apply
Pilot lead
Take companies from first contact to a published, verified period. Part sales, part implementation, all follow-through.
Go to marketClevelandFull time
Tell us what you would build.
The best applications we get are two paragraphs about the problem, not a cover letter about the company.