Narrowing a result set
There are 11 ways to narrow a result set, and the count beside each option is what you would be left with if you clicked it.
There are 11 ways to narrow a result set. Most work on rows already on screen, so their effect is instant and reversible.
In the filter bar
- Work mode: remote, hybrid or on-site.
- Date posted: how recent. Rows with no date at all are excluded from a window rather than assumed to be fresh, and the control tells you how many that is.
- Pay shown: only rows where the employer stated pay. The count beside it is how many rows it would hide, which matters a great deal outside the US. See why so many listings show no pay.
- Sort: covered in sorting results.
Behind "All filters"
- Experience, Contract and Hours, derived from the posting text.
- Job board: show only results from particular sources.
- Company: narrow to specific employers in the current results.
- Skills: matches rows naming any of the skills you pick, not all of them. Requiring all of them turns three clicks into an empty page.
- Tracked only: just the jobs you have saved. Needs a free account
- Keyword: free text over title, company and location.
Two things worth knowing
- The number beside each option is what you would get if you clicked it. Every count is computed with all your other filters applied but not that one, so it never promises rows a click cannot deliver, and never reads zero next to an option that would work.
- Filter down to nothing and it names the culprit. Instead of an empty page you get the one filter responsible, such as "Pay filter is hiding 41 of 42 results", with a single click to undo it.
Date posted and Remote only go back to the server rather than filtering what you already have. The rows on screen are the strongest matches for your words, so narrowing them locally answers the wrong question: it would show you the recent ones among your best matches, not the best matches among the recent ones.
Where it stops: There is no "last 24 hours" window, and there is no filter for employment type. The first was removed after measuring it: one UK role returned 91 listings in a day against 6,690 in a month, which is a control that mostly returns an empty page. The second was never real, because the underlying field arrives empty from every board. Contract and Hours are the two axes that carry data.
Related
- Sorting resultsFour orders: best match, newest, salary and CV match. Sorting only reorders, it never removes a row.
- When a search returns nothingEither your filters removed everything, in which case the page names the one responsible, or the index holds nothing yet for that query.
- Why so many listings show no payBecause the employer did not state any. We show pay as it was quoted and drop anything we cannot vouch for, rather than guessing.
Did this answer your question?
Still stuck? Ask us directly, and mention this article so we know where to start.