For most of the last decade, cost was something cloud teams heard about after the fact, usually in a message from finance. In the Cloud Engineering standard it is now a named capability. Cost discipline sits alongside platform design, infrastructure as code, resilience, cloud security and migration as one of six areas assessed on evidence from your own work.
Why cost earned its own line
Our employer panel was consistent on one point: the engineers they trusted most could explain the bill. A platform that stays up but cannot be afforded is not a success, and a cheap platform that falls over during a region outage is not a saving. Treating the two as separate conversations produced exactly the decisions nobody wanted to defend later.
The strongest candidates never described cost and resilience as a trade-off. They described one design decision with two consequences, and they could talk about both.
What assessors look for from Level 3
At BIPS Foundation and BIPS Practitioner the expectation is awareness: knowing the basic cost drivers and provisioning environments as code, with review. At BIPS Professional (BIPS-Pro) the level description changes. You own a platform in production, including its availability and its bill. Your portfolio should therefore include evidence such as:
- A cost attribution model you built or improved, so spend is visible by team, service or environment.
- A resilience decision where you costed the options, for example multi-zone against multi-region, and recorded why you chose one.
- A reduction in waste, such as rightsizing or scheduling non-production environments, with the reasoning before and after.
- A conversation with finance or leadership where you defended spend before anyone had to ask.
In the professional discussion, the assessor will pick one of those decisions and push on it. What would you have done with half the budget? Which failure would you have accepted? There is no single right answer. The point is that you can reason about both sides at once.
What it means for your portfolio
Don’t file cost evidence in a separate appendix. Put it next to the resilience decision it belongs to, because that is how the assessor will read it. At BIPS Specialist and BIPS Expert, where you lead a specialism or set strategy for the whole estate, we also expect evidence that you shaped how others make these decisions: tagging policy, budget guardrails written into infrastructure as code, or a FinOps practice that platform teams actually use.
FinOps and cost specialists are named in the audience for this standard for a reason. Many arrive from finance rather than engineering, and the portfolio route lets them evidence the engineering side through work they have already done alongside platform teams.