Published tracks

Five tools, one assessment standard.

Every track ends the same way: a task-based assessment inside the real tool, reviewed by a human before a credential is issued. What differs is the syllabus underneath.

Which track for which role?

RoleTrackWhy
Engineers running agents on production repositoriesClaude CodeTask framing, diff review and permissions in a live repository
Teams on OpenAI with CI-heavy workflowsCodexFailure triage without weakening tests
Engineers who live in the editorCursorContext selection and delegation boundaries in the IDE
Teams with GitHub Copilot already switched onGitHub CopilotAccept, edit or reject: consistent judgment on suggestions
Teams working across code, docs and data in Google's stackGeminiMixed-input tasks and source-checking
Final-year students and college batchesClaude Code FoundationsA lighter assessed task for a whole batch

Most teams start with Claude Code training for teams: a 2 to 4 week cohort on your own repositories that ends in a proctored task.

Looking for Microsoft 365 Copilot rather than GitHub Copilot? They're different products with separate credentials. Here's which Copilot certification you need.

Training students instead of employees?

There's a Foundations-level Claude Code programme for colleges and universities, with a lighter assessment so a whole batch can go through it.

See the student programme

Running a tool that isn't on this list?

We write the curriculum and the rubric around your internal or unreleased tooling directly.

See how custom tracks work

Not sure which track fits your team?

Send us the tool and the headcount — we'll tell you which published track applies, or whether this needs a custom one.