> For the complete documentation index, see [llms.txt](https://knowledgebase.flaik.com/flaik-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.flaik.com/flaik-knowledge-base/for-sups-managers/hiring/creating-a-job.md).
# Creating a Job
The Hiring tool was created to help you streamline the way you hire staff and provide visibility to your team on where you're at and how many instructors you still need to hire.
To start with Hiring, you need to create a new job. Simply click the "Create new job" card in the Jobs Page to get the ball rolling.
## Add Six Job Details
1. **Job Process Name** - an internal name to help you identify who this is for (e.g. Adult Instructors Full Time Returning)
2. **Employment Type** - this is typically Full Time Hourly, Part Time Hourly, etc... If you need to adjust or add Employment Types, this can be done through Admin Settings.
3. **Primary Discipline** - everyone needs a primary discipline. So select the best that matches the job you are creating. If you are creating an admin or child care job, you can use the Admin Discipline that we've added just for this purpose.
4. **Hire Type** - New or Returning (I think you've got that one).
5. **Positions Required** - This is to help you track how many instructors you need. As you send out offers and get responses, you'll see the circle on the job move from 0/200 to 25/200. This indicates how many staff you've hired for this job and how many you've got left to go.
6. **Job Title** - Mostly you'll use the Instructor job title for this one but you've got options (e.g. Child Care, Admin, Team Lead, Apprentice). You can add, edit, or delete job titles in Admin Settings.
**When you've filled out each area, click the ****Next**** button.**
## Job Offer Email Template
This is the first email that your staff will see (probably ever from flaik) so make it clear. The editor is on the left-hand side and there is a live preview on the right. The preview will update as you type in the editor.
{% hint style="warning" %}
**Note**: When composing your job offer letters, refrain from editing bracketed characters as these are used to query instructor names and job titles
I.e. **{{firstName}} {{resort.name}} {{offer.jobTitle}}**
{% endhint %}
## Insert Mail Merge
When editing the job template, you can use the **Insert mail merge** function to pull in data from staff profiles. These are limited to the fields displayed below.
## Offer Format
After creating the job email template, you'll need to complete the Job Offer Template. This contains the job offer details and is what the candidate will see when they click through from the email. We've put in standard mail marge fields like Job Title, Employment Type, Base Pay Rate and Request Pay Rate but you can add, delete or change these to meet your requirements.
{% hint style="info" %}
**Note**: If you need to add a document to the job offer, you can do this via the hyperlink  button in the editor toolbar
{% endhint %}
## Job Offer Reminders
\
After finishing the job offer template, you just need to finalize the reminders. You've got options for when you send the first reminder (1 Day, 2 Days, 1 Week, 2 Weeks) and any reminders you want to send (1, 2, 3).
## Send test email
To test, you can send yourself a test email so that you'll see what the instructor sees.
To finish creating your job, hit the blue Create Job button down the bottom and you're all set.
### Next Step: [Add Staff to Talent Pool](/flaik-knowledge-base/for-sups-managers/hiring/add-staff-to-the-talent-pool.md)
{% hint style="success" %} **CONGRATS!** You've completed Job Creation. 🎉
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://knowledgebase.flaik.com/flaik-knowledge-base/for-sups-managers/hiring/creating-a-job.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
