Careers

We are small, and the work is unusually wide. If you want one layer of one system, this is the wrong place; if you want the whole path from the disk to the customer's sentence, read on.

How we work

·You own what you ship, including how it behaves at three in the morning and how its failure reads to a customer.
·Write it down. Design decisions live in the code that implements them, in the comment explaining why the obvious approach was not taken.
·Verify rather than assert. "It should work" is not a report; the output of the thing working is.
·Say what is not done. An honest gap is a plan; a quiet one is a surprise with interest.

What we are usually looking for

·Infrastructure engineers who have operated something at scale and have the scars to show which abstractions leak.
·Systems engineers comfortable in the layer where Postgres, networking and process supervision meet.
·Product engineers who treat an error message as a design surface.
·Security engineers who would rather close a path than document it.

How to apply

There is no form. Write to careers@scaleai.markets and tell us about something you built that was harder than it looked, and what you would do differently. We read everything, and we reply either way.

We hire for judgment over credentials. If you have never worked somewhere with a name anyone recognises and can still answer the question above well, you are exactly who we want to hear from.