Salary validation
    • English (en) uk flag arrow_right

    The global remote work community tends to interact in English. Switching languages might impact your visibility.

  • Search
  • Jobs/gigs
  • Publish a job
  • Your jobs (posted or applied)
  • Preferences
  • Your genome
  • Signals
  • Messages
  • Torre's product roadmap
  • Request features
  • API for developers
  • Help
4.3.
Salary validation
Salary validation
4.3.1.
Purpose
The salary-matching feature’s purpose is to ensure that a user's salary expectations align with the salary range offered for a job, based on salary expectations of the candidate and proposed salary on the job.
4.3.2.
Data
4.3.2.1.
Candidates
The data for this factor is provided by the candidates themselves. Candidates can input and update their salary expectations during the onboarding process of the platform, in the edit section while viewing their profiles, or through interactions with the recruiter bot. Lastly salaries can be modified for specific job applications to be lower or higher just for those in particular.
4.3.2.2.
Talent seekers
Talent seekers can outline their budgeted salary range in the job post during onboarding or while editing the job.
4.3.3.
Data validation
To make sure jobs posted on our platform provide value to our job seekers and to make sure talent seekers have the best chance of finding the right talent, we do an automated market analysis for every job posted on the platform. We provide knowledge on how high salary expectations of candidates are based on all attributes of the job post.
4.3.4.
Algorithm validation
  • Daily and weekly metrics
  • Editorial reviews
  • Direct feedback from talent seekers
  • Direct feedback from candidates
4.3.5.
Description
Initially, we convert the salary of the candidates and the job to USD using a currency conversion library. Then we normalise the salary to an hourly rate. In most cases the periodicity is the same but we provide the option of specifying hourly, monthly and yearly compensations. Some job post might be unpaid. In this case only candidates with the preference “open to unpaid jobs” or with a salary expectation of 0 will be matched. For the salary of a job there is multiple ways of configuring them. Each one has a specified logic for them so they will be handled separately here.
4.3.5.1.
Fixed salary
The job’s salary is divided by the candidate salary with a maximum score of 1.
4.3.5.2.
Salary range
The job’s maximum salary is divided by the expected salary of the candidate with a maximum of 1.
4.3.5.3.
To be agreed upon
We match everyone equal with a score of 1. Extras:
  • Equity
  • Commissions
  • Bonuses
  • Health insurance
  • Other
4.3.6.
Mathematical description
Mathematical description Mathematical description-2
4.3.7.
Uncertainty
Uncertainty in this factor is defined by the range of the job compensation. If the compensation of a job has a range we assume the upperbound for defining if we want to match a candidate but the lowerbound defines the uncertainty for if that’s actually a match or not.
Fair artificial intelligence.
We’re committed to it.
headerSchema.headline