The short read
Cloud engineers configure and operate infrastructure and services. DevOps engineers improve the path from code to production. Platform engineers build reusable internal capabilities; SRE work focuses on measurable service reliability.
Role explained
What the work involves
AWS, Azure, Kubernetes and Terraform are common tools, but employers also need practical understanding of networking, identity, deployment, monitoring, incident response and cost or reliability trade-offs.
Typical outputs
- Repeatable infrastructure and deployment workflows
- Useful monitoring, alerting and incident notes
- Secure, documented services with clear ownership
Skills and examples to demonstrate
- Understanding of reliability, access and cost trade-offs
- Hands-on evidence of automation and operational thinking
- Ability to explain a deployment, outage or rollback clearly
Your Talent Passport
Make your work easy to understand
- Separate lab practice from production responsibility.
- Describe the service, automation and operational concern your project addressed.
- Name AWS, Azure, Kubernetes or Terraform only where you can explain a concrete task.
Make a plan
A practical 2027 learning checklist
Deploy a small service using infrastructure as code.
Add logs, a health check and a useful alert condition.
Practise explaining a safe rollback and least-privilege access.
Compare one managed service with a self-managed alternative.
Check the location and work mode
Where these roles are found
Bengaluru, Hyderabad, Pune, Chennai and Delhi NCR have established technology markets where cloud work may be attached to product teams, services or GCCs. A platform title can mean different levels of ownership; read the listed systems and on-call expectations carefully.