A job in Mercu represents a vacancy. Candidates either apply to a job or are added to it manually or via API from a third-party system.

There are three ways for creating a job:

To create a job from scratch, navigate to the "Jobs" tab in the side-nav, click on "New Job" and fill out the job creation modal.

The candidate-facing title of the job. Example: Head Barista.

A unique identifier for the job. You can leave the auto-generated value or enter your own. This field is internal-only.

The (physical) location where the successful candidate will work. Each job in Mercu can only be assigned to one location. If the same role is available in multiple locations, you’ll need to create a separate job for each. Make sure all required locations are set up in your account beforehand.

The person responsible for overseeing the job. Must be an existing portal user.

The recruiter and sourcer assigned to the job. These fields are currently for attribution and analytics only. Must be existing portal users.

The contract type for the role: Full-Time, Part-Time, or Casual.

To clone an existing job, go to "Jobs" in the side navigation, locate the job you want to duplicate, click the three-dot menu next to it, and select "Clone." This will duplicate the job along with its stages, campaigns, branching rules, interview settings, and workflows.

To create a new job from an existing template, go to "Jobs" in the side navigation, click "New Job," and select "Create from Template" in the modal. Then choose the relevant template and complete the required fields. You can read more about templates here.

Jobs created from templates are linked to their respective templates. This means the job inherits the template’s stages, campaigns, content, branching rules, and workflows. These elements cannot be modified at the job level - they must be updated at the template level.

Only job-specific settings can be edited at the job level. These include the location, hiring manager, recruiter(s), sourcer(s), interviewer(s), and interview settings.

Each job has a job profile containing its basic settings, including job name, job ID, location, hiring manager, recruiter, sourcer, job language, and job description.

You can update any of these fields at any time. Note that the job name and job description are candidate-facing, and changes take effect immediately.

If you change the job language after creating job stage campaigns, you should review the campaign content to ensure it matches the updated language.

If you cloned an existing job or created one from a template, you don’t need to configure job stages - they're either cloned from the original job or inherited from the template.

If you created a job from scratch, you must configure its stages. Each job requires at least one stage to allow application creation.

Except for the Review stage, each stage must have a stage-specific campaign configured (see Campaigns for details). Schedule stages also require interview settings to be defined (see Interview Settings for more information).

Used to collect candidate details and perform basic screening.

Used to conduct candidate assessments.

Used to schedule interviews. See Interview Settings for configuration details. (see here for more details on Interview Settings).

Used to notify successful candidates.

Used to notify candidates who are not progressing.

Used to place applications on hold. No campaign is linked to this stage, so moving a candidate into it does not trigger any communication.

After configuring or confirming the job stages - for jobs created from scratch or cloned - you need to create campaign content for each stage. Learn more about job stage campaigns here.

If your job includes a Schedule Stage, you must also configure the interview settings for that stage. Learn more about interview settings here.