Interview questions and answers

596 questions across 11 technologies - HTML, CSS, JavaScript, TypeScript, React, Angular, RxJS and NgRx. Every answer is short, uses plain words and comes with a code example where it helps.

Download for Windows - Read interview guides

Pick a technology

Study path by role

Fresher or junior web developer

Campus and junior rounds mostly test the basics: semantic tags and forms, the box model and Flexbox, then scope, closures and the event loop in JavaScript.

1. HTML - 2. CSS - 3. JavaScript

React developer

React questions build on JavaScript, so read closures, this and the event loop first. Then TypeScript, then React hooks, rendering and state.

1. JavaScript - 2. TypeScript - 3. React - 4. CSS

Angular developer

Angular rounds lean on TypeScript and RxJS as much as on Angular itself. Read change detection and dependency injection, then the RxJS operators, then NgRx if the job lists it.

1. TypeScript - 2. Angular - 3. RxJS - 4. NgRx

Java backend developer

Service and product companies ask core Java, OOP and collections first (HashMap internals almost always), then Java 8 streams and threads, then SQL joins and indexes. Experienced rounds add Spring Boot.

1. Java - 2. SQL

Python, data or analyst role

Expect Python data types, mutability and a short coding problem, then SQL: joins, GROUP BY with HAVING, and a window-function question such as top N per group or a running total.

1. Python - 2. SQL

Experienced frontend engineer

Senior rounds go deeper into performance and design choices: rendering and performance in React, change detection in Angular, the event loop, and CSS architecture.

1. JavaScript - 2. React - 3. Angular - 4. CSS

What each topic covers

HTML interview questions

CSS interview questions

JavaScript interview questions

TypeScript interview questions

React interview questions

Angular interview questions

RxJS interview questions

NgRx interview questions

SQL interview questions

Java interview questions

Python interview questions

How to use this hub

Read the section, not the whole page

Each topic is split into sections. Before an interview, read the two or three sections the role actually needs - change detection for Angular, hooks for React, the event loop for JavaScript.

Say the answer out loud

These answers are written the length a spoken answer should be: two or three sentences, then an example. Practise saying them, not reading them.

Follow the example

Where a question has code, type it into a sandbox and break it on purpose. You remember what you debug far longer than what you read.