☁️
Developer Archetype
The Cloud Architect
"Your infrastructure is code. Your code is infrastructure."
vibe
Draws architecture diagrams on a whiteboard and then deploys them with a git push.
Terraform modules, CloudFormation stacks, Ansible playbooks — you define infrastructure the way others write application code. Your repos are full of HCL, YAML, and shell scripts that provision entire environments. The cloud is your IDE.
Typical stack
Known examples
Yevgeniy Brikman
Author of "Terraform: Up & Running", co-founder of Gruntwork
Kelsey Hightower
Kubernetes evangelist, bridged dev and ops like no one else
HashiCorp engineering team
Terraform, Vault, Consul — infrastructure as code, codified
Signature traits
- Repos full of .tf files, YAML, and shell scripts — not a single React component in sight
- Can provision a production-ready cluster faster than most devs can write a TODO app
- Has strong opinions about state management — Terraform state, not Redux
- README files include architecture diagrams and deployment instructions
Strengths
- Thinks at system scale — networking, security groups, load balancers are second nature
- Automates everything — if it can be scripted, it already is
- Bridges the gap between development and operations fluently
Watch out for
- Application code skills may lag behind infrastructure expertise
- Repos look empty to recruiters who don't understand IaC
- Over-provisions complexity — sometimes a simple VPS is enough
How to level up
Build an application that runs on your infrastructure. Not a demo — something with users. The most impactful cloud architects understand what their infrastructure serves, not just how it's provisioned.
Top The Cloud Architects
1 dev analysed
