Build the systems other systems depend on
Allotropic designs and writes software for organisations that cannot absorb an outage, a lost record, or a quiet corruption of their data. The work is exacting, the review is honest, and the standard does not move.
Inside the practice
Most of what we build is invisible to the people it serves — a settlement path that never loses a transaction, an inventory ledger that never double-allocates, a field system that keeps working when the network does not.
That work rewards patience. We spend longer on design than most teams find comfortable, and we are unhurried about shipping until the failure modes are understood and written down.
How we support you
The conditions we set are simple: give people the tools, the time, and the clarity to do careful work.
Small teams with direct ownership. An engineer who writes a service also operates it, reviews its incidents, and decides when it is ready to ship. There is no separate layer between the people building a system and the consequences of it.
Salaries are benchmarked against the regional market for senior engineering work and reviewed twice a year. Every engineer gets the hardware they specify, licensed tooling, and a budget for the reference material their discipline requires.
Paid annual leave with a minimum we expect you to take, medical cover for you and your immediate family, and quiet weeks scheduled after major releases. Sustained output matters more to us than visible intensity.
Time is set aside for reading, prototyping, and deep study of the domains we serve. We support certification and formal study where it strengthens the practice rather than the CV.
How we hire
A short process, run by the engineers you would work with, with a clear answer at the end of it.
Engineers who can hold a whole system in their head, explain a trade-off without jargon, and say plainly when something is not ready. Depth in one discipline matters more than breadth across many.
A short conversation about your work, a paid technical exercise drawn from a real problem we have solved, a systems discussion with two engineers, and a final conversation about scope and expectations. Four steps, typically three weeks.
Use them. We expect you to understand and defend every line you submit, whether you typed it or generated it. In the technical exercise, tell us which tools you used and where their output needed correction.
Application material is used only for the role you applied to, held for twelve months, and deleted on request. We do not share candidate data with third parties.
Tell us what you need at any stage and we will adjust the format, timing, or tooling of the process. It has no bearing on the assessment.
Open roles
We have no advertised roles at the moment. We still read every open application, and we keep strong ones on file.
Nothing that fits? Write to careers@allotropicltd.com and tell us what you build.