On this page
The whole pillar stands on this
Who this is for
You keep being told to "showcase your projects", but you don't have projects worth showing, or you have ten half-finished tutorial clones and don't know if they count. Start here.
With no job history, projects are your experience, they're what your resume, your interview stories, and your GitHub all point to. But not all projects carry weight. A followed-along tutorial proves you can follow instructions. A project where you made decisions, hit problems, and fixed them proves you can do the job.
The goal isn't a big pile of repos. It's two or three projects you can talk about for ten minutes each, because you genuinely built them.
Tutorial clone vs. interview-worthy project
| Tutorial clone | Interview-worthy project |
|---|---|
| Followed step-by-step to a known end | You set the goal and figured out the path |
| Worked first try (because it was scripted) | Broke, and you debugged it, and can tell that story |
| Default everything | You made choices and can explain the trade-offs |
| Lives only on your laptop | Deployed, documented, reproducible by someone else |
| "I built a to-do app" | "I deployed a multi-tier app on AWS with IaC and a CI pipeline" |
Pro tip
You can START from a tutorial and turn it into a real project: change the stack, add a feature it didn't have, deploy it properly, write the README, and break-then-fix something. The moment you go off the rails and have to solve your own problem, it becomes yours.
What to build for a cloud / DevOps junior role
You don't need ten projects. You need a small set that, together, shows the core of the job. A strong starting trio:
- 1
1. A deployed, multi-tier app on real cloud
An app behind a load balancer, a managed database, sensible networking. Proves you can ship something that actually runs on AWS/Azure/GCP, not just locally.
- 2
2. The same infrastructure as code
Rebuild that environment with Terraform (or similar) so it's reproducible. This is the signal that separates "clicked around the console" from "engineer."
- 3
3. A CI/CD pipeline
Automate test + deploy on every push (GitHub Actions is fine). Shows you understand how code gets to production safely.
Pro tip
Bonus depth that punches above its weight: add basic monitoring/alerting, or write a short post-mortem of something that broke. Both show maturity most juniors don't demonstrate.
Depth beats breadth. One project taken all the way, deployed, IaC, CI, documented, with a real failure story, is worth more than five shallow ones. If you want a guided, portfolio-grade build to anchor this, the capstone projects are designed for exactly that.
Document it like it matters (because it's read)
An undocumented project is nearly invisible to a recruiter or engineer skimming your GitHub. The README is often read more than the code. Make each project legible in 30 seconds.
- What it does, one or two sentences, plainly.
- The stack, the tools, so the keywords are visible.
- An architecture sketch, even a simple diagram shows you think in systems.
- How to run it, proof it's reproducible, not a screenshot of a one-time success.
- What you learned / what broke, the line that turns a repo into a story.
Key takeaways
- With no job history, projects ARE your experience, choose them deliberately.
- Interview-worthy = your decisions, a real failure you fixed, deployed + documented.
- A tutorial becomes yours the moment you go off-script to solve your own problem.
- Cloud/DevOps starter trio: deployed app → infra as code → CI/CD pipeline.
- Depth over breadth, and document every project so it's actually seen.
Reading is step one. Now do it for real.
Rehearse this with the platform's live tools, the first time you say it out loud shouldn't be the time that counts.
Keep reading
This is general, educational career guidance, not legal, financial, immigration, or professional advice. Examples are illustrative and simplified. Norms vary widely by country, company, role, and over time, so always verify what applies to your own situation. Nothing here guarantees an interview, an offer, or any particular outcome.