Sometimes, but it is rare, because these roles expect you to have run production systems. The more reliable path is a first job in backend, DevOps or cloud support, where you learn production, then a move into SRE or platform work within a couple of years.
What people tell me
I am in my final year and I really enjoy the infrastructure side: Linux, Docker, a bit of Kubernetes and monitoring. I read about site reliability engineering and platform engineering and they sound like exactly what I want to do. But most job posts ask for several years of experience. Should I aim for these roles directly as a fresh graduate, or is that unrealistic? And if I cannot get one yet, what should my first job be?
A composite of the messages behind this question, with personal details left out.
Key takeaways
- Direct graduate SRE or platform roles exist but are uncommon; most people move in after a first job.
- Good first jobs are backend development, DevOps, cloud support or a junior role on an infrastructure team.
- Learn Linux, networking, one programming language, containers and Kubernetes basics properly before anything else.
- Build one small system you operate like production: SLO, dashboard, alerts, runbook and a postmortem.
- Tell interviewers you want to grow into reliability work; many teams have an internal path.
The honest answer
It can happen, but plan for it not happening. Site reliability and platform engineering are about keeping production systems healthy and making other engineers faster. Both roles are built on experience of running real software under real load, so most job posts ask for a few years of it. A small number of large companies hire graduates into SRE teams, and some startups will give a strong junior the infrastructure work, but these are the exception.
That is not a reason to give up on the goal. It is a reason to choose a first job that gets you there.
First jobs that lead to SRE and platform work
- Backend developer. You learn how services fail, how databases behave under load, and what good logging looks like. Many strong SREs started here.
- DevOps or cloud engineer. Pipelines, Terraform, containers and Kubernetes, which are the raw material of platform work.
- Cloud or technical support engineer. Less glamorous, but you debug real customer problems every day, which is exactly the skill SRE teams value.
- Junior role on an infrastructure team. Even if the title is generic, being close to the people who run production teaches you a lot.
In any of these, say early that you want to grow into reliability or platform work. Ask to shadow on-call, join incident reviews and help with monitoring. Internal moves are the most common way in.
What to learn while you are still studying
Get the foundations solid before the advanced topics:
- Linux and the command line, properly.
- Networking: DNS, HTTP, TLS, ports, and how to debug them.
- One programming language you can build small services and scripts in.
- Containers and Kubernetes basics, and one cloud.
The DevOps and cloud roadmap covers these in order. Once you are comfortable there, the Platform engineering and SRE roadmap is the next step, and its first stage on SLOs and error budgets is worth reading early because it changes how you think about systems. The cheat sheet is a good way to see what the field actually involves.
A project that stands out
Most graduate portfolios have web apps. Very few have a system the student ran like production. Build something small and operate it:
- Run it on a local Kubernetes cluster with kind, or on a cheap server.
- Write an SLO, build a dashboard and set up alerts.
- Break it on purpose, fix it, and write a short blameless postmortem.
A status page with multi-region uptime checks works well as a final year project and gives you a lot to talk about. For debugging practice, SadServers hands you broken servers to fix against a timer.
Keep the goal, be flexible on the route
Two years in a good backend or DevOps role, with on-call experience and a few incidents you helped resolve, will make you a much stronger SRE or platform candidate than a graduate who went straight in. More answers like this are in the questions library.
If you want help choosing your first role, create a free account and start the roadmap, or book a session and we can look at your options together.
Was this answer helpful?
Your situation is not quite this one?
Members get written answers to their own questions, a roadmap built for them and feedback on their projects. Early access is open: sign up and your account is active shortly after. Prefer to talk? A free call works too.