Search and location filters

Text search is phrase-oriented

In the jobs list, q searches the full-text title and description columns. title searches title. The implementation strips quotes and asterisks and wraps the resulting value as a phrase; it is not arbitrary Boolean syntax. q does not search company or location.

Location needs a stated meaning

The list supports location, city, state, and country predicates. Combined conditions match one indexed location row. The city filter uses the catalog location index; it does not assert that a sample location value was normalized correctly.

Sample explorer is separate

The website sample explorer searches the published catalog snapshot projection by title, company, or description and filters by ATS source. That browser behavior is not the jobs API search contract.

Use list fields

The filter reference describes the supported list filters and representation options.

How the location filters match

Every known location of a job is stored as one row with a city, a region, a two-letter country code and a search text. The search text is the location's street, city, region, postal code and country joined by spaces, in lower case.

• All location filters in one request must match the same location of the job. city=Paris&country=FR finds Paris, France; city=Paris&state=TX finds Paris, Texas.
• Send one place name per filter. The search text has no commas, so location=Austin, TX does not match; use city=Austin&state=TX.
• Use country with the code instead of a country name in location.
• Accents are kept: Montréal and Montreal are different text.
• For remote work, use work_arrangement=remote, not a location.
• has_location=false finds jobs with no known location.