What I told a graduating batch about cloud, and about jobs
My first workshop on cloud computing turned into forty minutes on something else entirely: whether any of them were going to get hired.
I delivered my first workshop on cloud computing earlier this year, at FAST.
I have always liked helping people coming up behind me, but a graduating batch is a particular audience. They are less curious about the technology than about what happens next, and whether they will cope with it. You look out at the room and see faces you want to help, because they are essentially you, a few years back.
That pushed me to prepare something closer to what I would have wanted to hear than what a syllabus would suggest.
The part that was about cloud
We started with why cloud matters specifically now, in a moment where everyone is expected to be a 10x engineer and the tooling only gets you there if the infrastructure underneath is not fighting you.
Then the fundamentals, deliberately provider-agnostic:
- Compute. Virtual machines, containers, functions, and what each one is actually for
- Storage. Object versus block versus file, and why the choice is usually made by the access pattern rather than the size
- Networking. VPCs, subnets, security groups, and why almost every outage a junior engineer causes is a networking one
- Security. Identity first, least privilege as a default rather than a cleanup task
The framing I kept returning to: these concepts transfer across every provider. The names change. S3 becomes Cloud Storage becomes Blob Storage. Learning the concept once means the third provider takes a weekend, not a year. Do not let anyone convince you that you have picked a side.
The part that was actually about jobs
Then we got to the difficult bit.
The most painful question you can ask a fresh graduate right now is whether they have landed a job. For many of them the honest answer is that they have not had an interview yet. Not a rejection. An interview.
That turned into forty minutes of real talk, and it was clearly the part of the session the room wanted.
On certifications. They are not a substitute for engineering ability, and anyone who tells you they are is selling a course. What they do is solve a narrower problem: getting a screener to spend thirty seconds on your CV instead of three. For someone with no production experience, that is a genuine unlock. It is the cheapest credible signal available to you. I went on to take both the AWS Solutions Architect and the GCP Professional Cloud Architect exams for something close to the same reason.
On the portfolio. One project you can explain in depth beats six you cloned from a tutorial. The question in an interview is never "did you build it", it is "why did you build it that way", and a tutorial gives you nothing to say.
On interviews. Most early-career candidates lose on communication, not knowledge. Being able to narrate your reasoning while you are stuck is worth more than arriving at the answer silently.
On the market. It is genuinely harder than it was when I graduated, and pretending otherwise would have been insulting. But a hard market is not a closed one, and the people who keep going are a much smaller group than the people who apply.
Afterwards
I do not know how much of it landed. You never really do. I hope a few bulbs went on.
Thanks to Usman Ghani and Sir Zaheer Sani for having me. I would do it again.
If you are organizing something similar and want someone to come talk about cloud architecture, serverless, or agentic systems, get in touch.