Documentation Index
Fetch the complete documentation index at: https://mintlify.com/chamals3n4/OpenATS/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Job Management is the foundation of your hiring workflow in OpenATS. Create detailed job postings with comprehensive descriptions, salary information, and required skills to attract the right candidates.Jobs can exist in multiple states: draft, published, inactive, closed, or archived. Only published jobs are visible to candidates.
Creating a Job Posting
Basic Information
Every job posting requires the following core details:Job Title
The position name that candidates will see (e.g., “Senior Full-Stack Engineer”)
Department
Associate the job with a specific department in your organization
Employment Type
Choose from: Full-time, Part-time, Contract, Internship, or Freelance(Values:
full_time, part_time, contract, internship, freelance)Location
Specify the job location or indicate if it’s remote
Job Description
Craft a compelling job description that includes:- Role overview and key responsibilities
- Required qualifications and experience
- Company culture and benefits
- Growth opportunities
Skills & Requirements
Add relevant skills to help:- Filter and match candidates automatically
- Power CV analysis and scoring
- Appear in candidate searches
Compensation Configuration
OpenATS supports flexible salary configurations to match your compensation strategy:Fixed Salary
Specify an exact compensation amount:Salary Range
Provide a minimum and maximum salary band:Salary information can be displayed on the public job posting or kept internal for recruiter reference only.
Job Status Lifecycle
Draft
Jobs start in draft mode, allowing you to:- Build out the complete job description
- Configure pipeline stages
- Add custom application questions
- Review with stakeholders
Published
When ready, publish the job to:- Make it visible on your careers page
- Accept candidate applications
- Begin receiving submissions
Managing Active Jobs
- Pause Applications
- Close Position
- Archive
Set status to Inactive to temporarily stop accepting new applications while keeping the job listing visible.
Accessing Jobs
By ID
Every job has a unique numeric identifier used internally in the system.By Slug
Jobs also have a URL-friendly slug (e.g.,senior-full-stack-engineer-2024) that:
- Appears in the public job posting URL
- Makes links more readable and shareable
- Is automatically generated from the job title
Deletion & Restrictions
This restriction ensures:- Candidate data is never orphaned
- Historical records remain intact
- Compliance requirements are met
Best Practices
Write clear, inclusive job descriptions
Write clear, inclusive job descriptions
Use gender-neutral language and focus on actual requirements rather than “nice-to-haves” that may discourage qualified candidates.
Keep skills lists focused
Keep skills lists focused
Add 5-10 core skills rather than an exhaustive list. This improves CV matching accuracy.
Update status promptly
Update status promptly
Close or pause jobs as soon as the position is filled to avoid collecting applications you won’t review.
Use departments consistently
Use departments consistently
Proper department categorization helps with reporting and hiring team assignments.
Next Steps
Configure Pipeline Stages
Set up your hiring workflow stages
Add Custom Questions
Create application screening questions
Build Hiring Teams
Assign team members to jobs
Start Tracking Candidates
Begin accepting applications