Files
jobboard/docs/plan-hosts/otherhosts.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

35 KiB

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.