Skills that make the work valuable
- Infrastructure as code
- Cloud identity and access controls
- Virtual networking
- Cloud cost monitoring
Build proof, not just a list
Create a reproducible infrastructure plan for a small application with restricted access, logging, and teardown instructions. Use local validation where possible and document estimated resource use, recovery assumptions, and cost limits.
How to price this work as a freelancer
Separate environment assessment, configuration, migration, and handover in the proposal. Identify who pays resource charges and approves capacity changes. Unexpected usage, idle resources, access delays, and ongoing security updates affect project economics; recurring operations require a defined service agreement beyond the initial infrastructure build.
Start with the income you need to replace
Required hourly rate = (target salary + benefits budget + annual business expenses) ÷ (annual billable hours × share of revenue retained after fees).
For illustration, $100/hour × 25 billable hours/week × 48 working weeks = $120,000 revenue. After $20,000 in business expenses, that leaves $100,000 profit before personal taxes. Replacing a $100,000 salary plus $15,000 in benefits under those assumptions takes $112.50/hour, with no percentage fees.
These are editable planning assumptions, not rates surveyed for cloud engineer work. Your personal taxes, location, contract terms, and workload still affect the comparison.
Employee or freelancer?
Working as an employee
An internal cloud role provides continuity with application teams and the organization paying infrastructure bills. You may inherit complex permissions and share incident coverage, so clarify operational duties and decision authority.
Running a freelance business
Cloud assessments and reproducible environment builds can produce useful bounded engagements. Clients need ownership of accounts, bills, and alerts, while your agreement defines migration support and future configuration changes.
Where this career could take you
- 01Junior Cloud Engineer
- 02Cloud Engineer
- 03Cloud Engineering Lead
An example path, with room for lateral moves or specialization. Progression depends on opportunities and demonstrated work; these steps do not imply a timetable or salary increase.
Try one small next step
Describe a small application environment in configuration files and validate them locally. Explain access rules, cost assumptions, and a complete teardown before creating any chargeable resources.