Track
Buildkite Partner Implementer
Currently examining version 1.0.0.
- Buildkite Platform Engineer — required before you can attempt this
This track is not yet open for attempts. The objectives below describe the exam being built.
What this credential attests
The holder can deliver a Buildkite implementation for someone else, more than once. It assumes everything in the Platform Engineer objectives and adds what changes when the organisation is not yours and you will eventually leave it.
Partner credentials are valid for one year rather than two, and carry commercial weight. See retakes and recertification.
Format
As with Platform Engineer: performed in a real organisation and verified against the Buildkite API. Tasks are scoped to delivery rather than operation — the assessment is whether what you built survives you.
Objectives
1. Assessing an existing estate
- Establishing what a customer’s builds actually cost them in wall-clock time before proposing changes
- Identifying which constraints are platform, which are pipeline design, and which are organisational
- Recognising the measurements that mislead: queue wait that is really approval latency, averages that hide a bimodal distribution
2. Delivering across organisations
- What genuinely transfers between customer implementations and what must be rebuilt: cluster and queue topology, plugin policy, secrets integration
- Standardising without hard-coding a customer’s assumptions into shared tooling
- Version-pinning and change control for anything you deploy into more than one organisation
3. Handover
- Leaving an implementation that a customer’s own platform team can operate, extend and debug without you
- Documenting queue topology and its reasoning, not just its configuration
- Access and credential handover: agent tokens, secrets integration ownership, who can change what after you leave
4. Boundaries and conduct
- What a partner credential does and does not claim on your behalf
- Not representing a customer’s configuration as Buildkite’s recommendation when it is a compromise
- Escalation paths, and when an implementation problem is a product gap
Preparing
Complete the Platform Engineer modules first. The Partner Implementer modules assume them and cover only what changes when the work is delivery.
Modules
Modules are associated with this credential rather than owned by it — each can be completed on its own, and can count toward more than one.