22 KiB
Survey: which filters the hosts take at the source
Work package S of plan-prep.md, 2026-09-30. Each host got at most two live requests, one small page each, against boards that are already attached (roledesk.db opened read-only for the targets). Nothing else was read except one page of HTML or JS where noted.
Marks used in the table:
- live: seen in a request of this survey.
- front end: taken from the site's own page (HTML or JS), not requested.
- code: stated in the reader's docstring from an earlier review, not repeated here.
- docs: from the vendor's public API documentation as remembered; not tested.
- untested: a guess, or nothing known.
All request counts are exact: a host with a "live" mark on a claim spent its two requests on it, so anything else about that host is code, front end or untested.
1. Filters per host
Country and remote are left out; they are in the readers already. "Combine" is how a keyword and a country (or another facet) meet; "unknown" is what an unknown value does.
SmartRecruiters (smartrecruiters:BoschGroup, 4,830 roles)
| Filter | Parameter and format | Several values | Combine | Unknown value | Mark |
|---|---|---|---|---|---|
| keyword | q=engineer; free text |
not tested; one request per term is safe | q with country=dk answered 0 where q alone answered 1,713 and DK holds 2 roles: AND |
not applicable | live |
| keyword scope | matches title and text: the first hit for q=engineer is "Pflichtpraktikum in der Fertigungsplanung" |
live | |||
| category | department=<id> and function are in each role (function.id = production); a filter on function is not documented |
untested | untested | untested | docs, untested |
| level | each role carries experienceLevel.id (internship, entry_level, associate, mid_senior_level, director, executive); no filter parameter is known |
untested | |||
| employment | role carries typeOfEmployment.id; no filter known |
untested | |||
| place | region=, city= next to country=; the role's location has all three |
untested | untested | untested | docs, untested |
Eightfold (eightfold:jobs.ericsson.com/ericsson.com, 618 roles)
| Filter | Parameter and format | Several values | Combine | Unknown value | Mark |
|---|---|---|---|---|---|
| keyword | query=software; free text |
untested | with location=Sweden it answered 102 of the 154 Swedish roles: AND |
untested | live |
| keyword scope | title, text and skills: "Master Thesis: Characterizing hardware imperfection of power amplifiers" matched software |
live | |||
| category | filter_function=product development, the value the tenant's filterDef.allFilters lists for function (19 values); with location=Sweden 92 of 154, every hit Product Development |
untested (repeat the parameter is the likely form) | AND with location | untested | live |
| level | none offered by this tenant: allFilters is skills, function, jobtype |
live | |||
| employment | jobtype (hybrid only here) is the work-location option, not the employment type |
live | |||
| place | location= takes a country name here; the facet values are "Stockholm, Stockholm County, Sweden", so a town string is the likely form |
untested | untested | untested | untested |
| notes | Every answer carries filterDef with the tenant's own filters and their option lists, so a reader can learn a tenant's names at run time. appliedFilters shows includeRemote: ['1'] by default, so location=Sweden already lists remote roles (154 of 618 includes them) |
live |
SuccessFactors (successfactors:careers.vestas.com, 668 roles)
| Filter | Parameter and format | Several values | Combine | Unknown value | Mark |
|---|---|---|---|---|---|
| keyword | q=engineer in /search/?q=&locationsearch= |
untested | with optionsFacetsDD_country=DK it answered 40 (of 64 Danish roles): AND |
not applicable | live |
| keyword scope | not determined | untested | |||
| category | optionsFacetsDD_department labelled "Job Family" |
untested; one country a request is what the reader does | untested | department=zzz with country=DK answered 5 roles from Italy, Canada and France: neither ignored nor empty, and the country facet was lost |
live |
| level | optionsFacetsDD_shifttype, labelled "Work Experience" on Vestas; the label and the facet are the tenant's choice |
front end | |||
| employment | optionsFacetsDD_customfield1, labelled "Type of Position" on Vestas; tenant's choice |
front end | |||
| place | locationsearch= is the free-text place box of the same form and is already in the reader's URL, empty |
untested | untested | untested | front end, untested |
| notes | The four facet <select> elements are in the HTML with only "All"; their values are filled by script, so a reader has no cheap way to learn them. The facet names above come from those name attributes |
live |
Phenom (phenom:www.careers.philips.com/global/en, 868 roles)
| Filter | Parameter and format | Several values | Combine | Unknown value | Mark |
|---|---|---|---|---|---|
| keyword | keywords in the POST body of /widgets; free text |
untested | with selected_fields.country=["Netherlands"] it answered 5 (NL plus Engineering answered 2): AND |
untested | live |
| keyword scope | text, not title: "Logistiek Medewerker & Warehouse Coördinator 7T MR" matched engineer |
live | |||
| category | selected_fields.category=["Engineering"]; exact strings as the role's category field; with NL it answered 2, both Engineering |
list, as country is (code); not repeated for category |
AND with country | untested | live |
| level | positionLevel in the role is en_GLOBAL on every role read: no level |
live | |||
| employment | type (Full time) is in the role; no filter tested |
untested | |||
| place | body has location and locationData (radius search in the site's own form); selected_fields also takes city and state keys on other Phenom sites |
untested | |||
| notes | aggregations came back empty for these bodies, so the facet values are not learnt from this request; the site's page asks for them another way |
live |
Workday (workday:lego.wd103/LEGO_External, 455 roles)
| Filter | Parameter and format | Several values | Combine | Unknown value | Mark |
|---|---|---|---|---|---|
| keyword | searchText in the POST body |
one request each is safe | searchText=engineer answered 106; the country facet under it counts 45 for Denmark: AND |
untested | live |
| keyword scope | not determined | untested | |||
| category | appliedFacets.jobFamily=[<id>, ...] (30 values on LEGO); the parameter name is the tenant's (jobFamilyGroup elsewhere) |
ids in one facet union: Mechanical Engineering (4) plus IT Engineering (8) with Denmark and engineer answered 12 |
AND across facets and with searchText |
untested | live |
| level | no level facet on LEGO; jobFamily has "Trainee / Intern / Apprentice" |
live | |||
| employment | workerSubType ("Job Type": Regular, Education Fixed Term, Student Worker, Temporary) and timeType (Full time, Part time) |
as jobFamily |
AND | untested | live |
| place | LEGO's Location facet lists countries only (13 values); other tenants nest a city facet under locationMainGroup |
as jobFamily |
code | ||
| notes | The reader's facets call already reads facet ids off one page; the facet list responds to searchText (counts change) |
live |
Oracle Recruiting Cloud (oracle:fa-evmr-saasfaprod1.fa.ocs.oraclecloud.com/CX_1, Nokia, 554 roles)
Requests go through finder=findReqs;siteNumber=CX_1,<name>=<value>,....
| Filter | Parameter and format | Several values | Combine | Unknown value | Mark |
|---|---|---|---|---|---|
| keyword | keyword=engineer; free text |
untested | answered 468 of 554 | untested | live |
| keyword scope | text: 468 of 554 roles cannot all have it in the title | live | |||
| category | selectedCategoriesFacet=<id> from categoriesFacet (10 values: Applied R&D 259, Direct Production 55 under the keyword) |
joined with ; (%3B): two ids answered 314 = 259 + 55 with the keyword: union |
AND with the keyword | an id the pod does not know answers the whole board (superset) | live; unknown from code |
| level | none: titlesFacet holds function codes (SWA Software, TRA Trainee), flexFieldsFacet holds unnamed attributes |
live | |||
| employment | none seen; selectedWorkplaceTypesFacet is the work-location type (ORA_HYBRID, ORA_ON_SITE, ORA_REMOTE) |
live | |||
| place | selectedLocationsFacet lists 10 countries only; workLocationsFacet lists sites; the answer also echoes Location, LocationId and Radius, which suggests a free place search |
live, untested |
Workable (workable:starling-bank, 48 roles)
| Filter | Parameter and format | Several values | Combine | Unknown value | Mark |
|---|---|---|---|---|---|
| keyword | query in the POST body of /api/v3/accounts/<slug>/jobs; {"query": "engineer"} answered 42 of 48 |
live | |||
| keyword scope | title and text, judged from the 6 of 10 hits that have it in the title: not determined | untested | |||
| category | department: the site sends a list of names taken from each department's filter array; my body ["Engineering"] was answered 400 (the request with location too), which of the two keys was refused is not known |
live (rejected), front end | |||
| level | none: no filter key | front end | |||
| employment | worktype, and workplace (hybrid, on_site, remote) |
front end | |||
| place | location: a list of {country, region, city, countryCode} objects, the shape of a role's locations; my body left out countryCode, which may have caused the 400 |
front end |
Teamtailor (teamtailor:careers.shine.co, 73 roles)
| Filter | Parameter and format | Several values | Combine | Unknown value | Mark |
|---|---|---|---|---|---|
| keyword | jobs.rss?per_page=5&query=zzzqqx answered no items |
not applicable | live, with no baseline request; the HTML twin /jobs?query= also shows no roles |
||
| category | the site's search form has department and location fields (ids); whether the feed reads them is not known |
front end, untested | |||
| level | none | front end |
Jibe (jibe:jobs.booking.com, 145 roles)
| Filter | Parameter and format | Several values | Combine | Unknown value | Mark |
|---|---|---|---|---|---|
| keyword | keywords=engineer answered 50 of 145 |
untested | untested | live | |
| keyword scope | text: titles include "Senior SAP Data Analytics Engineer" as well as engineers; not determined | untested | |||
| category | categories=Engineering with keywords=engineer answered 17, the number the answer's own filter.categories states for Engineering |
untested | AND | untested | live |
| level | filter.experienceLevels exists and is empty on Booking |
live | |||
| place | the answer's filter.locations lists {city, state, country, count}; the parameter for it was not tested |
live, untested | |||
| notes | The answer carries its filter block (brands, categories, locations, experience levels) with counts, for every request |
live |
Lever (lever:spotify, 79 roles)
| Filter | Parameter and format | Several values | Combine | Unknown value | Mark |
|---|---|---|---|---|---|
| keyword | none in the API | docs | |||
| category | team=<name> and department=<name>; role categories has both |
untested | AND: location=Stockholm&team=zzzqq answered [] |
returns nothing | live |
| level | level= is documented; not tested |
docs | |||
| employment | commitment=Permanent is documented and is a categories key |
docs, untested | |||
| place | location=Stockholm answered 33 of 79: the 11 in Stockholm and 22 whose allLocations lists it (London 17, New York 5), so it matches any of a role's places and is exact text |
untested | live |
Jobindex (search provider, RSS)
| Filter | Parameter and format | Several values | Combine | Unknown value | Mark |
|---|---|---|---|---|---|
| keyword | q; OR between words, "a b" a phrase, +word required |
code | |||
| category | subid=1 gave the channel title "Ledige job kategoriseret i Systemudvikling og programmering" and 20 matching titles; other ids not known |
not tested | live | ||
| place | geoareaid=<id> (the reader's AREAS: regions 1-5, Aarhus 8, Aalborg 7) |
code | |||
| notes | The HTML search page (/jobsoegning) carries no filter form in its source; its filters are script-drawn. Robots disallows geoareaid=, which the owner accepted on 2026-09-30 |
live |
Adzuna (search provider, needs a key)
The environment has no key, so nothing was requested. From the public API documentation: what (all words), what_or, what_phrase, what_exclude, title_only, where, distance, location0 to location7 (hierarchical place), category (a tag from /categories), full_time, part_time, contract, permanent, max_days_old, salary_min. The reader sends what and where. Mark: docs, untested. title_only is the only title-only keyword found on any host.
Platsbanken (search provider, JobTech)
| Filter | Parameter and format | Several values | Combine | Unknown value | Mark |
|---|---|---|---|---|---|
| keyword | q; ranks by all words (decisions) |
code | |||
| category | occupation-field=apaJ_2ja_LuF with q=python answered 497, the first hit Data/IT |
untested | untested | live | |
| place | region=<län id> (reader); municipality=AvNB_uwa_6n6 returned a Stockholm hit |
untested | reader raises on an id outside REGIONS |
live | |
| level | experience=false was in the same request as municipality and occupation-field; the answer was 1 hit, so it is not separable |
live, inconclusive |
2. Towns
How a town reaches the fetch today. An agent's any gate on place holds names ("Malmö", "Lund", "Helsingborg", "copenhagen", "odense" in agent 2). In reach.gate_reach, each name goes through gaz.lookup and _countries_of, which turns it into the country the place lies in; a name the gazetteer does not know makes the whole reach everywhere. The reach is a set of ISO codes and a remote flag; it holds no town. ask_for narrows it to the reader's declared dimensions, so Ask.countries gets SE and DK and Ask.places is empty for every board host, since none declares place. The gates then keep only the towns after the pull. A town gate therefore fetches its whole country.
For agent 2 this costs nothing: its any group has DK and SE beside the towns, so the towns are already covered. It costs where the group has towns and no country, and the country is large (Munich as DE).
Which hosts could take a town instead.
- Could, by what was seen: Eightfold (
location=, its facet values are town strings; untested), Workable (locationobjects withcity; untested body), Lever (location=Stockholm, live: exact text, matches any of a role's places), Adzuna (where,location0..7), Jobindex (geoareaid), Platsbanken (municipality). - Could, with facets: Workday on tenants that have a city facet (LEGO's is countries only), SuccessFactors (
locationsearch=, untested), Phenom (locationandlocationDatain the body, untested), Jibe (a city facet is listed; the parameter is not known). - Cannot: SmartRecruiters has
city=andregion=in its documentation but it is untested; Oracle lists ten countries and sites only; Teamtailor takes ids. - Only the search providers do so today (
Filters(place="one")on Adzuna, Jobindex and Platsbanken).
Recommendation. Leave towns as their country for the board hosts, and build place only where it saves a lot and the town is the agent's only reach:
- The saving is small in the live data. For agent 2, the DK and SE reach already leaves at most 149 roles on any big board (Ericsson), so a town would cut a country read of one or two requests.
- Town strings are the host's own, unlike ISO codes: each host needs a name-to-string table or a facet lookup, and a town the host spells differently returns nothing and, on the closing guard, wrongly closes roles.
- Hosts that state their places per role (all the big ones) leave the exact match to the gates and the gazetteer, which is already right.
So: F2 changes reach.py to carry places beside countries for a group that has towns and no country, and passes them only to readers that declare place (the three providers now; Eightfold and Lever if a later run shows the strings work). Everything else keeps the country.
3. Recommendation
Declarations per host
| Host | query |
category |
level |
place |
|---|---|---|---|---|
| SmartRecruiters | yes: q, one request per term (multi-word behaviour untested) |
no: the parameter is not verified | no | no |
| Eightfold | yes: query |
later: filter_function, ids learnt from filterDef |
no: no tenant filter seen | later: location=<town string> after a test |
| SuccessFactors | yes: q |
no: department gave a wrong answer for an unknown value and its values need script |
no: the "Work Experience" facet is a tenant label | no |
| Phenom | yes: keywords |
later: selected_fields.category needs the value list |
no: positionLevel is empty |
no |
| Workday | yes: searchText |
later: jobFamily ids from the existing facets call |
no | no |
| Oracle | yes: keyword |
later: selectedCategoriesFacet ids from categoriesFacet |
no | no |
| Workable | yes: query |
no: the body is not settled (400) | no | no |
| Teamtailor | yes, after one baseline request confirms the feed filters | no | no | no |
| Jibe | yes: keywords |
later: categories |
no | no |
| Lever | no: no keyword parameter; boards are small and read whole | no | no | later, as above |
| Jobindex, Platsbanken, Adzuna | already query and place; subid, occupation-field and category are available for category |
level is not worth declaring on any host: only SuccessFactors and Jibe have a facet for it, and on the tenants seen it is a tenant label or empty. Seniority stays a prep matter (title rules, host word).
What F2 should build first
The plan assumes terms narrow big boards. The live DB says how much:
| Board | Host | Open | In Europe | In DK or SE (today's reach) | Roles with a term in the title, Europe |
|---|---|---|---|---|---|
| Bosch | SmartRecruiters | 4,830 | 1,564 | 15 | 149 |
| Delivery Hero | SmartRecruiters | 975 | 314 | 11 | 143 |
| Coolblue | SmartRecruiters | 477 | 477 | 0 | 30 |
| Wise | SmartRecruiters | 417 | 279 | 0 | 160 |
| SAP | SuccessFactors | 807 | 365 | 6 | 128 |
| Scania | SuccessFactors | 750 | 532 | 58 | 28 |
| Vestas | SuccessFactors | 668 | 327 | 61 | 56 |
| Novo Nordisk | SuccessFactors | 428 | 138 | 93 | 45 |
| Philips | Phenom | 868 | 194 | 3 | 65 |
| Zeiss | Workday | 848 | 264 (295 with no country) | 1 | 59 |
| LEGO | Workday | 455 | 175 (45 with none) | 83 | 60 |
| Ericsson | Eightfold | 618 | 210 | 149 | 64 |
| Nokia | Oracle | 554 | 87 (54 with none) | 0 | 24 |
"Term in the title" is a count of the words head, director, VP, chief, CTO, CDO, data, AI, machine learning, forward deployed, solutions engineer or architect, professional services, research, innovation, principal, lead and manager in the title. It is a proxy for fetch_terms, and a lower bound on what a text filter returns: every host's keyword matched text, not only titles (Ericsson: software matched a thesis title without it; Nokia: engineer matched 468 of 554; Bosch: 1,713 of 4,830). Expect a keyword read to return several times these counts, and a broad term like engineer to cut little.
Findings:
- Narrow reach needs no terms. At DK and SE every big board is already at most 149 roles (Ericsson), and Bosch is two requests. Terms save requests only on the wide reach: the All roles tag, and the favourite reads the plan drops.
- The wide reach is where terms pay. SmartRecruiters reads Europe (33 countries) as the whole board, because
MAX_SERIESis 8 for aonehost: Bosch is 49 requests of 100 for 1,564 European roles. Oneqrequest per term (about 35% of the board forengineer, far less fordirectorordata) replaces it. - Order by the size of the whole read that terms replace, then by how sure the parameter is:
- SmartRecruiters
q: Bosch, Delivery Hero, Wise and Coolblue, 6,700 roles in the live DB, one live-verified parameter, AND with country. - SuccessFactors
q: SAP, Scania, Vestas and Novo Nordisk, 2,650 roles; verified. The reader already reads a country a request, so a term multiplies the series. - Workday
searchText(Zeiss 848, LEGO 455), Phenomkeywords(Philips 868), Eightfoldquery(Ericsson 618) and Oraclekeyword(Nokia 554): each verified once, each a small change to the request body or URL.
- SmartRecruiters
- Category next, and only for Workday, Oracle, Jibe and Eightfold. They state their own category ids in a response the reader already reads or can read (
facets,categoriesFacet,filter.categories,filterDef), and the union across values is verified on Workday and Oracle. But an agent's term (engineer) is not a category name, so it needs a mapping from term to category per tenant that nobody has: not before terms have run on real boards. - Level: never at the source. Place: the search providers now, Eightfold and Lever if a test proves a town string; the rest stay on country.
Guards F2 must keep
- A term filter needs the closing guards to hold: a keyword read is not a whole board, so
ats:sizemust not be overwritten by it, and roles outside it must not be closed as gone. - Unknown-value behaviour differs: Lever returns nothing, Oracle returns everything, SuccessFactors returned something unrelated, Workable answers 400. The runner must treat a facet value as known only when the host's own facet list stated it, as
seriesdoes for ids. - Keywords are text matches everywhere except Adzuna's
title_only; the agent's own scoring still decides relevance.
Open, and cheap to settle in F2's first hour
- SmartRecruiters: does
q="head of data"mean all words or any, and aredepartment,function,experienceLevelaccepted (one request each)? - Teamtailor: a baseline request to confirm the feed's
queryfilter. - Workable: which key of my body was refused (
departmentorlocation). - Eightfold: a
locationwith a town string, and repeatedfilter_functionvalues. - Adzuna: everything, once the key exists.