Certification
Certified means assessed on production work.
Not a course, not a badge, not a two-day workshop. An assessment of what an engineer can actually do when the system is real and somebody is depending on it.
It is also how you apply to work here. We hire only from the certified list, so this is the front door rather than a step after one.
01 · Curriculum
Four parts, none of them theoretical.
Roughly six weeks alongside delivery work, not instead of it. Engineers pay for certification themselves, and we refund it in full on the day they pass.
-
01
AI-native ways of working
Holding architecture and judgement while agents do production work. What to delegate, what to check, and what never to delegate.
-
02
The 10x Factory methodology
How scope, architecture, review and handover change shape when delivery runs an order of magnitude faster.
-
03
The delivery platform
Hands-on with the proprietary platform every engagement runs on, including where it is unreliable and why that matters.
-
04
Production assessment
The final gate is real delivery under review. An engineer either shipped something to our standard or they did not.
02 · Who it is for
Our engineers. And, increasingly, yours.
Every 10x Factory engineer is certified before they are put on an engagement. We also certify client engineers directly. 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.
- Experienced engineersSubstantial production background. This is not an entry route into engineering.
- Client engineering teamsRun as a cohort inside an existing engagement, against your own codebase.
- Delivery leadsA shorter track focused on scoping, review and handover rather than build.
- Re-validated, not renewedCertification is re-assessed when the tooling moves, not on a billing calendar.
03 · How it runs
From application to certified.
-
01
Technical conversation
Ninety minutes with two of our engineers, about systems you have owned and what went wrong with them.
-
02
Methodology and tooling
Structured work through the methodology and the delivery platform, against a real codebase rather than an exercise.
-
03
Supervised delivery
Production work on a live engagement, reviewed by a certified engineer throughout.
-
04
Certified
Granted against that delivery, and re-validated as the tooling changes.
You pay for certification yourself. We refund it in full when you pass, so the cost falls on the outcome rather than on the attempt.
Apply to certify
We read the repository before anything else. Pick one you can talk about honestly, including what is wrong with it.
Application received. We will come back to you about the technical conversation either way.
Before you go
We build in the open, and we would like to keep doing it.
A large part of what makes a six-week delivery possible is open source software that somebody else maintained, for free, for years. We contribute back to the projects our work depends on, and we fund maintainers who do not have an employer behind them.
If that matters to you too, consider chipping in. It goes to the same place our own contributions do.
Handled by PayPal. Entirely optional, and it has no bearing on your application.