Files
jobboard/docs/plan-hosts/workday.md
T
WolfandClaude Fable 5.1 0a1d3c67c7 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>
2026-09-29 16:52:40 +02:00

253 lines
21 KiB
Markdown

# 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.