Vacanta

Publication is checked against a transparency policy, and it fails closed. Every vacancy resolves a jurisdiction profile from its work location and eligible regions. The one that ships requires a salary minimum, maximum, currency and period, and forbids asking a candidate about their salary history. If a vacancy is missing a required field, or no active profile resolves for it, it does not publish. There is no override switch. When an employer complains that their posting will not go live, the answer is almost always a missing salary range.

Approving does several things in one indivisible step: it re-checks that the vacancy is still eligible, consumes exactly one posting entitlement (unless Launch Free Mode is on), makes the canonical version live, and appends to the ledger and the lifecycle history. Then, after the write is safely committed, it refreshes the public pages, queues the Google projection and notifies the employer. Those later steps can fail without undoing the publication — if the Google projection does not go out, the vacancy is still live and the syndication task retries it.

Rejecting records a reason. The employer sees it, can fix the vacancy and resubmit. A rejection does not consume their credit.

Approving does several things in one indivisible step: it re-checks that the vacancy is still eligible, consumes exactly one posting entitlement (unless Launch Free Mode is on), makes the canonical version live, and appends to the ledger and the lifecycle history. Then, after the write is safely committed, it refreshes the public pages, queues the Google projection and notifies the employer. Those later steps can fail without undoing the publication — if the Google projection does not go out, the vacancy is still live and the syndication task retries it.

Rejecting records a reason. The employer sees it, can fix the vacancy and resubmit. A rejection does not consume their credit.

Vacancies also carry a promotion slot: a Spotlight buys a 14-day pin plus eligibility for one newsletter placement. Featured status is derived from an active promotion rather than a flag someone sets, so it expires on its own.

Search runs on the database's own full-text index with weighted ranking and hard filters. There is no external search service and no model call on the search path, which is why results are fast and why search keeps working when everything else is degraded. Results explain themselves — a listing can show which of the candidate's skills and constraints matched.

Matching is assistive only. Nothing in Vacanta automatically rejects a candidate, hides them from an employer, or makes an employment decision. A human moves every application.

A scheduled task materializes each due run, resolves the matching vacancies and the recipient list, and sends in bounded batches. One failed recipient never aborts the rest. Suppression, alert pause, unsubscribe, bounce and complaint events are all applied before the next send, and the transactional stream stays separate from the broadcast stream so a bad newsletter cannot damage the reputation that carries password resets.

Submitting captures a snapshot: the vacancy as it stood, its screening questions as they stood, and the candidate's profile as it stood. That is what makes an application defensible months later — the posting can be edited or expire and the application still shows what was actually agreed to.

Screening questions use a fixed, constrained set of question types. This is a job board, not a form builder, and the constraint is what lets the jurisdiction policy reject a prohibited question — such as one asking for salary history — before the vacancy is ever published.

Moving an application validates the target stage against that company's own stage set and appends a history row recording who moved it, from where, to where, when, and through which surface. The history is append-only — a stage can be corrected but the record of the earlier move is never erased. The candidate is notified according to the company's policy.

Recruiters see only their own company, and within it only the vacancies assigned to them. A company owner sees everything in their company. You see everything everywhere.

Notes and ratings attach to an application. A rating currently rides along with a note rather than being set on its own.

With the worker configured, an uploaded file is queued and extracted into profile fields a few minutes later. The candidate reviews and confirms; anything they confirm is never overwritten by a later reparse.

Without it, three things still work exactly as before: uploading a file, editing the profile by hand, and submitting an application. Only automatic extraction is unavailable. That ordering is deliberate — an application is written to the database before any parsing is attempted, so a slow or dead worker can never cost a candidate their submission.

If parsing appears to do nothing, check that the worker is configured in the admin integrations area and reachable, and that the parse-dispatch scheduled task is running.

While it is on, an approved vacancy still creates and consumes a zero-price entitlement through the same ledger, the same moderation and the same expiry. Free publishing skips the payment, not the process. When you switch it off, entitlement checks apply from that moment.