Problems with consequences
Payments, settlement and platform work where the result is measurable and the user is not forgiving. It is harder, and it is better engineering.
Careers
We hire experienced engineers and give them work where correctness is not negotiable. If you want to know whether your code held up in production, this is the right place to be.
Why engineers join
Payments, settlement and platform work where the result is measurable and the user is not forgiving. It is harder, and it is better engineering.
Small teams with real ownership. Review is a habit here, not a ceremony.
We write specifications, design notes and runbooks. Engineers who only want to write code will find that odd; the ones who want to build systems will not.
We do not rotate engineers through accounts. When you start something, you are expected to finish it or hand it over properly.
Cutover weekends and certification windows are on-site or hands-on. The rest is planned around your life.
Certification, courses and conference time are budgeted per engineer, not a perk to be negotiated.
Open roles
We do not always list individual openings. If your experience matches the skills below, send your CV — we respond either way.
Hiring process
Send your CV and a short note on the systems you have worked on. No form-filling theatre.
A working discussion with two engineers about problems you have actually solved.
For engineering roles: a scoped exercise or a walkthrough of a real design you own.
Terms, start date, and a written plan for your first 90 days.
Candidate data is used only for recruitment and retention decisions. Ask us to delete your application at any time and we will.
A short note about the system you are proudest of is more useful to us than a formatted summary.