Recruitment Marketing Public

Job criteria in Recruitment Marketing are grouped into two categories:

• Explicit fields
• Non-explicit fields

An explicit field uses the "=" symbol, and requires the job criteria to be formatted as follows:

city = "Dublin"

In Recruitment Marketing, the following fields are explicit only:

• title
• description
• department
• category
• category_group
• employment_type
• level
• remote_job e.g. yes or no
• city
• state
• country_code e.g. IE, US
• country e.g. United States
• postal_code
• ats_integration_uid
• dropdown_field_1 - 15
• string_field_1 - 10

A non-explicit (or implicit) field is more suited to a keyword search. 

For example:

• When a user needs to search for an ID like "924123" the system will search all available fields for that keyword. Currently, the only implicit field in Recruitment Marketing is ats_uid. 

Complex Criteria

You can create more complex job criteria by adding any of the following operators:

• contains (~)
• not contains  (!~)
• in (^)
• not in (!^)
• or
• and

For example:

• To pull in all jobs where city contains Dublin, the criteria would look like this:
  city ~ Dublin
• If you would like to exclude all Dublin jobs from your results, the criteria would be, does not contain: city !~ "Dublin" and would look like this:
  city !~ "Dublin"
  

To include jobs from a range of cities use the ^ operator e.g: city ^ ("Dublin", "Cork", "New York") 

To exclude jobs from a range of cities use the !^ operator e.g: city !^ ("Dublin", "Cork", "New York") 

Note: The 'includes' and 'excludes' operators will only return exact matches. Therefore, in the above example, a job where the city is "New York City" would not be matched.

To create a more varied list of jobs, try a "this or that" criteria.

For example:

• All jobs in Dublin or Texas, the construct would be as follows:
  city = "Dublin" or state = "Texas" 

To create a more specific list of jobs, use "and".

For example:

• Where city is Dublin and all the jobs contain "rails" in their title, the construct would be as follows:
  city = "Dublin" and title ~ "rails"
  

Note: Where a field is not specified, the system will default to searching the job title and no other fields for a match. For example, in the case of [title ~ "aaa" or "bbb"], while the intention translates as [title contains "aaa" or "bbb"], what the system actually reads is, [title contains "aaa" or "bbb" is found in any of the fields listed above]. This is why it's important to qualify each criteria component, i.e. title ~ "aaa" or title ~"bbb".

More Accurate Criteria

Quotation marks

If the search value has spaces in it e.g. "New York" or "Business Analyst", then it is required to wrap the value in quotation marks. A criterion without the use of quotation marks such as city = New York will search for all jobs with a city of New and any jobs with an ATS uid of York

Inaccurate: city = New York

Accurate: city = "New York"

Specify keywords

As mentioned before category = Finance or Sales will actually check for jobs with a category of Finance and a title of Sales

Inaccurate: category = Finance or Sales

Accurate: category ^ ("Finance", "Sales")

Fields with multiple values set

Where a job has multiple values/categories selected against it, a standard "=" query won't find a match.

Including the options you're looking to include in a list will work instead.

city = "New York" and (category ^ ("Finance", "Sales"))

The above will target jobs in the city of New York and have either Finance or Sales categories selected against them.

Use parenthesis when mixing operators

Consider this query:

category = "Finance" and city = "Dublin" or category = "Sales" and state = "New York"

It is ambiguous whether the intention of the author is:

category = "Finance" and (city = "Dublin" or category = "Sales") and state = "New York"

or

(category = "Finance" and city = "Dublin") or (category = "Sales" and state = "New York")

These two queries will produce different results. For that reason, it is better to explicitly use parenthesis when mixing "and" and "or".

Efficient Criteria

Avoid unnecessary usage of or

Slower: city = "Dublin" and (category = "Finance" or category = "Sales" or category = "Business")

Faster: city = "Dublin" and category ^ ("Finance", "Sales", "Business")

Prefer equals to contains

If contains (~) is not needed, then using equals (=) will produce a faster page load time

Slower: city ~ "Dublin"

Faster: city = "Dublin"

Avoid multiple usages of not contains

Assume there are jobs connected to the following categories: "Business development", "Business Analyst", "Sales experts", "Technical Sales"

Very slow: category !~ "Business" and category !~ "Sales"

Faster: category !^ ("Business development", "Business Analyst", "Sales experts", "Technical Sales")

While the faster query is longer to write, it is better to use !^ and list all the explicit categories.