Job Posting Software: Distribute Roles Without Wasting Budget

The numbers behind this

What does job posting software actually do?

Job posting software takes one approved requisition, pushes it to every place candidates look, and pulls the resulting applications back into a single queue. Publishing is the easy half. The half that decides whether the money was well spent is measurement: which board sent the applicant, what that applicant cost, and whether anyone from that source reached an interview. Tools differ most in how honestly they report that. Some show clicks and applies and stop there. Better ones follow a source through to hire, so a board that produced fifty applicants and zero interviews can be switched off in week two instead of month three. If a tool cannot answer which source produced your last five hires, it is a publishing utility rather than a distribution system. Buyers comparing whole platforms usually start from what an ATS includes and treat posting as one module inside it.

Free boards, paid boards, or niche sites: which should you use?

Match the channel to how scarce the skill is. Widely available roles with large applicant pools rarely need paid placement. Free listings and your own careers page usually fill them, and paying only buys more resumes to read. Scarce or licensed roles behave the opposite way. The audience is small, so a niche board with two thousand qualified subscribers beats a general board with two million casual browsers. Aggregators sit in between: broad reach, pay per click, useful for testing demand before committing to a placement fee. A workable first test is one broad channel plus one specialist channel per role family, run for two weeks, keeping whichever produced interviews. Volume is not the metric. A channel that sends eight applicants and three phone screens is worth more than one sending four hundred and none, even at a higher unit price.

• ▸ Broad boards: fastest reach for roles with big applicant pools
• ▸ Aggregators: cheapest way to test demand before paying a placement fee
• ▸ Niche and association boards: often the only place licensed candidates look
• ▸ Your own careers page: no media cost, and it converts best when the apply flow is short

How does syndication work, and why do postings sometimes not appear?

Syndication means your system publishes a structured feed, usually XML, that boards and aggregators read on their own schedule. You do not push a posting to each site individually. You publish once, and each partner crawls the feed, decides whether the record is complete, and lists it. That indirection explains most missing-listing tickets. A blank location, an empty pay field where the partner requires one, a description under a minimum length, or a title carrying an internal requisition code can each cause a record to be skipped without any error reaching you. Refresh timing matters too. Some partners re-read hourly, others daily, so a correction can take a day to surface. Before escalating, confirm the role is genuinely open, the feed includes it, and every required field is populated. Enforcing those field checks at publish time is a good use of recruitment workflow automation.

What should a job posting cost per qualified applicant?

Judge spend on cost per qualified applicant, not cost per click or cost per applicant. Cost per click tells you what traffic costs. Cost per applicant tells you what a form completion costs. Neither tells you whether the person could do the job. Divide the money spent on a source by the number of applicants who passed your screen, and the ranking usually reorders itself: the cheap board becomes expensive, and the specialist site that charged a flat fee becomes the bargain. Set the benchmark against the whole hire, not a media budget in isolation. With average cost per hire at $5,475 (SHRM 2025 Benchmarking Report), advertising is one line among agency fees, referral bonuses, and recruiter time. If that total has never been split out, the breakdown in our guide to cost per hire is the place to start before arguing about board pricing.

Why do the same applicants show up from three different sources?

Because aggregators re-list postings that originated elsewhere, and candidates click more than one of them. Someone sees a role on an aggregator, does not apply, sees it again on a general board, then applies through your careers page a week later. Three touch points, one person, three systems each claiming credit. Duplicates also appear when the same candidate applies to two similar requisitions. Handle it in two places. First, deduplicate on email at intake, so recruiters see one profile with a full history rather than three thin ones. Second, decide an attribution rule and write it down: first touch, last touch, or the source recorded at submission. Any consistent rule beats an inconsistent one, because the comparison between sources is what you are actually buying. Reporting that quietly double counts will justify budget that produced nothing, which is the expensive version of this mistake.

When should you stop spending on a job?

Set the stop condition before the campaign starts, because almost nobody cancels a running job ad on instinct. Three triggers work well. Stop when the role has enough screen-passed candidates in play to fill it twice, since extra resumes past that point add reading work and no speed. Stop when a source has spent its test budget without producing a single screen-pass, and move that money rather than raising the bid. Stop when the requisition itself is stalled: if interviews are not being scheduled, buying more applicants deepens the backlog while the candidates already waiting go cold. Average time to fill sits around ~45 days (SHRM 2025 Benchmarking Report), and most of that is internal process rather than a shortage of applicants. Fixing the delay usually beats buying more traffic, and the tactics in reducing time to fill cost less than another sponsored week.

• ▸ Enough screen-passed candidates in play to fill the role twice over
• ▸ A source that has spent its full test budget with no screen-pass
• ▸ Interviews not being scheduled, which no amount of extra traffic fixes
• ▸ A requisition put on hold internally but still publishing and still charging

How do you write a posting that converts, and what must it disclose?

Write for a skim first, a decision second. Candidates read the title, the location and work model, the pay information, and roughly the first three lines. Everything below that gets read only once they are already interested. Lead with what the person will own in their first ninety days, keep requirements to things you would genuinely reject someone for, and name the work model plainly. Internal jargon and requisition codes in a title suppress both search matching and click-through. On disclosure: many jurisdictions now require a pay range in the advertisement, and the rules differ by country, state, and city, sometimes keying off where the candidate sits rather than the employer. Treat that as a question for your own legal advisor, keep a per-location pay field so the right range publishes automatically, and default to publishing it. Reusable job description templates keep those fields consistent across every posting you distribute.

What do free job posting sites actually give you?

Free listings are worth using, as long as you know what free buys. On most general boards and aggregators a free post gets an organic slot that competes on recency and relevance with everything else on the site, including sponsored listings placed above it. Visibility decays within days, and nothing tells you when it has. Free tiers also tend to cap how many roles run at once, limit how long a listing stays live, and give little or no source reporting. That last one hurts most, because a channel you cannot measure cannot be compared against one you can. Treat free as the default first layer: your own careers page, the free tiers on general boards, and any community or association list your candidates genuinely read. Then spend money only where the audience is scarce. Your careers page is the strongest free option you own, and the careers page builder guide covers making it convert.

Is a job posting site the same thing as job posting software?

No. A job posting site, or portal, is a destination candidates visit. Job posting software is the layer you publish from and collect into. Working portals directly means a login for each one, a different form for each one, applications landing in a different inbox for each one, and a reconciliation problem the first time two of them send the same person. Software collapses that into one record, one feed, and one queue with the source attached to every applicant. The switch usually pays for itself at a specific point: when more than two or three roles run at once, or when a second person needs to see the pipeline without being forwarded emails. Below that, publishing straight to a couple of portals is cheaper and perfectly reasonable. Above it, manual reconciliation quietly costs more than the software does. What a full platform includes is listed in ATS features.

Can you keep posting to the portals you already pay for?

Usually, and it is worth confirming before you sign anything. Most teams arrive with something already in place: unused slots on an annual package, a portal their industry actually reads, a recruiter holding a login nobody else has. Three questions decide whether any of it survives the move. Does the software hold a direct connection to that portal, or does it publish a feed the portal can crawl? Do your own credentials and contract carry over, or does the connection sit under the vendor's account where your slots become invisible? And does a role published through that connection still draw down a slot you have already bought? Where no direct connection exists, a crawlable feed is normally enough to get listings live. Give renewals one named owner as well, because unused slots are an easy line to keep paying for. Current connections are listed in integrations.

How quickly can a job go live?

Publishing takes seconds. Everything around it does not. The realistic sequence is internal approval, then each partner reading your feed on its own schedule, some hourly and some daily, then that partner indexing the record on its own site. So quick job posting is mostly about removing your own delays rather than buying faster software. Three things do it: approved description templates so nobody writes a role from scratch, saved location and pay fields per office so a required field is never left blank, and an approval chain with named alternates so one person on leave cannot hold a requisition for a week. The technical floor is minutes to hours. What turns a same-day post into a next-week post is almost always a missing approver. Templates to start from sit in the job description library, and approval routing sits in job requisition software.

Job distribution channels compared