The JobMinglr match score is not a black box. Here is exactly what goes into it and why it produces better results than keyword filtering alone.
When you see a match score on a JobMinglr opportunity, it is not a random number or a simple keyword count. It is a composite signal built from several layers of information about the candidate, the role, and the employer's stated priorities. Understanding how it works helps both candidates and recruiters use it more effectively.
The core principle is fit, not volume. We are not trying to surface every role that technically matches a keyword. We are trying to surface the roles where a candidate is likely to genuinely succeed and the candidate is genuinely likely to want the role. Both sides of the equation matter.
Candidate-Side Signals
On the candidate side, the match score draws on skills listed in your profile, your experience level and job history, your stated preferences for role type and industry, and your location or remote work preference. Each of these factors contributes differently depending on the weight the employer has placed on them.
Preferences matter as much as qualifications in our model. A candidate who is technically qualified but has stated they want a fully remote position will score lower on an in-office role — not because they are a bad candidate, but because the fit is genuinely lower. This saves both sides time.
Employer-Side Signals
Recruiters define what matters most for each role when they post to JobMinglr. Some roles weight technical skills heavily. Others weight cultural fit indicators or industry background more. The match score reflects these weights, not a one-size-fits-all formula.
Employers who take time to configure their role parameters get significantly better matches than those who leave defaults in place. The more signal they give the system, the more precisely the system can identify relevant candidates.
For teams using Greenhouse or Pinpoint integration, role data syncs automatically and recruiters can refine weights directly within their standard workflow without logging into a separate interface.
What the Score Is Not
The match score is a starting point, not a final verdict. A high score means the candidate looks like a strong fit based on available data. A lower score might reflect missing information in a candidate's profile rather than a genuine mismatch.
We encourage both candidates and recruiters to treat the score as a signal to investigate further rather than a hard cutoff. Some of the best matches we have seen started with a mid-range score that improved as both sides added more information to their profiles.
Hiring smarter?
Connect your ATS and get qualified candidates automatically.