Job ATS v1: Candidate Finder

Overview

The Candidate A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider. Finder component is used to source Candidates A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider. for the Job A job (vacancy, position, role) is an opening for which a customer's client needs a placement. without having to navigate away from the Bullhorn ATS. To access the Candidate Finder window, navigate to the Toggle Candidate Finder icon on the left side of the screen.

Using the Candidate Finder

1. Go the Select Candidate Source dropdown and select a Candidate source from the following:
   • Global Contact Search
   • List Views
   • Match
   • Call List
   • Job Board A website where open jobs are advertised Application First stage of Job placement flow (Application> Submittal>Interview>Offer> Placement)
   • Potentials
   • Long List Name of a BH4SF custom object. It 'captures' Candidates that look like a good match for a Job, before the actual hiring process begins. It's like a list of potential candidates
2. Use the search box or select from the dropdown, depending on the candidate source selection.
3. From the list of Candidates displayed, mark the checkboxes next to the desired names.
4. Go to the Add to dropdown at the bottom of the window and select the stage to add the Candidate.
5. Select the Add icon .
   

Candidate Source Details

• Global Contact Search: Searches the Contact object.
• List Views: Shows the Contact List Views that the logged in user has access to.
• Match: Only for Orgs where Daxtra A BH4SF partner. One of the Search and Match / Resume Parsing services providers integrated with BH4SF Search and Match is configured. It will return the Candidates that match the job according to the criteria set as part of the Daxtra Search and Match configuration.
• Call List: Shows the Call Lists A Mass Mailing tool that's used to mass mail a list of candidates or clients that the logged in user has access to.
• Job Board Application: Only for Orgs that use the Job Board Application object. This object is used by some Bullhorn for Salesforce customers to store applications that are sent in from an external Job Board.
• Potentials: Only for Orgs where Daxtra Search and Match is configured. It will return Candidates that have been selected as Potentials in Daxtra Search and Match searches.
• Long List: The Long List object (formerly known as Opportunity Potential sales to new or established customers. Discussed) stores data of Candidates in the pre-application stage. It is not included in the flows and back end triggers of the job stage objects: Application, Submittal The Second Stage of Job application flow. This is when the recruiter sends the Candidate CV to the client, a sort of first introduction., Send Out The third Stage of Job application flow. This is when the recruiter sets up a job interview between Candidate and Client. and Send Out Schedule, Offer The fourth Stage of Job application flow. This is when the candidate is offered the position (details about salary, locations etc are shared and candidate decides if he wants to take the job), Closing Report Fifth Stage of Job placement flow, a Candidate that reaches the Closing Report Placement stage has been assigned to a job. In BH4SF, a 'Closing Report' is a record that captures all the information related to the newly filled position (name of Candidate, position, salary, start date, which recruiter gets credit for the hire etc.). However, it can be used in ATS v1 as a first stage and the Longlist swimlane Clusters, or Swimlanes, are servers that hold our customer's databases, each cluster is like an apartment building and each customer's database is like an individual apartment. can be added to the Kanban board The main User Interface in ATSv1 (the page that opens after a job/candidate is selected and that shows buttons, stage columns, or swimlanes, and cards). One of the three UI Views in ATS v2 (the others being List View and Table View). Whether or not you are using Longlist in the ATS v1 Kanban, you can source candidates from the Longlist object in Candidate Finder and add them from there to any other stage.