Company · Careers
Show your working, for a living.
Sokros builds the marking infrastructure regulated qualifications run on. Small team, hard problem, every decision on the record.
London · Gulf region · remote across time zones
01 · What we're building
The unglamorous version, on purpose.
Here is the problem from inside. Centres can only mark what their qualified markers can read, and markers are scarce, expensive and, under load, inconsistent. Point a chatbot at the backlog and the first audit ends the experiment: same script, different answer, nothing on the record to defend.
So we built the version that survives the audit. A pipeline that reads evidence before it judges, checks hard requirements as rules, grades with written reasoning, and keeps every decision replayable, with zero third-party AI in the marking path.
That engine now marks live cohorts across 34 centres in 20 markets, and the same pattern (extract, gate, judge, audit) is extending to identity, inspection and bespoke regulated workflows. The interesting problems are still in front of us.
02 · How we work
The principles the work runs on.
The same standards we hold the engine to. If these read like your standards too, you will probably like it here.
Boring reliability is the product
We build the marking layer centres stand on, the way payments companies build rails. The win condition is a results day where nothing interesting happens.
Design for the audit, not the demo
If a decision cannot be explained from the record, it does not ship. That one rule shapes the architecture more than any feature request ever has.
Configuration over code
New qualifications, units and brief years are authored, not programmed. That is how a small team serves many awarding bodies without forking the engine.
Sovereignty is real work
In-region hosting and fully on-premise deployment exist because our customers' data obligations are real. We build for the strictest boundary first and relax from there.
03 · Open roles
Where we need people.
No open roles right now. Write anyway.
04 · How hiring works
Four steps, none of them a maze.
We hire the way we mark: evidence first, reasoning written down, and an answer you can hold us to.
Write in
Tell us what you have built and why this problem interests you. A short letter in your own words beats a templated CV.
A conversation
With the people you would actually work with, about the work itself. No brainteasers, no whiteboard theatre.
Show your working
A small exercise close to the real job, or a walkthrough of something you have already made. We read the reasoning, not just the result.
A decision in writing
Yes or no, with the reasons. We hold every grade the engine produces to that standard, so we hold ourselves to it too.
No perfect role? Write anyway.
Tell us what you want to work on. The team is small enough that a good letter is read by the people who would answer it.
London · Gulf region · remote across time zones