Job Roles & Candidates
Job roles are the core unit in Lynx. Everything—submissions, feedback, decisions, and chat—hangs off a role. This guide explains the role model, the candidate profile, and the submission workflow.
Job Roles
A job role represents an active search. A role includes:
- Role details (title, client, location, compensation, description)
- A pipeline (stages) that candidates move through
- A role-level chat for general discussion
- A hiring team: recruiting team members and client team members
- Candidate submissions tied to the role
Create a role
- Go to Job Roles
- Click Add Job Role
- Fill out role details and save
Role Settings
In role settings you can update fields and upload a job description file. The role supports extracting structured data from the job description to speed up setup.
- Open role → Settings
- Upload the job description file (optional)
- Click Extract to populate role fields from the file (overwrites existing values)
- Click Save to persist changes
Hiring Team (Recruiters + Clients)
Hiring team membership is role-specific. Invite recruiters and clients per role so access stays scoped.
- Open role → Settings → Hiring Team
- Invite under Recruiting Team Members and Client Team Members
- Click Save after changes
Candidate submissions
Candidates are created inside a role and move through a stage pipeline. The default pipeline includes:
- Pending Submission
- Submitted
- Interview 1, Interview 2, Interview 3
- Offer
- Hired
- On Hold (special state)
- Rejected (special state)
Add a candidate
- Open the role
- Click Add Candidate
- Enter candidate info and upload a resume (or paste resume content)
Candidate profile
A candidate profile is a structured review page that keeps key information in one place:
- Summary: AI-powered or manually written candidate summary
- Resume: formatted resume text view
- Candidate Information: contact and basic details (recruiter-editable)
- Recruiter Notes: internal-only notes visible to recruiters
- Chat: candidate-specific conversation and feedback
Submitting and moving stages
To submit a candidate to the client, move them from Pending Submission to Submitted using the stage/action controls. Stage transitions support:
- A notification message (editable before you confirm)
- Choosing who to notify
- Optional follow-up reminders (resend the last notification)
On Hold and Rejected
On Hold and Rejected are special states. They can be applied regardless of the current pipeline stage. Candidates can later be resumed (from On Hold) or reconsidered (from Rejected) to continue the workflow.