Design a search results experience
mediumComplete guide with examples and interview questions · 45 min
Say it out loud in an interview — clear, simple, no textbook wording.
If someone asks me to design a search results experience, I would say it is a page where the URL holds the query, the filters, the sort, and the page, and the list below it shows what matches. The search box finds things. The results page is where the user judges whether the finding worked.
Interviewers care because search combines state management with user trust. Filters, sorting, pagination, and the back button all share one state, and if any of them disagrees with the URL, the page feels broken even when the results are right.
The senior nuance is that the URL is the state. Component state that cannot be shared, bookmarked, or restored with the back button is a bug in a search experience, not an implementation detail.
Key takeaways
- •Search is a URL first: the query, filters, and page belong in the address bar
- •Facets are filters with counts, and counts must stay honest as filters combine
- •Sorting and filtering are server questions, but the UI owns their combined state
- •Empty results need guidance, not a blank page
- •A results page must stay usable while the next page is loading
Track your mastery
Sign in to save Q&A scores, coding challenge progress, points, and streaks across devices.
Sign in to save progress