Build the autocomplete every product needs, the way design system teams do: tested ranking that ignores case and accents, highlighted matches, the full ARIA combobox pattern, and async search with debounce, cancellation, caching, and every state.
What you'll build
An autocomplete that works with a keyboard and a screen reader, never shows stale results, and sends one request per pause.
"Build an autocomplete" is one of the most common frontend interview questions, and one of the most common components in real products: search boxes, address forms, tag pickers, @mentions. It's also one of the most often broken. A list of divs under an input looks right, but it's unusable with a keyboard, silent to screen readers, and full of race conditions.
You'll build a country picker the way a design system team would:
1countries.js sample data
2search.js normalize, rankMatches, highlight (pure, tested)
3api.js a pretend search service with slow and outage switches
4useAutocomplete.js debounce, cancel, cache, status
5Combobox.jsx the accessible combobox
6App.jsx a shipping form that uses itWhat you'll learn: search ranking, Unicode normalization, the combobox pattern from the WAI-ARIA Authoring Practices, aria-activedescendant, live regions, and how a single effect cleanup handles both debouncing and race conditions.