Recruitment software for a US billing desk

A candidate sends a resume, not a CV. A role is a req or an opening, and on a contract desk it is an assignment with a bill rate and a pay rate rather than a day rate. A contractor is W-2 or 1099 and the distinction changes the record, not just a label. Notice periods are short or absent, so the pipeline assumes a two-week horizon rather than a three-month one.

Salary fields store the currency a figure was quoted in and the period it was quoted for, so an annual base and an hourly rate are never compared as though they were the same number. Dates render month-day-year. Addresses take a five-digit ZIP and a state from a list rather than a free-text county.

None of this is clever, and it is the difference between a system a recruiter trusts and one they route around with a spreadsheet.

A US desk that reports on applicant flow has a structural problem: the data that has to be collected is exactly the data that must not influence a screening decision. Putting it on the candidate record next to the work history is the obvious design and the wrong one, because every recruiter who opens the record then sees it.

The design here separates the two. Self-identification data is captured through its own flow, stored apart from the candidate record a recruiter works in, and surfaced only as aggregate reporting. The screening surfaces never render it, and the audit log records who ran a report rather than who saw a field.

This is in build, not shipping, and the feature page says so with its evidence line. Nothing on this page should be read as a statement that it works today, and nothing anywhere on this site is a claim to be compliant with any part of federal or state employment law. The product gives the obligation somewhere to live; meeting it remains yours.

Recruiting outreach in the United States runs into two separate rule sets at once. Calls and texts sit under the Telephone Consumer Protection Act, where what matters is whether you can show the consent you relied on and when it was captured. Email sits under CAN-SPAM, where what matters is that an unsubscribe is honoured everywhere and quickly.

So consent is a field, not an assumption. Each candidate record carries the channel-level permission you hold, the date it was captured and the surface it was captured through. A suppression list is global rather than per-sequence, so a candidate who opts out of one cadence is out of all of them, and an attempt to message a suppressed record is blocked at send time rather than reported afterwards.

The same caveat applies as everywhere else on this site. These are fields and workflows with build statuses on their own pages. They are not a compliance product and they are not legal advice.

Indeed and ZipRecruiter are the two boards most US desks care about, and it would be easy to put two logos on this page and move on. The real state is that both connectors are in build rather than live, as their integration pages state with an evidence line each. Posting to LinkedIn and Indeed ships today; multi-board posting, where one req goes to several boards from one form, is in build for the Wave 1 release.

Until those land, the honest workflow is that you post through the board's own interface and bring applicants in through email capture and bulk resume import, both of which are live. Bulk import parses a folder of resumes into structured records, runs duplicate detection during the import rather than afterwards, and keeps the original file alongside the parsed text.

The integration pages are updated when a connector goes live, with the date. Nothing on this site shows a board logo it has not earned.

Three plans, priced per recruiter seat in US dollars: Starter at 39, Professional at 49 and Enterprise at 99 per user per month, with roughly seventeen percent off for annual billing. Starter and Professional carry a three-seat minimum and Enterprise a five-seat minimum. Enterprise also carries a platform fee alongside the seats. The trial runs fourteen days, takes no credit card, and there is no free-forever tier behind it.

The list prices themselves are flagged as provisional. Willingness to pay has not been validated with enough unrelated paying customers to call them locked, so they may move before general availability. Saying that now is cheaper for everyone than a quiet correction later, and it is the same disclosure the pricing page carries.

Sales tax is excluded from every figure. Whether it applies depends on your state and your exemption status, and the treatment applied appears on the invoice rather than being asserted here.

Primary data residency is AWS us-east-1 in the United States, with encrypted backups. A SOC 2 readiness programme is under way with continuous control monitoring; a Type I report is the first deliverable and no Type II report is claimed until one has been issued. California consumer rights under the CCPA are honoured for all US customers, and a data processing agreement and sub-processor register are published.

Read that list as what it is. A readiness programme is not a certification, a target is not a guarantee, and a published agreement is a document rather than an audit. The trust pages set out each posture with the same wording, and if your security review needs something that is not on that list the answer is better had during the sales conversation than after the first invoice.