A cloud engineer is the person who builds and operates the infrastructure layer: networking, compute, storage, identity, observability. The role is real; the LinkedIn version is mostly noise (certifications, buzzword bingo, vendor-specific titles that don’t mean anything outside the resume).
Table of contents
- The day-to-day
- The four specializations
- The certifications
- The skill stack
- The career path
- The cloud engineer vs platform engineer distinction
- The interview questions
- FAQ
The day-to-day
A typical cloud engineer’s week:
- Monday. Review weekend alerts, run a postmortem for the incident that happened on Saturday, write the action items.
- Tuesday. Implement the action items: deploy the new monitoring, fix the runbook, update the Terraform module.
- Wednesday. Meet with the application team about the new service they’re launching. Help them with IAM, networking, observability.
- Thursday. Capacity review: look at the next 90 days of usage, model the cost, raise the alarm if it doesn’t fit the budget.
- Friday. Documentation, training the on-call, cleaning up the backlog.
The role is operational, with a heavy dose of architecture. The team that treats it as a pure engineering role misses the operational half; the team that treats it as pure ops misses the architectural half.
The four specializations
Most cloud engineers specialize in one of four areas:
- Platform engineering. Build the internal developer platform: the deploy system, the observability stack, the secrets manager.
- Networking. VPCs, load balancers, DNS, VPN, CDN.
- Security. IAM, security groups, encryption, audit logs, compliance.
- Data infrastructure. Databases, data pipelines, data warehouse, caching layers.
The team that hires for the role should pick one of these four specializations, not “cloud engineer” as a generic title.
The certifications
The certifications that actually matter:
- AWS Solutions Architect Associate. The right certification for the team that wants a baseline of AWS knowledge.
- AWS Solutions Architect Professional. The right certification for senior engineers.
- CKA (Certified Kubernetes Administrator). The right certification for the team that runs Kubernetes.
- Terraform Associate. The right certification for the team that uses Terraform.
The certifications that don’t matter: anything from a vendor that does not have real market share. The team that hires for the role should weight the certification lower than the hands-on experience.
The skill stack
The five skills that matter:
- Linux fundamentals. The cloud is Linux. The team that can troubleshoot on the command line is the team that closes incidents fast.
- Networking. TCP/IP, DNS, HTTP, TLS, load balancing, firewalls. The team that understands the network layer debugs faster.
- One programming language. Python, Go, or TypeScript. The team that writes code automates the boring work.
- Infrastructure as code. Terraform, Pulumi, or CloudFormation. The team that click-ops the cloud is the team that has drift.
- Observability. Metrics, logs, traces, alerting. The team that has good observability catches issues before customers do.
The career path
The common path: cloud engineer -> senior cloud engineer -> staff cloud engineer -> principal engineer -> director of infrastructure. The team that wants to move to a different role can pivot to platform engineering, security engineering, or SRE from a cloud engineer role.
The cloud engineer vs platform engineer distinction
Modern titles blur:
- Cloud engineer. Builds and operates the cloud layer (AWS, GCP, Azure).
- Platform engineer. Builds the internal developer platform on top of the cloud.
- SRE. Owns the production reliability of the application layer.
- DevOps engineer. Cultural champion of DevOps practices; sometimes a role, sometimes a culture.
The team that hires for one of these titles should be clear about the scope. The team that uses “cloud engineer” as a catch-all has confused expectations.
The modern trend: the platform engineer is replacing the cloud engineer. The team that builds an internal developer platform (deploys, observability, secrets) has less need for a dedicated cloud engineer — the platform team handles the cloud.
The interview questions
The questions a strong cloud engineer candidate can answer:
- Design a system that handles 10x current load. Capacity planning, autoscaling, database read replicas, caching.
- Debug a slow API. Check load balancer health, check app server CPU, check database query plans, check network latency.
- Set up a new VPC with public and private subnets. CIDR planning, route tables, NAT gateway, security groups.
- Explain the difference between horizontal and vertical scaling. When to use each.
- Describe a production incident you’ve handled. Root cause, timeline, communication, postmortem.
The team that asks these questions and grades on the depth of the answer hires strong cloud engineers. The team that asks trivia (“what port does S3 use?”) hires memorizers.
FAQ
Is cloud engineer the same as DevOps?
Mostly. DevOps is the broader cultural movement (development + operations). Cloud engineering is one expression of DevOps, focused on the cloud infrastructure. The team that hires for either title is hiring for similar skills.
Do I need AWS certification?
Not strictly, but the AWS Solutions Architect Associate is a useful baseline. The team that hires without certification is fine; the team that hires only certified people misses out on the engineers who learned by doing.
What’s the difference between cloud engineer and SRE?
SRE (Site Reliability Engineering) is the proactive side: building the automation, the monitoring, the deployment pipeline. Cloud engineer is the infrastructure-side: building and operating the cloud layer. The two roles overlap heavily in practice.
Is cloud engineer a good career in 2026?
Yes. Every company that runs anything in the cloud needs cloud engineers. The demand is still growing. The team that picks this career path should specialize in one of the four areas above, not be a generalist.
What’s the difference between a cloud engineer and a cloud architect?
Cloud architects design systems; cloud engineers build them. The architect owns the high-level decisions; the engineer owns the implementation. Many people do both.
Do cloud engineers need to code?
Yes. Terraform, Python, or Go for automation. The team that hires for the role should test for at least one language.
Is the cloud engineer role becoming obsolete?
No, but it’s evolving. The cloud engineer of 2026 uses more managed services, writes more infrastructure-as-code, and focuses more on cost optimization than the cloud engineer of 2018.
If you are sizing the infrastructure for the kind of project this post covers, the RunxBuild hosting calculator is the right place to model the line items. The compute, the memory, the storage, the bandwidth, the database - each one is a separate number, and the team’s mental model for the platform is the sum of those numbers. The RunxBuild dashboard is where the team sees the actual usage in one place.
Useful related references: