Career Paths
Growth maps from beginner to senior to top-tier across engineering disciplines — gathered in one place for easy comparison
A collection of career growth paths across engineering disciplines. Each path is a map: a staged capability model, learning route, per-stage artifacts, and common pitfalls — from entry-level to senior to top-tier.
They live together so you can compare across them — you'll notice the disciplines are remarkably aligned on the arc ("junior = delivery, mid = end-to-end ownership, senior = systems and influence, top-tier = defining the field"); only the specific stack to master at each stage differs.
Client & Full-Stack
Front-End Engineer
From building pages to owning experience, performance, and architecture — to defining platforms
Mobile Engineer
Delivering native experiences under harsh device constraints, owning performance, stability, and release
Full-Stack Engineer
Owning end-to-end slices, growing convincing depth on top of breadth
Backend & Platform
Back-End Engineer
Services, data, distributed systems — staying correct and reliable under scale, concurrency, and failure
DevOps Engineer
Automation, observability, reliability engineering, and collaboration culture (incl. SRE / platform)
Developer Experience Engineer
Treating internal tools as products, with developers as your users
Data & AI
Data Engineer
Data pipelines, warehouses, and trustworthy data assets — the foundation for all analytics and AI
Machine Learning Engineer (ML / MLOps)
Owning a model's full lifecycle from data to production: training, deployment, monitoring, iteration
AI Engineer
Building AI products on existing/fine-tuned models: six pillars, eval discipline, shipping engineering
Security & Quality
Security Engineer
Guarding the trust boundary with adversarial thinking (authorized, defensive, responsible)
QA / Quality Engineer
Building quality into the process through engineering — test strategy, automation, quality systems
Technical Leadership
How to read these paths
- A map, not a checklist: no need to memorize end to end. Locate roughly which level you're at, then look at what the next level is missing.
- Time is only a reference: what sets promotion speed is feedback density — whether what you build has real users, real traffic, real failures, and whether you do retrospectives.
- Overall water line, not a single point: each path measures your level by a set of "capability pillars" — your overall level, not one standout skill.
- Prove the level with artifacts: every stage lists "artifacts" — things you can show, which are more convincing than a title on a résumé.