FinOps for Engineers
Independent prep for the FinOps Certified Engineer exam. Exam not included.
fundamentalsCourse Syllabus · 6 Weeks
Last updated August 31, 2026
A 6-week hands-on course for engineers who write the infrastructure and code that generates cloud spend — aligned with the FinOps Foundation's Engineering persona and the FinOps Certified Engineer exam guide.
$89 one-time. You sign in with Google before checkout so the course unlocks on that account. Independent course; official exam not included.
Why This Course.
Most "FinOps for engineers" content is generic framework theory wearing an engineering costume — the same six principles, retargeted at people who now write Terraform. This course is different: every week ends with something you'd actually commit — a tagging policy enforced in CI, a rightsizing script against real utilization data, a cost gate on a pull request — because the parts of FinOps that belong to engineers are the parts you can put in a diff, not a slide deck.
What You’ll Walk Away With.
- ✓Write a cloud-cost tagging policy and enforce it as a policy-as-code check that fails a Terraform plan on missing or malformed cost-allocation tags.
- ✓Produce an architecture decision record proposing a cost-aware redesign of one real workload, with a before/after cost estimate.
- ✓Build a rightsizing script that pulls real utilization metrics and outputs a ranked list of oversized resources with estimated savings.
- ✓Design a Kubernetes cost-allocation policy — namespace/label schema plus an OpenCost-style config — that produces a real per-team cost breakdown.
- ✓Ship a CI cost gate that blocks or flags a pull request whose infrastructure change crosses a defined cost-delta threshold.
- ✓Explain the Iron Triangle trade-off (cost, speed, quality) for a real deployment decision, and know which two you're protecting when you concede the third.
How This Course Is Built.
There's official Foundation material and a handful of video crash courses out there. This is a different kind of course:
- ✓Working code, not a slide deck — every deliverable is something you commit and run: a Terraform policy check, a rightsizing script, a CI cost gate.
- ✓Built by a practitioner, not just a certified instructor: someone who manages $10M+ in real multi-cloud spend and has had to get engineering teams to actually adopt cost guardrails, not just agree with them.
- ✓Infrastructure-as-code and CI/CD as the primary surface — not a chapter bolted onto a generalist framework. If you already touch Terraform, Kubernetes, or a deploy pipeline, this starts where you already are.
Scroll right to see the full comparison →
| Option | Price | Format | Working Engineering Artifacts |
|---|---|---|---|
| This course | $89 | Text + interactive + code | Yes |
| Typical Udemy "FinOps for Engineers" course | $15–90* | Video | No |
| Official FinOps Certified Engineer exam (FinOps Foundation) | $325 exam-only (course + exam option also sold) | Certification exam, self-study | N/A |
*Udemy pricing fluctuates heavily with frequent promotional discounts.
Who It’s For.
Backend, platform, and DevOps/SRE engineers who write the Terraform, Kubernetes manifests, and CI/CD pipelines that generate cloud spend, and want to build cost awareness directly into the systems they ship — not analysts building dashboards over someone else's cost data. That's what Practitioner (FOCP) is for.
It's not for people without hands-on infrastructure experience — you should already be comfortable writing Terraform or CloudFormation, deploying to a cloud provider, and touching a CI/CD pipeline before you start. And it's not for FinOps analysts or generalists who want dashboard-building and stakeholder-reporting skills — that's Practitioner (FOCP); this course assumes you already own the infrastructure and teaches you to build cost constraints into it.
Your Instructor.
Adam Morad
Cloud FinOps and data engineering practitioner. Adam manages $10M+ in annual multi-cloud spend, with a track record of cutting cloud costs 20 to 30% through rightsizing and commitment management, and writes and maintains every lesson on The FinOps Desk.
Previously worked at VAST Data, NemoData, Cyber@ Ben-Gurion University (Deutsche Telekom Innovation Labs).
Worked With
Companies Adam has worked with professionally. Not endorsements of The FinOps Desk.
Anodot
Wiv.ai
DoiT
Mapped to the FinOps Foundation's Engineering persona and the public FinOps Certified Engineer exam guide — tagging enforcement, rightsizing, automation, and the cost/speed/quality Iron Triangle all show up here. This course goes further into hands-on implementation (working IaC checks, CI gates, real rightsizing scripts) than the official course's conceptual module list, so treat it as engineering-heavy exam prep, not a guarantee of question-by-question coverage.
Curriculum.
01 · Foundations · Engineering Persona & the Iron Triangle
Cost as a Design Constraint
- The FinOps Framework in one pass: Inform / Optimize / Operate, seen from the engineering seat rather than the practitioner seat
- The Iron Triangle: cost, speed, and quality trade-offs, and which two you protect when a deploy decision forces a concession
- Where the Engineering persona sits relative to the FinOps Practitioner — what you own vs. what you report upward
- Reading a cloud bill as an engineer: unit cost per request, per pod-hour, per pipeline run — not org-wide accounting
- FOCUS (FinOps Open Cost & Usage Spec) for engineers: what a normalized billing schema buys you when you write your own cost queries
02 · Domain: Cost Visibility as Code
Tagging Enforcement & IaC Cost Checks
- Tagging strategy: mandatory keys, ownership tags, and cost-allocation tags that survive refactors
- Enforcing tags at the IaC layer with policy-as-code (OPA/Conftest, Sentinel, or native cloud policy rules) that blocks a plan or apply on missing tags
- Pre-merge cost estimation: wiring a cost-diff tool (e.g. Infracost) into pull request review
- Building cost visibility from resource tags and IaC state, not only from monthly billing exports
03 · Domain: Cost-Aware Architecture
Architecture Patterns That Don't Bankrupt You
- Workload placement: spot/preemptible vs. on-demand vs. committed capacity, and where each is actually safe
- Storage tiering and lifecycle policies: hot/warm/cold data patterns that don't need a human to remember them
- Data transfer traps: cross-AZ and cross-region egress, and the architecture patterns that avoid paying for them by accident
- Serverless vs. container vs. VM cost trade-offs for a given workload shape and traffic pattern
- Attributing shared cost fairly in multi-tenant infrastructure: shared clusters, shared databases, shared queues
04 · Domain: Rightsizing & Autoscaling Automation
Rightsizing and Autoscaling, Automated
- Rightsizing methodology: reading real utilization (CPU, memory, disk IOPS) against provisioned capacity
- Building a rightsizing script against an observability backend (CloudWatch, Prometheus, or a cloud cost API) that flags oversized resources
- Autoscaling economics: tuning HPA / VPA / cluster autoscaler for cost, not only for availability
- Idle-resource detection with safe guardrails — flag and confirm, not blind auto-delete
05 · Domain: Container & Kubernetes Cost Allocation
Kubernetes Cost Allocation
- Namespace- and label-based cost allocation in multi-tenant clusters
- Requests vs. limits: setting them so you avoid both waste and throttling, and why "just set it high" is a cost bug
- The OpenCost/Kubecost-style allocation model, and how cluster autoscaler decisions ripple into per-team cost
- Chargeback vs. showback at the namespace or team level, and what to automate vs. what stays a monthly report
06 · Applied · Continuous Enforcement
CI/CD Cost Gates
- Where cost checks belong in the pipeline: pre-merge estimate, pre-deploy budget gate, or post-deploy drift detection
- Building a CI cost gate that blocks or warns on a pull request whose infrastructure change crosses a cost-delta threshold
- Wiring budget alerts and anomaly detection to deploy events, so a spend spike traces back to a specific release
- The handoff back to the FinOps Practitioner: what you own end-to-end vs. what you surface for the cross-functional team
Frequently Asked.
How much time does this take?
Do I need infrastructure or cloud experience already?
How does this relate to the Practitioner (FOCP) course?
Is this the official FinOps Foundation course?
What if I don't pass the FinOps Certified Engineer exam?
What happens once I pass the FinOps Certified Engineer exam?
Interested?.
$89
One-time payment · full 6-week course, all exercises, and FinOps Certified Engineer exam prep.
Not right for you? Refunds are handled per our refund policy — email support@finopscourse.com.
Try the free Week 1 lesson, then reach out with any questions about the full course.