Company · Careers
We're hiring engineers who believe both. If a payout run that balances to the cent gives you quiet satisfaction, keep reading.
Why this problem
Most software can be approximately right. Ours can't. A payout is either settled or it isn't; a ledger balances or it doesn't. There is no "close enough" when the number is someone's payroll.
Remote-first, written-first, and honest about the parts of infrastructure work that other job pages skip.
The team is distributed across US and EU time zones. We hire for overlap, not location. Twice a year the whole company meets in person; the rest of the year we meet in documents.
Significant changes start with a design doc, not a branch. Decisions get written down with their reasoning, so the person debugging at 2am — usually future you — knows why the system works the way it does.
Engineers join a compensated on-call rotation. Real pages are rare — boring is a feature, and we invest heavily to keep it that way — but money moves 24/7 and someone has to be reachable when a rail misbehaves.
Ledger code ships with property tests, not just examples. Every cent in must equal every cent out plus fees, on every run, forever. A reconciliation break is a stop-the-line event, not a ticket.
Modest list, real items. We'd rather pay well and keep the perks page short.
We pay at the top of our band and everyone holds equity. No negotiation games — the offer is the offer.
Full coverage for you, subsidized for dependents. US plans through a national carrier; EU equivalents by country.
Plus local public holidays. Taking it is expected, not tolerated — tired people write bad ledger code.
A one-time setup budget plus an annual refresh. A good chair and a second monitor are cheaper than back pain.
Annual budget for books, courses, and conferences. Payments is a deep field; we pay for the depth.
The whole company, in person, twice a year. Travel and lodging covered. Roadmap by day, no trust falls.
Open roles
Every role touches money movement directly. Apply by email with anything you've built or written that shows how you think.
No matching role? Write anyway — careers@latchpay.xyz. We read every note, and a small team's roadmap changes fast.
Hiring process
No leetcode theater. We evaluate you on real-shaped problems, and we never ask candidates to move real money or handle production credentials — at any stage.
30 minutes with the hiring manager. What you've built, what you want to build, and whether this problem space actually interests you.
90 minutes on problems shaped like our real ones — idempotent retries, reconciliation breaks, a rail that returns funds three days late. Sandbox and whiteboard only.
Walk us through something substantial you've shipped — code, a design doc, an incident writeup. We care how you reason, not how you perform.
Meet the people you'd work with, ask them anything. If it's a fit, a written offer follows within two business days.
Questions before you apply? Contact us →
Send us anything you've built or written — we read every note.