The skills frontend engineers use on the job, from HTML and CSS fundamentals through JavaScript, TypeScript, component frameworks, state, accessibility, performance, and AI-assisted development. Start at the top and work down, basics first. Free to read, no signup required.
How to use this: tap a step on the map to open its details, skill pills, and guidance in a side panel. Where a step has more than one valid option, they hang off it as a small connected group. Work down the spine in order; each stage assumes the ones above it. You don’t need to master every topic before moving on. Aim for working competence, build interfaces as you go, and deepen the harder topics when a real project or role calls for them.
Where code lives
GitHub
GitLab
Bitbucket
Pick one, deeply
React
Vue
Svelte
Angular
Approaches
CSS Modules
Tailwind CSS
CSS-in-JS
Static hosting
Vercel
Netlify
Cloudflare Pages
AI coding tools
GitHub Copilot
Cursor
Claude Code
GitHubGitLabBitbucket
ReactVueSvelteAngular
CSS ModulesTailwind CSSCSS-in-JS
VercelNetlifyCloudflare Pages
GitHub CopilotCursorClaude Code
Build real interfaces: that’s what makes it stick
Frontend is learned in the browser, not on paper. Every topic above only becomes real once you’ve used it to build something people can click. Deployed, polished projects are also what frontend portfolios and interviews are built on.
Rebuild a UI you admire pixel-for-pixel. It forces real CSS layout, responsiveness, and attention to detail.
A small app that fetches from a public API with proper loading, error, and empty states.
An accessible, keyboard-navigable component library (modal, tabs, combobox), which is the hard part of real UI work.
A dashboard with real data, charts, filtering, and a light/dark theme built from design tokens.
Deploy it publicly, put it on GitHub with a real README, and run it through an accessibility and performance check. One polished, deployed interface you can talk through beats ten half-finished tutorials.
Frequently asked questions
There’s no fixed number. Consistent practice and real projects matter most. From zero to job-ready is commonly several months to a couple of years; if you already program, focused frontend study can get you interview-ready faster. Building and shipping real interfaces is what makes the difference, not the length of a course.
Learn one modern component framework deeply. React, Vue, Svelte, and Angular are all employable. React has the largest job market in many regions, but the component model and state concepts transfer across all of them, so the deeper skill is the model, not the brand.
Very. Frameworks and styling libraries sit on top of CSS, so when a layout breaks or something looks off, you debug it in CSS. Strong fundamentals here set you apart, because a lot of developers skip them and it shows.
No. Frontend is one of the most portfolio-driven fields, so a set of polished, deployed projects and solid fundamentals is what interviews test. A degree helps with some hiring filters and CS fundamentals, but plenty of frontend engineers are self-taught or came through bootcamps.
Not to start. You do need to comfortably consume APIs and understand how the client talks to a server. Picking up some backend later widens your options (and leads toward full-stack roles), but you can go deep on frontend without becoming a backend engineer.
No. HTML/CSS, JavaScript, a framework, and API handling are the non-negotiable core. Performance, advanced testing, and build tooling you deepen as real roles demand them. Nobody is equally strong across all of it, and senior engineers still look things up.
Get a personalized plan for real interviews
This page covers what to learn. When you’re ready to get hired, Interview Ready turns it into a personalized 30-day plan built around your resume and a specific target role: real practice in the right order (DSA, UI and system design, behavioural), a guided Build-a-Project track alongside it, and progress tracking the whole way. Start free.
