Hirers must specify a pay type, salary range and description of the remuneration package for their job ad. This can be automatically mapped from your software’s internal representation, or presented as SEEK-specific input:
Remuneration packages are specified in the
offeredRemunerationPackagefield within all job posting mutations, and its schema is defined by the input type
A hirer must specify the pay type for the remuneration package. This is expressed using a combination of two fields:
There are currently four valid pay types:
Employment paid for the number of hours worked
Employment paid on a monthly basis
Employment paid on an annual basis
Annual plus commission
Employment paid on an annual basis plus a results-based commission
The SEEK API now supports dynamically querying valid pay type combinations with the
payTypesquery . These may be presented to a hirer for selection in a job posting flow.
This can help prevent entering a nonsensical pay type combination. For example, a job ad with an hourly rate of $70,000 will render a hirer’s job ad undiscoverable in recommendations and search
SEEK may display the pay type alongside the salary description for clarity.
The SEEK API supports 16 currencies in total. We recommend displaying a shortlist of 9 currencies that are predominantly used across our Asia-Pacific markets:
These currencies can be dynamically queried with the
currenciesquery . This will allow newly supported currencies to be readily available to your hirers.
Any supported currency can be used in any location. SEEK will take care of currency conversions when candidates refine their job searches by salary range. SEEK will not perform conversions on the free-text salary description; we recommend hirers to provide a description in the dominant currency of the position’s location with the currency clearly denoted.
Our location implementation options now let you select the recommended
currenciesfor a given location. The ISO 4217 currency codes are listed in order of preference. In most cases there will be a single currency returned, and we recommend pre-selecting the first option for an optimal hirer experience:
Suggestions will appear below the field as you type
"contextualName": "Bukit Batok West Region SG",
Enter a pay range to offer candidates (this will not show on your ad).
For currencies supported by the SEEK API, your software must supply the same currency that the hirer sees when they are filling out the pay details of their position. If your posting form includes currencies that are not supported by the SEEK API, you may programmatically convert the salary range to a supported currency.
SEEK may display the currency alongside the salary description for clarity.
When posting a job ad, the hirer must specify a salary range with a minimum and maximum amount. The amount is a floating point value in the major currency unit (e.g. dollars), calculated over the provided interval. You may specify a precision up to the minor unit of the currency. For example, the AUD currency accepts
12.34to represent the natural number
1234in cents. On the other hand, it does not accept
12.345as such a value attempts to subdivide the minor unit.
The salary range is used to provide more relevant job search results to candidates, but the monetary values in
maximumAmountare not visible in search results nor on the job ad. Hirers can provide a salary description to communicate the remuneration package to the candidate. SEEK may display the supplied
intervalCodealongside this description for clarity.
Mark the maximum amount as a mandatory input in your interface. We have observed that some hirers currently omit the maximum amount, which defaults it to the minimum and affects the performance of their job ads. The input field will be required in our schema in future.
Salary ranges are used to refine candidate job searches but the monetary values aren’t directly visible to candidates. The hirer must provide a free text description if they want to communicate the position’s remuneration. SEEK may display the supplied
intervalCodealongside this description for clarity.
RemunerationPackageInput.descriptionsfield displays a friendly remuneration package description to candidates. Hirers can use this field to give a short summary of remuneration, including further benefits such as bonus options and superannuation. Note that this field has a maximum length of 50 characters, which roughly corresponds to a single English sentence.
For example, if a hirer set the salary description field to
$100k–$120k + super + bonusit will appear on SEEK like so:
Senior Software Engineer
Information & Communication Technology (Engineering - Software)
$100k–$120k + super + bonus
Posted just now
There are two categories of salary validation rules:
- The basic rules documented on this page and the corresponding schema documentation. For example, the maximum amount must always be greater than or equal to the minimum amount.You should enforce these rules in your software’s frontend to give the hirer feedback before they continue with the job posting flow.
- Internal rules that the SEEK API only enforces when the hirer attempts to post the job ad.SEEK will revise its internal salary rules in the future. To support this, your software should display all validation error messages it receives from the SEEK API to the hirer.
When a job ad’s salary fails validation the posting mutation will fail with a
BAD_USER_INPUTerror. The error will contain both a top-level summary
While the SEEK API will attempt to provide an actionable summary, this is not always possible when multiple fields have errors. You’re encouraged to map the
invalidFieldsmessages back to the relevant fields in your job posting form. Otherwise, the hirer might not have enough information to correct the invalid fields.
When a hirer provides an overly-long description and a salary range where the minimum is greater than the maximum, the SEEK API will respond with a set of invalid fields like the following:
"message": "Invalid remuneration",
"/input/positionProfile/offeredRemunerationPackage/ranges/0/maximumAmount/value": "Must be greater than or equal to the minimum value",
"/input/positionProfile/offeredRemunerationPackage/descriptions": "Cannot exceed 50 characters"
Note that the SEEK API was unable to generate a top-level
messagethat summarised both validation errors. This demonstrates the importance of mapping the
invalidFieldsmessages to the relevant fields on your job posting form.