roadmap
- 01
- 02
- 03
- 04
- 05
- 06
- 07
- 08
Prepare for Angular Material interviews, from building a theme and overriding its tokens to form fields, dialogs and tables. Covers the CDK's overlays, drag and drop, focus utilities and harnesses.
119 of 119 questions in your plan: 0 known, 0 in progress, 0 due, 0 skipped, 119 new. 0 cut, outside your plan.
Angular Material rarely gets a round of its own. It comes up inside the Angular part of a frontend loop, often as a code review of a screen built with it, or in a take-home that the reviewer reads with the kit's conventions in mind. The opening questions are about wiring: why a `mat-select` inside a `mat-form-field` shows no error until the user has touched it, how a dialog receives its input through `MAT_DIALOG_DATA` and hands a result back through `afterClosed()`, why sorting stops working once the table's data source is recreated rather than updated. Later questions move from use to diagnosis. A restyle that reached into a component's internal classes with `::ng-deep` disappears after an upgrade, and the interviewer wants the supported route: the system variables and the component's overrides mixin. A date picked in the browser arrives at the server a day early, and the answer lies in the date adapter and the time zone a native `Date` carries. A menu clipped by a scrolling container leads to how the CDK overlay renders outside the component's own element. From senior level up, candidates are also asked to choose a layer: when a finished Material component fits, and when a team that owns its design should build on the CDK or on Angular Aria's headless directives and still inherit their keyboard and focus behaviour.
Theming opens the plan because every component reads its colors, type and density from the theme. [Sass](/topics/fe-sass) comes first, since a theme is written with `@use` and a mixin call, then the [strategy behind light, dark and dense modes](/topics/found-design-systems-theming), then [setting up a Material theme](/topics/fe-angular-material-theming) itself. Customizing styles follows directly: [token tiers](/topics/found-design-systems-tokens-tiers) explain why a system variable is the right place to change a color, and [view encapsulation](/topics/fe-angular-components-templates-styling) explains why a component's own styles cannot reach Material's internals without `::ng-deep`, before the plan reaches [the supported overrides](/topics/fe-angular-material-style-overrides). The middle of the plan is the components teams use daily. Form controls start from [custom value accessors](/topics/fe-angular-forms-cva), because putting your own control inside a [form field](/topics/fe-angular-material-form-fields) builds on that contract, and [datepickers](/topics/fe-angular-material-date-pickers) add the adapter question. [Dialogs and snack bars](/topics/fe-angular-material-dialogs) come before the [CDK overlay and portals](/topics/fe-angular-material-overlays) they are built on: you meet the component first, then the mechanism that positions it. Tables and lists continue the same way, from [sorting and paging a table](/topics/fe-angular-material-tables) to [virtual scrolling](/topics/fe-angular-material-virtual-scroll) for long lists and [drag and drop](/topics/fe-angular-material-drag-drop) for reordering them. The last stretch treats the CDK as a toolkit for widgets Material does not ship. [ARIA roles and states](/topics/found-accessibility-aria) and [keyboard operability](/topics/found-accessibility-keyboard-nav) come before the CDK's [focus traps and key managers](/topics/fe-angular-material-a11y), which put both into practice. [Headless patterns](/topics/found-component-library-composition) then frame [Angular Aria and the unstyled CDK widgets](/topics/fe-angular-material-headless). Testing closes the plan: the [harness API](/topics/fe-angular-testing-harnesses) belongs to the CDK, and [Material's own harnesses](/topics/fe-angular-material-harnesses) are built on it, so the second reads best after the first.
Application developers, who use the kit rather than extend it, get most of their questions from the opening five modules, from theming through tables. For them, raising importance to must know and narrowing level to the range of the job is a reasonable first pass. Engineers who maintain an in-house component library on top of the CDK should switch study order to by topics and give the last three modules the most time, because their interviews turn to focus management, key managers and writing a harness for a new component. Coming from React and Material UI, expect the same Material Design ideas behind a different API: the theme is a Sass mixin rather than a provider, and styles are scoped by Angular's view encapsulation. This roadmap assumes you already know Angular. Components, signals, dependency injection, routing, forms beyond the value-accessor contract and `TestBed` itself belong to the [Angular roadmap](/roadmaps/angular), which carries this kit as one of its modules. For tokens and theming as a practice that outlives any one library, the [Design Systems roadmap](/roadmaps/design-system) goes further.
Angular Material rarely gets a round of its own. It comes up inside the Angular part of a frontend loop, often as a code review of a screen built with it, or in a take-home that the reviewer reads with the kit's conventions in mind. The opening questions are about wiring: why a mat-select inside a mat-form-field shows no error until the user has touched it, how a dialog receives its input through MAT_DIALOG_DATA and hands a result back through afterClosed(), why sorting stops working once the table's data source is recreated rather than updated.
Later questions move from use to diagnosis. A restyle that reached into a component's internal classes with ::ng-deep disappears after an upgrade, and the interviewer wants the supported route: the system variables and the component's overrides mixin. A date picked in the browser arrives at the server a day early, and the answer lies in the date adapter and the time zone a native Date carries. A menu clipped by a scrolling container leads to how the CDK overlay renders outside the component's own element. From senior level up, candidates are also asked to choose a layer: when a finished Material component fits, and when a team that owns its design should build on the CDK or on Angular Aria's headless directives and still inherit their keyboard and focus behaviour.
Theming opens the plan because every component reads its colors, type and density from the theme. Sass comes first, since a theme is written with @use and a mixin call, then the strategy behind light, dark and dense modes, then setting up a Material theme itself. Customizing styles follows directly: token tiers explain why a system variable is the right place to change a color, and view encapsulation explains why a component's own styles cannot reach Material's internals without ::ng-deep, before the plan reaches the supported overrides.
The middle of the plan is the components teams use daily. Form controls start from custom value accessors, because putting your own control inside a form field builds on that contract, and datepickers add the adapter question. Dialogs and snack bars come before the CDK overlay and portals they are built on: you meet the component first, then the mechanism that positions it. Tables and lists continue the same way, from sorting and paging a table to virtual scrolling for long lists and drag and drop for reordering them.
The last stretch treats the CDK as a toolkit for widgets Material does not ship. ARIA roles and states and keyboard operability come before the CDK's focus traps and key managers, which put both into practice. Headless patterns then frame Angular Aria and the unstyled CDK widgets. Testing closes the plan: the harness API belongs to the CDK, and Material's own harnesses are built on it, so the second reads best after the first.
Application developers, who use the kit rather than extend it, get most of their questions from the opening five modules, from theming through tables. For them, raising importance to must know and narrowing level to the range of the job is a reasonable first pass. Engineers who maintain an in-house component library on top of the CDK should switch study order to by topics and give the last three modules the most time, because their interviews turn to focus management, key managers and writing a harness for a new component. Coming from React and Material UI, expect the same Material Design ideas behind a different API: the theme is a Sass mixin rather than a provider, and styles are scoped by Angular's view encapsulation.
This roadmap assumes you already know Angular. Components, signals, dependency injection, routing, forms beyond the value-accessor contract and TestBed itself belong to the Angular roadmap, which carries this kit as one of its modules. For tokens and theming as a practice that outlives any one library, the Design Systems roadmap goes further.