Field
Cloud
Build and operate computing environments across modern cloud platforms.
Cloud is the same infrastructure problems — compute, network, identity, storage — expressed entirely through APIs and code. That changes the job more than it sounds: you stop configuring boxes and start describing systems. Honest note: cloud is usually a second job, reached from support, systems or networking.
Inside cloud
All 11 roles in this field
Each page covers what you actually do, the technologies, where the work happens, the honest downside, and only then the certifications.
Cloud Architect
Choose the shape of a system, then live with the trade-offs you picked.
A senior destination
Cloud Engineer
Build and run infrastructure that exists only as an API call.
Usually a second role
Cloud Network Engineer
Solve routing problems that exist only as API calls.
Usually a second role
Cloud Security Engineer
Secure infrastructure that can be created, changed and destroyed in seconds.
Usually a second role
DevOps Engineer
Make shipping software boring — automated, repeatable and reversible.
Usually a second role
Platform Engineer
Build the internal platform other engineers deploy onto, so they stop reinventing it.
A senior destination
Site Reliability Engineer
Decide how reliable a system needs to be, and engineer it to stay there.
A senior destination
DevSecOps Engineer
Put the security checks inside the pipeline, so nobody has to remember them.
A senior destination
Identity Engineer
Own the system that decides who everyone is and what they may reach.
Usually a second role
Security Architect
Decide the shape of defence before anything is built — then defend the decision.
A senior destination
Zero Trust Engineer
Stop trusting anything for being "inside", and build what replaces that assumption.
A senior destination
Technologies you’ll meet here
Click any of them for a plain-English explanation.