Skip to main content
All CollectionsMercu HireJobs
Creating a Job
Creating a Job

See this guide on how to create a job.

Jascha avatar
Written by Jascha
Updated this week

A 'Job' in Mercu represents a vacancy. In order to create and process applications, you need to create a job.

A 'Job' has a name, ID, location, hiring manager, type, and stage workflow. Each of which can be configured according to your needs.

Step 1: Creating a Job

There are two ways for creating a job:

  1. From scratch

  2. By cloning an existing job

From scratch

To create a job from scratch, navigate to the 'Jobs' tab > click on 'New Job' > fill out the job creation modal.

  • Job Name: This is the name of your job and candidate-facing.

  • Job ID: A unique identifier for each job. You can either leave the field as is OR enter your own job ID.

  • Job Location: The location for which you are hiring. In Mercu, each job can only belong to one location. If you would like to make the same role available across multiple locations, you'll need to set up multiple different jobs. You'll need to set up these locations in your account before creating a job. See this guide on how to create locations in Mercu.

Please note that Job Location is the location where the successful candidate will work. You can have separate locations for each interview stage.

  • Hiring Manager: The manager assigned to look after this job.

  • Type: The contract type for which you are hiring (FT, PT, Casual).

By cloning an existing job

To clone an existing job, navigate to the 'Jobs' tab > click on the meatballs (the three dots) next to the job > click on 'Clone'. This clones the job, including the stages, interview settings, and campaigns.

Cloning does not clone the original job's applications AND workflows.

Step 2: Configuring Stages

If you cloned an existing job, you do not need to configure job stages, as these would have been cloned from the existing job.

If you created a job from scratch, you need to configure the job's stages. Each job needs at least one stage for you to be able to create applications under that job.

Apart from the Review stage, each stage also requires you to create a stage-specific campaign (see here for more details on Campaigns). Schedule stages further require you to configure the stage's interview settings (see here for more details on Interview Settings).

Form Stage

Form Stages are intended for collecting candidate details and run basic screening.

Assessment Stage

Assessment Stages are intended for running candidate assessments.

Schedule Stage

Schedule Stages are intended for interview scheduling (see here for more details on Interview Settings).

Offer Stage

Offer Stages are intended to notify successful candidates. Offer Stages also serve as the trigger for any third-party HRIS integration.

If you set up a third-party HRIS integration, then whenever a candidate completes an Offer Stage, that HRIS integration will be triggered and the candidate will be created in the respective third-party HRIS.

Reject Stage

Reject Stages are intended to notify unsuccessful candidates.

Review Stage

Review Stages are intended to "hold" applications. They do not have a campaign linked to them. Hence, moving an application into a Review Stage doesn't trigger any message to the respective candidate.

Did this answer your question?