Remote and hybrid flags on LinkedIn, Indeed and Stepstone: how each board marks the workplace and how to normalise it

LinkedIn, Indeed and Stepstone each mark remote and hybrid work differently. Here is what each flag means, where it is missing, and how to map all of them onto one clean field.

Each of the three boards marks workplace type in its own way. LinkedIn has an explicit field with three values: on-site, hybrid and remote. Indeed mostly derives a label from the location field and the job text, which shows up as "Remote" or "Hybrid work" next to the location. Stepstone exposes a home office indicator as a job attribute, and the wording differs per country site. None of the three uses the same vocabulary, and none of them guarantees the flag is accurate.

To normalise them, map every board onto one small enum with four values: on_site, hybrid, remote and unknown. Keep the original raw value in a second column so you can audit the mapping later. Treat a missing flag as unknown, not as on-site. That one rule prevents most of the bad conclusions people draw from workplace data.

Why the flags differ in the first place

A job board stores what the employer typed into the posting form. The form on each board was designed at a different time, for a different market, with different defaults. LinkedIn added a structured workplace type field to job posts in 2021 and made it part of the posting flow. Indeed has for years accepted jobs through direct posting, through XML feeds from applicant tracking systems and through crawling career sites. Many of those sources carry no workplace field at all, so Indeed fills the gap with its own interpretation. Stepstone is a European board with separate country sites, each with its own form labels and its own translation of the concept.

The result is three data models that overlap in meaning but not in shape. If you scrape or export from more than one of them, you have to do the translation yourself.

LinkedIn: an explicit three-value field

LinkedIn is the easiest of the three because the workplace type is a real field. When a recruiter creates a job, they choose on-site, hybrid or remote. The value appears on the job card and in the job detail page, and it feeds the "Remote" and "Hybrid" filters in job search. LinkedIn documents the field in its help centre for job posters, which you can reach from the LinkedIn Help pages at linkedin.com/help/linkedin.

Two limits matter here.

First, the field is chosen by the poster, not verified by LinkedIn. A role marked remote can still require residence in a specific country or state. That detail lives in the description text, not in the flag. A role marked hybrid tells you nothing about how many days per week are on site.

Second, what you can see depends on whether you are logged in. A visitor without a session can open a public job page and usually sees the title, company, location and workplace type in the header. Search filters, the full list of results for a query and many detail pages require a login, and LinkedIn's User Agreement at linkedin.com/legal/user-agreement prohibits automated access to the logged-in product. For a normalisation pipeline, that means the LinkedIn side is usually limited to public job pages or to data you export yourself from a Recruiter or company account.

Mapping is direct:

  • On-site becomes on_site
  • Hybrid becomes hybrid
  • Remote becomes remote
  • No value on the page becomes unknown

Indeed: a derived label, not a field

Indeed does not show a single workplace field that every job fills in. Instead, the job card shows a location string, and that string can carry a suffix such as "Remote" or "Hybrid work". Older postings, and postings that arrived through a feed, sometimes have "Remote" in the location field itself, because the employer typed it there before Indeed had a separate option. Indeed also has a "Remote" filter in search, and the way jobs land in that filter is partly rule-based: Indeed reads the location and the description and decides.

Indeed describes what employers may and may not put in a posting in its Job Posting Standards at indeed.com/legal/job-posting-standards. That page is useful because it tells you what Indeed asks for, which is not the same as what you will find in practice. Jobs from external feeds and crawled career sites are the main source of inconsistency.

A visitor who is not logged in can search Indeed and open job pages. That is more than LinkedIn allows. The limit is different: Indeed shows a lot of job detail inside its own viewer, and some fields are only visible after a click through to the employer's site. Indeed also blocks aggressive automated access, so a scraper that hits it at high rate will see captchas or empty responses. Indeed's terms are published at indeed.com/legal.

For normalisation, treat the Indeed label as a string to parse rather than a code to read:

  • Location string ends with "Remote" or the job card shows a "Remote" badge: remote
  • Label says "Hybrid work" or "Hybrid remote in": hybrid
  • Location is a city with no suffix: on_site, but only if the description does not contain a remote statement
  • Everything else: unknown

The last rule is where honesty matters. A city with no suffix does not prove the job is on site. It only proves the poster did not use Indeed's remote option. If you want higher confidence, run a second pass over the description text with a short list of phrases such as "fully remote", "work from home", "hybrid" and "on site". Store the result as a separate column named something like text_signal, and never let it overwrite the board's own label silently.

Stepstone: an attribute that varies by country

Stepstone runs separate sites for Germany, the Netherlands, Belgium, Austria and other markets. Each site shows a home office or remote indicator on the job card and in the detail page, but the label is in the local language and the exact wording has changed over the years. On the German site the indicator has used phrases around "Homeoffice", on the Dutch site phrases around "thuiswerken". The indicator typically expresses whether working from home is possible or partly possible, which is closer to a yes or partial answer than to the three-way LinkedIn split.

That difference is the main normalisation trap. A Stepstone flag that says home office is possible does not tell you whether the role is fully remote. In most cases it means hybrid. If you map it to remote, your remote count will be inflated and your hybrid count will be too low. The safer mapping is:

  • Indicator says fully remote or 100 percent home office: remote
  • Indicator says home office possible or partly: hybrid
  • No indicator: unknown

Stepstone pages are readable without a login. A visitor sees the title, employer, location, the home office indicator and the full description. What a visitor does not see is any structured export. There is no public job search API for Stepstone, and the site's terms limit automated use. For a one-off list, manual export by copying the job cards you need is slow but free and within the rules.

Use structured data when the board provides it

All three boards, and most employer career sites, embed JobPosting structured data for search engines. The schema at schema.org/JobPosting has a jobLocationType property, and Google documents the TELECOMMUTE value for it in its job posting structured data guide at developers.google.com/search/docs/appearance/structured-data/job-posting. When that property is present it is the cleanest signal on the page, because it was written by the same system that wrote the visible flag and it uses a fixed vocabulary.

The limit is coverage. Many postings omit jobLocationType, and TELECOMMUTE only expresses remote. There is no standard value for hybrid. So structured data gives you a reliable remote flag where it exists, and nothing for the hybrid case. Combine it with the board's own label and the description pass described above, and record which of the three sources produced the final value.

A normalisation table you can copy

Use one table for all boards. Six columns are enough:

  • board: linkedin, indeed or stepstone
  • raw_workplace: the exact string as shown on the page
  • structured_type: the jobLocationType value if present, else empty
  • text_signal: remote, hybrid, on_site or empty, from the description pass
  • workplace: the final enum, on_site, hybrid, remote or unknown
  • workplace_source: which column decided the final value

Decide the final value in a fixed order. Structured data wins for remote. The board's explicit field or label wins next. The text signal only fills in when both are empty. Unknown is a valid outcome and should stay in the data. If you later report that a share of jobs is remote, report the share of jobs with a known value, and state how many were unknown.

Free routes, and when they are the better choice

If you only need data for your own company's jobs, use the board's own account tools. LinkedIn, Indeed and Stepstone all let an employer export or view their own postings with the workplace field intact. That is free, complete and allowed.

If you need jobs across many employers for a small sample, manual collection works. Open twenty or fifty job pages, copy the title, location and the workplace flag into a spreadsheet, and apply the mapping above by hand. For a one-time analysis this takes an hour and costs nothing.

If you need ongoing coverage of many employers, the free routes stop being practical. Indeed once offered a publisher API for job search, but access for new applicants has been restricted for years, so do not plan around it. LinkedIn's official APIs for jobs are limited to approved partners. Stepstone has no public job API. At that point you either build and maintain your own scraper, with the terms of service and the rate limits described above, or you buy results from a tool that already does the normalisation.

Our Stepstone Jobs Scraper reads Stepstone job cards and detail pages, keeps the raw home office indicator alongside a normalised workplace value, and charges per result rather than per month. If Stepstone is one of the boards you need to cover, see the Stepstone Jobs Scraper page for the output fields and the current price per result.


Want the signal instead of the raw filings? Get a free report preview. Prefer the tool to the write-up? Browse all data feeds or connect the free MCP server.