GCP Prep

Cloud Career Guide

5 min readUpdated August 23, 2026

Cloud is not one career. This guide describes the main directions, what the work actually feels like, and how to choose between them without guessing.

Table of contents

The main directions

DirectionThe workSuits you if
Cloud / infrastructure engineeringBuilding and running the platform other teams deploy onto.You like systems, automation and making things reliable.
DevOps / platform engineeringDelivery pipelines, developer experience, reducing friction.You enjoy improving how other people work.
Site reliability engineeringAvailability, performance, incident response, capacity.You are drawn to failure modes and measurement.
Cloud architectureDesigning systems and setting direction across teams.You like ambiguity, trade-offs and talking to stakeholders.
Data engineeringPipelines, warehouses and the platforms analytics runs on.You like data modelling and getting correctness right at scale.
Cloud securityIdentity, boundaries, detection and compliance.You think adversarially and enjoy finding what breaks.
Machine learning engineeringGetting models into production and keeping them working.You like the intersection of software engineering and modelling.

How to choose without guessing

Reading descriptions only takes you so far. The reliable method is to sample the work.

  1. 1Spend a weekend on a small project in each direction that interests you — a deployment pipeline, a data pipeline, a security review of your own project.
  2. 2Notice which one you keep thinking about afterwards, and which one you had to force yourself to finish.
  3. 3Read three real job adverts in each direction and check whether the daily responsibilities appeal, not just the title.
  4. 4Talk to someone doing the job. Most people will answer a specific, respectful question about their work.

Getting the first role

  • Adjacent routes work better than direct ones. Support engineering, internal transfer and consultancies hire people without prior cloud experience far more readily than product engineering teams.
  • Consultancies and managed service providers hire in volume and train people. The pace is demanding and the learning rate is unmatched.
  • Internal transfer is the easiest route of all if you already work in IT. You have relationships and domain knowledge that external candidates do not.
  • Small companies value breadth. If you can do a bit of everything, a small team is often more interested than a large specialised one.

Staying employable

  • Learn concepts rather than products. Products get renamed; the reasons they exist do not.
  • Keep one thing you are genuinely deep in, and enough breadth to know what you do not know.
  • Renew certifications that match your current direction; let the rest lapse without guilt.
  • Write about what you learn, even privately. It is how understanding consolidates.
  • Change environments every few years. Repeated experience is not the same as accumulated experience.