- Print
- DarkLight
Setting up your first positions
This page details how to get your first positions setup in Leadline. As a pre-requisite, we suggest you read the Leadline Platform Overview before you read this page.
In the Leadline platform, a Position represents a job requisition plus the associated advertising, application, and automation rules for that job. If you prefer to call it a 'job', that is fine - but note throughout the remainder of this guide we will use the term Position.
Learn More
Why the term “Position”? It’s more empowering as it pertains to finding quality candidates. Read the post we wrote about it here.
Basic overview of a Position
Using the definition above, here is a high-level breakdown of a Position in Leadline:
Job Requisition - The job-specific details directly related to the role. This includes things like job title, job status, job code, job location, and job description.
Advertising Rules - The way the job is advertised, and where it is advertised. This includes the ad template for display purposes, and the follow-up messages and processes that occur when an application is received.
Application Rules - The basic candidate information collected in the 5-minute application. This might include things like resume, start data, certification, start-date availability, working preferences, and a virtual cover letter.
Automation Rules - The workflow processes & tasks the system will automate for you. This includes things like source tracking, managing team member access, organizing the job for reporting purposes, scheduling interviews with candidates, and sending SMS job updates.
About Position statuses and the publishing process
Leadline allows you to make iterative updates to your jobs, without having to "re-post" the job if it has already been advertised somewhere. To do this, the system implements a common publishing workflow outlined below:
<Visual depicting publishing lifecycle>
If the job is "published", it means candidates can apply to the job; if they click on a Leadline-hosted link to the position, they will see the Landing Page for that job.
About Pages
Leadline allows you to customize what information is displayed to a candidate when they click on a link to the position. Personalizing this experience as much as possible is important for increasing your candidate conversion rate. To do this, you want to make sure the branding and content for the job is engaging, and has a clear call-to-action to entice them to apply. You can do this using the Pages feature in Leadline.
Our Customer Success team is happy to help you set up your first template with high-quality, nicely branded content from your company's website. Contact your customer success manager for setup support.
You can implement multiple templates and use them interchangeably with any of your jobs. This is a great tool for teams who want to integrate their marketing resources with Leadline where content may be developed based on the target demographic or audience for the job ads. Two examples;
Agencies working on behalf of their clients can promote each client's respective brand effectively and professionally as part of their recruiting/hiring service.
Internal hiring teams can run campaigns for different jobs based on category or type (eg. contentA is displayed for Job1 & Job2 ads, and contentB is displayed for Job3 & Job4 ads)
In addition to Landing Pages, your marketing team has another opportunity to drive additional value to your brand through the Leadline process - at the end of the application. After a candidate application is successfully submitted, the platform will serve a customizable 'Match' or 'Not a Match' message to the candidate, which can include links to additional resources or next-steps requirements.
Important note:
The Match and Not a Match pages are served based upon the score the candidate receives on their application. If it is 50% or higher, they receive the Match message. If they score below a 50%, they receive the Not a Match message. For one uniform message across all jobs, set the contents of your Match and Not a Match pages to the same information. We are currently planning on improving this for the community (ETA Summer 2024).
Some example uses of the Match and Not a Match page are as follows:
Match Pages:
Fast-tracking
A candidate who uploads all the requested pre-qualifying information and responds favorably using preferred answers (configured by the recruiting team) should be told their application will move quicker than others and should standby for next steps, an interview, etc.
Expectation setting
A candidate who provides more than 50% of the required and requested information might want to look out for a call or text from a recruiter, versus someone with less information who may need to look out for an email requesting more information (or visa-versa, depending on your process for handling higher-quality candidates).
Not a Match Pages:
Soft rejection messages
A candidate skips the sole 'upload your resume' question and scores a 0%. You might want to let these candidates know that without a resume, the process will move slower and therefor they should expect a call or text from you requesting more information.
Hard rejection messages
A candidate does not consent or respond favorably to a deal-breaker question and needs to be told they have been formally disqualified for not adhering to that requirement ("as required by _______.")
About Application Questionnaires
Leadline allows you to collect information from your leads to assist you in accelerating your hiring and decision making process. To do this, the system lets you add application questions to your jobs. Unlike most application processes, at Leadline we are collecting something we call quality intent signals by gauging how interested the candidate is to work for your company based upon the information they are willing to give you up-front.
By default, every job has 1 pre-defined question: a resume collection question, and the resume upload is not mandatory (optional).
Questions for a specific job can be added manually using Leadline's portal interface. You can choose some questions in an out-of-the-box template library, or you can add custom questions.
Coming soon - Customizable question libraries
Customizing your question library is on our roadmap for Summer 2024. Reach out to your customer success manager for more information on the release date.
Certain questions in Leadline ask for you to configure a preferred response. This value will train the system to specifically highlight users who respond with this preferred response value (hence the term, "match score"). This is a great way to quickly filter through candidates using a CRM-style search & filter experience based on opt-in data supplied by the candidate before beginning to parse through resumes.
Some examples of use cases and questions for the Leadline Apply Process:
Collect a resume.
Collect a virtual cover letter.
Collect a start-date.
Pre-capture acknowledgment of things that will be required "during later stages in the application process"
Collect working preferences (eg. shift schedules, remote types)
Collect proof of on-hand licensure or certification
Lastly, every application in Leadline has a basic compliance attestation and capture form to weed-out people who try to skip the application altogether or potentially provide inaccurate/fraudulent information.
The (summarized) end-to-end Position Apply Process
To summarize everything in the above sections, here is a visual that summarizes what the logical candidate journey and workflow looks like for a job published through Leadline.
Click here to see a live view of a demo applicant experience using a dummy position setup by our team.
<Visual>