Work_Arrangement

Where the
work happens.

Every listing on the board carries one of five work arrangement states. This page defines the five states exactly, explains how each one gets assigned, and shows where the method admits it does not know.

The States

Five states, one answer

A listing gets exactly one state. The five are mutually exclusive, and the boundary cases are pinned: remote friendly is not a softer remote, it is an office role with an open door.

On-site

Tied to a place

The role is anchored to a named office or work location, and the listing offers no remote work. Most office jobs never write that you must come in, so a named location without any remote mention reads as on-site.

Hybrid

A set split

The role requires both office presence and remote work on a set or regular split, for example a fixed number of office days each week. The split may be described as flexible, but if both office and remote work are part of the job, it is hybrid.

Remote friendly

Office first, door open

The role is anchored to an office by default, but the listing opens a door to remote work without promising it: remote considered, remote possible for the right candidate, some remote flexibility, occasional work from home. Not the same as remote.

Remote

No office required

The role can be done fully remotely with no required office presence, or is advertised as remote or work from anywhere. A listing that only calls itself a remote friendly position, without naming any office or location, also belongs here. Reading the whole listing beats matching a phrase.

Not specified

Said nothing

The listing gives no signal at all: no named city or office, no remote mention, no split. Rather than guess, we say so. You will see this state on the board and in the charts, because an honest blank is worth more than a wrong label.

Fully remote

One state only

Only the Remote state counts as a fully remote job. Remote friendly does not, because the office is still the default. When you filter the board to Remote, you get the roles you can do from anywhere, and nothing softer.

Provenance

How the state is decided

A classification model reads the full description, plus the listing's location, and picks exactly one state. The location matters because listing bodies often never name the city: without it, a genuinely on-site role looks like it said nothing at all.

Every answer carries a confidence score. Listings that enter through our intake queue get a human check before publishing, with that confidence shown next to the field, and the same criteria run in a nightly pass over the whole board, so the states stay comparable across jobs and over time.

The same definitions apply everywhere the state appears: the panel on a job page, the filter on the board, and the work arrangement chart on the X-Ray.

Honest Limits

What we do not do

We do not guess from silence. A named location with no remote mention reads as on-site, because that is the practical default of office work. A listing with no location and no working terms at all is marked Not specified, and stays that way.

Classifications can be wrong. A clause buried in a benefits list can read like an arrangement, and a vague listing can sit right on the boundary between two states. When the state matters to your decision, check it against the description, which sits right next to it.

If a state looks wrong, report it below the listing. The disclaimer covers the rest.

Try It