Using the Legacy Career Portal
As of January 15th, 2024, the Legacy Career Portal will no longer be available. While the product has been deprecated for some time, this means you will no longer be able to access it at all after January 15th.
Overview
Bullhorn's Career Portal is a configurable website that gives job seekers access to your company's published jobs. Note that this article describes the features of our legacy Career Portal. To learn about our current offering, view the Publishing Jobs to the Open Source Career Portal and Indeed article.
Upon enabling the Career Portal, Bullhorn will provide you with your Portal's unique URL. Users can then include this URL in email signatures, social networking accounts, and, most commonly, on your corporate website. However, it's important to note that the Career Portal is only supported for Internet Explorer and Firefox, and, if linking from your website, is not supported when used in an iframe or an embedded link. Instead, the Career Portal must open in its own browser window.
How Candidates Use the Career Portal
Anyone can browse your public job listings in the Portal. However, in order to apply for a job, candidates must create an account, or "profile" for the career portal, providing the following information (required fields are marked by a red asterisk):
|
|
Candidates also have the option of uploading a single resume. Candidates cannot upload multiple resumes, or change a resume after uploading it.
When the candidate saves their profile, two things happen:
- Bullhorn parses the candidate’s profile information to create a new candidate record.
- By default, this new candidate record in Bullhorn has a status of New Lead and is owned by your company’s Unassigned account. If a candidate tries to create a second profile with the same email address, Bullhorn will recognize the account as a duplicate and not add it as a record. It’s important to note that no one is email notified when these new records are parsed into Bullhorn. However, all candidates who create a profile appear on the Candidate Web Responses list.
- Bullhorn sends the candidate an automated welcome email containing their profile username and password.
- The candidate can use the credentials contained within the automated email to log into the Career Portal and apply for jobs, forward jobs to friends, and update their contact information if necessary. If a candidate updates the contact information in their profile, Bullhorn automatically updates the corresponding information on their candidate record. The reverse is also true; if a user updates the candidate’s contact information in their Bullhorn record, the information in the Career Portal profile is updated accordingly.
Once the candidate applies to a job listed on the Career Portal, they appear on the Job Web Responses list. Bullhorn logs a job web response against the associated job record in Bullhorn and the owner of that job record is email notified. If the candidate applies to the same job several times only one job web response is logged; however, a note is added for each additional post. If a candidate applies to several different jobs, a job web response is logged for each job. A job web response does not create an internal submission; rather, they are meant to indicate interest in a job and give users the opportunity to review each candidate before deciding whether to submit them to the job. Once the candidate is submitted or rejected, they no longer appear on the job web responses list.
Publishing Jobs to the Career Portal
Users with the required action entitlements can publish open jobs directly from the job records in Bullhorn simply by choosing Publish from the Select an Action drop-down and then clicking Publish in the Corporate Job Board section. Closed jobs cannot be published to the Career Portal. For step-by-step instructions, view the Publishing Jobs to Your Corporate Website article.
If you are using the standard Career Portal and the Web Services API 2.0, the application will not generate events in the Bullhorn API system. For more information, view the API documentation.