Skip to content

Job Multiposting: One Job Record, Many Boards

Recruitment teams often end up juggling logins for every job board they use.

Job Multiposting moves that work into the ATS: you open a job, start a campaign, review the suggested boards and publish. The same record then carries the posting, the applicants and the campaign results, so you are not reconciling separate systems later.

The posting flow, step by step

The workflow starts from a job you already have. Open the record, choose Advertise, give the campaign a name, and confirm three details: the job function, the location and the industry. Those three inputs drive the board suggestions, so accuracy at this point matters more than speed.

Once the board list appears, select the destinations you want, review the campaign and publish. There is no separate developer console and no new posting interface to learn — the same screens you use to create a job carry the campaign through to publication.

A worked example

Take a record like the one shown in the interface preview: job ID 782, App Developer at NVIDIA, Mumbai, marked open. Naming the campaign after the role and client keeps it findable later. Confirming 'App Developer' as the function, 'Mumbai' as the location and the relevant industry gives the recommendation engine the context it needs; a vague function or a missing location tends to produce a broader, less useful board list. After publishing, the campaign sits against job 782, so applications and performance data stay tied to that record rather than being scattered across board dashboards.

What the board network covers

The directory spans generalist boards, regional specialists and niche sites. Global names such as Indeed, LinkedIn, Google for Jobs, Monster and Adzuna sit alongside UK and EU boards including Reed, Totaljobs, CV-Library, StepStone and Xing, APAC options such as SEEK and Jora, and niche destinations for technology, finance and healthcare roles. Some listings are flagged free to post; others depend on the contract you hold with that board.

Board availability, pricing and free-posting status change over time. Treat the directory as a starting point for selection and confirm current terms with each board before you commit budget.

Your existing board contracts stay as they are

Multiposting does not replace your agreements with LinkedIn, Reed, CV-Library or any other board. You keep the contracts you already have; the ATS becomes the place from which you launch and track postings under them. That distinction matters when you are evaluating the feature: it is a control layer, not a media-buying replacement.

Who does what

Access follows the permissions you configure. Recruiters can start campaigns directly from a job record, managers can review how campaigns are performing, and administrators handle contracts and account settings. Because the roles map onto the same job data, nobody needs a second login to see what was posted where.

Before you switch on multiposting

Use this checklist to avoid the common setup mistakes:

  • Confirm the feature is enabled on your account; campaign tools will not appear until it is.
  • Audit which board contracts you hold and which of those boards appear in the directory.
  • Agree a campaign naming convention so postings stay searchable by role and client.
  • Check that job records have accurate function, location and industry fields before launching.
  • Decide who holds recruiter, manager and admin permissions.
  • Set an expectation for reviewing campaign performance, not just publishing.
  • Confirm current board pricing and free-posting status independently of the directory.

Three different problems, three different fixes

When a posting does not appear where expected, the cause is usually one of three things, and they are not interchangeable.

A setup problem means the campaign was never completed — the function, location or industry was left vague, or the board selection was not confirmed. Fix it by reopening the campaign and correcting the inputs.

A contract problem means the board itself is not covered by your agreement, or the terms have changed. Fix it with the board, not in the ATS.

An enablement problem means the feature is not active on the account at all. Fix it with your account administrator before troubleshooting anything else. Separating these three saves hours of misdirected support tickets.

If you already use a separate multiposting tool

The usual complaint about standalone multiposting platforms is fragmentation: jobs are published in one system while candidates and applications land in another. Consolidating means the posting, the applicant record and the campaign result share one source of truth. Whether that trade-off is worth a migration depends on how much manual reconciliation your team currently does — count the steps before deciding.

Frequently asked questions

Do I need to renegotiate my existing job board contracts to use this?

No. Contracts with boards such as LinkedIn, Reed or CV-Library continue unchanged. The ATS lets you manage those contracts and launch postings from one place instead of logging into each platform separately.

Do I need technical skills to use Job Multiposting?

No. If you can create a job record, you can run a campaign: select the job, choose boards, review and publish. The interface is built for recruiters rather than developers.

How many people on my team can manage campaigns?

As many as your permission settings allow. Recruiters launch campaigns from job records, managers review performance, and admins manage contracts and settings.

We already use another multiposting tool. Is switching worth it?

The case for switching is consolidation. With a separate tool, jobs live in one system and candidates in another. Here, posting, candidate tracking and campaign performance share one platform, which removes a reconciliation step.

How quickly can we start using Job Multiposting?

Once the feature is enabled on your account, you can launch almost immediately. Existing jobs are already in the system, so the first campaign is a matter of selecting boards and confirming details. Many teams run their first campaign the same day.