Each path is an ordered reading list for a specific role — ordered "why first, then how," curating existing articles rather than duplicating them. Paths marked Developing have real, useful entries already but aren't complete end-to-end yet.
Start here if you're 0-1 year into a technology career with no prior IT job. This path builds from absolute first principles — the internet, the operating system, version control — before touching anything operational.
For L1/L2 support engineers working ticket queues who want to move from reactively closing tickets to proactively understanding the systems behind them.
For Windows/Linux administrators looking to deepen operational and troubleshooting skill, with a focus on IIS, permissions, deployment safety, and structured incident response.
This path is still in early development — no Sitecore-specific content has been published yet. In the meantime, a few general web-technology and infrastructure guides that Sitecore engineers rely on daily are listed below.
For developers moving into operations, CI/CD, and deployment ownership — from understanding what a pipeline actually automates through to writing safe, idempotent deployment scripts and rolling back when something goes wrong.
A starting set of fundamentals for anyone new to cloud platforms (GCP/Azure). This path is still developing — the core deployment and monitoring basics are here, but broader cloud-fundamentals coverage is still being built out.
This path is still in early development. Leadership- and mentoring-specific content hasn't been written yet, but two existing pieces — on systems thinking and root-cause analysis — are directly relevant to leads today.
You're about to start college for CS/IT. This path sets honest expectations, gets your first environment working, and gives you the mindset that separates students who thrive from those who just get by.
Your first year is about fundamentals and habits, not chasing frameworks. This path builds a real mental model of how programs and the web work, and the single most useful tool you'll use for the next four years: Git.
Second year is where you start to specialise: data structures and algorithms in earnest, your first project that isn't a tutorial clone, and learning how to learn a new technology on your own.
Third year is internship-and-preparation year: finding your first internship, writing a resume when you have 'no experience', doing an internship well, and building a realistic interview-prep plan.
Final year is about landing the first job and finishing strong: surviving placement season, scoping a capstone project that isn't a mess, and understanding what actually changes when you go from student to employee.
A structured path from understanding CAT to targeting a specific business school — exam mechanics, syllabus, scoring, study plans by timeline, and a first IIM profile to aim for.