Start with your field. Land on a list you can actually read.

Every field on the board, ordered by how many roles are open in it right now and drawn to scale against the largest bucket on the board, so the spread between the deepest field and the shallowest is visible rather than asserted. Open one to see the roles inside it priced by real counts, then narrow by remote, pay, experience or country — and one sentence under those narrowings says how much of that field states a work mode, a pay figure, an experience level or an employment type at all, from the board's hourly per-field scan, because a filter over a column employers often leave blank hides roles rather than proving they are not there. A field's count is the board's own facet sweep, which runs four times an hour and stamps the page with the time it was taken; everything you open is counted live when you open it and counted again once a reading is a few minutes old. A posting coming down never means someone was hired: a hire, a withdrawal, a cancelled requisition and a retitle look identical to us. The live counts load when the page opens in a browser.

Every field on the board

Operations & Logistics — 140,015 →Healthcare & Clinical — 106,203 →Sales & Partnerships — 79,314 →Hospitality & Retail — 77,355 →Engineering & IT — 70,247 →Finance & Accounting — 34,064 →Customer Success & Support — 30,537 →Marketing & Comms — 16,560 →People & Recruiting — 10,926 →Education — 10,577 →Science & Research — 8,140 →Data & AI — 7,575 →Legal & Compliance — 7,489 →Administrative — 6,806 →Product — 6,715 →Security & Trust — 6,062 →Design — 4,054 →Roles we could not sort into a field — 170,437 →

Ordered by how many roles are open in each one, largest first. Counts as at 2026-09-18, read from the board's own field scan when this page was built. The live page re-reads these when it opens in a browser. Seventeen fields plus the roles we could not sort into a field: a posting lands in that last bucket when no rule of ours matched its department or its title, which is a gap in our own vocabulary rather than something missing from what the employer published. Every posting we serve carries exactly one of these, so between them they reach the whole board — and the last one is not a residue, it is a large part of the inventory that no field page can see.

The roles inside a field, priced

Role names are ours, not the board's. The number beside one is a live count of exactly the search that row opens, so a role we named that matches nothing is left out rather than shown as zero.

Narrowings that state what they hide

Remote, on-site, states the pay, a pay floor, open to beginners, full-time, posted this week, one-click apply — each with its live count, and one sentence beneath them saying how much of that field states a work mode, a pay figure, an experience level or an employment type at all. A filter can only search what employers published.

What our closure record says about the employers in a slice

Not a ranking. For the slice you assembled, how many employers we found, how many of those we hold any closure record for, and how many of those have taken roles down and not put them back up — with the gap in our record stated as plainly as the finding.

Check an employer

Any board we carry: how many of its roles we hold, and — where its own feed states a total — how much of its hiring is not on this page, with the day we read it.

See also the live board and the Ghost Job Index.