Job Posting
The job posting page is where one opening is run from start to finish: its dates, who applied, how they are scored, each stage's work, how the posting is set up and what it costs. Open it from HR → Hiring → Recruitment → Postings (click a row), from an open position on the Hiring Dashboard, or from a batch. A new posting starts as a draft: New Job Posting explains the form.
The page has up to six tabs: Overview, Applications, Screening, Stage work, Set-up and Budget. You see only the tabs your role allows: Applications needs applicant access, and Budget needs offer access or hiring-cost access (each half of the tab shows to its own access: the salary half with offer access, the hiring cost half with hiring-cost access).
The header and the posting's life
A posting is Draft, Pending approval, Published or Closed; the status and a Batch or Individual chip sit beside the title and code. The days to the next stage cutoff are on the Overview (Next cutoff in General information), not in the header. The buttons follow the status:
An approver sees Waiting on your approval (with Review approvals) when their level is next, and decides with Approve or Reject in the header. Reject asks for a reason: the posting goes back to draft and shows Sent back by the Approver with that reason. The person who created a posting cannot approve it; they see Waiting for another approver.
Overview
The first card, Pipeline, is the posting's workflow as its progress line: the stages in order (closed, open, ahead, each with its cutoff), the workflow's name and the run's status, and where the run is now. Click a stage to open its work (Applications, Screening or Stage work); Open run opens the run in Processes. The workflow starts when the posting is published. A posting made without a workflow says so: its stages move on their cutoff dates (the workflow is chosen when a posting is made). The next card, General information, holds the posting's facts (the code, status and hiring type are in the header). Below it come, when they apply: Sources (where the applicants came from, with how many were hired), the Hiring cost meter (hiring-cost access), Targets by section (each section's "3 / 6 hired"), Manpower requests (Manpower Request access) and the Job description as it was when the posting was made (a copy: later edits to the job description never change a posting that is already out).
| Stage | Cutoff | Days left on 10 Nov 2026 | Applications at the stage | General information reads |
|---|---|---|---|---|
| Exam | 15 Nov 2026 | 5 | 12 | Next cutoff: Exam · 15 Nov 2026 · 5 days left; To decide: 12 still at Exam › |
| Exam (nobody left at it) | 15 Nov 2026 | 5 | 0 | Next cutoff shows; To decide is hidden |
Applications
This posting's own applications, in the same list as Recruitment › Applications with the posting already chosen: the stage cabinets and quick views, the Board and Table views, bulk decisions and the Excel export. In the Table view, click a column header for its menu: sort, or Filter by [column]… where the column can be filtered. Click a name to open the application record.
Screening
The Screen stage scores every application against rules you set, so HR reads the strongest first. Scores only rank applicants. A missed must-have moves someone down; the cutoff hides low scores. People make every decision.
| Applicant | Score | Shown in the ranked list? |
|---|---|---|
| Applicant A | 72 | Yes, rank 1 |
| Applicant B | 55 | Yes, rank 2 |
| Applicant C | 38 | Hidden; the toggle reads Show below cutoff (1 hidden) and reveals it |
Stage work
One page for each stage that needs HR's hands: pick the stage in the rail and work its people. The Stage work stages are Exam, Interview, Briefing, Document check, Detailed application and Offer; the Screen stage is worked on Screening, and every other stage on Applications. Configure (the stage's settings) is on the stage; the sections below say what each kind of stage records.
Schedule (Exam, Interview, Briefing) picks the Candidates, a Start (blank keeps them unscheduled), a Length (minutes) that sets the end time, One after another (one slot each), a Location, a Meeting Link (starting with https://) and a Note. An interview also needs the Interviewers and a Lead, who enters the panel consensus; when you pick no lead, the first interviewer is the lead. The button reads Save Schedule (n) for n candidates. Candidates are not emailed: tell them the time and place yourself.
Ranking and Decisions is the list on each stage: people ranked by the stage's score, one toolbar with the quick views and the bulk bar. While rows are ticked the bulk bar (Advance, Hold, Reject) replaces the figure tiles, so the list never moves. A person decides; the score only ranks. Advancing checks the stage's Required to move on.
| Panel method | Stage score | Example: interviewers score 80 and 90 |
|---|---|---|
| Average | The average of the interviewers' scores. | 85 |
| Separate | Each score is shown side by side; their average ranks. | 80 and 90 shown; ranks on 85 |
| Consensus | One score the panel agrees, entered by the lead interviewer or HR. | The agreed score, for example 85 |
The Medical Result Step
The medical is not a Stage work stage: it is recorded on the workflow and shows on the candidate's Medical tab. On the Medical workflow's Medical result step you answer the result once: pick Cleared, Repeat labs or Not cleared in the step's Medical result question above the form. The Medical Result form records that answer with the round (clinic, dates, class, notes); it does not ask the result again.
Clinic Links and Exam Result Files
When the medical or the exam is run by an outside clinic or exam provider, keep their links and files on the posting and the candidate:
Detailed Application
A Detailed application stage (after the exam, before the interviews) asks the candidates who passed for a longer form and their documents, through a link of their own, like the first application form.
- Set the documents onceIn Hiring → Settings → Pipeline defaults, Detailed application documents lists what applicants attach (built in: Transcript of Records, Diploma, PSA birth certificate, Signed application form). Mark each one Required or not, rename, remove or add.
- Adjust the stage's formOn the posting, open Stage work, pick the Detailed application stage and click Edit form. The form starts with a More about you section for your own questions and a Documents section with one file question per document. Every save makes a new version; applicants who already answered keep the form they saw.
- Send each applicant their linkEach applicant at the stage has a row. Copy link copies their own link (the same link if you copy it again) to send them. They open it on the careers site, answer, attach the files (PDF, Word, JPG or PNG, up to 10 MB each) and send it once.
- See what came backThe row shows Waiting or Sent back, and any required document missing. The answers and files are on the candidate's record, Application tab; each file opens through a short-lived link and every opening is logged. A link stops working once the applicant moves to another stage before sending it.
Set-up
The posting's own configuration, in three sections: Stage set-up (the timeline and the pipeline workflow), Application Form and Sourcing Links, plus Batch on a batch posting (the batch's other job positions, and Add job position to it). A dot on the tab means unsaved Application Form edits.
Stage set-up
Above the stages, the timeline names the pipeline they came from (From pipeline: and its name) or reads Built by hand.
Filling the Stage Dates
A posting with many stages needs a start, cutoff and end for each. On the posting's timeline, Fill dates lays them out from the Open and Review days set in Pipeline defaults, back to back. Open and review days are working days: rest days, holidays and company days off are skipped, and no start, cutoff or end lands on one. The rest days are those of the work schedule most employees are on (Saturday and Sunday when there is none); the holidays and days off are the company's national and local holidays and whole-company days off, and an exchange working day counts as a working day.
- Hire-by date (work backwards) — the last stage ends on the working day before the hire-by date.
- A start date (work forwards) — the first stage starts on the date you pick.
Each stage opens at 09:00 and its cutoff and end are at 17:00. Stages that are already open or closed keep their dates. Every date stays editable; nothing is saved until you click Save Timeline. If the first stage would start before today, Ante says so — pick a later hire-by date or shorten the stages. If the company calendar can't be read, the dates are laid out on calendar days and the message says so.
| Stage | Starts | Cutoff | Ends | Days skipped |
|---|---|---|---|---|
| Application | 1 Dec 2026, 09:00 | 21 Dec 2026, 17:00 | 28 Dec 2026, 17:00 | Open: the weekends of 5–6, 12–13 and 19–20 Dec and the 8 Dec holiday. Review (22, 23 and 28 Dec): the 24 and 25 Dec holidays and the 26–27 Dec weekend. |
| Screening | 29 Dec 2026, 09:00 | 7 Jan 2027, 17:00 | 7 Jan 2027, 17:00 | Open (29 Dec, 4, 5, 6 and 7 Jan): the 30 and 31 Dec and 1 Jan holidays and the 2–3 Jan weekend. |
The Posting's Pipeline Workflow
A posting runs one workflow of its own: the workflow behind the Hiring pipeline chosen in New posting (Hiring › Settings › Hiring pipelines keeps each pipeline's workflow in step). The posting's stages come from it, in order: one Hiring stage step per stage, then Hiring offers; steps added in the Process Builder (an approval, a task) run between them. Each stage card names its step. Each stage's step finishes when you confirm that stage's cut in Applications, and Hiring offers finishes when accepted offers reach the openings or the hire-by date passes. The Stage set-up tab shows the workflow and its run, with Open the workflow; the workflow can't be swapped afterwards, and changing it later doesn't change this posting's stages (edit them here). The workflow starts by itself when the posting is published; if it is not running on a published posting, Start workflow starts it.
An older posting whose stages were linked to a workflow's steps by hand keeps those links, shown read-only until it closes. A posting made before pipelines kept a workflow says so; its stages move on their cutoff dates.
A posting's pipeline workflow runs once per posting, so it is never offered in an application's Start workflow list.
Application Form
What applicants fill in on the Careers site. General Information lists the standard fields: First Name, Last Name and Email are always shown and required; Middle Name, Mobile Number, Date of Birth and City can each be shown and required. Below it are the posting's own Questions, each Required or not, of these types: Short text, Long text, Single choice, Multiple choice, Yes / No, Date, Number, File request and Rating scale.
Every save makes a new version; applications already in keep the questions they answered. A closed posting's form cannot change.
Sourcing Links
Share a separate link on each channel to see where applicants come from. A Company site link is made when the posting is published. Add Link asks for the channel (the list kept in Hiring Settings › Sourcing channels), a label HR recognises, and for a referral link the referring employee, who is credited. Each link counts its applications and can be switched off.
Starting From an Earlier Posting
A posting you run again (the same channels, the same questions) does not need to be set up from scratch. On the posting, click Copy from another posting:
- Sourcing Links tab — every active link of the posting you pick is added as a new link with its own address (so each posting counts its own applicants). Links the posting already has are skipped.
- Application Form tab — the other posting's form replaces this one as its next version. Applications already in keep their answers. Save or discard your edits first.
A closed posting takes neither.
Budget
Shows with offer access or hiring-cost access, each card to its own access: Salary with offer access, Hiring cost with hiring-cost access.
| Budget per opening / month | 30,000 | |
|---|---|---|
| Openings | × | 2 |
| Salary budget / month | = | 60,000 |
| Committed / month (accepted offers) | − | 28,000 |
| Left / month | = | 32,000 |
| Spent (cost lines not voided) | 18,000 | |
|---|---|---|
| Hires | ÷ | 2 |
| Cost per hire | = | 9,000 |
On a batch the budgets of its postings are summed; open a posting for its own cost lines.
How It Connects
Set up first
- New Job Posting — creates the draft with its job description, openings and first stages.
- Pipeline Defaults — the approval rule, the Open and Review days that Fill dates uses and the offer answer window.
- Interview Guides — a stage can copy a guide's questions and criteria instead of writing them again.
Gets its data from
- Manpower Requests — approved requests the posting fills, shown on its Overview.
- Talent Pool — Invite to apply stores an invitation to a published posting for people kept for later; nothing is sent from Ante yet, and the message (from the Talent Pool settings) can be changed before sending.
Feeds into
- Application record — each applicant of the posting has one, where stage decisions are made.
- Interviews — interviews scheduled on a stage show in the Interviews list and calendar.
- Offers — offers are made at the Offer stage and counted against the posting's budget.
- Hiring Reports — the Funnel counts each posting's applications, offers and hires.