Technology
Cloud Engineering
The Cloud Engineering standard recognises people who can build infrastructure that survives contact with real traffic, real budgets and real failure.
GCE-035 levels
View the standard →
The DevOps & Reliability standard recognises people who shorten the distance between an idea and production while making outages rarer and shorter. On-call practice is assessed, because reliability claims mean little without it.
Each area is evidenced from your own work. Assessors look for what you decided and why, not for a rehearsed answer.
The same six-level framework, expressed in the terms of this discipline. Experienced applicants can enter directly at a higher level through the portfolio route.
| Level | Post-nominal | What it certifies | Professional Experience | Annual CPD |
|---|---|---|---|---|
| 1BIPS Foundation | BIPS-F | Understands pipelines, version control and why automation reduces risk. | 0–1 yr | 10 h |
| 2BIPS Practitioner | BIPS-P | Maintains delivery and monitoring for a service, under review. | 1–3 yrs | 15 h |
| 3BIPS Professional | BIPS-Pro | Owns the reliability of a production service, including its on-call rotation. | 3–6 yrs | 20 h |
| 4BIPS Specialist | BIPS-S | Leads a specialism — platform, SRE, release engineering — with evidence. | 6–10 yrs | 25 h |
| 5BIPS Expert | BIPS-E | Sets engineering practice and reliability standards across an organisation. | 10+ yrs | 30 h |
You submit real work against the six capability areas.
An assessor checks provenance and your role in it.
A recorded conversation about decisions and trade-offs.
Your credential is issued and listed publicly.
Owns uptime as an engineering problem.
Makes shipping boring and repeatable.
Gives other teams a fast, safe path to production.
Sets the practice the whole org delivers through.
Reliability claims are assessed against real incident records.
How teams actually use SLOs to make trade-offs.
What to let a system fix on its own.
The Cloud Engineering standard recognises people who can build infrastructure that survives contact with real traffic, real budgets and real failure.
The Software Engineering standard certifies people who write code others can safely change years later.
The Cyber Security standard certifies people who can find weaknesses before an attacker does, and hold a response together when something gets through.