Learn
Modules map onto the sections of each track's exam objectives. Work through a track and you have prepared for its exam.
Sign in to track your progress. You can read everything without an account.
Collections
Curated sequences for a particular audience. You do not have to work through a whole track to get something useful.
Partners and consultants implementing Buildkite for customers — What changes when the organisation is not yours and you will eventually leave it.
Anyone who owns build times, on either side of the platform line — The changes that actually reduce wall-clock time, and how to tell which constraint you have before changing anything.
Developers writing their first pipelines — Enough to write a correct pipeline and read a failing build, without touching anything about running the platform.
Security and compliance reviewers, who will never write a pipeline — What the controls are, what each one actually guarantees, and the questions worth asking of an existing organisation.
Platform and CI engineers who own the Buildkite estate — Topology, security, access and diagnosis — the full Platform Engineer track in order.
All modules
Filter by topic: clear
Writing pipelines Build speed Capacity and cost Security and governance Migrating to Buildkite Delivery and handover
Buildkite Partner Implementer
What transfers between customer implementations, what must be rebuilt, and how to standardise without hard-coding one customer's assumptions.
Delivery and handover · Migrating to Buildkite
Counts toward: Buildkite Partner Implementer (required)
Leaving an implementation the customer's own team can operate, extend and debug without you.
Delivery and handover
Counts toward: Buildkite Partner Implementer (required)
How this differs from the exam
Practice has unlimited retries, tells you which checks failed, and offers a hint. The exam is timed, gives you one attempt, and returns a score only. Badges are not credentials — see what a credential attests.