Five questions, sampled across categories and difficulty. Click reroll for a new set. Simulates the surface area of a typical 60-minute round.
5 questions selected
Don't start coding — reduce ambiguity first: ask clarifying questions, restate your understanding back, identify the user problem behind the feature request, and surface assumptions explicitly. Then de-risk with a quick prototype/wireframe to get concrete feedback, and ship iteratively so reality corrects the spec. Show you're comfortable driving clarity, not waiting for it.
A higher-order function takes a function as an argument, returns a function, or both. Examples: map/filter/reduce, setTimeout, event listeners, and function factories. They're the basis of composition, currying, and decorators in JS.
How would you build a scalable chat UI for an LLM-powered product
Yes — frame it around when and why: Zustand for lightweight global client state with selector-based subscriptions and minimal boilerplate; Redux Toolkit for large apps needing structure/middleware/devtools; Jotai for atomic state; and React Query for server state (a different problem).
Frontend system design: Performance, SSR, and SEO