The survey of the 155 companies without a board is in docs/plan-hosts. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
167 lines
21 KiB
Markdown
167 lines
21 KiB
Markdown
# 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 `&` 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 `&`. 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.
|