Frontend Engineer
My main roleBuilding web interfaces that stay fast, accessible and maintainable as products grow
10 stages, 51 topics, ~34 weeks
TypeScript
React
Next.js
TanStack Query
Learning maps for each role on a software team, drawn from my own journey: frontend is what I do every day, the other roles are what I learned working next to teammates and digging in on my own.
Each bar is a role and each segment is a stage. Longer segments take more time.
Building web interfaces that stay fast, accessible and maintainable as products grow
10 stages, 51 topics, ~34 weeks
Designs, builds and runs the APIs, data and services behind every product
10 stages, 52 topics, ~37 weeks
Build iOS and Android apps that feel smooth, work offline and ship safely
10 stages, 50 topics, ~34 weeks
Find risk before users do and turn quality into something the team can measure
10 stages, 50 topics, ~36 weeks
Builds infrastructure, pipelines and platforms so teams ship fast, safely and reliably
10 stages, 56 topics, ~42 weeks
Build products on top of LLMs: APIs, RAG, agents, evals and running it all in production
10 stages, 58 topics, ~31 weeks
Each role opens with what I wish I had known earlier. Use it to decide where to spend your effort.
Each stage builds on the one before. Skip ahead if you must, and come back when you get stuck.
Each stage ends with a project that has clear acceptance criteria. Finish it before moving on.