CloudWebSchool
Cloud Career Path Builder
Answer 10 questions about your background, experience, and interests. The tool scores five cloud career paths using a deterministic rules engine and generates a practical 30/90/180-day plan with relevant reading links. No AI. No data stored.
How the Cloud Career Path Builder works
The builder asks 10 questions covering your background, experience level, primary interest, coding and Linux confidence, on-call appetite, cloud preference, study time, certification plans, and portfolio status.
Eight of the ten questions carry scoring weights for five career paths: Cloud Engineer, DevOps Engineer, SRE, Cloud Security Engineer, and Cloud Data Engineer. The two non-scoring questions (cloud preference and weekly study time) are used purely to select relevant links and recommend an appropriate time-based roadmap.
Scores are summed across all questions, normalised against each path's maximum achievable score, and ranked. The top three paths are shown with score bars. If the top two paths are within 15% of the highest score, the result is flagged as ambiguous and both are shown as equally valid starting points.
Immediate path vs long-term direction
Some paths — particularly SRE and Cloud Security — are realistic targets for experienced engineers but are very hard to enter directly from zero. If your answers suggest you want one of those roles but your experience level indicates you are early in your career, the tool will show two things separately:
- Best immediate path: a realistic starting role you can target now (typically Cloud Engineer or DevOps Engineer), with a concrete 30/90/180-day plan.
- Long-term specialist direction: the advanced role you are building toward, with a note on when and how to make that transition.
This two-phase framing reflects the reality of the job market: SRE and Cloud Security roles at most companies explicitly require 2–4 years of prior cloud or platform experience. The stepping-stone recommendation is practical, not discouraging.
Why browser-only, no data storage
Career questions touch on background, experience, and ambitions — information that is genuinely personal. CloudWebSchool has no interest in collecting it, profiling you, or using it for any purpose beyond generating your result. All computation happens in your browser using a self-contained JavaScript file. Nothing is sent anywhere. The moment you close the tab, the data is gone.
Three example profiles
Example 1 — IT support engineer moving into cloud
Background: IT support/sysadmin. Experience: beginner (completed some tutorials). Interest: infrastructure. Coding: low. Linux: medium. On-call: open to it. Cloud: AWS. Study time: 6–10 hours. Certs: yes soon. Portfolio: none.
Expected result: Cloud Engineer as the primary path. The IT support background maps directly to cloud engineering, and the interest in infrastructure reinforces it. The 30-day plan focuses on AWS free tier, Linux basics, and deploying a first VM. The cert recommendation points to the AWS Solutions Architect Associate guide. Reality check: Terraform appears in most cloud engineer job descriptions — prioritise it early.
Example 2 — Software engineer pivoting to DevOps
Background: software engineer. Experience: some hands-on. Interest: automating deployments and CI/CD. Coding: high. Linux: medium. On-call: open to it. Cloud: no preference. Study time: 11–15 hours. Certs: not a priority. Portfolio: 1 project.
Expected result: DevOps Engineer as the primary path. The software engineering background and high coding confidence are strong signals. The specific interest in automation and CI/CD aligns precisely with DevOps work. The 6-month roadmap is recommended given the study hours. The project recommendation points to the CI/CD pipeline build guide. Reality check: Projects are the primary interview signal in DevOps — prioritise working pipelines over certification.
Example 3 — Data analyst moving into data engineering
Background: data analyst. Experience: some hands-on (used cloud in a role). Interest: data pipelines and infrastructure. Coding: medium. Linux: low. On-call: not interested. Cloud: GCP. Study time: 6–10 hours. Certs: maybe later. Portfolio: none.
Expected result: Cloud Data Engineer as the clear primary path. The data analytics background plus a strong interest in data infrastructure produces a decisive score. The cert recommendation points to the GCP Associate Cloud Engineer guide as the foundation before a data-specialist cert. The project recommendation links to the data pipeline build guide. Reality check: Strong SQL is non-negotiable — fix any weaknesses there first.
Frequently asked questions
Is this an AI career coach?
No. The tool uses a deterministic rules engine: each answer carries fixed scoring weights for each of the five career paths. The same answers always produce the same result. There is no AI, no machine learning, and no external service involved. Every scoring decision in the engine is documented and explainable.
Does this tool store my answers?
No. Answers and results exist only in your browser's memory during the current session. Nothing is written to local storage, session storage, cookies, or any database. Closing or refreshing the tab discards everything permanently.
Can this tool tell me whether to choose Cloud Engineering vs DevOps vs SRE?
It can give you a well-reasoned starting point. The interest question (question 3) carries the most weight by design — if your stated interest is specific and honest, the recommendation is usually clear. Where scores are close, the tool flags ambiguity and shows both paths. Use the result as a starting hypothesis to test against real job descriptions and conversations with people already in those roles.
Why might SRE not be the right first role?
SRE roles at most companies — particularly those with a formal SRE practice — expect candidates to have 2–4 years of prior cloud or platform engineering experience. You need to know how to provision infrastructure, manage Kubernetes, debug production systems under pressure, and interpret observability data before most SRE teams will interview you seriously. The stepping-stone recommendation is not discouraging — it is the fastest path to the role you want.
Should I get certifications before building projects?
Not as a rule. For most cloud roles, a working project demonstrates more practical ability than a certification alone. A reasonable approach: start certification study to give your learning structure, but build projects in parallel rather than waiting to pass before touching real infrastructure. The two activities reinforce each other. That said, certifications matter more in some roles (Cloud Security, compliance-heavy environments) than in others (DevOps, data engineering).
How accurate is the recommendation?
The tool is directionally useful, not definitive. It uses 10 questions and fixed weights to approximate a much more nuanced decision. The results are most reliable when your interest answer is specific and honest — that question carries the most influence. Treat the output as an informed starting point, not a binding verdict. Read the reasoning in the results panel carefully, and cross-reference with real job descriptions before making career decisions.