DevOps & Reliability
The DevOps & Reliability standard recognises people who shorten the distance between an idea and production while making outages rarer and shorter.
The Cloud Engineering standard recognises people who can build infrastructure that survives contact with real traffic, real budgets and real failure. Cost discipline is assessed alongside resilience, because in practice they are the same conversation.
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 core services, the shared responsibility model and basic cost drivers. | 0–1 yr | 10 h |
| 2BIPS Practitioner | BIPS-P | Provisions and maintains environments as code, with review. | 1–3 yrs | 15 h |
| 3BIPS Professional | BIPS-Pro | Owns a platform in production, including its availability and its bill. | 3–6 yrs | 20 h |
| 4BIPS Specialist | BIPS-S | Leads a specialism — networking, multi-region, platform engineering — with evidence. | 6–10 yrs | 25 h |
| 5BIPS Expert | BIPS-E | Sets cloud strategy and is accountable for the estate 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.
Builds and runs the platform other teams deploy onto.
Turns infrastructure into a product with real users.
Chooses the shape of the system and defends the trade-offs.
Owns the estate, its resilience and its cost.
Our employer councils begin shaping the next professional standard.
Resilience and spend are assessed together from Level 3.
Capacity planning when inference is the main cost line.
The DevOps & Reliability standard recognises people who shorten the distance between an idea and production while making outages rarer and shorter.
The Cyber Security standard certifies people who can find weaknesses before an attacker does, and hold a response together when something gets through.
The Software Engineering standard certifies people who write code others can safely change years later.