KloudSkool Project Review
Find out whether your KloudSkool project meets the standard, before you put it in front of an employer.
Every project in KloudSkool comes with a brief and acceptance criteria. Building it is one thing. Knowing whether you've built it well is another.
A Project Review is a detailed, written assessment of a project you've completed in KloudSkool, checked against that project's brief and the standards a real engineering team would expect. You get a clear picture of what's strong, what's missing and exactly what to fix first.
Which projects can be reviewed
- The end-to-end projects within the KloudSkool modules
- The KloudSkool capstone project
Reviews are only available for KloudSkool projects. We don't review other courses' projects, personal side projects or work projects.
What you submit
A link to your GitHub repository for the project
Your Terraform or other infrastructure-as-code
Your architecture diagram
A short write-up of the decisions you made and anything you changed from the brief
A written review report
The report covers:
- Brief and acceptance criteria: which requirements you've met, partly met or missed.
- Architecture: whether your design fits what the brief asks for, and where it could be simpler or stronger.
- Security: exposed secrets, open network rules, over-permissive access and other issues an interviewer would spot.
- Infrastructure as code: structure, reusability, state handling, naming and variables.
- CI/CD: whether your pipeline is safe, repeatable and doing what a real team would expect.
- Networking: segmentation, access paths and anything that's open when it shouldn't be.
- Repository and documentation: README quality, structure, and whether someone else could understand and deploy it.
- Cost and operations: obvious waste, missing monitoring and logging.
Plus:
- A score against the KloudSkool review rubric: so you can see where you stand in each area.
- A prioritised fix list: the three to five changes that would improve the project most, in order.
- Interview prep notes: the questions an interviewer is likely to ask about this project, so you can prepare your answers before it goes on your CV.
- One re-check: fix the priority items within 30 days and we'll confirm whether they've been addressed.
- Turnaround
- Within 5 working days of a complete submission.
- Reviewed by
- Faisal or an approved KloudSkool reviewer, working to the same rubric.
What you won't get
- No reviews of projects from outside KloudSkool. Only KloudSkool module projects and the capstone.
- We won't fix your code or build anything for you. You get the findings and the direction; the work is yours.
- No live call. The review is written so you can come back to it. If you want to talk it through, book a 1:1 separately.
- No debugging of your environment. If something isn't deploying, ask in support; a review is for finished work.
- No unlimited back-and-forth. The review includes one re-check of the priority fixes.
- No access to your Azure subscription or accounts. Never send passwords, keys or credentials. We review your code and diagrams only.
- It's not a certification and not a job guarantee. It tells you how your project measures up and how to make it stronger.
Before you buy
- You need access to the KloudSkool module the project belongs to.
- Your repository must be public, or shared with our reviewer account.
- The project should be finished. If it doesn't deploy yet, use support first and submit for review once it does.
- If something's missing from your submission, we'll ask for it before the review starts. The 5-day clock starts once it's complete.
- Refunds are available up until your review starts.
KloudSkool Project Review
per project
- Written review report across eight areas
- Rubric score, prioritised fix list and interview prep notes
- One re-check of the priority fixes within 30 days
- Within 5 working days of a complete submission
Refunds are available up until your review starts. Prices are valid at the time of publication and may change without notice.