What we mean when we say certified

Every engineer at 10x Factory is certified before they are put on an engagement. That word is doing a lot of work, and it is worth saying exactly what it does and does not mean.

It is not a course. It is not a badge from a model vendor. It is an assessment of what an engineer produces when the system is real and somebody is depending on it.

What it covers

AI-native ways of working. Not prompt technique, but the practice of holding architecture and judgement while agents do production work. Knowing what to delegate, what to check, and what to never delegate is most of the skill.

The 10x Factory methodology. How scope, architecture, review and handover change shape when you ship every week instead of every quarter.

The delivery platform. Hands-on competence with the platform every engagement runs on, including its failure modes. An engineer who does not know where the platform is unreliable will trust it in exactly the wrong place.

Production delivery. The final gate is real work on a live engagement, reviewed by a certified engineer throughout. An engineer either shipped something to our standard or they did not.

The line we teach

The whole discipline reduces to one judgement, made repeatedly: what is mechanical, and what is consequential.

Mechanical work is voluminous, specified, and checkable. Connector implementations. Schema migrations. Test scaffolding. CRUD surfaces. Channel definitions. Agents are extremely good at this, and a certified engineer's job is to define the check that makes the output trustworthy rather than to write the output.

Partic is the cleanest example. The conformance suite was built before any connector existed. Once a connector is defined as anything that passes a fixed set of behavioural tests, generating one becomes tractable and reviewing one becomes fast. That is the whole reason a fifteen-connector launch surface was not the schedule.

Consequential work is where being wrong is expensive and being wrong is easy to miss. On Outra it was identity resolution and the privacy boundary. On Matrix it was the query planner and the access-control model. On NewsletterJet it was deliverability, where reputation is slow to build and immediate to lose. None of that was delegated on any of those projects, and certification is largely about being able to tell which category a given piece of work falls into before you start it.

What it is not

It is not a route into engineering. Certification assumes substantial production background: engineers who have owned systems other people depended on, and been on call for them. The judgement we are assessing is not teachable in six weeks. What is teachable in six weeks is how to apply it when agents are doing the typing.

It is also not permanent in the way a qualification is. The platform moves faster than any curriculum. A practice that was correct nine months ago can be actively wrong now; we have retired advice twice this year. Certification is re-validated as the platform changes rather than on a fixed schedule, because the fixed schedule is the part that turns certification into theatre.

Why we make engineers pay for it

Engineers fund their own certification, and we refund it in full on the day they pass.

The reason is simple. Anything given away free gets treated as free, and certification only means something if failing it is possible. Putting the cost on the attempt and refunding it on the outcome keeps the standard honest without making it a barrier to anyone who can actually clear it.

We certify client engineering teams too, run as a cohort inside an existing engagement against their own codebase. On several engagements that was the highest-value thing we did, and the client ended up needing fewer of our people. That is the intended direction. A capability you have to keep renting is not a capability.