Each skill is a few short lessons, then practice. You rate yourself at the start and again at the end.
Core to the job
Chapter 2
Cloud costs
Build a cost dashboard and set a spend alert
What you'll learn
Cost allocation
Cost per unit
Rightsizing resources
Commitment break-even
Spend that looks wrong
Limits set in advance
Cheaper for the same work
Practice
Build a Tag Coverage Report and Decide What to Chase First30 min
Read a Cloud Bill and Spot the Top Three Cost Drivers15 min
Chapter 2
Cloud platforms
Read a cloud bill and find which services cost most
What you'll learn
Core cloud services
Identity and permissions
Service tradeoffs
Cloud cost drivers
Well-Architected review
Practice
Find 3 wasted cloud resources from a sample bill20 min
Forecast capacity for a growing service25 min
Chapter 4
Automation mindset
Pitch automating a repetitive task, naming its benefit and limits
What you'll learn
Toil test
Automation value
Safe defaults
Maintenance cost
Practice
Pitch an Automation Idea for a Repetitive Process30 min
Chapter 6
Spreadsheets
Build a spreadsheet summary that updates when filters change
What you'll learn
Formula references
Lookup logic
Pivot tables
Auditable workbook
Practice
Rebuild a savings plan model so somebody else can check it in five minutes40 min
Chapter 7
Documenting infrastructure work
Write a task guide and draw how system parts connect
What you'll learn
Runbook purpose
Decision record
Document type
Current version
Practice
Audit one runbook and update it20 min
Write a runbook for one repetitive task25 min
4 more in the plan
Problem solvingTest each possible cause of a problem instead of guessingCh 6
What you'll learn
Problem vs symptom
Clean problem splits
Root cause
Deciding under uncertainty
Practice
Separate the Problem from the Symptom10 min
Critical thinkingSpot a weak assumption and ask where numbers come fromCh 6
What you'll learn
The hidden assumption
Argue the other side
The base rate
Fact vs inference
Wanting it to be true
CommunicationRewrite an update for two different readers, cutting extra linesCh 8
What you'll learn
Lead with the point
Match detail to the reader
Said versus heard
Specific feedback
Practice
Write a Six-Line Delay Message10 min
Working with othersContribute to group work, ask for help and credit teammatesCh 8
What you'll learn
Early team friction
Clear ownership
Challenge ideas, not people
Lead or follow
Practice
Write a Request That Makes It Easy to Say Yes10 min
Your plan
Chapter by chapter.
12 chapters, in this order. Chapter 1 is free.
1~2 wks
See the work of a FinOps engineer
StartFree
2~2 wks
Keep cloud costs under control
Skills
3~2 wks
Build a cloud environment from code
Project
4~2 wks
Automate repeat work instead of clicking
Skills
51–2 wks
Talk to two working cloud cost engineers
People
6~2 wks
Build spreadsheets everyone can work from
Skills
7~2 wks
Document systems so others can follow
Skills
8~2 wks
Make yourself understood across a team
Skills
9~2 wks
Capstone: find savings in a cloud bill
Project
101–2 wks
Answer the questions interviewers ask
Interview
111–2 wks
Decide how you will get in
Decide
12on your timeline
Send your first applications
Apply
The job
What a FinOps Engineer does
Runs cloud financial operations (FinOps), the practice of giving engineering, finance, and product one real-time view of cloud spend. Finds waste, drives cost-aware build choices, and proves savings without slowing teams down.
The work
Build cost dashboards so each team sees its own cloud spend
Set budgets and alerts that flag overspend before bills grow
Hunt waste like idle resources and oversized instances, then fix it
Drive rightsizing so each workload uses only what it needs
Plan commitment purchases like reserved instances and savings plans for steady discounts
Allocate shared costs back to the teams that caused them
Track the cost of running AI and graphics processing unit (GPU) workloads
Report savings and forecasts to finance and engineering leaders
A typical day
Review yesterday's spend and any budget alerts that fired overnight
Dig into a cost spike to find the team and service behind it
Meet engineers to plan a rightsizing change and agree on tradeoffs
Model a savings plan purchase and check it against forecast usage
Update dashboards and share a short savings summary with finance
Tools
Cloud platforms: AWS, Microsoft Azure, Google CloudNative cost tools: AWS Cost Explorer, Azure Cost ManagementFinOps platforms: CloudHealth, Apptio Cloudability, VantageDashboards: Grafana, Looker, Power BIInfrastructure as code: TerraformScripting and queries: Python, SQLSpreadsheets: Excel, Google Sheets
Ways in
There is more than one route.
Ways to study
Bachelor degree in computer science, IT, finance, or information systems
Diploma or certificate in cloud computing or data analytics
FinOps certification such as the FinOps Certified Practitioner credential
Self-study with a free cloud account plus billing and cost labs
How people get their first job
Start in cloud, DevOps, or IT support and take on cost-tracking tasks
Move from a finance or analyst role into cloud cost work
Build a free-tier cloud project and publish a cost breakdown report
Earn a FinOps Certified Practitioner credential and a cloud fundamentals cert
Volunteer to audit and cut cloud spend for a small team or nonprofit
How long does it take to become a finops engineer with Welica?
The plan is 12 chapters, 4–5 months at 15 to 30 minutes a day. You can go faster or slower; the plan moves with you.
Do I need a degree?
Not always. Common routes are bachelor degree in computer science, IT, finance, or information systems, diploma or certificate in cloud computing or data analytics, finOps certification such as the FinOps Certified Practitioner credential, or self-study with a free cloud account plus billing and cost labs.
What is free?
Chapter 1, See the work of a FinOps engineer, is free for good. Premium unlocks the rest of the plan.