Careers
What the work is actually like
Building software that moves other people’s money is unusually unforgiving and unusually interesting. This page is written for someone deciding whether to apply rather than for a careers-page checklist.
What hiring looks like
Roles posted as they open, not on a schedule
A short, tagged list by function and location — nothing sits open for months waiting for a hiring plan to catch up.
Open roles
No roles published right now
There are no published openings at the moment.
Roles appear here when they open. We would rather show an empty list than leave adverts up for positions that are already filled. Speculative applications are read.
Apply speculativelyWhat it is like
Three things worth knowing before you apply
The domain is the hard part
Most of the difficulty here is not the code. It is understanding why a margin call behaves differently on a weekend, or why a rounded figure on a statement becomes a complaint. People who enjoy that do well.
You will talk to customers
Engineers join scoping calls and hear the problem directly rather than through three layers of summary. It is slower and it produces better decisions.
Being wrong is cheap, hiding it is not
Placeholder figures on this site are marked as placeholders. That habit comes from the same place as how we handle mistakes internally: state it, fix it, move on.
How we hire
Four stages, and a decision either way
Application
A short exchange about what you have built and what you want to work on. No timed puzzles.
Conversation
With someone who does the job you are applying for, about work you have actually done.
Practical
A realistic problem close to the real thing, discussed together rather than graded in silence.
Decision
A yes or a no with a reason, within a stated window. We do not leave people waiting.
FAQ
Careers: common questions
6 short answers to what teams ask before a demo.
Open roles are listed on this page when there are any. If the list above is empty, there are none published at the moment — we would rather show nothing than leave stale adverts up.
Yes. Tell us what you want to work on and what you have built. Speculative applications are read, and occasionally a role gets created around one.
Arrangements vary by function and by role, and the honest answer differs enough that it belongs in the specific job description rather than in a blanket statement here.
For some roles it helps considerably; for others it is learnable and curiosity matters more. Where it is genuinely required, the job description will say so plainly.
A problem resembling real work, worked through together. No take-home task that quietly consumes a weekend, and no whiteboard algorithm you would never write in the job.
We state a window at the start and hold to it. If a decision slips, you hear why rather than hearing nothing.
Still have a question?
A specialist will answer it directly, with your set-up in mind.
Ask a specialistTell us what you want to build
Roles occasionally get created around a good speculative application. It costs a paragraph to find out.