Paged results or endless scroll for job search listings: making the call

You own the search results page of a job board. How would you decide whether results should be split into numbered pages or keep loading as the job seeker scrolls? ```hint Match the pattern to the search behavior Think about how job seekers actually move through results: do they skim once, or open a job, go back, compare and return later? Ask which pattern supports that behavior on each device, and who else is affected by the choice. ``` ### Clarifying Questions - Which surfaces are in question: the mobile app, mobile web, desktop web, or all of them? - Does opening a job take the seeker to a separate page, or show the details next to the list? - Do sponsored job listings appear among the results, and is their placement part of the decision? - Do search engines index the results pages, so that they bring in new job seekers? ### What a Strong Answer Covers - The goal of the results page for job seekers and employers, and the metric that captures it. - How seekers browse (skimming, comparing, returning to results) and how each pattern helps or hurts that behavior on each device. - Effects beyond the seeker: sponsored listing revenue, applicant quality for employers, search engine crawling, accessibility and page performance. - An experiment that reads the right outcome and is not fooled by inflated job views. - A recommendation, possibly a hybrid or a different answer per surface, with the conditions that would change it. ### Follow-up Questions - Infinite scroll raises job views sharply but applications stay flat. What do you conclude? - After the change, employers report more applicants who do not match their requirements. How would you investigate and respond? - How would your answer change for a seeker who saved a search and returns every day to see new postings?