In this chapter
We'll tour the main career paths in IT — frontend, backend, full-stack, data, DevOps, cloud, cybersecurity and AI/ML — what each one does every day, which Acts of this course it builds on, and where to go next, explained as the specialties doctors choose after general training.
The Problem in Real Life
Anna admits it: "I liked almost everything. Building the API was fun. Debugging Sale Day was the most exciting hour of my life. The security week scared me and I loved it."
John laughs. "That's normal after a foundation year. You've seen all of it. Now let's look at what each path actually feels like on a Tuesday afternoon — not on its best day."
Pick the problems you want to spend your days on, not the job title that sounds best.
John
"I Want to Work in IT" vs. Knowing Which Kind of Work
Many different jobs
"IT" covers dozens of jobs that feel completely different day to day (Act 01).
Titles hide the work
The same title can mean different work at different companies.
Where to go next
Each path needs different deeper skills — and a different next course.
Career Paths: Frontend, Backend, Full-Stack, Data, DevOps, Cloud, Security and AI/ML
The doctor analogy: every doctor first studies general medicine — the whole body. Only after that do they choose a specialty: heart, children, surgery, emergency. A surgeon still understands the heart; they just spend their days on something else. This course was your general medicine. Now come the specialties.
- Frontend — what users see and touch: building the interface in the browser or app: layout, interactions, accessibility, performance. Daily: components, CSS, state, talking to APIs. Built on Acts 12, 17 (DevTools), 23. You enjoy: visual detail, user experience.
- Backend — the logic and data behind it: APIs, business rules, databases, integrations, performance. Daily: endpoints, SQL, queues, tests, debugging. Built on Acts 07–10, 12–14, 22, 23. Next: the live Relational Databases and Non-Relational Databases courses. You enjoy: logic, data, how systems fit together.
- Full-stack — both, at a smaller depth: common in startups like BlueTicket. Built on almost everything here, including Acts 25 and 27. You enjoy: owning a feature from screen to database.
- Data — making sense of numbers: data analysts answer business questions with SQL and dashboards; data engineers build the pipelines and storage that move data reliably. Built on Acts 03, 09, 13. Next: the database courses and Storage Systems. You enjoy: questions, patterns, accuracy.
- DevOps / SRE / platform — keeping it running: pipelines, infrastructure as code, containers, monitoring, incidents, reliability. Built on Acts 05, 06, 14, 19–21, 26. Next on BizTechLab: Linux Fundamentals, Docker, Networking Fundamentals and Kubernetes (planned). You enjoy: Sale Day mornings, automation, calm under pressure.
- Cloud — designing on cloud providers: choosing and connecting cloud services, cost, security and scale. Built on Acts 11, 14, 20, 22. Often combined with DevOps. You enjoy: architecture, trade-offs.
- Cybersecurity — protecting it: finding and fixing weaknesses, monitoring for attacks, responding to incidents, security reviews. Built on Acts 11, 12, 22 and everything about how systems work. You enjoy: thinking like an attacker, careful detail.
- AI / ML — teaching computers from data: training and using models, building features with AI services, evaluating results. Needs Python, maths and statistics, data skills, and solid engineering to put models into real products. Built on Acts 03, 09, 13, 23. You enjoy: experiments, maths, uncertainty.
- Also: QA / test automation (Act 17), mobile development, engineering management later on (Act 01's roles). Many careers move between paths — your first choice isn't forever.
| Path | A typical Tuesday | Builds on Acts | Core skills to deepen |
|---|---|---|---|
| Frontend | Building a checkout screen, fixing layout bugs | 12, 17, 23 | HTML/CSS, JavaScript/TypeScript, a framework, accessibility |
| Backend | A new API endpoint, a slow query, a queue worker | 07–10, 12–14, 22, 23 | A language deeply, SQL, APIs, testing, design |
| Full-stack | A feature from screen to database | Most of the course | Frontend + backend basics, deployment |
| Data | A sales report, a data pipeline | 03, 09, 13 | SQL, Python, data modelling, BI tools |
| DevOps / SRE | A pipeline change, an alert, an incident review | 05, 06, 14, 19–21, 26 | Linux, networking, Docker, Kubernetes, IaC, monitoring |
| Cloud | Designing a multi-zone setup, cost review | 11, 14, 20, 22 | A cloud provider, networking, IaC, security |
| Cybersecurity | A threat model, a vulnerability fix, log review | 11, 12, 22 | Networking, OS, web security, scripting |
| AI / ML | Training or evaluating a model, an AI feature | 03, 09, 13, 23 | Python, maths and statistics, data, ML tools |
Anna's choice: "Backend, with DevOps on the side. I loved the API and database work, and Sale Day showed me I like the operations part too." John agrees — BlueTicket needs exactly that — and suggests her next step: go deep on databases with the Relational Databases course, then Linux and Docker as they arrive. Samantha writes it on the review form: Backend Engineer (with DevOps).
Key Takeaway
After a foundation year, choose a specialty like a doctor does: frontend (what users see), backend (logic and data), full-stack (both, less deep), data (analysis and pipelines), DevOps/SRE/platform (keeping it running), cloud (designing on providers), cybersecurity (protecting it) and AI/ML (learning from data). Choose by the problems you want to spend your days on; each path builds on different Acts and leads to different next courses — and you can change later.
Why This Matters
Choosing a direction lets you focus your learning, projects and job applications instead of spreading yourself thin. Knowing what each path really involves day to day — not just its title — helps you pick work you'll enjoy, and explain your choice convincingly in interviews.
Backend, with DevOps on the side. John opens a job board and picks three real-looking adverts. "Now let's see what the market thinks a backend engineer is — and how much of it you already know."