1. Home
  2. Advanced Setup & Configuration
  3. Promoting “Remote” or “Work From Home” Roles

Promoting “Remote” or “Work From Home” Roles

As work changes in our changing times, fully “Remote” or “Work From Home” opportunities are growing in popularity. It is important to our users that they know how to create their jobs in Bullhorn and configure Matador Jobs to promote these “Remote” opportunities.

“Remote” features are not available to users of Matador Jobs Lite. Consider an upgrade to Matador Jobs Pro and begin promoting your “Remote” or “Work From Home” jobs today! See pricing or request a demo!

How it Works

Matador Jobs reads values from the Bullhorn onSite field on the job object. When enabled, most users will see a drop-down labelled by either “Telecommute” or “Work Location Requirements” and the field is often optional.

When Matador accesses Bullhorn and gets job data, it tries to read the onSite value, and when present and equal to certain “trigger” values, we activate our Remote job features for that role.

“Trigger” Values

When a value is found in onSite, Matador compares the value against a list of “Remote” terms. If there is a match, Matador Jobs will consider the role a “Remote” job. The list of default “Remote” terms is:

  • No Preference
  • Telecommute
  • Off-Site
  • Off Site
  • Work from Home
  • WFH
  • Remote

In the event your company uses terms for Remote work that are not found in the above list or your terms are in your local language, your developer can use a the developer filter 'matador_import_remote_definitions' to teach Matador additional terms that can flag a role as “Remote”.

Remote Features

The following remote features are activated for jobs that contain a “trigger” value from onSite:

  1. “Remote” term for Locations Taxonomy, if setting is turned on.
  2. “Remote” bubble in the Job Info bar.
  3. Class matador-job-remote added to shortcode job listings, allowing theme developers to add styles to highlight these roles.
  4. Job Meta Field isRemote with the value of “Remote”, which template developers can use to detect remote roles and add features.
  5. Remote Job attributes in the Job Structured Data allowing external tools like Google for Jobs Search to promote your remote roles.

Setting Up onSite In Bullhorn

Like a majority of our features, Remote work features require some sort of data from the Bullhorn JobOrder data object to trigger them. Unlike a number of our features, the onSite data point we use to source this information from is not enabled by default in most Bullhorn accounts. Therefore, to take advantage of these features, this will require some initial setup in your Bullhorn account.

Configure “onSite” in Bullhorn Field Mappings

If you do not see “Work Location Requirements” or “Telecommute” fields on your Bullhorn edit job screen, it may mean onSite is not configured. You may need to enable it using Bullhorn’s Field Mappings tool.

As a general rule, we at Matador Jobs are experts in using the Bullhorn API, not the Bullhorn ATS web application. Therefore, we strongly recommend you make any changes to your Bullhorn field mappings with the help of Bullhorn support, unless you are experienced making these changes on your own. For this reason, we do not provide screenshots of this process.

  1. In Bullhorn, go to Admin > Field Mappings.
  2. Open a Job mapping and search for ‘onSite’ in the “Field” search box. Press Enter or Return to start search. This will narrow the list of fields to just onSite.
  3. In the field edit for the onSite field, uncheck “hidden” if checked.
  4. Scroll up and click “save”.

While you’re here, you can modify some other settings for the field if you desire, including:

  1. Change its label. The default is “Work Location Requirements”, which doesn’t scream “change me to make a job show as remote,” in our opinion. Feel free to change the label in a way that makes sense for your organization.
  2. Set the field as required. When a job is imported into Matador, no value in onSite will result in the job being marketed as on site, not remote. Make sure you require your recruiting team to select a value.
  3. Expand the field using the arrow at the left to review its “Value List”. Bullhorn’s default options are ‘No Preference,On-Site,Off-Site’. While you may add or remove from these values, we recommend only adding new values as your older jobs or 1st-party or 3rd-party Bullhorn tools may expect certain values in that list. See above for a list of terms that will trigger Remote features.
  4. As an alternative to changing values, you can edit the “Display Value List’ field to change what your recruiting team sees without changing the actual values in the field. This is ideal for users who use languages other than English, but also useful to leave existing values unchanged while making more clear options for recruiters when creating/updating jobs.

This is extremely important: Bullhorn allows users to set up templates using one or all of the Job I to Job V mappings. It is our opinion that all five mappings should be updated, so everything you did above you now need to do again for the four other mappings.

Update “Remote” Jobs in Bullhorn

After you’ve configured the onSite field for all Job I to Job V mappings, you can begin using it. Edit the jobs you’d like to market as “Remote” and change the onSite field to one of the values that trigger a “Remote” job handling in Matador. This change can now be imported into Matador.

Import Updated Jobs in Bullhorn

To ensure faster sync speeds, Matador may not update the job automatically. To trigger an update, make sure you do one of the following:

  • Republish the Job in Bullhorn, which will result in it being updated in Matador on the next regular sync.
  • On your Matador-powered website, go to WP Admin > Matador Jobs and then hover over the updated job and click “edit”. On the “edit” screen, click “Sync This Job.” This will force an update to occur immediately for just that job.
  • On your Matador-powered website, go to WP Admin > Matador Jobs > Settings and then click “Hard Sync”. This will force an update to occur for all jobs.

Digging Into the “Remote” Job Features

Though we explained each of the Remote Job Features above, let’s dig in a little bit! Some of these features work out-of-the-box while some can be tools in the template developer’s toolbox.

“Remote” term for Locations Taxonomy, if setting is turned on.

Many of our users prominently use the Locations taxonomy on their site, most often to “filter” jobs or aid in search. A job only has one location taxonomy term, usually state/province or city, but now a second can be added when the job is remote.

To use this, you need to enable the new setting “Remote” Location Taxonomy Term under Matador Jobs > Settings > Job Listings (tab).

Once set, on your next job sync, all your jobs that trigger “Remote” features will get a second Location term and the term will be searchable with your drop-downs or filters.

An example of the “Remote” Location Taxonomy Term in a list of states on a user’s site.

The value of the term defaults to “Remote”, translated to your local language if a translation file exists, unless filtered with the 'matador_import_location_remote_term_name' filter. The filter is shared with all “Remote” features.

“Remote” bubble in the Job Info block

Jobs that trigger “Remote” features will get a new bubble in the Job Info bar. If you are using the Job Info bar, you will see the bubble appear after the location and before the job type bubble.

Example of the “Remote” bubble on a Matador Jobs test site.

The bubble’s default label is “Remote”, translated into your local language if a translation file exists, unless filtered by the 'matador_import_location_remote_term_name' filter. The filter is shared with all “Remote” features.

matador-job-remote class on Function/Shortcode jobs

Most customization for Matador Jobs is styling jobs via CSS. If you use the [matador_jobs] shortcode to list your jobs, all job entries’ <article> tags will get an extra class matador-job-remote, giving theme developers new ways to promote a remote role using CSS styling.

isRemote meta field

All jobs that triggered Remote features will also have a value assigned to the isRemote post meta with the value of “Remote”. This opens up several use cases, including:

  • Use the shortcode [matador_job_field] or the Matador Jobs template function matador_get_the_job_field() and matador_the_job_field() to present a formatted html block.
  • Use matador_the_job_meta() or matador_get_the_job_meta() or the core WordPress’s get_post_meta() function to assign the value to a variable and perform logical operations or output its value in custom HTML.
  • Include isRemote in the fields parameter for the [matador_job] and [matador_jobs] shortcodes and their associated template functions matador_job() and matador_jobs() or in the matador_job_info() function.
  • and more!

The default value of the isRemote meta field is “Remote”, translated to your local language if a translation file exists, unless filtered by the 'matador_import_location_remote_term_name' filter. The filter is shared with all “Remote” features.

Remote Job attributes in the Job Structured Data (Basic)

Jobs that trigger “Remote” features will generate additional meta data in the Job Structured data block. These will communicate to Google for Jobs Search and other aggregators that access the structured data that the job is Remote or Work From Home.

Jobs will be promoted throughout the country where the job is located. A “Remote” job in New York, USA, will be promoted to people all over the USA. For this reason, please heed the two very important following notes about this:

  1. If your “Remote” jobs do not provide a location, the job will require values in the workLocationRequirements fields of the structured data.
  2. If you want to narrow or widen the markets your jobs can be promoted in, for example, the “Remote” job in New York, USA can only be offered to people in New York, USA, or a role in Frankfurt, Germany can be offered to people in Germany, Netherlands, and Belgium, you need to provide values in the workLocationRequirements fields of the structured data.

To use the workLocationRequirements fields in your structured data, see the related section on the Advanced Job Structured Data page.

Updated on April 23, 2021

Was this article helpful?

Related Articles