Job Publishing FAQ
As of October 1st, 2023, Indeed will be requiring an email address to be included with every Job Posting through Indeed Syndication via Jobcast. If the user in the "Published Contact Recruiter" field on the Job Publishing screen does not have an email address associated with them, the email will not be published to Indeed.
Overview
This article contains the frequently asked questions about jobs within
Frequently Asked Questions
How can I update information on an already published job?
If you want to use Indeed Syndication, then please contact Bullhorn Support to begin the setup process.
What happens when a candidate that already exists in my database applies for a job?
This is determined by what your company chose when the OSCP Enablement form was filled out: Parse web responses as existing if candidate is in database. Yes or no?
Yes: Automatically updates the fields on the candidate's existing record by parsing the new resume. The new resume is also added as an attachment under the Files tab on the candidate's record.
No: attaches the candidate's new resume to their existing record. This is meant to prevent any important information from being unnecessarily overwritten. In this case, you should review the newly attached resume and if it is more up-to-date than the information on the record, then you can parse it as an existing candidate from the Files tab.
If you would like to change the default behavior when existing candidates apply for jobs, please contact Bullhorn support.
Will I receive an email notification when a candidate applies to a position?
Email notifications are sent to the user in the Published Contact Info field. This field is configured on a per-job basis.
The Published Contact Info field may be hidden in your database. An administrator will need to unhide the field responseUserIDon all Job tracks using Field Mappings.
What happens when I copy published jobs?
Copied jobs will not be published automatically to the OSCP or Career Portal. A job must be manually published after copying the job.
Depending on your workflow, you may require a job to be approved as part of the publishing process. In this case, a standard user will not have access to publish the job, and a user with full job publishing entitlements will need to publish the job.