roadmap
- 01
- 02
- 03
- 04
- 05
- 06
- 07
- 08
Go into frontend interviews able to explain CSS, not just use it. Covers the cascade and specificity, the box model, flexbox and grid, responsive design, web fonts, stylesheet tooling, and what each style costs the renderer.
291 of 291 questions in your plan: 0 known, 0 in progress, 0 due, 0 skipped, 291 new. 0 cut, outside your plan.
Few interviews give CSS a round to itself. In frontend loops it usually comes up in two places: the fundamentals conversation, beside JavaScript and the browser, and a UI coding round where you build a layout from a mockup, often in plain HTML and CSS. Design-system roles add a conversation about keeping a component library's styles maintainable.
Most of the technical questions hand you a symptom and wait for the reason. A modal with z-index: 9999 still renders under the header, because an ancestor with a transform opened a stacking context the modal cannot leave. A flex item holding a long URL pushes past its container instead of shrinking, because its automatic minimum size is its content. A child's height: 50% does nothing, because the parent's height is not definite. A new utility class loses to an old rule with an ID in its selector, a collision that cascade layers were added to prevent.
Seniority shows in the word because. Naming the property that fixes the bug is enough early on; past the junior band, the follow-up asks for the rule that caused it. Senior conversations add cost: why animating transform stays smooth where animating top stutters, why reading offsetHeight right after changing a class forces a synchronous layout, why a late web font moves text the reader is already reading.
Most questions about a page's styles lean on two earlier ones, which declaration wins and how big a box is, so the language module opens on selectors and specificity and the box model. Flexbox and grid follow because each lets a container replace normal flow for its children, bending sizing rules the box model set. Responsive design and custom properties then make those layouts adapt and change at runtime, positioning and stacking takes boxes out of flow and decides what paints on top, and the module closes on architecture: what happens to all of it when many people write it.
The tooling stretch answers problems architecture raises. Sass gave stylesheets variables and nesting years before the language had its own, which makes the gap between a Sass variable, fixed at build time, and a custom property, resolved per element in the cascade, a standard follow-up. PostCSS and CSS Modules also work at build time, one rewriting syntax through plugins, the other rewriting class names so they stay local.
Type & Color turns from boxes to what fills them. Font loading and subsetting decide what shows while a web font is still downloading and whether the swap shifts the line; contrast asks whether the text can be read at all.
The last module reads the first again as a bill. The critical rendering path explains why a stylesheet holds back the first paint, reflow and compositing sort earlier properties by the pipeline stage a change to them reruns, and animation strategy prices the motion introduced in the first module per frame.
A frontend or full-stack interview a few weeks away is decided mostly in the first module, so spend the hours there: lift importance to must know, close the level range around the seniority the job advertises, and visit the tooling stretch only if the job description mentions one of its tools. The coding round usually starts from an empty editor, so rebuild a few layouts by hand as you go, such as a sticky header, a card grid that reflows with no media query and a modal over a scrolled page. If you style through a utility framework, the class names will be familiar and the rules behind them less so; the box model and stacking repay that gap first. Senior and design-system candidates are better served by putting study order on by topics and reading through to the last module, where architecture and rendering cost settle those conversations. The plan styles markup it does not teach: document structure, semantics and forms belong to the [HTML roadmap](/roadmaps/html). The JavaScript, frameworks and browser APIs around the styles are in the [Frontend Developer roadmap](/roadmaps/frontend), which places CSS among everything else a frontend loop asks.
A frontend or full-stack interview a few weeks away is decided mostly in the first module, so spend the hours there: lift importance to must know, close the level range around the seniority the job advertises, and visit the tooling stretch only if the job description mentions one of its tools. The coding round usually starts from an empty editor, so rebuild a few layouts by hand as you go, such as a sticky header, a card grid that reflows with no media query and a modal over a scrolled page.
If you style through a utility framework, the class names will be familiar and the rules behind them less so; the box model and stacking repay that gap first. Senior and design-system candidates are better served by putting study order on by topics and reading through to the last module, where architecture and rendering cost settle those conversations.
The plan styles markup it does not teach: document structure, semantics and forms belong to the HTML roadmap. The JavaScript, frameworks and browser APIs around the styles are in the Frontend Developer roadmap, which places CSS among everything else a frontend loop asks.