Plan a module per host, six packages of new hosts and the by-hand list

The survey of the 155 companies without a board is in docs/plan-hosts.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
WolfandClaude Fable 5.1 committed 2026-09-29 16:52:40 +02:00
1 parent 6f273cfdd6
commit 0a1d3c67c7
12 files changed
+3177

No files matched your search

+128
View File
@@ -0,0 +1,128 @@
# Plan: a module per host, new hosts, and the list of companies checked by hand
Planned 2026-09-29. Three waves of work packages with disjoint files, built in parallel worktrees made from `main`, merged by the planner. This file and `docs/plan-hosts/` are folded into `decisions.md` and deleted when the work lands.
## Why
187 of the 362 companies have no board attached: 32 on Teamtailor, whose parser landed today without the boards being attached, and 155 on a host the app cannot read or on no host it could name. They include LEGO, Novo Nordisk, Vestas, Danske Bank, SimCorp, Ørsted, Klarna and Zalando. A company the app cannot read is shown as "not readable yet" with a link that nobody can edit, so the owner has no list to work through by hand.
## What the survey found
Nine Sonnet agents read every one of the 155 career sites on 2026-09-29. Their notes are in `docs/plan-hosts/`: `workday.md`, `successfactors.md`, `otherhosts.md`, `own-1.md` to `own-4.md`, and `survey-own.json` with one record per company (verified `jobs_url`, class, host, identifier, listing URL, roles seen, evidence). Raw responses for fixtures are in the session scratchpad, `/tmp/claude-1000/-home-claude-cboxcode-jobboard/1734d897-7509-48fc-844c-efe768acbf7a/scratchpad/`, and a builder copies the ones it needs, trimmed, into `tests/fixtures/ats/`.
| Route | Companies | Examples |
|---|---|---|
| Board on a host the app reads already | 49 + 32 Teamtailor | Bosch, Wise, Ubisoft, Checkout.com, Lunar, DFDS, Voi, Remote |
| SuccessFactors | 20 | Novo Nordisk, Vestas, Carlsberg, Pandora, Coloplast, Scania, SAP, Tryg |
| Workday | 19 | LEGO, Zeiss, SimCorp, Zendesk, Unity, Saxo Bank, Red Hat |
| Oracle | 4 | Danske Bank, Nokia, Sinch, Milestone |
| Phenom | 3 | Philips, Just Eat Takeaway, King |
| Eightfold | 3 | Microsoft, Ericsson, Infineon |
| Eleven small hosts | 15 | Klarna (Deel), Booking.com (Jibe), sennder (Gem), Einride (Jobylon) |
| Sitemap and structured data | 8 | Arm, Mambu, Odoo, Aiven, AUTO1, ASML |
| Own JSON API | 8 | Ørsted, Nordea, Amazon, Vinted, Dynatrace |
| Own HTML list | 10 | Zalando, Netcompany, Google, Bolt, CHECK24 |
| By hand | about 25 | Revolut, Meta, Maersk, Bang & Olufsen, Visma, HashiCorp |
The 49 were missed because the slug is not the company's name (`BoschGroup`, `jimdo.com`, `workatbackbase`), the board is on a custom domain, the board is on Lever's EU host, or the careers page refuses a plain request.
## Decisions
**A host is a module.** `plugins/ats.py` holds eight hosts in six parallel tables, and `app/jobs/discover.py` holds three more, so two builders adding a host edit the same lines. Each host moves into `plugins/atshosts/<host>.py`, and `ats.py` and `discover.py` build their tables from the package. The package is a sibling of `ats.py` and not `plugins/ats/`, since `desk.sources.registry` globs `plugins/*.py` and the tests patch names on the `ats` module.
**A host is handed the fetch.** A host module imports nothing from `plugins.ats`. Its functions receive `get`, which `ats.py` binds to its own `_get` at call time, so the allow-list, the redirect rule, the byte cap and the deadline stay in one place and a test that patches `ats._get` reaches every host.
**A description read per role is read once.** Workday, SuccessFactors and BambooHR state the description only on the role's own page. A host with a `detail` function has it called for roles not yet read in detail, at most `DETAIL_CAP` (200) per board per pull; the ids read are kept in `ats:detailed:<target>`. A known role is sent without a description on later pulls, which `upsert_role` ignores since an empty value never overwrites a filled column. Completeness is decided by the listing alone.
**robots.txt is honoured.** A host module names the page whose path must be allowed. The shared code reads the site's robots.txt at most once a day per board and fails a board that disallows it for `*`, with the reason "robots.txt disallows it". This takes Novonesis, Darktrace, Criteo and Bang & Olufsen off the automatic route. The SuccessFactors reader uses `/sitemap.xml`, `/search/` and `/job/` only, never `/services/` or the `career*.successfactors.eu` back end.
**No reader is built on a key lifted from a site's script.** Maersk's API, New Work's and Welcome to the Jungle's search index answer only with a key that the page's JavaScript carries. They go on the by-hand list.
**The by-hand list is the `companies` table.** A company is on it when it has no shown board and is not known from a search only. `careers_url` and `notes` exist already; migration 15 adds `hand_reason` and `checked_at`. No second table, since a company has one careers link and the list needs no history of checks.
**A link typed by hand is kept.** `add_discovered` and the seed fill `careers_url` only when it is empty.
**A company has one board.** DFDS has eleven Teamtailor boards by country, and Onfido, Tink and Glovo sit inside their owners' boards. DFDS gets its Danish board; the other three go on the by-hand list with reason `group`.
## Contracts between packages
Host module, `plugins/atshosts/<host>.py`:
```python
NAME = "workday" # the host of a target `workday:<slug>`
LABEL = "Workday" # the Sources page's select
PATTERNS = (r"https?://...",) # discover: over a URL, group 1 is the slug
def slug_ok(slug: str) -> bool: ... # strict; a slug that fails is no target
def allowed(slug: str) -> Callable[[str], bool]: ... # hostnames a fetch may reach
def careers_url(slug: str) -> str: ... # the page a person opens
def robots_page(slug: str) -> str: ... # optional; the URL robots.txt must allow
# one of the two
def feed_url(slug: str) -> str: ...
def parse(body: bytes, slug: str) -> list[Row]: ...
def page(get: Get, slug: str, cursor: Any) -> Page: ...
def rows(decoded: Any, slug: str) -> list[Row]: ...
# optional
def detail(get: Get, slug: str, row: Row) -> Row: ...
def probe_url(slug: str) -> str: ...
def probe_ok(body: bytes) -> bool: ...
```
`Get` is `get(url, *, method="GET", payload=None, headers=None) -> bytes`. `Row` and `Page` are as in `plugins/ats.py` today. `plugins/atshosts/__init__.py` lists the modules with `pkgutil.iter_modules`, sorted by name, so a new host registers by existing.
Slugs: Workday `lego.wd103/LEGO_External`; SuccessFactors, Phenom and the sitemap reader take the site's hostname, with a path where the site has one (`jobs.teradyne.com/MiR`); Oracle `<host>/<siteNumber>`.
Company JSON, in `GET /api/companies`: `CompanyOut` gains `domain`, `notes`, `hand_reason`, `checked_at` and `by_hand` (bool). `hand_reason` is one of `''`, `unread` (readable, no parser yet), `robots`, `blocked` (the site answers a program with a challenge), `key`, `group`, `gone`, `added` (by hand or by an import, not looked at). `from_search` is false for a company with a `hand_reason`.
| Endpoint | Body | Answer |
|---|---|---|
| `POST /api/companies` | `name`, `careers_url`, `notes`, `hand_reason` (default `added`) | 201 `CompanyOut`; 409 when the key is taken |
| `PATCH /api/companies/{key}` | any of `name`, `careers_url`, `notes`, `hand_reason` | `CompanyOut`; the key stays; 409 on `name` for a company with a board |
| `POST /api/companies/{key}/checked` | none | `CompanyOut` with `checked_at` now |
| `DELETE /api/companies/{key}` | none | 204; 409 when it has a board or open roles; its `agent_companies` rows go with it |
`careers_url` is http or https, as `safeUrl` demands on the page.
## Work packages
Wave 0, in parallel, from today's `main`:
| WP | Branch | Model | Owns |
|---|---|---|---|
| 0 Host modules | `wp0-hosts` | Opus | `plugins/ats.py`, `plugins/atshosts/`, `app/jobs/discover.py`, `tests/test_ats.py`, `tests/test_discover.py`, `tests/test_atshosts.py` |
| 1 By-hand backend | `wp1-byhand-api` | Sonnet | `app/models.py`, `app/storage/schema.py`, `app/storage/store.py`, `app/web/api.py`, `app/jobs/sources.py`, `app/cli.py`, `tests/test_storage.py`, `tests/test_web.py`, `tests/test_sources.py` |
| 2 By-hand page | `wp2-byhand-ui` | Opus | `app/templates/settings/sources.html`, `app/static/byhand.js`, `app/static/companies.js`, `app/static/app.css`, `app/web/pages.py` |
Wave 1, in parallel, from `main` after WP0 is merged. Each owns its modules in `plugins/atshosts/`, `tests/test_ats_<host>.py` and `tests/fixtures/ats/<host>*`, and nothing else:
| WP | Branch | Model | Hosts |
|---|---|---|---|
| 3 | `wp3-workday` | Sonnet | Workday |
| 4 | `wp4-successfactors` | Sonnet | SuccessFactors |
| 5 | `wp5-oracle-phenom` | Sonnet | Oracle, Phenom |
| 6 | `wp6-json-hosts` | Sonnet | Eightfold, Jibe, Pinpoint, BambooHR, Gem |
| 7 | `wp7-small-hosts` | Sonnet | Deel, Jobylon, HR-ON, HR Manager, Rippling, HiBob |
| 8 | `wp8-sitemap` | Sonnet | `sitemap`: job URLs from a sitemap, the role from the page's JSON-LD or microdata |
Wave 2 is decided after wave 1 by the roles each company would add: a module per company for the own JSON APIs (Ørsted, Nordea, Amazon, Vinted, Dynatrace, RELEX, Siteimprove, Bending Spoons) and the own HTML lists (Zalando, Netcompany, Google with DeepMind, Bolt, CHECK24). Until then these companies are on the by-hand list with reason `unread`.
**WP0.** The eight hosts move into modules with no change in behaviour: the existing tests pass with edits to imports only. `careers_url`, `is_known_target`, `_allowed_host` and `_paged` lose their Teamtailor branches to the module. `_get` takes `headers`. `detail` and the robots check are added to the shared code with tests against a fake host. `discover.py` takes `READABLE`, `HOSTS`, `_PROBES` and the body checks of `probe` from the modules; the hosts it names but cannot read stay in a table of its own. Discovery gains Lever's EU host. The tests that use `workday:` or `successfactors` as the unreadable host use `taleo` instead.
**WP1.** Migration 15, the four endpoints, `CompanyOut`'s new fields, `remove_company` taking the `agent_companies` rows, `careers_url` filled only when empty in `add_discovered` and `seed_companies`, the seed reading `hand_reason`, and `app companies add`, `edit`, `checked` and `remove` in the CLI. The `workday:` and `successfactors` fixtures in its three test files become `taleo`.
**WP2.** A section "Check by hand" in the Sources rail, after Company boards: a count, a New company button, and rows sorted by `checked_at`, never checked first. A row shows the name, the affinity control, the reason, the careers link, the note, "checked 3 days ago", and Checked, Edit and Remove. New and Edit use the form pattern of the job boards section (`sources.js`: a `<template>`, the row becomes the form in place). The filter "Not readable yet" in Company boards is removed, since the section replaces it. Until WP1 is merged the page is built against the contract above.
**WP3 to WP8.** One module per host as the contract says, with parser tests from a saved response, paging and completeness tests against a fake `get`, and the allow-list and slug tests. Each host's notes name the listing, the paging quirks and the fields.
## Planner, after the merges
- After WP1: write the survey into the live database and `seed/companies.json`: the verified `jobs_url` as `careers_url` for the 155, and the `hand_reason` of each company that stays by hand.
- Attach the 49 boards the survey found and the 32 Teamtailor boards with `set_board`, which fetches each before it lands. Not attached: Wallbox and Metacore (empty boards, possibly stale), Glovo, Cognigy.
- After each host of wave 1: attach its boards, add it to `TRUSTED_POSTED_HOSTS` where its date is a posting date, and name it in `README.md`.
- Run a full pull on a copy of the live database before the live one.
- Read one Workday and one SuccessFactors board from the deployed server, since every Workday host is behind Cloudflare and the survey ran from this machine.
- Correct the seed: Yousign is Youtrust, Philips's link is the global site, Novonesis's tenant is `novonesis`, Booking.com and Arm are not on iCIMS.
- Fold this file into `decisions.md` and delete it with `docs/plan-hosts/`.
+320
View File
@@ -0,0 +1,320 @@
# Career sites on smaller ATS hosts: can they be read without a browser?
Probed 2026-09-29 with `curl -m 20`, a Chrome User-Agent, at most one request per second per host, no login. "Verified" means I made the request and parsed the response. "Inferred" means I did not observe it. No host blocked me; no captcha or challenge was met anywhere.
Fixtures (one raw listing per host that worked, plus a detail sample where useful) are in the same directory as this file:
| Host | Listing fixture | Extra fixtures |
|---|---|---|
| oracle | out-otherhosts-oracle.json | out-otherhosts-oracle-detail.json |
| bamboohr | out-otherhosts-bamboohr.json | out-otherhosts-bamboohr-detail.json |
| pinpoint | out-otherhosts-pinpoint.json | out-otherhosts-pinpoint-detail.html |
| icims | out-otherhosts-icims.html | out-otherhosts-icims-detail.html, out-otherhosts-icims-sitemap.xml |
| jibe (Booking.com) | out-otherhosts-jibe.json | |
| talentbrew (Arm) | out-otherhosts-talentbrew.json | |
| gem | out-otherhosts-gem.json | out-otherhosts-gem-detail.json |
| eightfold | out-otherhosts-eightfold.json | out-otherhosts-eightfold-detail.json |
| phenom | out-otherhosts-phenom.json | out-otherhosts-phenom-detail.html |
| wttj | out-otherhosts-wttj.json | |
## Corrections to the app's data
- Booking.com: not classic iCIMS. `careers.booking.com` links to `jobs.booking.com/booking/jobs`, which is iCIMS Jibe (a separate product with a JSON API). iCIMS itself sits behind it only for applying.
- Arm: not a classic iCIMS list. `careers.arm.com` is TalentBrew (Radancy). The `*-arm.icims.com` hosts only serve login and redirect to `careers.arm.com/search-jobs`.
- Philips: the stored `careers_url` (`/na/en/`) is the North America site with 306 roles. The global site `/global/en` has 865.
- Yousign: renamed Youtrust. `yousign.com` now serves `youtrust.com`. On Welcome to the Jungle the organization slug is `youtrust` (12 roles); the stored slug `yousign` yields 0 roles.
- Native Instruments: the ATS is Pinpoint but the board is the shared one of the parent, `inmusicbrands.pinpointhq.com` (21 roles across inMusic brands, only 1 for NI Berlin).
- Just Eat Takeaway: Phenom shows the list, but applying goes to Workday (`applyUrl` on `wd3.myworkdaysite.com`). The list is still readable on Phenom.
- Xeneta: the board is small (2 roles, both in Bucharest, none in Oslo).
- Infineon: the suggested Eightfold endpoint `/api/apply/v2/jobs` returns 403 `Not authorized for PCSX`. The working one is `/api/pcsx/search`.
## Per-company table
| Name | Host confirmed | Identifier | Human-facing jobs URL | Listing endpoint | Roles seen | Verified | Note |
|---|---|---|---|---|---|---|---|
| Milestone Systems | Oracle Recruiting Cloud (yes) | host `fa-ewto-saasfaprod1.fa.ocs.oraclecloud.com`, siteNumber `CX_1001` | https://fa-ewto-saasfaprod1.fa.ocs.oraclecloud.com/hcmUI/CandidateExperience/en/sites/CX_1001/jobs | `.../hcmRestApi/resources/latest/recruitingCEJobRequisitions?onlyData=true&expand=requisitionList&finder=findReqs;siteNumber=CX_1001,limit=200,offset=0` | 20 (TotalJobsCount 20) | yes | region segment is `ocs`, not `us2` etc.; the host is linked from milestonesys.com/careers |
| Configit | BambooHR (yes) | subdomain `configit` | https://configit.bamboohr.com/careers | `https://configit.bamboohr.com/careers/list` | 2 (meta.totalCount 2) | yes | one is an unsolicited-application placeholder; embedded on configit.com via `embed.js` |
| Xeneta | Pinpoint (yes) | subdomain `xeneta` | https://xeneta.pinpointhq.com/ | `https://xeneta.pinpointhq.com/postings.json` | 2 | yes | both roles Bucharest; list has no posted date |
| Native Instruments | Pinpoint (yes, parent board) | subdomain `inmusicbrands`, filter `job.division.name == "inMusic NI GmbH"` | https://inmusicbrands.pinpointhq.com/ (linked from native-instruments.com/pages/careers) | `https://inmusicbrands.pinpointhq.com/postings.json` | 21 total, 1 for NI (Berlin, DE) | yes | shared board: must filter by division; department is null |
| Mambu | iCIMS (yes, classic) | subdomain `careers-mambu` | https://careers-mambu.icims.com/jobs/search?ss=1&in_iframe=1 (linked from mambu.com/en/careers) | `https://careers-mambu.icims.com/sitemap.xml` (IDs, lastmod) and `.../jobs/search?ss=1&in_iframe=1&pr=0` (cards) | 8 | yes | sitemap lists 8 jobs plus an intro URL; `pr=1` returns no cards |
| Booking.com | iCIMS Jibe (host differs from app's guess) | Jibe path `booking`, filter `brand=Booking.com` | https://jobs.booking.com/booking/jobs | `https://jobs.booking.com/api/jobs?page=1&limit=100&brand=Booking.com` | 98 for Booking.com, 146 with the Booking Holdings brand | yes | limit 200 returns 422, 100 is the cap; `brand=` filters, `brands=` does not |
| Arm | TalentBrew (Radancy), not iCIMS list | site `careers.arm.com`, org id 33099 | https://careers.arm.com/search-jobs | `https://careers.arm.com/search-jobs/results?...RecordsPerPage=100&CurrentPage={n}...` (full query in section below) and `https://careers.arm.com/sitemap.xml` | 399 (page 4 has 99) | yes | JSON envelope carrying HTML; list has no date |
| sennder | Gem (yes) | board `senndertechnologies-gmbh` | https://jobs.gem.com/senndertechnologies-gmbh (sennder.com/de/open-positions embeds it) | `POST https://jobs.gem.com/api/public/graphql` (JobBoardList) | 33 | yes | list has no date or description; detail query gives both |
| Productboard | Gem (yes) | board `productboard` | https://jobs.gem.com/productboard | same POST | 11 | yes | 12 CZ + 4 US locations across 11 roles |
| Infineon | Eightfold PCSX (yes, other endpoint) | host `jobs.infineon.com`, domain `infineon.com` | https://jobs.infineon.com/careers | `https://jobs.infineon.com/api/pcsx/search?domain=infineon.com&query=&location=&sort_by=relevance&start=0` | 1292 total, 10 per page | yes | `num` is ignored; 130 requests for a full poll; `/api/apply/v2/jobs` is 403 |
| Just Eat Takeaway.com | Phenom (yes) | refNum `TAKEGLOBAL`, path `/global/en`, pageId `page11` | https://careers.justeattakeaway.com/global/en/search-results | `POST https://careers.justeattakeaway.com/widgets` (refineSearch) | 103 (totalHits 103; sitemap also 103 job URLs) | yes | `size` 200 returned all 103 in one call; apply is on Workday |
| Philips | Phenom (yes) | refNum `PHILUS`, path `/global/en`, pageId `page6` | https://www.careers.philips.com/global/en/search-results | `POST https://www.careers.philips.com/widgets` (refineSearch) | 865 global (306 on `/na/en`) | yes | `size` 500 worked (500 of 865 in 1.7 MB); app's URL is the NA site only |
| Yousign (now Youtrust) | Welcome to the Jungle (yes) | org slug `youtrust` | https://www.welcometothejungle.com/en/companies/youtrust/jobs | Algolia `POST https://CSEKHVMS53-dsn.algolia.net/1/indexes/wttj_jobs_production_en/query` | 12 | yes | app slug `yousign` returns 0; the same 12 appear in the `_fr` index |
## What one role gives, per host
| Host | Title | URL | Location with country | Remote indication | Date posted | Description | Pay |
|---|---|---|---|---|---|---|---|
| Oracle | list `Title` | build: `{base}/hcmUI/CandidateExperience/en/sites/{site}/job/{Id}` (inferred, standard pattern; not fetched) | list `PrimaryLocation` ("Copenhagen, Denmark") and `PrimaryLocationCountry` ("DK"); `secondaryLocations` array | list `WorkplaceType` ("Hybrid", "On-site", or empty) | list `PostedDate` (date); detail `ExternalPostedStartDate` (timestamp) | detail only: `ExternalDescriptionStr` (plus responsibilities/qualifications strings, often empty) | none seen |
| BambooHR | list `jobOpeningName` | `https://{sub}.bamboohr.com/careers/{id}` (detail returns it as `jobOpeningShareUrl`) | list `location.city`; country only in detail `location.addressCountry` ("Denmark") | list `isRemote` (null in sample) and `locationType` ("2" for a hybrid-looking role; mapping 0/1/2 is inferred) | detail only: `datePosted` | detail only: `description` HTML | detail `compensation` (null in sample) |
| Pinpoint | list `title` | list `url` | list `location.name`/`city`; `province` holds country or region inconsistently; ISO country only in the detail JSON-LD `addressCountry` | list `workplace_type` (onsite/hybrid/remote) | detail JSON-LD `datePosted` only | list: `description`, `key_responsibilities`, `skills_knowledge_expertise`, `benefits` as HTML | list `compensation_*` fields, shown when `compensation_visible` is true (false in both samples) |
| iCIMS classic | card `h3` and anchor title | card anchor `href` (`/jobs/{id}/{slug}/job`) | card "NL-Amsterdam" (country code prefix); detail JSON-LD `jobLocation[].address.addressCountry` | none observed | detail JSON-LD `datePosted`; sitemap has `lastmod` | card gives a truncated snippet; full text in the detail JSON-LD `description` | none seen |
| Jibe (Booking.com) | `title` | `https://jobs.booking.com/booking/jobs/{slug}` (page returned 200); `apply_url` is the iCIMS apply link | `city`, `country`, `country_code`, `full_location`, lat/long | none obvious; `location_type` was "LAT_LNG" (a geo type, not remote) | `posted_date` | in the list: `description` HTML (about 1.7 MB per 100 roles) | `salary_value`, `salary_min_value`, `salary_max_value` (all "0" in the sample) |
| TalentBrew (Arm) | card anchor text | card `href` (`/job/{city}/{slug}/33099/{jobId}`) | card `location` ("Cambridge, United Kingdom"); detail JSON-LD `addressCountry` | none | detail JSON-LD `datePosted` ("2026-6-25", unpadded); list has none | card teaser only; full in detail JSON-LD `description` | JSON-LD `baseSalary` present but empty |
| Gem | `title` | build: `https://jobs.gem.com/{board}/{extId}` (detail page path in the bundle; `extId` may be numeric or base64-like) | `locations[]` with `name`, `city`, `isoCountry` (ISO alpha-3: ESP, DEU) | `locations[].isRemote`; `job.locationType` (IN_OFFICE, HYBRID; REMOTE inferred) | detail `firstPublishedTsSec` (epoch seconds); list has none | detail only: `descriptionHtml` | detail `compensationHtml` (null in sample) |
| Eightfold | `name` | `https://jobs.infineon.com` + `positionUrl` (`/careers/job/{id}`); detail gives `publicUrl` | `locations`, `standardizedLocations` ("Shanghai, Shanghai, CN" ends with ISO alpha-2) | `workLocationOption` (onsite/hybrid; remote inferred), and facet "Remote" | list `postedTs` (epoch seconds); `creationTs` too | detail only: `jobDescription` HTML | none seen |
| Phenom | `title` | `https://{host}/global/en/job/{jobSeqNo}/{Title-Slug}` (sitemap has these); list `applyUrl` points at the apply system | `country`, `city`, `cityStateCountry`, `multi_location` | none in the list fields I saw | list `postedDate`; detail JSON-LD `datePosted` | list `descriptionTeaser` only; full text in the detail JSON-LD `description` (HTML-escaped) | none seen |
| WTTJ | `name` | `https://www.welcometothejungle.com/en/companies/{orgSlug}/jobs/{slug}` (fetched, 200) | `offices[]` with `city`, `country`, `country_code` | `remote` ("punctual", "partial", "fulltime", "unknown") and `has_remote` | `published_at` | list: `summary`, `key_missions`, `profile`; full HTML in the job page JSON-LD | `salary_minimum`, `salary_maximum`, `salary_currency`, `salary_period` in the list |
## Host sections
### Oracle Recruiting Cloud
Verified for Milestone Systems only.
One method for all companies on the host: yes, the REST resource is the same on every tenant. The identifiers differ (host, siteNumber). Both come from the human URL `https://{host}/hcmUI/CandidateExperience/{lang}/sites/{siteNumber}/jobs`. The site number is not always `CX_1001` (on other tenants it can be `CX`, `CX_1`, ...; inferred).
Algorithm:
1. `GET https://{host}/hcmRestApi/resources/latest/recruitingCEJobRequisitions?onlyData=true&expand=requisitionList&finder=findReqs;siteNumber={site},limit={n},offset={o}`
2. `items[0].TotalJobsCount` is the total. `items[0].requisitionList[]` holds the roles. The outer `hasMore` / `count` describe the single search wrapper (count 1), so ignore them.
3. Without `expand=requisitionList` (or `requisitionList.secondaryLocations`) the roles are missing and the response is only facets. This is the easy mistake.
4. Page with `offset += limit` until `offset >= TotalJobsCount`. `limit=200` returned all 20 in one call; `limit=5&offset=15` returned the last 5 (verified).
5. Detail: `GET .../recruitingCEJobRequisitionDetails?expand=all&onlyData=true&finder=ById;Id="{Id}",siteNumber={site}` (quote the Id as `%22..%22`). Returns `ExternalDescriptionStr`, `ExternalPostedStartDate`, `workLocation`, `secondaryLocations`.
Identifier to store: `host` + `siteNumber`; per role `Id`.
Requests per poll: `ceil(total / 200)` (1 here), plus one detail call per new role.
Bot protection: none met. Anonymous, no cookies, no headers beyond User-Agent.
Worth a parser: yes if any target uses it, because it is the cleanest API in this set. Oracle Fusion HCM is common among large enterprises and mid-caps; among European tech and Nordic companies it is uncommon (inferred from general knowledge), though Milestone shows it exists. One company in this list.
```
curl -m 20 -A "Mozilla/5.0 ..." 'https://fa-ewto-saasfaprod1.fa.ocs.oraclecloud.com/hcmRestApi/resources/latest/recruitingCEJobRequisitions?onlyData=true&expand=requisitionList&finder=findReqs;siteNumber=CX_1001,limit=200,offset=0'
curl -m 20 -A "Mozilla/5.0 ..." 'https://fa-ewto-saasfaprod1.fa.ocs.oraclecloud.com/hcmRestApi/resources/latest/recruitingCEJobRequisitionDetails?expand=all&onlyData=true&finder=ById;Id=%2224345%22,siteNumber=CX_1001'
```
### BambooHR
Verified for Configit only.
One method: yes (the endpoints are per-subdomain and identical). Human page `https://{sub}.bamboohr.com/careers` is a JS app calling the JSON endpoints; company sites embed `https://{sub}.bamboohr.com/js/embed.js`.
Algorithm:
1. `GET https://{sub}.bamboohr.com/careers/list` returns `{"meta":{"totalCount":N},"result":[...]}` with all roles, no paging (2 of 2 here; whether larger boards page is not tested).
2. `GET https://{sub}.bamboohr.com/careers/{id}/detail` returns JSON `result.jobOpening` with `description`, `datePosted`, `location.addressCountry`, `compensation`, `jobOpeningShareUrl`. Send `Accept: application/json` (I did; the `.../careers/{id}` URL without it returns HTML).
Identifier: subdomain; per role `id`.
Requests per poll: 1 for the list, plus one detail call per new role (needed for date, country, description).
Bot protection: none met.
Worth a parser: probably yes. Two trivial endpoints, no auth. BambooHR is widespread among small and mid-size companies, mostly US, with a fair number of European and Nordic scale-ups (inferred); one company in this list.
```
curl -m 20 -A "Mozilla/5.0 ..." https://configit.bamboohr.com/careers/list
curl -m 20 -A "Mozilla/5.0 ..." -H 'Accept: application/json' https://configit.bamboohr.com/careers/37/detail
```
### Pinpoint
Verified for Xeneta and inMusic Brands (Native Instruments).
One method: yes, but a board may be shared by several brands (Native Instruments), so the mapping from company to board is many-to-one and a filter is needed (`job.division.name`, here "inMusic NI GmbH"). The company's own site only links the board.
Algorithm:
1. `GET https://{sub}.pinpointhq.com/postings.json` returns `{"data":[...]}` with every open posting including full HTML text. No paging keys, no total (2 and 21 roles; a large board might page, not tested).
2. Per posting: `id`, `title`, `url`, `location{name,city,province}`, `workplace_type`, `employment_type`, `compensation_*`, `description`, `key_responsibilities`, `skills_knowledge_expertise`, `benefits`, `job{requisition_id, department, division}`. `deadline_at` is present.
3. Date posted is missing from the list. The detail page `{url}` embeds JSON-LD JobPosting with `datePosted`, `identifier.value` (the UUID) and `addressCountry`.
4. `HEAD` on `/postings.json` returns 404 (only GET works).
Identifier: subdomain (plus division filter if shared); per role `id` or the UUID in `url`.
Requests per poll: 1. Plus one detail per new role if a date or ISO country is wanted.
Bot protection: none met.
Worth a parser: yes, cheapest of all. Pinpoint is popular among UK and Nordic scale-ups and mid-size firms (inferred); two companies in this list.
```
curl -m 20 -A "Mozilla/5.0 ..." https://xeneta.pinpointhq.com/postings.json
curl -m 20 -A "Mozilla/5.0 ..." https://inmusicbrands.pinpointhq.com/postings.json
curl -m 20 -A "Mozilla/5.0 ..." https://xeneta.pinpointhq.com/en/postings/a85d5d45-b334-4f5c-aaea-d0b399b08a2e
```
### iCIMS (classic portal), Jibe, and TalentBrew
"iCIMS" in the app covers three different front ends, so there is no single method.
**Classic portal** (Mambu, verified):
1. `GET https://careers-{tenant}.icims.com/sitemap.xml`: one `<loc>` per job (`/jobs/{id}/{slug}/job`) with `lastmod`, plus `/jobs/intro`. Matched the 8 cards on the list page (verified). robots.txt allows it and lists the sitemap.
2. Alternative: `GET https://careers-{tenant}.icims.com/jobs/search?ss=1&in_iframe=1&pr={page}` with `pr` starting at 0. Cards are `li.iCIMS_JobCardItem` with location ("NL-Amsterdam"), title anchor and a snippet; the header says "Page 1 of N". `pr=1` on Mambu returned no cards. Page size and behaviour on multi-page tenants not verified (Mambu has one page).
3. Detail: `GET .../jobs/{id}/x/job?in_iframe=1` (slug not needed, verified) carries a JSON-LD JobPosting with `datePosted`, `description`, `jobLocation[].address.addressCountry`, `validThrough`, `employmentType`.
Identifier: tenant subdomain (`careers-{tenant}`); some tenants use other prefixes (`experienced-arm`, `careers-holdings-workingatbooking`; inferred that the app must store the whole host). Per role: numeric job id.
Requests per poll: 1 sitemap (or `ceil(total/pageSize)` list pages) plus one detail per new role.
Bot protection: none met. Some tenants return "gone" (`careers-workingatbooking.icims.com` gave 404) or redirect to the customer's own site (Arm: JS redirect to `careers.arm.com/search-jobs`).
**Jibe** (Booking.com, verified): JSON API on the company's own `jobs.` host.
1. `GET https://jobs.booking.com/api/jobs?page={p}&limit=100[&brand=Booking.com]`, `page` starting at 1. Response has `totalCount` (146) and `jobs[].data` with all fields including full description. `limit=200` is a 422, so 100 is the cap. Page 2 returned the remaining 46. Brand filter is `brand=` (98 roles for Booking.com, 48 for Booking Holdings); `brands=` is ignored.
2. Response is large (1.7 MB per 100 roles) because it repeats filter facets and HTML descriptions.
3. Identifier: host and the path prefix (`/booking/`), `slug` (equals `req_id`). Requests per poll: `ceil(total/100)` (2). Bot protection: none met.
4. Other Jibe sites use the same `/api/jobs` path (inferred; only Booking tested).
**TalentBrew / Radancy** (Arm, verified): the list is HTML inside JSON.
1. `GET https://careers.arm.com/search-jobs/results?ActiveFacetID=0&CurrentPage={n}&RecordsPerPage=100&TotalContentResults=&Distance=50&RadiusUnitType=0&Keywords=&Location=&ShowRadius=False&IsPagination=False&CustomFacetName=&FacetTerm=&FacetType=0&SearchResultsModuleName=Search+Results&SearchFiltersModuleName=Search+Filters&SortCriteria=0&SortDirection=0&SearchType=5&PostalCode=&ResultsType=0&fc=&fl=&fcf=&afc=&afl=&afcf=` returns `{"filters":"<html>","results":"<html>","hasJobs":true,...}`. A shortened query returned 60 bytes and no jobs, so send the full parameter set.
2. In `results`, `<section id="search-results" data-total-job-results="399" data-total-pages="4" data-current-page="1">`. Job cards are `li.job-card` with `a.job-card__title[href][data-job-id]`, `span.location`, `span.category`, optional `span.job-card__intro`. Cards with class `job-card--content` are non-job content pages; ignore them.
3. Pages 1 to 3 hold 100 jobs each and page 4 holds 99 (verified). The `data-total-results="516"` includes 117 content items, so use `data-total-job-results`.
4. `https://careers.arm.com/sitemap.xml` (169 KB) lists all 399 `/job/...` URLs in one request without titles (verified).
5. Detail: JSON-LD `datePosted` ("2026-6-25", unpadded), `description`, `identifier` (requisition number "2025-16272"), `jobLocation[].address`.
6. Identifier: site host and org id `33099` (the number in every job URL); per role the trailing numeric id.
Worth a parser:
- Classic iCIMS: sitemap plus detail JSON-LD is easy and generic; iCIMS is very common among large enterprises and mid-caps (inferred). Only Mambu is on classic in this list.
- Jibe: a clean API, but it is a different product (Booking only here). Cheap to build (about 30 lines) if Booking.com matters.
- TalentBrew: HTML scraping of a Radancy front end; used by big employers (Arm). Sitemap plus detail JSON-LD is the generic route and shares code with classic iCIMS.
- Recommendation: one "sitemap plus JSON-LD detail" reader covers classic iCIMS, TalentBrew and (partly) Phenom. That is a better investment than three host parsers.
```
curl -m 20 -A "Mozilla/5.0 ..." https://careers-mambu.icims.com/sitemap.xml
curl -m 20 -A "Mozilla/5.0 ..." 'https://careers-mambu.icims.com/jobs/search?ss=1&in_iframe=1&pr=0'
curl -m 20 -A "Mozilla/5.0 ..." 'https://careers-mambu.icims.com/jobs/3461/x/job?in_iframe=1'
curl -m 20 -A "Mozilla/5.0 ..." 'https://jobs.booking.com/api/jobs?page=1&limit=100&brand=Booking.com'
curl -m 20 -A "Mozilla/5.0 ..." https://careers.arm.com/sitemap.xml
```
### Gem
Verified for sennder and Productboard.
One method: yes, the board is identified by a vanity path and one GraphQL endpoint serves all boards. The company's own site either embeds it (sennder: `gemJobBoardUrl` in the page) or links to `jobs.gem.com/{board}` (Productboard). The HTML at `jobs.gem.com/{board}` is an empty React shell with no embedded data, so the GraphQL call is the only way without a browser.
Endpoint (found by reading `static.gem.com/scripts/jobBoards.*.js` and `ExternalJobBoardList.*.js`): `POST https://jobs.gem.com/api/public/graphql` with `Content-Type: application/json`. The Apollo batch variant `/api/public/graphql/batch` also exists in the bundle (not used). No auth, no CSRF token needed (I sent an Origin and Referer of jobs.gem.com; whether they are required was not tested).
Algorithm:
1. List: query `JobBoardList` with `variables {"boardId": "{board}"}` selecting `oatsExternalJobPostings(boardId){ jobPostings { id extId title locations{ id name city isoCountry isRemote extId } job{ id department{ id name extId } locationType employmentType } } }`. Returns all roles in one response (33 and 11), no paging, no total field (count the array).
2. Detail: query `ExternalJobPosting($boardId, $extId)` selecting `oatsExternalJobPosting(boardId, extId){ id title descriptionHtml extId firstPublishedTsSec locations{...} job{ locationType employmentType requisitionId teamDisplayName department{name} } compensationHtml }`. The role URL is `https://jobs.gem.com/{board}/{extId}`.
3. `extId` is either numeric (Greenhouse-synced, "8084509002") or an opaque string ("am9icG9zdDoG..."); store it as a string.
4. Query text is kept in `gem-q.py`-style form below; the GraphQL schema is fixed by the bundle, so the queries may break when Gem ships a new bundle (risk).
Identifier: board vanity path (`senndertechnologies-gmbh`, `productboard`), the segment after `jobs.gem.com/`. Per role `extId`.
Requests per poll: 1, plus one detail per new role for the date and description.
Bot protection: none met (plain POST from curl worked). Rate limits not hit.
Worth a parser: yes. One POST for the whole board. Gem is used by US-founded and growth-stage tech companies and by some European scale-ups (inferred); two companies in this list.
```
curl -m 20 -A "Mozilla/5.0 ..." -X POST -H 'Content-Type: application/json' -H 'Origin: https://jobs.gem.com' --data '{"operationName":"JobBoardList","variables":{"boardId":"senndertechnologies-gmbh"},"query":"query JobBoardList($boardId: String!) { oatsExternalJobPostings(boardId: $boardId) { jobPostings { id extId title locations { id name city isoCountry isRemote extId } job { id department { id name extId } locationType employmentType } } } }"}' https://jobs.gem.com/api/public/graphql
curl -m 20 -A "Mozilla/5.0 ..." -X POST -H 'Content-Type: application/json' -H 'Origin: https://jobs.gem.com' --data '{"operationName":"ExternalJobPosting","variables":{"boardId":"senndertechnologies-gmbh","extId":"8084509002"},"query":"query ExternalJobPosting($boardId: String!, $extId: String!) { oatsExternalJobPosting(boardId: $boardId, extId: $extId) { id title descriptionHtml extId firstPublishedTsSec locations { id extId name city isoCountry isRemote } job { id locationType employmentType requisitionId teamDisplayName department { id extId name } } compensationHtml } }"}' https://jobs.gem.com/api/public/graphql
```
### Eightfold
Verified for Infineon only; the suggested `/api/apply/v2/jobs` endpoint does not work there.
One method: the PCSX search API is the same on any Eightfold career site (inferred; only Infineon tested). Infineon fronts Eightfold with its own domain `jobs.infineon.com`, so the identifier is the company host plus the `domain` parameter (`infineon.com`, visible in the HTML as `domain=infineon.com`). Many customers use `{name}.eightfold.ai` instead (inferred).
Algorithm:
1. `GET https://{host}/api/pcsx/search?domain={domain}&query=&location=&sort_by=relevance&start={n}` returns `{"status":200,"data":{"positions":[...],"count":1292,"filterDef":{...}}}`. Ten positions per page; `num=100` is ignored (verified: 10 returned). `start=10` gives the next ten. `start=1285` gave the last 7 (verified).
2. `sort_by=timestamp` orders roughly by newest (first page timestamps descending, but the last page was not sorted), so early-stop is not reliable.
3. Position fields: `id`, `displayJobId`, `name`, `locations`, `standardizedLocations`, `postedTs`, `department`, `workLocationOption`, `positionUrl`.
4. Detail: `GET https://{host}/api/pcsx/position_details?position_id={id}&domain={domain}&hl=en` returns `data.jobDescription` (HTML), `publicUrl`, `efcustom*` fields.
5. robots.txt of jobs.infineon.com allows `/api/pcsx` and `/careers`, and disallows everything else. No sitemap (404).
6. `/api/apply/v2/jobs?domain=infineon.com&start=0&num=10` returns 403 `{"message":"Not authorized for PCSX"}`. Some other tenants may still allow it (inferred; not tested).
Identifier: host and `domain`; per role `id` (numeric, store as a string) or `displayJobId`.
Requests per poll: `ceil(total/10)`, so 130 for Infineon (about two minutes at one per second). Twice a day is fine, but this is the heaviest poll in the set. The `count` field lets you compare totals to skip work only when nothing changed (a changed total is not required for new roles, so this is only a hint).
Bot protection: none met. Unauthenticated JSON is served.
Worth a parser: moderate. Eightfold is used by large enterprises (Infineon and others); it is less common in European tech scale-ups and Nordic mid-caps (inferred). One company in this list, and paging cost is high, so build it only if you want large-enterprise coverage.
```
curl -m 20 -A "Mozilla/5.0 ..." 'https://jobs.infineon.com/api/pcsx/search?domain=infineon.com&query=&location=&sort_by=relevance&start=0'
curl -m 20 -A "Mozilla/5.0 ..." 'https://jobs.infineon.com/api/pcsx/position_details?position_id=563808971955206&domain=infineon.com&hl=en&queried_location=&triggered_by='
```
### Phenom
Verified for Just Eat Takeaway and Philips.
One method: yes. Both sites are Phenom "Career Connect" sites on the company's domain and answer the same `POST /widgets` call. Per-site parameters: `refNum` (in the HTML, `TAKEGLOBAL`, `PHILUS`), the locale path (`/global/en`, `/na/en`), `lang` (`en_global`, `en_na`), `country` (`global`, `na`) and `pageId` (`page11`/`page9-ds-migration` for JET, `page6` for Philips; the value in `phApp.pageId` on the page). The `pageId` I used for JET (`page11`) differs from the home page value (`page9-ds-migration`) and still worked, so it may not be critical (not tested with a wrong value).
Algorithm:
1. `POST https://{host}/widgets` with `Content-Type: application/json` and this body: `{"lang":"en_global","deviceType":"desktop","country":"global","pageName":"search-results","ddoKey":"refineSearch","sortBy":"","subsearch":"","from":0,"jobs":true,"counts":true,"all_fetch":false,"pageType":"landingPage","size":100,"clearAll":false,"jdsource":"facets","isSliderEnable":false,"pageId":"page11","siteType":"external","location":"","keywords":"","global":true,"selected_fields":{},"sort":{"order":"desc","field":"postedDate"},"locationData":{}}`.
2. Response: `refineSearch.totalHits` (103), `refineSearch.hits` (roles returned), `refineSearch.data.jobs[]`. Page with `from += size`. `from=100,size=10` returned the last 3 (verified). `size=200` returned all 103; `size=500` returned 500 of 865 on Philips (1.7 MB). `size=100` is the safe value.
3. Job fields: `title`, `jobSeqNo` (`TAKEGLOBALR053200ENGLOBAL`, used in the URL), `reqId`, `postedDate`, `city`, `country`, `cityStateCountry`, `descriptionTeaser`, `category`, `type`, `applyUrl`, `latitude`, `longitude`.
4. Role URL: `https://{host}/{country}/{lang}/job/{jobSeqNo}/{Title-With-Dashes}` (from the sitemap and detail page; the slug part is decorative, not tested). Detail page has JSON-LD JobPosting with `description` (HTML-escaped entities, decode twice), `datePosted`, `addressCountry`, `employmentType`, `identifier.value` (req id).
5. Cross-check: `sitemap.xml` under the locale path lists every job URL (JET: 103 `/job/` URLs of 191, equal to totalHits; Philips: `sitemap_index.xml` points at sitemap1 and sitemap2 with 500 and 376 job URLs, against 865 hits, so the sitemap includes some duplicates or other locales). A sitemap route (sitemap plus JSON-LD detail) works with no POST at all.
6. The `na` Philips site scopes to North America (306). To read all of Philips use `/global/en`. Whether per-country sites (`/de/de` etc.) exist as subsets is inferred.
Identifier: host, locale path, `refNum` and `pageId`; per role `jobSeqNo` (the `reqId` is not unique across languages; inferred).
Requests per poll: `ceil(total/100)`: 2 for JET (or 1 with size 200), 9 for Philips global. Descriptions need one detail page per new role.
Bot protection: none met from curl. The site sets cookies but the POST worked without any.
Worth a parser: yes. Phenom is common among large employers (Philips, JET here; many others in retail, pharma, industrials; inferred). Not typical for Nordic small companies. Two companies in this list, both large, so the return is good.
```
curl -m 20 -A "Mozilla/5.0 ..." -X POST -H 'Content-Type: application/json' -H 'Origin: https://careers.justeattakeaway.com' --data @body.json https://careers.justeattakeaway.com/widgets
curl -m 20 -A "Mozilla/5.0 ..." https://careers.justeattakeaway.com/global/en/sitemap.xml
curl -m 20 -A "Mozilla/5.0 ..." https://www.careers.philips.com/global/en/sitemap_index.xml
curl -m 20 -A "Mozilla/5.0 ..." https://careers.justeattakeaway.com/global/en/job/TAKEGLOBALR053200ENGLOBAL/Corporate-Affairs-Specialist
```
(`body.json` is the body from step 1, with `pageId` `page6` for Philips.)
### Welcome to the Jungle
Verified for Yousign/Youtrust.
One method: yes. All companies live in a shared Algolia index, so the identifier is the organization slug. The app's slug is stale here (`yousign` yields 0; `youtrust` yields 12), so slugs need to be taken from the company's `welcometothejungle.com/en/companies/{slug}/jobs` URL, and that URL can change on rebrand.
Algorithm:
1. `GET https://www.welcometothejungle.com/en/companies-v1/{slug}/jobs` (the `/en/companies/{slug}/jobs` URL answers 200 but only contains a meta refresh to `companies-v1`). The HTML embeds a JSON config with `ALGOLIA_APPLICATION_ID` (`CSEKHVMS53`), `ALGOLIA_API_KEY_CLIENT` (`<redacted>`, a search-only key that the site itself ships to every visitor) and `ALGOLIA_JOBS_INDEX_PREFIX` (`wttj_jobs_production`). Re-read these from the page if the key rotates instead of hard-coding them.
2. `POST https://CSEKHVMS53-dsn.algolia.net/1/indexes/wttj_jobs_production_en/query` with headers `X-Algolia-Application-Id`, `X-Algolia-API-Key`, `Content-Type: application/json`, `Origin: https://www.welcometothejungle.com` and body `{"query":"","filters":"organization.slug:{slug}","hitsPerPage":100,"page":0}`. Response has `nbHits` (12), `nbPages`, `hits[]`. Page with `page += 1` while `page < nbPages`.
3. The index suffix is the display language (`_en`, `_fr` exist; `_de` does not). The `_en` and `_fr` indices return the same 12 roles with the same `reference` UUIDs, so read one index only.
4. A free-text query for "youtrust" matched 16 hits, including other companies' roles, so always filter by `organization.slug`.
5. Hit fields: `name`, `slug`, `reference` (UUID), `published_at`, `offices[]`, `remote`, `contract_type`, `salary_*`, `summary`, `key_missions`, `profile`, `organization`. Full description text is not in the hit; the job page carries JSON-LD JobPosting with `description`, `datePosted`, `baseSalary`, `jobLocation` (fetched, 200).
6. Role URL: `https://www.welcometothejungle.com/en/companies/{orgSlug}/jobs/{slug}`.
Identifier: organization slug; per role `reference` (UUID) or `slug`.
Requests per poll: 1 (plus 1 page load to refresh the key if it is not cached), plus a detail page per new role if the full description is wanted.
Bot protection: none met on Algolia. The WTTJ pages answer normal GETs. Algolia's public key is search-only, and its use is limited to what the site does itself. Keep volume low.
Worth a parser: only if French or Southern European companies matter. WTTJ is widely used by French companies and increasingly by other European ones as an aggregator, and many of those also use another ATS underneath (inferred). One company in this list. Note that a company can appear on WTTJ without its real ATS being WTTJ, and some companies have no roles there.
```
curl -m 20 -A "Mozilla/5.0 ..." https://www.welcometothejungle.com/en/companies-v1/yousign/jobs
curl -m 20 -A "Mozilla/5.0 ..." -X POST -H 'X-Algolia-Application-Id: CSEKHVMS53' -H 'X-Algolia-API-Key: <redacted>' -H 'Content-Type: application/json' -H 'Origin: https://www.welcometothejungle.com' --data '{"query":"","filters":"organization.slug:youtrust","hitsPerPage":100,"page":0}' 'https://CSEKHVMS53-dsn.algolia.net/1/indexes/wttj_jobs_production_en/query'
```
## Summary of recommendations
| Host | Readable without a browser | Effort | Companies here | Recommendation |
|---|---|---|---|---|
| Pinpoint | yes, 1 GET | trivial | 2 | build |
| BambooHR | yes, 1 GET plus detail | trivial | 1 | build |
| Gem | yes, 1 POST (GraphQL) | small | 2 | build |
| Oracle Recruiting Cloud | yes, 1 GET | small | 1 | build (cleanest API; only 1 company) |
| Phenom | yes, 1 POST or sitemap | small | 2 | build |
| iCIMS classic / TalentBrew | yes, sitemap plus JSON-LD detail | small, shared | 1 (Mambu) plus Arm | build the generic "sitemap plus JSON-LD" reader |
| Jibe | yes, 1 to 2 GETs | trivial | 1 (Booking) | optional; cheap once JSON-LD reader exists |
| Eightfold PCSX | yes, but 10 per page | medium (130 requests for Infineon) | 1 | build only if large enterprises matter |
| Welcome to the Jungle | yes, Algolia | small | 1 | optional; slug staleness is the main risk |
What I verified by a live request: every listing endpoint named in the table, every paging claim marked verified above, the detail endpoints for Oracle, BambooHR, Pinpoint (page), iCIMS (page), Gem, Eightfold, Phenom (page) and the WTTJ job page. What I only infer: multi-page behaviour of classic iCIMS and BambooHR/Pinpoint on large boards, the Oracle job URL pattern, other Eightfold tenants allowing `/api/apply/v2/jobs`, whether Gem requires Origin/Referer headers, how widespread each host is, and how long the WTTJ Algolia key stays valid.
+60
View File
@@ -0,0 +1,60 @@
# Own-site batch 1: how each career site can be read
31 companies, all classified from live responses (2026-09-29). Full data is in `out-own-1.json`.
## Counts per class
| class | n | companies |
|---|---|---|
| known-host | 9 | ada-health (greenhouse, 0 roles), dfds (teamtailor x11 subdomains), lunar (teamtailor), idealista (teamtailor), checkout-com (ashby), skyscanner (ashby), tomtom (lever EU), whereby (lever, 0 roles), otovo (recruitee) |
| new-host | 8 | pandora, terma, universal-robots, volvo-cars (all SAP SuccessFactors), siemens (avature), microsoft (eightfold), king (phenom), sinch (oracle recruiting cloud) |
| own-api | 4 | dynatrace (Coveo proxy), new-work (Algolia), relex-solutions (WordPress REST), vinted (Next.js data with Greenhouse records) |
| html | 5 | check24, zalando, bolt, lucca, bird |
| jsonld | 2 | sophia-genetics, aiven |
| browser | 1 | meta |
| none | 2 | wefox, unbabel |
## Counts per host
- successfactors: 4 (pandora `pandoraas`, terma `termaas`, universal-robots via Teradyne `teradynein`, volvo-cars `C0000870892P`)
- teamtailor: 3 clean (lunar, idealista, dfds with 11 country boards); unbabel has a dangling Teamtailor custom domain
- ashbyhq: 2 (checkout-com slug `checkout.com`, skyscanner slug is a UUID)
- lever: 2 (tomtom on the EU instance, whereby)
- greenhouse: 1 clean (ada-health, empty); vinted and aiven show Greenhouse traces but no board token was found
- avature, eightfold, phenom, oracle recruiting cloud: 1 each
- recruitee: 1 (otovo)
Discovery misses worth fixing in the app: Lever EU (`api.eu.lever.co`), custom domains for Teamtailor and Recruitee (`careers.<domain>`), an Ashby slug that contains a dot, an Ashby slug that is a UUID visible only in a JS chunk, and Greenhouse boards linked from a button rather than from the page source.
## New hosts and how the listing is read
**SAP SuccessFactors (career5 / career2 / career41.sapsf.com).** All four companies expose the standard public XML feed `https://<careerN host>/career?company=<id>&career_ns=job_listing_summary&resultType=XML`, which returns every requisition as a `<Job>` element with title, description, req id and dates in one response (0.3 to 5 MB). Verified: pandora 583 roles, terma 104, volvo-cars 40 (matches its sitemap and the "of 40" search text), teradyne 486 in total. The company id comes from the `company=` parameter in the apply or register links on the career page (`jobs.volvocars.com`, `jobs.teradyne.com` and the Terma page carry it). For Universal Robots the feed is the whole Teradyne group; UR roles are the 30 sitemap URLs under `/Universal-Robots/job/` of `jobs.teradyne.com`, so a filter on that path or the business-unit field is needed. Pandora's own site is a Paradox.ai template over the same data.
**Avature (jobs.siemens.com, portal 144).** The list page `/en_US/externaljobs/SearchJobs` is server-rendered but shows 6 rows per page and "999+ results". An RSS feed at `/en_US/externaljobs/SearchJobs/feed/` returns 20 `<item>` elements with job links; `jobOffset` and `jobRecordsPerPage` did not change the result, so the feed alone cannot enumerate Siemens' roles. The sitemap lists only static pages. Job pages have no JobPosting JSON-LD. A reader would have to page the HTML search or use filter URLs; not solved.
**Eightfold (apply.careers.microsoft.com).** `GET /api/pcsx/search?domain=microsoft.com&query=&start=0&num=10` returns JSON with `data.positions` and `data.count` (2319 seen). It needs no login, but the first call returned 429 and other paths (`/api/apply/v2/jobs`) return 403 "Not authorized for PCSX", so it must be polled slowly with a normal browser User-Agent. Paging is by `start` and `num`. Location filters go in extra query parameters.
**Phenom (careers.king.com).** POST `https://careers.king.com/widgets` with the JSON body the site's own script sends (`ddoKey: refineSearch`, `pageName: search-results`, `size`, `from`, `jobs: true, counts: true`, `country: us`, `lang: en_us`) returns `refineSearch.totalHits` (33) and the job objects. The sitemap `/sitemap.xml` also lists the 33 `/job/` URLs. `refNum` is `ACMKDSUS`.
**Oracle Recruiting Cloud (iaings.fa.ocs.oraclecloud.com, site SinchCareer).** `GET /hcmRestApi/resources/latest/recruitingCEJobRequisitions?onlyData=true&finder=findReqs;siteNumber=CX_1,limit=25,offset=0` returns JSON with `TotalJobsCount` (79) and a `requisitionList`; page with `offset`. The site number `CX_1` is on the candidate-experience page as `data-sitenumber`. Sinch's own pages give no link to this site; it was found by web search, and Sinch also has an empty Workable account.
## Own-site notes
- dynatrace: `POST /api/coveo/search/` with `{"q":"","numberOfResults":1000}` gives `totalCount` 108 and the results; the sitemap and JobPosting JSON-LD are a fallback.
- new-work: the given `new-work.se/en/career` is a stub; `corporate.xing.com/en/career` ships `window.algoliaSettings` (public search key, app `4TACNCQ35A`, index `new-work-se-live-en`). The query only works with a `Referer` of the corporate site; 17 job hits with `filters: type:Job`.
- relex-solutions: standard WordPress REST `wp-json/wp/v2/job`, 43 items (`X-WP-Total`).
- vinted: `careers.vinted.com/jobs` embeds 201 Greenhouse-EU job records (`internal_job_id`, `gh_jid`) in an 8.9 MB page; the board token was not found (`boards-api.greenhouse.io` 404 for four guesses).
- dfds: `/api/trpc/careers.getPostings` aggregates 158 postings whose links point to per-country Teamtailor boards.
- tomtom, checkout-com: the site proxies Lever EU and Ashby respectively; the vendor APIs work directly.
## Not classified cleanly
- wefox: Wix site, careers under `careers-archiv`, no role list in the HTML, JOIN board 404. `none` with the caveat that a Wix-rendered widget could not be ruled out.
- unbabel: careers domain CNAMEs to Teamtailor but does not serve (TLS mismatch, 421), the main site moved to TransPerfect infrastructure, the Workable account is empty.
- meta: every careers HTML route returns a 400 error page to curl; the sitemap has no role URLs. `jobs_url` is the well-known `/jobsearch`, not verified by response.
- idealista: `www.idealista.com` is behind DataDome (captcha page); `careers.idealista.com` was tried directly and is Teamtailor, but the link from the main site could not be seen.
- sinch: see above; the connection to the Oracle site is by web search only.
## Method notes
One request per second per host, `curl -m 20 -L`, browser User-Agent, no login. The Algolia call for new-work used a Referer header matching the site that ships the key. Scratch files are in `wo1/` next to this note.
+47
View File
@@ -0,0 +1,47 @@
# Own-site career pages, batch 2 (30 companies)
Every request was a live curl on 2026-09-29. Machine-readable results are in out-own-2.json.
## Counts per class
| class | n | companies |
|---|---|---|
| known-host | 12 | mews, cognigy, solaris, airtame, automattic, metacore, rovio, vivino, manomano, dexter-energy, glovo, schibsted |
| new-host | 10 | zeiss, danske-bank, seaborg, depop, onfido, snyk, tink, allegro, einride, klarna |
| own-api | 3 | maersk, bending-spoons, amazon |
| jsonld | 1 | odoo |
| browser | 3 | adjust, personio, tradeshift |
| none | 1 | wetransfer |
## Counts per host (primary host of each company)
- greenhouse.io: 6 (mews `mewssystems`, cognigy `nice` filtered, solaris `solarisbank`, airtame `airtamejobs`, automattic `automatticcareers`, metacore `metacore`)
- teamtailor: 3 (vivino, manomano, schibsted; vivino and manomano on custom domains)
- lever.co: 1 (rovio `rovio-2`); smartrecruiters.com: 1 (glovo, via the `DeliveryHero` board); recruitee.com: 1 (dexter-energy `dexterenergyservices`)
- myworkdayjobs.com: 5 (zeiss, depop, onfido, snyk, tink); Maersk also uses Workday and SAP behind its own API
- oraclecloud.com: 1 (danske-bank); hr-manager.net: 1 (seaborg); jobylon.com: 1 (einride; schibsted has a second Jobylon feed); successfactors: 1 (allegro); jobs.deel.com: 1 (klarna)
- own site: odoo, maersk, bending-spoons, amazon, wetransfer (via parent)
- not readable by curl: adjust and personio (Vercel checkpoint), tradeshift (list source unknown)
## How each new-host listing is read
**Workday (myworkdayjobs.com).** POST JSON to `https://<tenant>.<wdN>.myworkdayjobs.com/wday/cxs/<tenant>/<site>/jobs` with `{"appliedFacets":{},"limit":20,"offset":0,"searchText":""}`. The response has `total` and `jobPostings` with `title`, `externalPath`, `locationsText`; no login or cookie was needed. Verified for zeiss (`zeissgroup.wd3`, site `External`, 847), depop (`etsy.wd5`, site `Depop_Careers`, 20), onfido (`entrust.wd1`, site `EntrustCareers`, 81), snyk (`snyk.wd103`, site `External`, 21) and tink (`visa.wd5`, site `Visa`, 760). Onfido and Tink are inside their acquirer's board and can only be separated by `searchText` or location facets. The tenant of zeiss, onfido and depop was found through web search, not from the company page (zeiss and onfido pages are a JS widget and a Cloudflare challenge respectively).
**Oracle Recruiting Cloud (danske-bank).** Public REST without login: `GET https://ejqi.fa.ocs.oraclecloud.eu/hcmRestApi/resources/latest/recruitingCEJobRequisitions?onlyData=true&finder=findReqs;siteNumber=CX_1001,limit=25,offset=0` returns `items[0].TotalJobsCount` (135) and `items[0].requisitionList`. Job pages are `https://ejqi.fa.ocs.oraclecloud.eu/hcmUI/CandidateExperience/en/sites/CX_1001/job/<id>`. Only `limit=1` was requested, so paging with larger limits is not tested.
**HR Manager / Talentech (seaborg).** `GET https://api.hr-manager.net/JobPortal.svc/<customer>/PositionList/rss/?incads=true` returns an RSS channel; customer is `seaborg_tr`. It returned a valid channel with zero items, matching the portal's "no positions" text. Item format was therefore not seen. Denmark and Norway use this host for many companies, so the reader is probably reusable.
**SAP SuccessFactors (allegro).** Career site on a custom domain (`careers.allegro.eu`, tenant `career55.sapsf.eu`, company `allegrospz`). `GET https://careers.allegro.eu/sitemap.xml` lists every job as `https://careers.allegro.eu/job/<slug>/<id>/` (312 seen), and a job page carries JSON-LD `JobPosting`. The candidate-facing `career55.sapsf.eu/career?...` page is a sign-in shell. The SmartRecruiters company `Allegro` remains but only holds a notice that the company moved to SAP.
**Jobylon (einride).** No JSON found. The widget iframe `GET https://cdn.jobylon.com/jobs/companies/<company_id>/embed/v2/?target=jobylon-jobs-widget&page_size=50` (company id 3143) is HTML that assigns `JBL.embed_v2['jobs'] = [ {id: '...', url: '/jobs/<id>-<slug>/', ...}, ...]` (33 entries), which can be parsed. Jobylon also has per-company feeds of the form `https://feed.jobylon.com/feeds/<uuid>/?format=json`, but the uuid is set by the company; Schibsted's public feed (`41f7d609-c6ba-4fc0-9032-dcb01f8db52d`, 4 postings) is in its theme bundle and works without login. No feed uuid was found for Einride.
**Deel job board (klarna).** `https://jobs.deel.com/<slug>` (slug `klarna`) is a Next.js page whose server payload contains `"jobPostings":[{"id":...,"jobId":...,"title":...}]` (95 entries); job pages `https://jobs.deel.com/klarna/job-details/<uuid>/overview` carry JSON-LD `JobPosting`. No public JSON API was found. Whether the list is paginated beyond the 95 was not tested.
## Things to know before building
- Slugs that differ from the company name (naive slug guessing fails): mews -> `mewssystems`, solaris -> `solarisbank`, airtame -> `airtamejobs`, automattic -> `automatticcareers`, rovio -> `rovio-2`, dexter-energy -> `dexterenergyservices`, cognigy -> shared `nice` board with a metadata filter (field id 4952164101 = Cognigy).
- Glovo roles are a subset of the Delivery Hero SmartRecruiters board (987 roles); the 270 Glovo-only roles were seen only on careers.glovoapp.com through a WordPress `admin-ajax.php` action.
- Maersk's list API returns 401 unless a constant `Consumer-Key` header (taken from the site's JS) is sent; the app owner should decide whether that is acceptable.
- Companies now inside another one: onfido (Entrust), tink (Visa), wetransfer (Bending Spoons), cognigy (NICE), adjust (AppLovin, unverified), seaborg (now Saltfoss).
- automattic.com answered 403 to a Chrome-like User-Agent but 200 to `Mozilla/5.0`; other sites blocked curl outright: adjust.com and personio.com (Vercel Security Checkpoint, HTTP 429), allegro.pl (DataDome), entrust.com, manomano.fr and rovio.com feed (Cloudflare), depop.com (403).
- The `jobs_url` for automattic is the Greenhouse board, because `automattic.com/work-with-us/jobs/` currently shows only a scam warning and no roles.
+73
View File
@@ -0,0 +1,73 @@
# Own-site career survey, batch 3 (30 companies)
Probed 2026-09-29 with curl only. All figures below come from live responses unless marked as inferred.
## Counts per class
| class | n | companies |
|---|---|---|
| known-host | 11 | enpal, soundcloud, idealo, travelperk, swappie, raspberry-pi, starling-bank, prima, bol, paradox-interactive, trustly |
| new-host | 12 | prisma, coloplast, dixa, mobile-industrial-robots, simcorp, tryg, zenegy, ovhcloud, nokia, vipps-mobilepay, outsystems, ericsson |
| html | 4 | auto1-group, apple, asml, framer |
| browser | 2 | silverfin, hashicorp |
| none | 1 | featurespace |
| own-api, jsonld | 0 | |
## Counts per host
| host | n | companies |
|---|---|---|
| ashbyhq.com | 3 | enpal (150), travelperk/perk (126), trustly (22) |
| greenhouse.io | 2 | soundcloud (soundcloud71, 14), bol (bolcom, 30) |
| teamtailor.com | 2 | swappie (0 open), paradox-interactive (17) |
| workable.com | 2 | raspberry-pi (raspberrypi, 4), starling-bank (106) |
| lever.co | 1 | prima (EU region, 98) |
| recruitee.com | 1 | idealo (idealocareer, 21) |
| successfactors (RMK career sites) | 4 | coloplast (313), tryg (38), ovhcloud (82), mobile-industrial-robots (1, via jobs.teradyne.com/MiR) |
| myworkdayjobs.com | 2 (+1 behind ASML) | simcorp (270), outsystems (91); ASML's own site is fed by Workday tenant asml |
| rippling.com | 1 | prisma (2) |
| hibob.com | 1 | dixa (2) |
| hr-on.com | 1 | zenegy (2) |
| jobylon.com | 1 | vipps-mobilepay (0 open) |
| oraclecloud.com | 1 | nokia (602) |
| eightfold.ai | 1 | ericsson (632) |
Two findings the discovery step should take into account:
- Prima is on the **EU region of Lever**. `api.lever.co/v0/postings/prima` returns 404, `api.eu.lever.co/v0/postings/prima?mode=json` returns 98 postings. The Lever reader must try the EU host.
- Three companies use a Teamtailor/Recruitee/Ashby site on a **custom domain** (swappie `careers.swappie.com`, paradox `career.paradoxplaza.com`, idealo `jobs.idealo.com`), so host matching by `*.teamtailor.com` misses them; the vendor shows in the page (`app.teamtailor.com/companies/...`, `jobs.idealo.com/api/offers/`).
## new-host: how each listing is read
**Rippling** (prisma). The careers page shows "Loading roles" and its JS chunk calls `GET https://api.rippling.com/platform/api/ats/v1/board/prisma-careers/jobs`, which returns a plain JSON array of `{uuid, name, department{label}, workLocation{label}, url}` with no auth. Identifier is the board slug (`prisma-careers`). Only 2 general-application roles at the time.
**SuccessFactors Recruiting Marketing (RMK) career sites** (coloplast, tryg, ovhcloud, MiR via Teradyne). Custom domains (`careers.coloplast.com`, `careers.tryg.com`, `careers.ovhcloud.com`, `jobs.teradyne.com/MiR/`) backed by `career5.successfactors.eu` or `career41.sapsf.com`. The list `/search/?q=` is server-rendered HTML (25 per page, "Results 1 - 25 of 313"), and `/sitemap.xml` lists every job URL `/job/<city>-<title>/<id>/` (coloplast 313, tryg 38, teradyne 487 of which 1 under `/MiR/`). Job pages are HTML; JSON-LD was not checked. The sitemap is the cheapest enumeration; OVH has no sitemap (404) but shows all 82 rows on one page.
**Workday** (simcorp, outsystems; ASML underneath). `POST https://<tenant>.<wdN>.myworkdayjobs.com/wday/cxs/<tenant>/<site>/jobs` with body `{"appliedFacets":{},"limit":20,"offset":0,"searchText":""}` returns `total` and `jobPostings` (title, externalPath, locationsText, postedOn). Identifiers: simcorp/wd3/SimCorp_Jobs (270), outsystems/wd503/OutSystems (91). ASML has several sites (ASMLBERLIN answered 15, site "ASML" is 404), so its own sitemap `/api/job-posting-sitemap` (629 English URLs) is the better route.
**HiBob** (dixa). `GET https://<sub>.careers.hibob.com/api/job-ad` with header `companyIdentifier: <sub>` returns JSON `jobAdDetails[]` (id, title, department, site, employmentType, description, publishedAt) plus `filterGroups`. Without the header it answers 401. Dixa has 2 "Expression of interest" ads only.
**HR-ON** (zenegy). `zenegy.com/jobs` embeds `recruit.hr-on.com/frame-api/customers/zenegyaps.js` (companyId 679), which frames `https://zenegyaps.hr-on.com/`. That page is server-rendered HTML with `show-job/<id>` links; no JSON-LD, sitemap, RSS or feed (all 404). Needs a small HTML parser; 2 links seen (one an unsolicited application).
**Jobylon** (vipps-mobilepay). Company page `https://emp.jobylon.com/companies/1056-vipps-mobilepay/` injects the list through `https://cdn.jobylon.com/jobs/companies/1056/embed/v1/?target=x`, a JS file that carries the job list as an HTML fragment (`jobylon-job-list`). No JSON API found (`/api/companies/1056/jobs/` is 404); the customer XML/JSON feed needs a private key. Currently "There are currently no jobs".
**Oracle Recruiting Cloud** (nokia). `jobs.nokia.com/en/sites/CX_1` is the Candidate Experience UI. The custom domain redirects REST calls to the pod, so call `https://fa-evmr-saasfaprod1.fa.ocs.oraclecloud.com/hcmRestApi/resources/latest/recruitingCEJobRequisitions?onlyData=true&expand=requisitionList&finder=findReqs;siteNumber=CX_1,limit=25,offset=0`; `items[0].TotalJobsCount` was 602 and `items[0].requisitionList` holds the page.
**Eightfold** (ericsson). `https://jobs.ericsson.com/api/pcsx/search?domain=ericsson.com&query=&start=0&num=10` returns JSON `data.positions[]` and `data.count` (632); page size is capped at 10, paged by `start`. `/api/apply/v2/jobs` answers 403 "Not authorized for PCSX".
## html and browser notes
- auto1-group: server-rendered list (15 per page, 564 jobs), per-country job sitemaps `sitemap-jobs-<cc>.xml`, job pages carry schema.org microdata `itemtype=JobPosting` (not JSON-LD).
- apple: `jobs.apple.com` per-locale sitemaps (`sitemap-jobs-en-de.xml` has 118); job pages embed the record in a hydration payload, no JSON-LD.
- asml: sitemap plus `__NEXT_DATA__` on every job page (contains applyUrl, datePosted, location).
- framer: Framer CMS, role rows rendered server-side, 8 seen.
- silverfin: Cloudflare challenge (403); hashicorp: Vercel Security Checkpoint (429), roles now on IBM careers (Avature), which returned an empty 202. Both need a browser or were not read.
- featurespace: now a Visa-branded site (Visa logo, Visa product news); `/careers` is an empty shell.
## Not verified by a live request (inferred)
- raspberry-pi: the link from raspberrypi.com/careers to Workable comes from web search (the site is behind Cloudflare); the Workable account `raspberrypi` was read live.
- hashicorp: the move of roles to IBM careers is from web search; the Avature host `ibmglobal.avature.net` appeared in careers.ibm.com's sitemap.
- featurespace: acquisition by Visa is inferred from page branding.
- starling-bank: the embed source on the careers page is client-side and was not seen; the Workable account `starling-bank` was matched by its identical intro text.
- paradox-interactive: paradoxinteractive.com answers HTTP 406 to any Mozilla User-Agent and only worked with curl's default UA; the roles host career.paradoxplaza.com was reached with the default UA as well.
+55
View File
@@ -0,0 +1,55 @@
# Own-site career boards, batch 4 (30 companies)
Survey done 2026-09-29 with curl only. Every class below rests on a response received in this run, except where a note says otherwise.
## Counts per class
| class | n | companies |
|---|---|---|
| known-host | 17 | bosch, jimdo, quantum-systems, taxfix, tado, contractbook, deezer, ubisoft, wallbox, satispay, backbase, sendcloud, wise, remote, hemnet, sana, voi |
| new-host | 3 | kmd, dnb (both SuccessFactors), umbraco (HR-ON) |
| own-api | 3 | siteimprove, ørsted, nordea |
| html | 6 | google, google-deepmind, ableton, netcompany, shopify, visma |
| browser | 1 | revolut (Cloudflare managed challenge) |
| jsonld, none | 0 | |
## Counts per host (the host that serves the roles)
- teamtailor 5: contractbook (careers.scrive.com), deezer, sendcloud (jobs.sendcloud.com), hemnet (career.hemnet.se), voi (careers.voi.com). Three of them run on a custom domain, so a Teamtailor reader that assumes `<slug>.teamtailor.com` only works for deezer, sendcloud and hemnet (subdomain verified 200), not contractbook (scrive.teamtailor.com is 404) and voi (voi.teamtailor.com is 404).
- ashbyhq.com 4: jimdo (`jimdo.com`), taxfix (`taxfix.com`), satispay, sana (`sana-roles`). Slugs are not always the bare company name.
- smartrecruiters.com 3: bosch (`BoschGroup`), ubisoft (`Ubisoft2`), wise (`Wise`).
- greenhouse.io 2: backbase (`workatbackbase`), remote (`remotecom`).
- successfactors 2 (new-host): kmd, dnb; nordea also sits on SuccessFactors underneath its own API.
- recruitee.com 1 (quantum-systems, custom domain), personio 1 (tado), workable.com 1 (wallbox, 0 jobs).
- hr-on.com 1 (umbraco).
- Own sites: google and google-deepmind (same Google Careers system), ableton, netcompany, siteimprove, ørsted, nordea, shopify, visma.
## new-host: how each listing is read
### SuccessFactors career sites (kmd, dnb; also nordea underneath)
Both boards are SAP SuccessFactors "jobs2web" sites on a company domain (`jobs.kmd.net`, `jobb.dnb.no`; nordea: `careers.nordea.com`), with the classic URL shape `/job/<City>-<Title>-<code>/<numeric id>/`. What was verified:
- `/sitemap.xml` on the company host lists every job URL: 12 for `jobs.kmd.net` (matches the 12 vacancies in KMD's own Umbraco JSON), 18 for `jobb.dnb.no`, 176 for `careers.nordea.com`. DNB's sitemap holds duplicates per location, and its `/search/` page reports only 2 for the default language filter, so the sitemap is the better source.
- A job page (checked for kmd and dnb) contains a JSON-LD `JobPosting`.
- No JSON API was tried. Reading a board is therefore: fetch the sitemap, fetch each new URL, parse the JSON-LD. The SuccessFactors probe done by others may replace this.
### HR-ON (umbraco)
Umbraco's own page embeds an HR-ON widget (`div#hrskyen`, "e-Recruitment by HR-ON") loaded lazily by JavaScript. The public board is `https://umbraco.hr-on.com/` (Danish HR-ON e-recruitment, tenant `umbraco`), a server-rendered HTML page with role links of the form `/show-job/<id>`. Verified: the page loads without JavaScript, `/feed` and `/rss` are 404, and a detail page has no JSON-LD. Today the list holds no real vacancy, only the unsolicited-application entry `show-job/67008`, so the parser could not be tested against a real role row. Reading it means an HTML parser for `show-job` links, and it should treat "only 67008" as zero roles. Not verified: whether other HR-ON tenants use the same markup (`hr-on.com/`, `hr-skyen.dk` redirect to the vendor site).
## Own-api endpoints found
- siteimprove: `GET https://marketingservices.siteimprove.com/api/utility/getjobs` returns a plain JSON array (10 roles: id, title, location, category, jobtype); detail page `/open-positions/position?id=<uuid>`.
- ørsted: `POST https://orsted.com/api/jobs/jobList` with a JSON body (fields `offset,start,length,item,countryFilterID,category,employmenttype,country,location,jobtitle`; ids copied from the page's `.career-list` data attributes); `recordsTotal` 53. GET returns 405, and a request without a `Referer` got an Azure WAF 403 once.
- nordea: `GET https://www.nordea.com/en/api/jobs-list?page=N` (10 per page, `count` 175); every hit carries `field_ad_url` to the SuccessFactors job page.
## Notes worth knowing before building
- google and google-deepmind: server-rendered list at `/about/careers/applications/jobs/results/?company=DeepMind&location=...&page=N`, 20 links per page, the total is stated as "Showing 1 to 20 of N rows" (DeepMind 84, Zurich 46). Job pages carry no JSON-LD and there is no jobs sitemap. Roles are also inside `AF_initDataCallback` blobs.
- shopify: `/careers` lists 36 postings server-side; the boards are Ashby (`?ashby_jid=`), but slugs shopify, Shopify and shopify.com are all 404 on the Ashby posting API, so no ATS slug was found. Job pages hold the JobPosting object only inside serialized page data.
- visma: a Webflow list of 55 positions, each linking to a subsidiary board (Lever, Teamtailor, Recruitee, Jobylon, karriere.vismaenterprise.no, werkenbij.*, finn.no, peple.nl). It is a link aggregator, not one ATS.
- netcompany: 174 links `/job/<REF>-<City>/`, one per role and city; no JSON-LD.
- Discovery misses worth generalising: bosch, ubisoft, wise, backbase and deezer sit behind a company-branded front (jobs.bosch.com, ubisoft.com search, wise.jobs on Attrax, a Webflow page, deezerjobs.com) that only shows the ATS through link targets or job ids. In four cases the ATS host appeared in a job link or a JSON-LD/`ashby_jid` parameter, not on the careers home page.
- wallbox: the only board found (Workable `wallbox`) has 0 jobs and wallbox.com/careers is a 500, so it may be stale.
- Blocks met: revolut.com (Cloudflare challenge on every path), hemnet.se and voi.com/careers (403), deezerjobs.com detail pages (Cloudflare 403), satispay.com (302 to its 404 page for every path from curl). None was worked around.
+145
View File
@@ -0,0 +1,145 @@
[
{
"key": "milestone-systems",
"name": "Milestone Systems",
"domain": "milestonesys.com",
"careers_url": "https://www.milestonesys.com/careers/",
"ats": "oracle",
"ats_slug": "",
"country": "DK",
"city": "Brøndby",
"status": "researching"
},
{
"key": "configit",
"name": "Configit",
"domain": "configit.com",
"careers_url": "https://configit.com/about/careers/",
"ats": "bamboohr",
"ats_slug": "",
"country": "DK",
"city": "Copenhagen",
"status": "researching"
},
{
"key": "xeneta",
"name": "Xeneta",
"domain": "xeneta.com",
"careers_url": "https://www.xeneta.com/",
"ats": "pinpoint",
"ats_slug": "",
"country": "NO",
"city": "Oslo",
"status": "researching"
},
{
"key": "native-instruments",
"name": "Native Instruments",
"domain": "native-instruments.com",
"careers_url": "https://www.native-instruments.com/pages/careers",
"ats": "pinpoint",
"ats_slug": "",
"country": "DE",
"city": "Berlin",
"status": "researching"
},
{
"key": "mambu",
"name": "Mambu",
"domain": "mambu.com",
"careers_url": "https://mambu.com/en/careers",
"ats": "icims",
"ats_slug": "",
"country": "DE",
"city": "Berlin",
"status": "researching"
},
{
"key": "booking-com",
"name": "Booking.com",
"domain": "booking.com",
"careers_url": "https://careers.booking.com",
"ats": "icims",
"ats_slug": "",
"country": "NL",
"city": "Amsterdam",
"status": "researching"
},
{
"key": "arm",
"name": "Arm",
"domain": "arm.com",
"careers_url": "https://careers.arm.com/",
"ats": "icims",
"ats_slug": "",
"country": "GB",
"city": "Cambridge",
"status": "researching"
},
{
"key": "sennder",
"name": "sennder",
"domain": "sennder.com",
"careers_url": "https://www.sennder.com/de/open-positions",
"ats": "gem",
"ats_slug": "",
"country": "DE",
"city": "Berlin",
"status": "researching"
},
{
"key": "productboard",
"name": "Productboard",
"domain": "productboard.com",
"careers_url": "https://www.productboard.com/careers/open-positions/",
"ats": "gem",
"ats_slug": "",
"country": "CZ",
"city": "Prague",
"status": "researching"
},
{
"key": "infineon",
"name": "Infineon",
"domain": "infineon.com",
"careers_url": "https://jobs.infineon.com/careers",
"ats": "eightfold",
"ats_slug": "",
"country": "DE",
"city": "Munich",
"status": "researching"
},
{
"key": "just-eat-takeaway-com",
"name": "Just Eat Takeaway.com",
"domain": "justeattakeaway.com",
"careers_url": "https://careers.justeattakeaway.com/global/en",
"ats": "phenom",
"ats_slug": "",
"country": "NL",
"city": "Amsterdam",
"status": "researching"
},
{
"key": "philips",
"name": "Philips",
"domain": "philips.com",
"careers_url": "https://www.careers.philips.com/na/en/",
"ats": "phenom",
"ats_slug": "",
"country": "NL",
"city": "Amsterdam",
"status": "researching"
},
{
"key": "yousign",
"name": "Yousign",
"domain": "yousign.com",
"careers_url": "https://youtrust.com/",
"ats": "welcometothejungle",
"ats_slug": "",
"country": "FR",
"city": "Paris",
"status": "researching"
}
]
+101
View File
@@ -0,0 +1,101 @@
[
{
"key": "novo-nordisk",
"name": "Novo Nordisk",
"domain": "novonordisk.com",
"careers_url": "https://www.novonordisk.com/careers/find-a-job.html",
"ats": "successfactors",
"ats_slug": "",
"country": "DK",
"city": "Bagsværd",
"status": "researching"
},
{
"key": "vestas",
"name": "Vestas",
"domain": "vestas.com",
"careers_url": "https://careers.vestas.com/search/?q=&locationsearch=",
"ats": "successfactors",
"ats_slug": "",
"country": "DK",
"city": "Aarhus",
"status": "researching"
},
{
"key": "demant",
"name": "Demant",
"domain": "demant.com",
"careers_url": "https://careers.demant.com",
"ats": "successfactors",
"ats_slug": "",
"country": "DK",
"city": "Smørum",
"status": "researching"
},
{
"key": "carlsberg",
"name": "Carlsberg",
"domain": "carlsberggroup.com",
"careers_url": "https://careers.carlsberg.com/",
"ats": "successfactors",
"ats_slug": "",
"country": "DK",
"city": "Copenhagen",
"status": "researching"
},
{
"key": "bang-olufsen",
"name": "Bang & Olufsen",
"domain": "bang-olufsen.com",
"careers_url": "https://www.bang-olufsen.com/de/de/story/careers",
"ats": "successfactors",
"ats_slug": "",
"country": "DK",
"city": "Struer",
"status": "researching"
},
{
"key": "systematic",
"name": "Systematic",
"domain": "systematic.com",
"careers_url": "https://jobs.systematic.com/search/?createNewAlert=false&amp;q=&amp;locationsearch=DE+%2B+AT+%2B+CH&amp;optionsFacetsDD_country=&amp;optionsFacetsDD_customfield2=",
"ats": "successfactors",
"ats_slug": "",
"country": "DK",
"city": "Aarhus",
"status": "researching"
},
{
"key": "scania",
"name": "Scania",
"domain": "scania.com",
"careers_url": "https://jobs.scania.com/go/Jobs-at-Scania/9096601/",
"ats": "successfactors",
"ats_slug": "",
"country": "SE",
"city": "Södertälje",
"status": "researching"
},
{
"key": "sap",
"name": "SAP",
"domain": "sap.com",
"careers_url": "https://careers.sap.com/",
"ats": "successfactors",
"ats_slug": "",
"country": "DE",
"city": "Walldorf",
"status": "researching"
},
{
"key": "signavio",
"name": "Signavio",
"domain": "signavio.com",
"careers_url": "https://careers.sap.com/",
"ats": "successfactors",
"ats_slug": "",
"country": "DE",
"city": "Berlin",
"status": "researching"
}
]
+134
View File
@@ -0,0 +1,134 @@
[
{
"key": "zendesk",
"name": "Zendesk",
"domain": "zendesk.com",
"careers_url": "https://www.zendesk.de/company/careers/",
"ats": "workday",
"ats_slug": "",
"country": "DK",
"city": "Copenhagen",
"status": "researching"
},
{
"key": "unity",
"name": "Unity",
"domain": "unity.com",
"careers_url": "https://unity.com/careers/positions",
"ats": "workday",
"ats_slug": "",
"country": "DK",
"city": "Copenhagen",
"status": "researching"
},
{
"key": "lego-group",
"name": "LEGO Group",
"domain": "lego.com",
"careers_url": "https://www.lego.com/de-de/careers",
"ats": "workday",
"ats_slug": "",
"country": "DK",
"city": "Billund",
"status": "researching"
},
{
"key": "saxo-bank",
"name": "Saxo Bank",
"domain": "home.saxo",
"careers_url": "https://www.home.saxo/about-us/careers",
"ats": "workday",
"ats_slug": "",
"country": "DK",
"city": "Copenhagen",
"status": "researching"
},
{
"key": "novonesis",
"name": "Novonesis",
"domain": "novonesis.com",
"careers_url": "https://www.novonesis.com/en/careers/jobs",
"ats": "workday",
"ats_slug": "",
"country": "DK",
"city": "Lyngby",
"status": "researching"
},
{
"key": "gn-group",
"name": "GN Group",
"domain": "gn.com",
"careers_url": "https://www.gn.com/",
"ats": "workday",
"ats_slug": "",
"country": "DK",
"city": "Ballerup",
"status": "researching"
},
{
"key": "equinor",
"name": "Equinor",
"domain": "equinor.com",
"careers_url": "https://www.equinor.com/careers",
"ats": "workday",
"ats_slug": "",
"country": "NO",
"city": "Stavanger",
"status": "researching"
},
{
"key": "axis-communications",
"name": "Axis Communications",
"domain": "axis.com",
"careers_url": "https://www.axis.com/de-de",
"ats": "workday",
"ats_slug": "",
"country": "SE",
"city": "Lund",
"status": "researching"
},
{
"key": "mister-spex",
"name": "Mister Spex",
"domain": "misterspex.com",
"careers_url": "https://corporate.misterspex.com/de/karriere/",
"ats": "workday",
"ats_slug": "",
"country": "DE",
"city": "Berlin",
"status": "researching"
},
{
"key": "darktrace",
"name": "Darktrace",
"domain": "darktrace.com",
"careers_url": "https://www.darktrace.com/careers",
"ats": "workday",
"ats_slug": "",
"country": "GB",
"city": "Cambridge",
"status": "researching"
},
{
"key": "criteo",
"name": "Criteo",
"domain": "criteo.com",
"careers_url": "https://careers.criteo.com/en/working-at-criteo/belonging-inclusion/",
"ats": "workday",
"ats_slug": "",
"country": "FR",
"city": "Paris",
"status": "researching"
},
{
"key": "red-hat",
"name": "Red Hat",
"domain": "redhat.com",
"careers_url": "https://www.redhat.com/en/jobs",
"ats": "workday",
"ats_slug": "",
"country": "CZ",
"city": "Brno",
"status": "researching"
}
]
+166
View File
@@ -0,0 +1,166 @@
# SAP SuccessFactors career sites: reading without a browser
Probed 2026-09-29 with curl and python3 urllib, Chrome User-Agent, at most 1 request/s per host, `-m 20` timeout, no login. About 330 requests in total. No 403, 429, captcha or bot wall was met. Everything below was verified by a live request unless marked "inferred".
## Result table
All 9 rows are SuccessFactors. 8 of 9 are readable with one parser: 7 are the RMK front end on their own host, Novo Nordisk turned out to have one too (`careers.novonordisk.com`), and Signavio is a keyword slice of SAP's site. Bang & Olufsen only links to the back end, which robots.txt disallows.
| Company | Human-facing jobs URL | Served by | Best listing method | Roles seen | Detail method | Verified | Note |
|---|---|---|---|---|---|---|---|
| Vestas | https://careers.vestas.com/search/?q=&locationsearch= | RMK (table layout, 10 per page) | `sitemap.xml` for ids (774) or `/search/?startrow=N` paging (states total) | 661 in search (en_GB), 774 in sitemap | job page microdata JobPosting: `datePosted`, `addressCountry` (ISO), `hiringOrganization`, title, description; no employmentType/salary/JSON-LD | yes | Sitemap is a superset: 113 extra ids are German/French postings of the same roles (e.g. Zistersdorf EN id ...033 and DE id ...933). Also `/googlefeed.xml` (8 MB RSS with descriptions, 774 items). |
| Demant | https://careers.demant.com/search/?q=&locationsearch= | RMK (tile layout, 10 per page) | `sitemap.xml` (308) or search paging | 308 in both, identical id sets | microdata: `datePosted`, `validThrough`, `streetAddress` = "Smørum, DK, 2765" (country is the 2-letter token), `hiringOrganization`; country name also in `data-careersite-propertyid="customfield4"` | yes | Job URLs carry a brand segment: `/demant/job/...`, `/audika_Poland/job/...`. Listing tile has ID (customfield2), Brand, Country, Location. |
| Carlsberg | https://careers.carlsberg.com/search/?q=&locationsearch= | RMK (tile layout, 10 per page) | `sitemap.xml` (105) | 68 in search en_GB, 105 in sitemap | microdata: `datePosted`, `validThrough`, `streetAddress` "Fredericia, DK", `hiringOrganization` | yes | 37 sitemap-only roles exist only in other locales (`locale=fr_FR` gave 16, `de_DE` 11, `sv_SE` 4, `fi_FI` 3 that the English search misses). Sitemap is the only complete list without looping locales. Brand segment in path (`/Kronenbourg/job/`). |
| Systematic | https://jobs.systematic.com/search/?q=&locationsearch= | RMK (table layout, 10 per page) | `sitemap.xml` (47) or search paging | 47 in both | microdata: `datePosted`, `streetAddress` "Bern, CH, 3008", `hiringOrganization`; no `itemprop=title` (use `og:title` or `<h1>`); no validThrough | yes | Given careers_url has a DE+AT+CH filter baked in; the base host lists all 47. |
| Scania | https://jobs.scania.com/search/?q=&locationsearch= | RMK (tile layout, 15 per page) | `sitemap.xml` (760) or search paging | 760 in both, identical id sets | microdata: `datePosted`, `validThrough`, `streetAddress` "Vilnius, LT, LT-02300", `hiringOrganization` | yes | Given careers_url `/go/Jobs-at-Scania/9096601/` is a landing page of the same site; `/search/` on the host works. Tile has location, work area, full/part time, permanent/temporary, date. |
| SAP | https://careers.sap.com/search/?q=&locationsearch= | RMK (table layout, 25 per page, no date column) | `sitemap.xml` is an RSS/Google-Base feed with descriptions: 921 items in one request (1.8 MB gzipped, 15 MB raw); or search paging (33 requests) | 815 in search, 921 in feed | microdata: `datePosted` (has time), `streetAddress` "SANTIAGO DE SURCO, PE, 0033", `hiringOrganization`, `industry`; page is 235 KB | yes | Feed items: `<link>`, `<guid>`/`<g:id>`, `<title>` with "(City, CC, zip)", `<g:location>`, `<g:job_function>`, `<g:expiration_date>` (no posting date). 106 extra items are other-locale postings. Search ignores the date sort. |
| Signavio | https://careers.sap.com/ (same site as SAP) | same as SAP | `/search/?q=signavio` keyword search | 39 hits | as SAP | yes (as a slice) | No separate Signavio site. Only a keyword match on the title/description, so it is not an exact company filter. |
| Novo Nordisk | https://www.novonordisk.com/careers/find-a-job.html (AEM/Akamai, Vue widget) | Own AEM JSON servlet in front; real SF RMK site at `https://careers.novonordisk.com` | RMK `sitemap.xml` (419) or RMK search with 100 per page (5 requests); own JSON `GET /bin/nncorp/careersearch?keyword=&country=&category=&locale=en` returns all rows in one request | 419 RMK; 427 rows / 418 unique req ids in JSON API | RMK job page: HTML only (microdata JobPosting stripped; only `itemprop=title` and `description`), no JSON-LD. AEM job ad page `/content/nncorp/global/en/careers/find-a-job/job-ad.{jobId}.html` is HTML only (og:title, h1) | yes | JSON API has no dates and no URLs; `jobId` = "346501.en_GB" = SF requisition id. AEM job page location is text only. RMK job page location: `p#job-location span.jobGeoLocation` = "Bangalore, Karnataka, IN". See "Novo Nordisk" below. |
| Bang & Olufsen | https://www.bang-olufsen.com/de/de/story/careers | Only a link to SF back end `https://career5.successfactors.eu/career?company=bangolufse` | none allowed | not read | not read | no | Back end host robots.txt is `Disallow: /` and `Disallow: /*company`. No RMK host found (careers./jobs./career.bang-olufsen.com do not resolve). Needs a decision, see below. |
## Anchors for the RMK pages
Both listing layouts use the same job link and total.
- Job link: `href="(/[^"]*?/job/[^"]*?/(\d+)/)"` (the id is the last path segment; unescape `&amp;` in the href; some paths have a brand prefix before `/job/`).
- Table layout (Vestas, Systematic, SAP): rows `<tr class="data-row">`; `a.jobTitle-link` (title text); `span.jobLocation` ("City, Region, CC, zip"); `span.jobDate` (Vestas, Systematic only; "29 Sept 2026"); total in `<span class="paginationLabel" aria-label="Results 1 – 10">Results <b>1 – 10</b> of <b>661</b>`.
- Tile layout (Demant, Carlsberg, Scania): `<li class="job-tile job-id-{id}" data-url="/.../job/.../{id}/">`; fields as `id="job-{id}-desktop-section-{field}-value"` with `{field}` = `date`, `location` or company-specific `customfieldN`, labels in `...-label`; total in `<span id="tile-search-results-label">Showing 1 to 10 of 308 Jobs</span>`. Field set differs per company: Demant has no `location` field but `customfield4` (country name) and `customfield5` (city); Scania and Carlsberg have `location` with a trailing country code.
- Job page: `<div class="jobDisplayShell" itemscope itemtype="http://schema.org/JobPosting">` followed by `<meta itemprop="datePosted" content="Tue Sep 29 02:00:00 UTC 2026">` (Java Date format, parse `%a %b %d %H:%M:%S UTC %Y`), `<meta itemprop="validThrough">` (not always), `<meta itemprop="hiringOrganization">`, `itemprop="jobLocation" > itemprop="address"` with either `addressLocality`/`addressRegion`/`addressCountry` (Vestas) or a single `streetAddress` = "City, CC, zip" (others). Title: `span[itemprop=title]` inside `h1`, fallback `<meta property="og:title">`. Description: `span[itemprop=description] > span.jobdescription` (HTML). No `employmentType`, no `baseSalary`, no JSON-LD on any of the 8 sites; contract-type is at best a custom field in the listing (Scania: "Permanent / Temporary").
## Novo Nordisk
Three layers were seen, all live:
1. `www.novonordisk.com/careers/find-a-job.html` is AEM; a Vue widget calls `/bin/nncorp/careersearch?keyword=&country=&category=&locale=en`. One request returned all 427 rows (341 KB, includes filter dictionaries `subCategories`, `states`, `cities`). Row: `jobId` "346501.en_GB", `jobTitle`, `jobLocale`, `jobLocationLabel` "India, Bangalore", `jobCountry.value`, `jobCategory`, `jobSubCategory`, `jobState`, `jobCity`. `country=Denmark` gave 93 rows (English country name as filter value). Detail URL is built by the widget as `https://www.novonordisk.com/content/nncorp/global/en/careers/find-a-job/job-ad.{jobId}.html` (200, HTML only, description in `.job-display-details`). The API mixes locales (274 en_GB, 140 en_US, 11 ja_JP, 1 de_DE, 1 fr_FR) so req ids repeat; 418 unique.
2. The job page's apply link points to the SF back end `career2.successfactors.eu/career?...career_job_req_id=346501`, which redirects to `https://careers.novonordisk.com/job/Bangalore-Data-Architect-I-Karn/1442129433/`. That host is a normal RMK site, so the generic method works: sitemap 419, search 419 in 5 requests (100 per page).
3. The back end `career2.successfactors.eu/career?company=novonordisk&career_ns=job_listing_summary&resultType=XML` does return an XML listing (2.7 MB, `<Job><JobTitle><Job-Description><ReqId><filter7> country ...`), but only 266 reqs, and robots.txt on that host disallows everything. It was fetched once by accident of probing order and not used further. Do not build on it.
Recommendation: use `careers.novonordisk.com` with the generic RMK method. Novo's RMK job pages have no microdata, so dates and country come from the search listing (date column) and the `span.jobGeoLocation` anchor, or use the JSON API (country in `jobCountry`) as the list and RMK only for dates. Mapping between the two: the RMK URL is only reachable through the redirect from the `career_job_req_id` back-end URL (disallowed) or through the RMK listing; the RMK id (1442129433) is not the req id (346501). So mixing both is not cheap; pick one. Simplest is RMK only.
## Bang & Olufsen
`career5.successfactors.eu/career?company=bangolufse` is the only job entry point on their site. `robots.txt` there is `Disallow: /` and `Disallow: /*company`. One HEAD request returned 200 (page exists, no redirect). It was not read. Inferred, not verified: the same back end supports `career_ns=job_listing_summary&resultType=XML` like Novo's, but that is disallowed too. Options: skip B&O, ask the user to accept the back end, or check whether a `jobs.` host exists behind a differently named CNAME. Not tried: search engines for an RMK host.
## General answers
### One reading method for most
Yes: 7 of 9 rows are RMK (Vestas, Demant, Carlsberg, Systematic, Scania, SAP, plus Novo via `careers.novonordisk.com`), Signavio is a slice of SAP. Algorithm, all URLs relative to the stored base (scheme + host, no trailing slash):
1. Id list (1 request). `GET {base}/sitemap.xml` with `Accept-Encoding: gzip`.
- If the body starts with `<urlset`: for each `<loc>` matching `/job/.*/(\d+)/` take `(url, id)`. Unescape `&amp;`. The URL has to be used as given, since the slug and brand prefix vary.
- If it starts with `<rss` (SAP only): for each `<item>` take `<link>` and `<g:id>`; title, `<g:location>` and `<g:job_function>` come for free; descriptions are escaped HTML.
- The sitemap covers every locale; `<lastmod>` is a constant (the build day) and useless for change detection. It was not stale: every id found by paging the search was also in the sitemap.
2. Diff against stored ids. Ids gone from the sitemap are closed roles.
3. For each new id, `GET` its URL (1 request each, 80 to 250 KB uncompressed) and read the microdata anchors above (datePosted, country, title, description). If no `itemtype=JobPosting` is present (Novo), use `og:title` plus the listing row.
4. Optional cheaper daily path without job pages: the search listing (below) gives title, location, date and country for 10 to 100 roles per request.
Search listing (needed where the sitemap over-counts translations, or if only title/date/location are wanted): `GET {base}/search/?q=&locationsearch=&sortColumn=referencedate&sortDirection=desc&startrow={N}`, N = 0, pagesize, 2*pagesize ... Read the total from the results label (both layouts), stop when `N >= total`. The page size is fixed per site and not settable (`pagesize=100` was ignored): Vestas/Demant/Carlsberg/Systematic 10, Scania 15, SAP 25, Novo 100. Detect it as the number of rows on the first page. Beyond the end, Demant returns 0 rows; Vestas returned a non-empty odd page (`startrow=670` with 661 total), so trust the stated total, not an empty page. Paging to the end was run for all 7 sites: unique ids equalled the stated total each time (815, 760, 661, 419, 308, 68, 47).
Caveat on completeness: the search only lists postings in the site's default locale (`locale=` sets it). Vestas 661 vs 774, Carlsberg 68 vs 105, SAP 815 vs 921. Some of the extras are translations of the same requisition (Vestas), some are roles that exist only in another language (Carlsberg's Kronenbourg/French roles). The app has to choose: sitemap (complete, duplicates per language) or search (deduped per locale, misses local-language-only roles). No requisition id is exposed in the sitemap, so dedupe by translation is not possible without opening the job page (inferred). Recommendation: sitemap as the source of ids.
### Companies with their own method
- SAP: the "sitemap.xml" is an RSS feed with 921 items, 15 MB raw and 1.8 MB gzipped. Use the feed as one request; it is heavier than other sitemaps (Vestas 157 KB) but one request beats 33 pages. It has no posting date; get it from the job page `datePosted`. Signavio: `q=signavio` search only (title/description keyword), or filter SAP results by text in the description (inferred).
- Novo Nordisk: RMK host `careers.novonordisk.com`, job pages have no microdata (see above). The AEM JSON API is an alternative for the whole list in one request and country filter, but no dates.
- Bang & Olufsen: back end only, disallowed. Not readable in good conscience.
### Country filter on the server
Works on all 7 RMK hosts, verified: `&optionsFacetsDD_country=CC` (exact facet, ISO codes on Vestas and Demant; SAP `DE` gave 177) and `&locationsearch=CC` (text match on the location, slightly looser: SAP 186 vs 177). Counts for Denmark: Vestas 62 of 661, Demant 17 of 308, Carlsberg 7, Novo RMK 85, Systematic 24 (that count is DK-only), Scania `SE` 54, SAP `DE` 177. The facet dropdown options are filled by JavaScript, so the valid values are not in the HTML; ISO 2-letter codes worked everywhere tried. Novo API: `country=Denmark` (English name). No country filter for the sitemap; parse the country from `streetAddress` / `addressCountry` on the job page.
### Minimal identifier per company
The site base URL, `https://{host}` (e.g. `https://careers.vestas.com`). Everything else is derived: the layout (table or tile) is auto-detected, the page size from the first page, the sitemap at `/sitemap.xml`. For Signavio also a keyword. Optional: a country code for the server-side filter. Not needed: SF company id, ats_slug. The input `careers_url` values are not the base for four rows (Novo: AEM page; Scania: `/go/...`; Systematic: filtered search URL; Signavio: SAP host); store the host root.
### Requests per daily poll, 500 open roles
- Full re-read by search paging: 50 requests at 10 per page, 34 at 15, 20 at 25, 5 at 100 (Novo). Each page is 43 KB gzipped (Vestas measured), 250 to 300 KB raw.
- Sitemap route: 1 request (Vestas 157 KB raw, Scania 158 KB, SAP feed 1.8 MB gzipped) plus 1 job page per new id. With 5 to 20 new roles a day that is about 6 to 21 requests.
- Read only new roles: the search default order and `sortColumn=referencedate&sortDirection=desc` are date-descending on all 6 sites with a date column (verified by the dates on page 1 and on the last page; `asc` reverses it). SAP shows no date column and ignores the sort. Ids are not ordered with the date (about 50 percent of adjacent pairs ascend; old ids such as 1372305933 sit near the top), because the shown date is the last (re)posting date. So "stop at first known id" is wrong. Use: walk pages while any row date is >= (last poll date minus 1 day) or any id on the page is unknown; typical daily cost 1 to 2 requests plus job pages. Order within one day is not defined. Not verified over several days (only today's data was seen).
- Closed roles are only detected by a full id list (sitemap or full paging).
- No `ETag`, `Last-Modified` or `304` support seen on the sitemap (`Cache-Control: no-cache, no-store`), so conditional GET is not available.
### Rate limiting and bot protection
None met: no 403, 429 or captcha in about 330 requests at 1 per second with a Chrome User-Agent; curl's default User-Agent also got 200 on one Vestas search. RMK hosts: `server: nginx`, `JSESSIONID` cookie, `Cache-Control: no-store`. `www.novonordisk.com` sits behind Akamai (`Akamai-Cache-Status` header) but served the page and JSON API without challenge. One quirk: on the RMK sites any unknown `*.xml` path such as `/googlefeed.xml`, `/sitemal.xml`, `/jobs.xml` returned the same 8 MB Google feed on Vestas (a catch-all); `/feed/` returned an error page. So do not probe feed paths blindly.
### robots.txt
All 6 RMK hosts tested (`careers.vestas.com`, `careers.demant.com`, `careers.carlsberg.com`, `jobs.systematic.com`, `jobs.scania.com`, `careers.sap.com`) plus `careers.novonordisk.com` serve the identical 252-byte file (identical md5), no `Sitemap:` line:
```
User-agent: *
Disallow: /applybutton/
Disallow: /talentcommunity/
Disallow: /mobile/talentcommunity/
Disallow: /emailsubscribe/
Disallow: /email/image/
Disallow: /services/
Disallow: /preapply/
Disallow: /error
Disallow: /unsubscribe/
Disallow: /reset/
```
Consequences: `/search/`, `/job/`, `/sitemap.xml` and `/googlefeed.xml` are allowed. `/services/` is disallowed, which contains the RSS endpoint `/services/rss/job/?locale=en_US&keywords=(...)`; it was therefore not fetched, and its existence is inferred only. `/talentcommunity/apply/{id}/` (the Apply link) is disallowed; never follow it.
`www.novonordisk.com/robots.txt` is a single line: `Sitemap: https://www.novonordisk.com/sitemap.xml` (nothing disallowed, so `/bin/nncorp/careersearch` is allowed).
`career2.successfactors.eu/robots.txt` and `career5.successfactors.eu/robots.txt` (the back end):
```
User-agent: *
Disallow: /
Disallow: /*company
Allow: /login
```
So every `career?company=...` URL is disallowed, including the XML listing.
Deviations from robots: while probing Novo I fetched one back-end job URL (it redirected to the RMK page), one back-end XML listing (2.7 MB, saved as `sf/novo_sf_list.xml` in the scratchpad) and one HEAD on the B&O back end, before I had read that host's robots.txt. Nothing further was requested from those hosts.
## Curl commands that worked
```bash
UA='Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0 Safari/537.36'
B=https://careers.vestas.com # any RMK host: careers.demant.com careers.carlsberg.com jobs.systematic.com jobs.scania.com careers.sap.com careers.novonordisk.com
# robots
curl -sL -m 20 -A "$UA" $B/robots.txt
# id list: sitemap (SAP: RSS feed instead of urlset)
curl -sL -m 30 -A "$UA" -H 'Accept-Encoding: gzip' --compressed $B/sitemap.xml -o sitemap.xml
grep -o '<loc>[^<]*</loc>' sitemap.xml | wc -l
# search listing, date descending, paged; total in the results label
curl -sL -m 20 -A "$UA" "$B/search/?q=&locationsearch=&sortColumn=referencedate&sortDirection=desc&startrow=0"
curl -sL -m 20 -A "$UA" "$B/search/?q=&locationsearch=&startrow=650"
curl -sL -m 20 -A "$UA" "$B/search/?q=&locationsearch=&optionsFacetsDD_country=DK" # server-side country filter
curl -sL -m 20 -A "$UA" "$B/search/?q=signavio&locationsearch=" # keyword (SAP host)
# job page (microdata)
curl -sL -m 20 -A "$UA" "$B/job/Chetwynd-Stock-Keeper-Brit/1432067433/"
# Novo Nordisk JSON API on the AEM host
curl -sL -m 20 -A "$UA" 'https://www.novonordisk.com/bin/nncorp/careersearch?keyword=&country=&category=&locale=en'
curl -sL -m 20 -A "$UA" 'https://www.novonordisk.com/bin/nncorp/careersearch?keyword=&country=Denmark&category=&locale=en'
curl -sL -m 20 -A "$UA" 'https://www.novonordisk.com/content/nncorp/global/en/careers/find-a-job/job-ad.346501.en_GB.html'
```
Extraction that was run (python3): ids `re.findall(r'href="([^"]*/job/[^"]*?/(\d+)/?)"', html)` de-duplicated; total `re.search(r'Results <b>\d+\D+\d+</b> of <b>(\d+)</b>')` or `re.search(r'Showing \d+ to \d+ of (\d+)')`; microdata `re.findall(r'<meta itemprop="([^"]+)" content="([^"]*)"')`.
## Fixtures saved beside this file
- `out-successfactors-list.html`: Vestas search page 1, table layout (661 total, 10 rows).
- `out-successfactors-list-tile.html`: Demant search page 1, tile layout (308 total).
- `out-successfactors-list-sitemap.xml`: Systematic `sitemap.xml` (47 urls).
- `out-successfactors-list-novo.json`: Novo Nordisk JSON API, all 427 rows.
- `out-successfactors-job.html`: Vestas job page (microdata with `addressCountry`).
- `out-successfactors-job-demant.html`: Demant job page (microdata with `streetAddress` "Smørum, DK, 2765", `validThrough`).
- Scratchpad working files (all listing id sets from the full paging, SAP feed, Vestas google feed, other job pages) are in `sf/` beside this file.
## Verified versus inferred
- Verified by live request: every count in the table; paging to the end on 7 hosts; sitemaps and their id-set differences to search; country filters; date sort on 6 hosts; microdata contents on 6 job pages plus Novo RMK and AEM pages; the Novo JSON API; robots.txt on 9 hosts; the SAP feed; the Vestas Google feed; no rate limiting.
- Inferred only: existence and content of `/services/rss/job/` (disallowed, not fetched); whether B&O's back end supports the XML listing; how the sitemap and search behave over several days (only one day observed); that duplicates between locales cannot be merged without opening the page; whether `optionsFacetsDD_country` values other than ISO codes exist.
File diff suppressed because it is too large. Load diff
+252
View File
@@ -0,0 +1,252 @@
# Workday career sites read without a browser
Probed on 2026-09-29 from a plain (non-datacentre, WSL) IP with `curl` and `urllib`, one request per second per host, browser User-Agent, no cookies, no login. About 400 requests in total. "Verified" means I got a 200 with real data from a live request. "Inferred" is marked as such.
## Result per company
All 12 are on Workday and all 12 answer the list and detail endpoints without any token or cookie. Verified = yes means list, offset paging to `total`, and one detail call all worked.
| Company | tenant | wd | site | list total seen | verified | human-facing jobs URL | note |
|---|---|---|---|---|---|---|---|
| Zendesk | zendesk | wd1 | zendesk | 124 | yes | https://zendesk.wd1.myworkdayjobs.com/zendesk | Only site in robots.txt. Entries carry `remoteType`. |
| Unity | unitytech | wd1 | Unity | 123 | yes | https://unitytech.wd1.myworkdayjobs.com/Unity | Tenant is `unitytech`, not `unity`. No country facet, only city-level `locations`. `total` is repeated on every page. |
| LEGO Group | lego | wd103 | LEGO_External | 453 | yes | https://lego.wd103.myworkdayjobs.com/LEGO_External | robots.txt lists `LEGO_Executive` as Disallow (not probed). Country facet is called `Location` (top-level). One posting in the list has only `bulletFields` (no title, no path), so 452 of 453 are readable. Many retail and hourly roles. |
| Saxo Bank | saxobank | wd3 | CareeratSaxoBank | 50 | yes | https://saxobank.wd3.myworkdayjobs.com/CareeratSaxoBank | Second site `Sharedexclusive` (1 role, not the main one). |
| Novonesis | novonesis | wd103 | Novonesis_Careers | 134 | yes | https://novonesis.wd103.myworkdayjobs.com/Novonesis_Careers | The careers page links `novozymes.wd103...`, which answers 422 on the list endpoint and 500 (maintenance page) on the HTML. The working tenant is `novonesis` (found by trying it; the old host name is stale). robots.txt: `Disallow: /Novonesis_Careers/`. |
| GN Group | gn | wd3 | GN-Careers | 80 | yes | https://gn.wd3.myworkdayjobs.com/GN-Careers | Main site. Seven more brand sites on the same tenant: BeltoneCareers 126, JabraCareers 23, ReSoundCareers 24, AudigyCareers 4, SteelSeriesCareers 8, BeltoneIndependentlyOwned 124, ReSoundConversion 0. Overlap with GN-Careers not checked. |
| Equinor | equinor | wd3 | EQNR | 10 | yes | https://equinor.wd3.myworkdayjobs.com/EQNR | Only 10 roles, mostly summer internships and graduate programmes. Second site `EQCONF` has 0. The company careers page links only EQNR. I did not find a separate site for experienced hires, so Equinor's real list may live elsewhere (unverified). |
| Axis Communications | axis | wd3 | External_Career_Site | 98 | yes | https://axis.wd3.myworkdayjobs.com/External_Career_Site | Has `remoteType`, `endDate`. Country facet `locationCountry`; the facet count (37 for Sweden) differed from the filtered total (35). |
| Mister Spex | misterspex | wd103 | Mister_Spex_Careers | 70 | yes | https://misterspex.wd103.myworkdayjobs.com/de-DE/Mister_Spex_Careers | Careers page links use the `/de-DE/` locale segment; without it works too. German descriptions. Mostly stores in Germany. |
| Darktrace | darktrace | wd3 | DarktaceExternal | 73 | yes | https://darktrace.wd3.myworkdayjobs.com/DarktaceExternal | Site name is misspelt by the company ("Darktace"). robots.txt: `Disallow: /DarktaceExternal/`. |
| Criteo | criteo | wd3 | Criteo_Career_Site | 81 | yes | https://criteo.wd3.myworkdayjobs.com/Criteo_Career_Site | robots.txt: `Disallow: /Criteo_Career_Site/`. Three school-fair sites (EPITASchoolFair2026, CentraleSupelec2026, IESEG2026) have 0 roles. |
| Red Hat | redhat | wd5 | jobs | 151 | yes | https://redhat.wd5.myworkdayjobs.com/jobs | Site id is case-insensitive in the API (`jobs` and `Jobs` both work); `externalUrl` uses `Jobs`. Facet keys are single letters (`a` = Country). |
Sum of `total` over the main sites: 1,447 roles.
## General answers
### Is the description only in the detail call, and what does a poll cost?
Verified: the list entry has only `title`, `externalPath`, `locationsText`, `postedOn` (relative text), `bulletFields` (job req id, sometimes a location), and on some tenants `remoteType`. No description, no date, no country id. So the description costs one request per role.
The page size is fixed. `limit` 20 works everywhere; 21, 25, 30, 40, 50 and 100 return HTTP 400 on every tenant tried (all 12 for 50/100, the other 11 for 21). So a board with 800 roles needs 40 list requests to enumerate.
- First import of 800 roles: 40 list + 800 detail = 840 requests, about 14 minutes at one request per second.
- Steady-state daily poll: 40 list requests plus one detail request per new role. With the usual churn (order of 5 to 30 new roles per day) that is 45 to 70 requests.
- With a server-side country filter the list shrinks a lot: LEGO Denmark is 95 roles = 5 list requests instead of 23.
Cheaper new-role detection, verified as far as stated:
- `total` and the ids arrive on page 0 with one request. If `total` and the 20 ids on page 0 are unchanged, nothing new was posted at the top. This can miss the case of one role removed and one added if the new one is not on page 0, which order makes unlikely (see below).
- Default order is newest first, but not strictly. Over the full LEGO list (453) and Red Hat list (151) the `postedOn` day count is nondecreasing with a few violations (LEGO: a "Posted 30+ Days Ago" entry at position 24 followed by a "Posted Today" entry; Red Hat: 28 then 27; several 8-then-7 flips). `postedOn` also saturates at "Posted 30+ Days Ago". So "stop at the first known id" is a heuristic. A safer rule is to stop after one full page (20 ids) with no unknown id. Reposted or amended roles can surface later in the list.
- There is no sort parameter. I tried `sortBy`, `sort` and `orderBy` in the body; the response was 200 with the same `total` and, for `sortBy`, the same order, so unknown keys are ignored. Inferred: order is fixed by Workday.
- `siteMap.xml` (listed in robots.txt for allowed sites) is capped at 100 URLs, has no `lastmod`, and equals the first 5 list pages (checked on LEGO: all 100 URLs are in the list, in list order; Novonesis also 100). It saves at most 4 requests for a large board and is no substitute for paging. Sites that Disallow have no sitemap line (Darktrace, Criteo main; Novonesis serves one anyway, 200).
- The detail response carries `similarJobs` (2 entries, each with `startDate`), not useful for enumeration.
### Offset paging
Verified on 11 tenants (Novonesis paged only to page 0 after the tenant fix, total 134, first page and detail verified): paging `offset` 0, 20, 40, ... until `offset >= total` returns exactly `total` unique `externalPath` values (LEGO: 452 unique plus the one path-less entry). Quirks that matter for code:
- `total` is only reliable on the first page (`offset` 0). On later pages it is `0` on 9 tenants (Zendesk, LEGO, Saxo, GN, Axis, Mister Spex, Darktrace, Criteo, Red Hat) and correct on Unity and Equinor. Read `total` once from page 0.
- Offset at or beyond `total` does not return an empty list. It returns page 0 again (seen on Zendesk: offset 124, 140, 200 gave the first 20 roles and `total` 124). A loop that stops on an empty page never ends; stop on `offset >= total`.
- The path-less entry (LEGO): `{"bulletFields": ["0000036369"]}`. Skip entries without `externalPath`.
### Fields in the detail response
Verified on all 12 (one role each). `jobPostingInfo` always has:
- `title`, `jobDescription` (HTML, 4.8 to 10.9 KB), `location` (text), `postedOn` (relative text, e.g. "Posted 4 Days Ago"), `startDate`, `timeType`, `jobReqId`, `jobPostingId`, `externalUrl`, `country` (`descriptor`, `id`), `jobRequisitionLocation` (`descriptor` plus `country.alpha2Code`), `canApply`, `posted`.
- `startDate` is an ISO date (`2026-09-29`). In all 12 samples it matches the relative `postedOn` text (Posted Today = today, Posted 4 Days Ago = 2026-09-25, Posted Yesterday = 2026-09-28). So it is the usable real posting date. Its meaning is inferred from that match. It is not a job start date.
- `externalUrl` is the canonical human URL, without a locale segment (`https://zendesk.wd1.myworkdayjobs.com/zendesk/job/Lisbon-Portugal/Business-Development-Representative_R35239`).
- `country.alpha2Code` is only inside `jobRequisitionLocation.country`, so the ISO country code is available there.
Optional per tenant:
| field | present on |
|---|---|
| `remoteType` (In Office, Hybrid, Remote, No, On-Site) | Zendesk, Axis, Novonesis, Criteo, Red Hat. Absent on the other 7; no remote/hybrid signal there except the description text. |
| `additionalLocations` (list of text) | Equinor, Darktrace, Red Hat, only when the role has several locations. The list shows "2 Locations" in `locationsText` in that case. |
| `endDate`, `timeLeftToApply`, `jobPostingEndDateAsText` | Axis, LEGO, Novonesis, Equinor, Red Hat (application deadline) |
| `videoInfo` (large blob with signed tokens) | LEGO, Saxo, GN. Ignore it. |
Pay: there is no structured pay field on any tenant. Pay appears only inside the description HTML, when at all. Of 12 sample roles: Unity states a range (`Base Salary Range ... Zone A: $114,600 - $171,800 USD gross`), Red Hat has a generic compensation paragraph, Criteo, Saxo and Mister Spex say "attractive salary"/"Gehalt" without numbers, the other 6 say nothing. Sample size is one role per company, so this says only that pay is text-only.
`timeType` values differ in spelling ("Full time" vs "Full-time" on Mister Spex).
### Server-side country filter
Verified: yes, via `appliedFacets` with the facet parameter name and the value ids from the `facets` array of the first list response. Values in one facet are OR-ed (Darktrace `Country: [UK, US]` gave 53 where the facet counts summed to 54, likely count drift between two requests seconds apart), different facets are AND-ed. Combining with `searchText` works (Darktrace UK plus "engineer" gave 21). An unknown facet key returns HTTP 400.
The parameter name differs per tenant, so it cannot be hard-coded:
| tenant | country facet parameter | where |
|---|---|---|
| zendesk, saxobank, gn, axis, misterspex | `locationCountry` | nested under `locationMainGroup` |
| darktrace, criteo, novonesis | `Country` | top-level facet |
| lego | `Location` | top-level facet, values are countries (`Denmark` 95) |
| redhat | `a` (descriptor "Country") | top-level, single-letter keys |
| unitytech | none; only `locations` (cities) | pick the city ids |
| equinor | none; only `locations` (cities) | pick the city ids |
Filter results checked live (facet count then filtered total): Zendesk Portugal 16 then 16; Unity Copenhagen 11 then 11; LEGO Denmark 95 then 95; Saxo Denmark 14 then 14; Novonesis Denmark 21 then 21; GN Denmark 15 then 15; Equinor Hammerfest 1 then 1; Axis Sweden 37 then 35; Mister Spex Germany 67 then 67; Darktrace UK 35 then 35; Criteo France 20 then 20; Red Hat `a`=United States 53 then 53 (Czechia not in its list today).
The country value ids look tenant-independent: United States `bc33aa3152ec42d4995f4791a106ed09` and United Kingdom `29247e57dbaf46fb855b224e03170bc7` appear on LEGO, Darktrace, Red Hat, Unity; Denmark `49ab063f422741e2aef271de00efeac8` on LEGO, Saxo, Novonesis. Verified for those three, inferred for the rest. Safest is to look up the id by `descriptor` in the first response's `facets` per tenant (one request, which the poll makes anyway), and to fall back to post-filtering on the detail `country` when a tenant has no country facet.
Post-filtering from the list alone is weak: `locationsText` is often a city or "2 Locations" or, on LEGO, only a country name, so the country of a role is cleanly known only from the detail (`country`, `alpha2Code`) or from a facet filter.
### Rate limiting and bot protection
Verified: none met. All hosts are behind Cloudflare (`server: cloudflare`, `cf-ray`, `__cf_bm` cookie), yet no 403, 429 or challenge page came back in about 400 requests at one per second. Every response was 200, or 400/404/422/500 for my own deliberately wrong inputs. I did not send bursts, so the actual rate limit is unknown. I only probed from one IP, which is not a datacentre address; whether a cloud server IP gets a Cloudflare challenge is unverified. Plan for it: treat 403/429/503 as "back off and retry tomorrow", keep the one-request-per-second pacing.
### Does every tenant answer the same way?
The protocol is the same on all 12 (same paths, same JSON shape, no auth). Differences that matter:
- Facet names and country facets (table above); Red Hat uses `a` to `e` as facet parameters.
- `total` on later pages (0 vs repeated); wrap-around at the end.
- Optional detail fields (`remoteType`, `additionalLocations`, `endDate`).
- Unknown or stale tenant or site: HTTP 422 on the list (Novonesis with the stale `novozymes`), HTTP 404 with `errorCode S21` for an unknown site name, HTTP 200 with `total: 0` for a real but empty site (Equinor `EQCONF`, Criteo school sites), HTTP 400 for a bad body, limit above 20, or unknown facet key.
- The site name in the URL is case-insensitive (`jobs` vs `Jobs`).
### Minimal identifier per company
Three parts are needed: tenant, data-centre and site. Proposed string form: `{tenant}.{wd}/{site}`, for example
```
lego.wd103/LEGO_External
unitytech.wd1/Unity
novonesis.wd103/Novonesis_Careers
redhat.wd5/jobs
```
From it the app builds everything: list `https://{tenant}.{wd}.myworkdayjobs.com/wday/cxs/{tenant}/{site}/jobs`, detail `.../wday/cxs/{tenant}/{site}{externalPath}`, human URL `https://{tenant}.{wd}.myworkdayjobs.com/{site}`. The per-role key to store is `jobReqId` (also the last token of `externalPath` and of `bulletFields[0]`); `externalPath` is the stable fetch key (note it can end in `-1`, `-2` on reposts, e.g. Red Hat `..._R-059566-2`). The tenant is not always the company name (`unitytech`, `novonesis` vs the linked `novozymes`), so store it as found and do not derive it from the domain.
Discovery for a new company: fetch the careers page and grep for `myworkdayjobs.com` (worked for all 12 without JavaScript); then `https://{host}/robots.txt` lists all sites of the tenant as `Sitemap:` or `Allow:` lines (worked for 9 of 12; the three that Disallow their main site show the site only in the `Disallow` line). Then verify with the list call. A stale tenant shows as 422.
### robots.txt and terms
Verified: robots.txt exists on every host (fetched on all 12). It is generated per tenant and per site, and only names site paths, never `/wday/cxs/`. Quotes:
LEGO (`lego.wd103`):
```
Sitemap: https://lego.wd103.myworkdayjobs.com/LEGO_External/siteMap.xml
User-agent: *
Allow: /LEGO_External/
Disallow: /LEGO_Executive/
Disallow: /refreshFacet/
```
Novonesis (`novonesis.wd103`):
```
User-agent: *
Disallow: /Novonesis_Careers/
Disallow: /Novonesis_Careers_Private/
Disallow: /refreshFacet/
```
Darktrace: `Disallow: /DarktaceExternal/`. Criteo: `Disallow: /Criteo_Career_Site/` (while allowing its three school sites). The other 9 hosts have `Allow: /{site}/` for their main site and `Disallow: /refreshFacet/` only (Zendesk, Unity, Saxo, GN, Equinor, Axis, Mister Spex, Red Hat, LEGO).
Reading: three of the 12 (Novonesis, Darktrace, Criteo) have switched their main site to Disallow for all user agents, which is Workday's "do not let search engines index this site" setting. Strictly the rule covers the page path `/{site}/`, and the JSON API sits under `/wday/cxs/`, which no robots.txt here mentions; but the intent is that the employer does not want automated crawling of that site. This is a policy decision for you: honour it (skip those three), or treat the cxs endpoint as the page's own backing API for a once-daily poll of public data. I did not find a terms-of-use statement on the hosts (the JSON has no legal text, the HTML app shell does not carry one in the parts I saw; I did not fetch a Workday terms page). No authentication or captcha was touched, and the requests to those three sites were the same handful of calls as for the others.
## Sample responses (trimmed)
List entry (Zendesk, `total` 124, from `out-workday-list.json`):
```json
{
"total": 124,
"jobPostings": [
{
"title": "Business Development Representative",
"externalPath": "/job/Lisbon-Portugal/Business-Development-Representative_R35239",
"locationsText": "Lisbon, Portugal",
"postedOn": "Posted Today",
"remoteType": "In Office",
"bulletFields": ["R35239"]
}
],
"facets": [
{"facetParameter": "remoteType", "descriptor": "Remote Type",
"values": [{"descriptor": "Hybrid", "id": "e92222236f4b100194e5184e4fa00000", "count": 43}]},
{"facetParameter": "locationMainGroup",
"values": [{"facetParameter": "locationCountry", "descriptor": "Country",
"values": [{"descriptor": "Portugal", "id": "2e8c5034deb045d49315417c347472ca", "count": 16}]}]}
]
}
```
Detail (Zendesk, `jobPostingInfo` only, description cut, from `out-workday-detail.json`):
```json
{
"jobPostingInfo": {
"id": "f0833f8f93df1000fd891e465ff10000",
"title": "Business Development Representative",
"jobDescription": "<h2>Job Description</h2><p ...>(10,880 chars of HTML)</p>",
"location": "Lisbon, Portugal",
"postedOn": "Posted Today",
"startDate": "2026-09-29",
"timeType": "Full time",
"jobReqId": "R35239",
"jobPostingId": "Business-Development-Representative_R35239",
"jobPostingSiteId": "zendesk",
"country": {"descriptor": "Portugal", "id": "2e8c5034deb045d49315417c347472ca"},
"jobRequisitionLocation": {"descriptor": "Portugal - Lisbon - Office",
"country": {"descriptor": "Portugal", "id": "2e8c5034deb045d49315417c347472ca", "alpha2Code": "PT"}},
"remoteType": "In Office",
"externalUrl": "https://zendesk.wd1.myworkdayjobs.com/zendesk/job/Lisbon-Portugal/Business-Development-Representative_R35239",
"canApply": true,
"posted": true
},
"hiringOrganization": {"name": "CLEVERLY LDA (Portugal)", "url": ""},
"similarJobs": ["2 entries with title, externalPath, timeType, locationsText, postedOn, startDate"],
"userAuthenticated": false
}
```
The full raw files are `out-workday-list.json` (Zendesk page 0, limit 20) and `out-workday-detail.json` (the same role, R35239), a matching pair to use as fixtures. Full responses of all 12 tenants are also in `wd/raw_{tenant}_list.json` and `wd/raw_{tenant}_detail.json`.
## Commands that worked
Set once: `UA='Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0 Safari/537.36'`. The list POST (LEGO Denmark filter), the Zendesk detail GET, robots.txt, siteMap.xml and the careers-page grep were re-run verbatim with `curl` and gave the results stated above. The paging, limit, sort and facet experiments were run with the equivalent `urllib` calls.
Find the site:
```
curl -sS -m 20 -A "$UA" https://www.equinor.com/careers | grep -o 'https://[a-z0-9.-]*myworkdayjobs.com[^"<> ]*' | sort -u
curl -sS -m 20 -A "$UA" https://gn.wd3.myworkdayjobs.com/robots.txt
```
List (page 0, 20 roles, `total` and `facets` in the response):
```
curl -sS -m 20 -A "$UA" -X POST \
-H 'Content-Type: application/json' -H 'Accept: application/json' \
-d '{"appliedFacets":{},"limit":20,"offset":0,"searchText":""}' \
https://lego.wd103.myworkdayjobs.com/wday/cxs/lego/LEGO_External/jobs
```
List filtered by country (LEGO Denmark, facet parameter `Location`):
```
curl -sS -m 20 -A "$UA" -X POST \
-H 'Content-Type: application/json' -H 'Accept: application/json' \
-d '{"appliedFacets":{"Location":["49ab063f422741e2aef271de00efeac8"]},"limit":20,"offset":0,"searchText":""}' \
https://lego.wd103.myworkdayjobs.com/wday/cxs/lego/LEGO_External/jobs
```
Next page: change `"offset":20`, `40`, ... while `offset < total` (take `total` from page 0).
Detail (`externalPath` from the list entry):
```
curl -sS -m 20 -A "$UA" -H 'Accept: application/json' \
https://zendesk.wd1.myworkdayjobs.com/wday/cxs/zendesk/zendesk/job/Lisbon-Portugal/Business-Development-Representative_R35239
```
Sitemap (100 newest URLs, no dates): `curl -sS -m 20 -A "$UA" https://lego.wd103.myworkdayjobs.com/LEGO_External/siteMap.xml`
Things that failed, on purpose or not: `"limit":21` and up gives HTTP 400; the stale `novozymes.wd103` tenant gives HTTP 422 on the list and a 500 maintenance page on the HTML; an unknown site gives 404 `S21`; an unknown facet key gives 400.
## Not verified
- Behaviour from a cloud or datacentre IP (Cloudflare challenge risk).
- The real rate limit; I never exceeded one request per second per host.
- Whether Equinor has experienced-hire roles on another site or system.
- Whether facet ids for countries are identical across all tenants (checked for US, UK, DK only).
- Whether `startDate` always equals the posting date (matched in all 12 samples, one role each; also verified for the old "Posted 4 Days Ago" case on LEGO and Equinor).
- Any terms-of-service text of Workday or the employers about API access.