11TrainingCertification Programs
Not who attended. Who can do the work.
Attendance proves nothing. We agree the competencies with your leads, teach them against your own systems, and assess with project work marked by practising engineers. What you get back is a straight answer to the question every skills matrix guesses at: who can be trusted with which work.
- Shape
- Multi-week cohort, part-time
- Format
- Modules, assessed project work, written review
- You leave with
- A capability map you can staff from
01 — The problem
Everyone attended. Nobody changed.
Training budgets get spent on sessions with excellent feedback scores and no measurable outcome. Six months later nobody can name a capability the team gained, and the same quiet assumptions about who is good at what still decide who staffs which project.
- Skills matrices filled in from memory and optimism.
- Client questionnaires asking for evidence you cannot produce.
- Two engineers with the same title and a year of capability between them.
- A course everyone passed, because passing was never in question.
02 — What you get
A standard you set, marked by people who ship
We define competence in terms specific enough to assess, build modules that teach it against your codebase and your backlog, and mark real project work rather than a multiple-choice exam. Passing means someone demonstrated the skill in front of a reviewer who could tell.
- Competency framework agreed with your leads, written in terms specific enough to mark
- Modules built on your codebase, your backlog, and your constraints
- Assessed project work with written feedback for every participant
- Certification records naming the criteria each person was marked against
- A capability map of the team — per person, per competency
- Gap analysis and a refresh cadence, so the record doesn’t rot
03 — How it runs
Define
Agree what competence means for your work, in terms specific enough that two reviewers would mark the same answer the same way.
Deliver
Modules run against your systems, with exercises pulled from your actual backlog rather than a sample project.
Assess
Project work marked by practising engineers, with written feedback each participant keeps.
Certify
Records issued, capability map published, and the refresh cadence set before the cohort closes.
04 — Proof
20+
Years of production experience
PhDs
And industry veterans setting the bar
1000+
GitHub stars behind the material
The curriculum comes from delivery, not textbooks. The open-source infrastructure our team maintains — RedisOplog, @bluelibs/nova, @bluelibs/runner — is used by developers worldwide, and the bar we mark against is the one we hold our own engineers to on Fortune 500 work, including StoneX Group.
05 — Straight answers
Is this an accredited certification?
No. It is a Day1 programme, marked by practising engineers against competencies you approve. No external accreditation body is involved and we won’t imply otherwise. What it certifies is that someone did the work in front of a reviewer qualified to judge it.
What if someone fails?
They get specific feedback and a route back. A programme where everyone passes tells you nothing you didn’t already assume.
Why not use a vendor certification?
Vendor exams verify product knowledge. This verifies whether someone can do your work, on your systems, which is what you are actually staffing against.
How long does it take?
Usually several weeks part-time, sized around real project work so delivery keeps moving while the cohort runs.
Know what your team can do before a delivery date depends on it.