- Home
- ›
- Field Notes
- ›
- How to Become a Cloud/DevOps Engineer With No Experience
How to Become a Cloud/DevOps Engineer With No Experience
The DevOps engineer path doesn't run through years of experience — it runs through certifications and real projects. Here's the exact roadmap.
DevOps engineer. UK market, £50k–£80k, no degree required, companies cannot fill the roles fast enough. If you have been scrolling job boards wondering why every listing asks for 3–5 years of experience while you have none, here is the actual situation: the requirement is a relic, not a rule. And there is a shorter path than the job listings imply.
The global DevOps market was valued at $6.78 billion in 2020. By 2030, it is projected to reach $57.90 billion. The barrier to entry right now is certifications and project work — not years of experience.
Why DevOps Has an Experience Paradox (And Why It Is Different)
Most entry-level tech roles have a genuine experience paradox. Data analysis, cybersecurity, software engineering — the experience requirements are real friction because the skills took time to accumulate and the work is complex.
DevOps is different. The core skills of DevOps — cloud infrastructure, CI/CD pipelines, containerisation, automation — are learnable in a defined, structured way. You do not need to spend years to understand what a Docker container does. You need to learn it, practice it, and demonstrate it.
The experience requirement in DevOps job listings is mostly a relic. It exists because HR teams copied it from senior roles, because hiring managers assume seniority, and because no one has given them a better signal to evaluate.
That signal is certifications plus project work. And that is a much shorter path than the job listings imply.
The Certifications That Actually Matter
Forget the long list. Here are the certifications that open doors in the UK and US market right now.
AWS Solutions Architect Associate is the starting point. It costs around $150, takes most people 2–3 months of focused study, and validates your ability to design distributed systems on AWS — which matters because most companies use AWS and most want someone who understands it.
AWS Developer Associate builds on that. Where Solutions Architect is design, Developer Associate is implementation: deploying applications, using AWS SDKs, building CI/CD pipelines on AWS. The two together give you a solid foundation.
Terraform Associate comes third. Terraform lets you provision cloud resources with code instead of clicking through cloud consoles. Every serious DevOps team uses it. Most people prepare in 1–2 months.
Certified Kubernetes Administrator (CKA) is the last piece of the core four. Kubernetes is the standard for container orchestration in 2026. The CKA is hands-on — you configure an actual cluster — which makes it a more credible signal than a written test.
Four certifications, around $1,000–$1,200 total. Not cheap, but a fraction of a degree’s cost and time.
The Projects That Demonstrate Real Ability
Certifications get you past the ATS filter. Projects get you past the interview.
The problem with learning DevOps from courses alone is that courses give you a sandboxed environment. Everything works. Nothing breaks. There are no stakeholders, no production consequences, no trade-offs.
Real project work is different because there are real constraints. You have to make things work under pressure, deal with things breaking, and explain your decisions.
Here is what those projects should look like.
Build a CI/CD pipeline from scratch. Take a simple web application — anything will do, even a static site — and set up a full CI/CD pipeline using GitHub Actions or GitLab CI. The pipeline should run tests on every pull request and deploy to a cloud environment on merge. Document what you did and why you made each decision. This is the DevOps equivalent of a portfolio piece. It shows you understand the workflow that DevOps is meant to improve.
Deploy infrastructure with Terraform. Write Terraform code that provisions a complete environment on AWS — VPC, subnets, an EC2 instance or ECS cluster, RDS database, load balancer. Make it modular. Make it repeatable. Then destroy it and rebuild it from scratch using just your Terraform files. Being able to do this cleanly is what senior DevOps engineers actually do day-to-day.
Set up monitoring and alerting. Deploy a simple application and set up Prometheus and Grafana to monitor it. Configure alerts so you get notified when the application goes down or resource usage crosses a threshold. Write a runbook explaining what you set up and how to use it. That kind of work separates someone who has learned DevOps from someone who has done it.
Contribute to open source infrastructure projects. The DevOps community is unusually active in open source. Finding a well-maintained infrastructure tool on GitHub, identifying a real issue, and submitting a meaningful contribution is one of the strongest signals you can show. It is public, it is reviewable, and it demonstrates that you can work in a collaborative environment.
These four projects, done properly, are worth more than a year of helpdesk experience.
The Salary Reality
Here is what this path leads to, according to current UK market data.
Entry-level DevOps or cloud engineering roles in the UK typically start between £35,000 and £50,000. With 2-3 years of experience and strong AWS skills, that range moves to £55,000-£75,000. Senior DevOps engineers in London regularly command £80,000-£100,000.
The US market is comparable. Entry-level cloud/DevOps roles in major US metros typically start at $70,000-$95,000, according to Glassdoor data.
Demand is there. Qualified supply is not. That gap is your opportunity.
The Gap Between Certification and Employment
Here is the uncomfortable part of this post.
Certifications open doors. They do not walk you through them.
Many people who hold AWS certifications and can pass technical interviews still struggle to land DevOps roles because they cannot answer the question: “what did you actually build?”
Hiring managers in this space have seen plenty of candidates who know the theory and cannot operate in a real environment. The pipeline breaks at the interview, not at the application stage.
This is where structured project work makes the difference. A certification shows you studied. A delivered project — with code, decisions, outcomes — shows you can operate.
FursaFlow works here. When you deliver a real cloud infrastructure project, a working DevOps engineer reviews and verifies it. That’s different from a course certificate or a tutorial project. It’s someone with credibility on the line saying: this person built something real and it met a standard.
That is what gets you past the interview.
The Timeline
Most people who study consistently and work through these projects reach an employable level in 4-6 months. The certifications take 2-3 months of focused study each if you are working full-time. The projects take 1-2 months on top of that.
That is not a shortcut. But it is a defined path — which is more than most entry-level tech careers offer.
What to Do Next
Start with AWS Solutions Architect Associate. Work through the official study materials, use practice exams, and schedule the exam when you are consistently scoring above 80% on practice tests.
Once you have passed, build one of the projects above. Not after you have all four certifications. After the first one.
Then repeat.
Related posts: