Skip to content
FrontDepth, Home

Back to the topic

Practice: Approaching a frontend system design interview

Answer first, then compare. Rate yourself honestly — it drives your weak-areas list.

0 predict-output · 6 open

Questions up to level

Shows questions up to the selected level.

No practice questions for this level yet.

  1. Open questionMiddle

    Design an autocomplete. What do you ask first, and what do you write down before drawing anything?

    Think it through first

    Answer out loud or in your head as if you were in an interview, then reveal.

  2. Open questionMiddle

    How does a frontend system design round differ from a backend one, and how do you use the 45 to 60 minutes?

    Think it through first

    Answer out loud or in your head as if you were in an interview, then reveal.

  3. Open questionMiddle

    Design the client data model for a chat app: the entities, client vs server state, normalization and cache keys.

    Think it through first

    Answer out loud or in your head as if you were in an interview, then reveal.

  4. Open questionSenior

    Polling, Server-Sent Events or WebSocket: how do you choose for an analytics dashboard, a news feed and a chat app?

    Think it through first

    Answer out loud or in your head as if you were in an interview, then reveal.

  5. Open questionSenior

    Design an infinite feed: how do you paginate, render thousands of items and keep the page fast?

    Think it through first

    Answer out loud or in your head as if you were in an interview, then reveal.

  6. Open questionSenior

    How do you state and defend trade-offs in a design round, and what makes an answer senior rather than middle?

    Think it through first

    Answer out loud or in your head as if you were in an interview, then reveal.