Networking and identity
Diagram a fictional application’s traffic paths and access needs.
Useful evidence: A network sketch, least-privilege permissions and checks for an access failure.
Career guide · cloud engineering
Do you need a certification for cloud engineering?
Build and operate cloud systems that meet a real requirement. Choose learning for the platform, operational responsibility and practice you need—not a universal certificate sequence.
AWS and Azure credentials cover different work. Choose the platform and task first, then check the course’s starting knowledge, practical access and exam scope.
Day-to-day work
What does a cloud engineer do?
- Translate a system requirement into an infrastructure plan, including dependencies and operating constraints.
- Configure and integrate compute, storage, networking and access for the chosen environment.
- Monitor systems, investigate faults and maintain useful operational records.
- Test changes, reliability and recovery arrangements before relying on them.
- Document designs and operations, and coordinate changes with security, application and support teams.
Adapted from O*NET’s broader systems-engineering tasks and the named AWS/Azure role scopes below. Individual cloud jobs divide these responsibilities differently. O*NET tasks · checked 2026-10-15.
Microsoft describes Azure administration across compute, storage, networking, identity and governance. AWS describes deploying, managing and operating workloads. These issuer scopes help compare learning; neither defines every Cloud Engineer job.
Build evidence of your work
Skills to learn—and ways to practice them.
These optional exercises use invented data, offline examples and permitted environments. They help describe a learning gap; completing them is not a prerequisite to asking for training.
Compute and storage
Explain how an invented workload’s capacity and data needs affect a design.
Useful evidence: Assumptions, alternatives and the observations needed to choose.
Automation and change
Review a small infrastructure definition in a permitted lab or offline example.
Useful evidence: The proposed change, validation, rollback and cleanup plan.
Monitoring and diagnosis
Use invented metrics and logs to investigate a service interruption.
Useful evidence: A timeline, competing explanations and the next useful check.
Recovery and reliability
Plan how a fictional service would recover from a failed dependency.
Useful evidence: Recovery assumptions, a test plan and the limits of the result.
Cost and communication
Compare two fictional deployment choices and explain them to a manager.
Useful evidence: Usage assumptions, cost limits, tradeoffs and who approves a change.
Use approved environments. Do not scan a workplace, expose private logs or create paid cloud resources for these examples. A permitted lab’s account, cost limits and cleanup need to be agreed separately.
Dated occupation context
Cloud engineer salary: understand the proxy.
$116,580Median annual wage · United States · May 2025
Computer Occupations, All Other · SOC 15-1299
Computer Occupations, All Other · SOC 15-1299
This is a broad occupation proxy, not a measured Cloud Engineer salary. The task profile uses Computer Systems Engineers/Architects (O*NET 15-1299.08); its parent BLS wage group is Computer Occupations, All Other (SOC 15-1299), which includes other specialties. Read the BLS occupation evidence.
BLS projects 5% employment growth from 2025 to 2035 for Computer Occupations, All Other. That broad group is not a forecast for cloud engineer jobs alone. Read the projection scope.
Compare location, industry, experience and responsibilities in actual vacancies. The wage period and projection window differ.
Existing governed wage record reused; original observation 2026-06-25 and wage source retained. Corroboration checked 2026-10-15. Historical projections elsewhere retain their original dates.
How to get started without a compulsory badge ladder.
BLS lists a bachelor’s degree as typical entry education for the broad wage group. That does not establish a Cloud Engineer hiring rule or course prerequisite. Compare the actual vacancy’s platform, systems experience, scripting and operational responsibilities.
- Identify the work. Read the actual responsibilities, platform, tools and expected level of ownership.
- Describe your starting point. Note relevant work, systems knowledge and what you can already explain or demonstrate.
- Choose learning for a gap. A focused skill course, internal mentoring, free documentation or full certification preparation can serve different needs.
- Check separate requirements. Course admission, recommended experience, exam eligibility and employer hiring criteria are different questions.
Related starting points: Network administration duties and training · IT support duties and training.
Related learning
Which training fits your cloud engineering gap?
Compare the learning choices for this work, then inspect the detailed guide’s curriculum, experience guidance and delivery evidence. These are alternatives and supporting skills, not a compulsory sequence.
Microsoft Azure Administrator Associate · AZ-104
Azure administration: compare identity, storage, compute, networking and monitoring work with the named course and its starting knowledge.
AWS CloudOps Engineer Associate
Operating AWS workloads: compare monitoring, recovery, deployment and troubleshooting preparation. Inspect the target experience and lab access.
AWS Solutions Architect Associate
AWS architecture decisions: compare design tradeoffs and the preparation scope. Architecture preparation is different from operating a service.
Google Associate Cloud Engineer
For a Google Cloud requirement, inspect the existing deployment and operations guide, named preparation and purchase limits.
AWS Cloud Practitioner
For cloud vocabulary and service awareness. Foundational literacy alone does not demonstrate engineering or operations ability.
CompTIA Linux+
For a Linux systems gap relevant to the role. Choose this scope when the actual environment requires it, rather than collecting another badge.
Choose self-paced, live virtual or classroom instruction
Self-paced: compare lessons, personally operated labs, feedback and access expiry. A video library and a lab subscription are different packages.
Live virtual: verify the instructor, time zone, class hours, interaction and each learner’s practice access.
Classroom: verify where the instructor is, equipment and travel. Attendance from a centre may still mean remote teaching.
Check the delivering seller’s current vendor authorization for the exact entity and region, named course/version, labs, support, voucher, cancellation and final invoice. The linked guides retain their own dated evidence and unknowns. No new price, seat or authorization claim is made here.
Turn the task gap into a useful training brief.
Name the work, platform, starting knowledge and practice or feedback you need. Actual employer requirements, timing and budget are optional context. Research and private planning need no contact details.
A short request lets Learnerside reply; detailed planning is optional. Provider sharing needs separate consent naming the recipient.
Sources and evidence scope
- BLS: Computer Occupations, All Other: Broad occupation wage and 2025–2035 outlook; not a Cloud Engineer series. Checked 2026-10-15.
- O*NET: Computer Systems Engineers/Architects, 15-1299.08: Broader task profile, updated 2026; salary comes from parent SOC15-1299. Checked 2026-10-15.
- Microsoft: Azure Administrator Associate: Platform role scope and recommended starting knowledge. Checked 2026-10-15.
- AWS: CloudOps Engineer Associate SOA-C03 guide: Operations scope and target candidate experience. Checked 2026-10-15.
- Linked certification guides retain their own course, provider and observation dates. This page does not reverify their offers.
Practice examples and learning-fit suggestions are Learnerside analysis, not exam questions, a hiring rule or a promise of pay, employment or exam results.