Ship to real devices
Your work reaches phones in real hands within weeks. No mockup phase, no indefinite backlog of “enterprise-ready” work that never ships.
Company
Careers
A wallet is infrastructure people rely on with money they cannot replace if it goes wrong. That shapes how we work, and it shapes who we hire.
Why this work is worth doing
Self-custody puts a real responsibility on the software. There is no support team to reverse a mistake, no account to reset and no customer service line to reach. The only defence a user has is the quality of what we shipped — which makes engineering judgement here unusually visible, and unusually important.
It is also a rare combination: a codebase used by millions, a security model you can reason about end to end, and a product where clarity is a feature rather than polish.
Security is a feature
Threat modelling is part of design review, not a gate at the end. Secure defaults are decided early, when they are cheap.
Small, senior teams
Own a problem end to end. The person who designs the flow writes the copy and answers the support tickets it generates.
Open roles
Everything below is remote-friendly, with generous time off and a hardware budget for the device you test on. If a role is not a fit but the problem interests you, an application that says so is still worth reading.
- Senior Mobile Engineer, iOS
- Own the wallet and staking surfaces on iOS. You will work in Swift against real hardware, with a strong preference for a small codebase and explicit types. Ask about this role
- Senior Mobile Engineer, Android
- Own the Android wallet experience, including background reliability and the transaction signing path. Kotlin, deep familiarity with Android lifecycle behaviour, and an instinct for what users will get wrong.
- Blockchain / Smart Contract Engineer
- Design and audit the staking contracts and the transaction construction clients rely on. You will be comfortable writing tests that try to break your own code before someone else does.
- Security Engineer
- Threat modelling, dependency review, signing-path auditing and incident response. You will disagree with product on features you believe are unsafe, in writing, with reasons.
- Product Designer
- Own staking flows end to end — from the growth curve to the early-exit warning. Portfolio matters more than years of experience; we want to see decisions, not just screens.
- Support Specialist
- Help users who may have just lost access to funds. The job is calm, precise and genuinely difficult. You will never be asked to request anyone’s recovery phrase.
How we work
- Written first. Design documents and decision records before implementation. Most arguments are won in a paragraph, cheaply.
- Small diffs, fast review. Review within a working day, because a blocked diff is a stopped company.
- Say no out loud. Disagreeing with a decision is expected; hiding that you disagree is not.
- User funds first. Any change that affects custody, signing or transaction construction gets a second reviewer regardless of seniority.
- No dark patterns. If we would be uncomfortable explaining a screen to a user, it does not ship.
What we look for
Evidence of good judgement in past work matters far more than a list of technologies. We care about whether you can explain a trade-off you made, what you would do differently, and why the boring path was the right one.
Nothing listed that fits?
Write to us anyway. We hire for how people think more than for a specific framework, and roles here change as the team does. Use support and pick the careers option.