METHODOLOGY

A score you can inspect.

Public-fit scores organize a shortlist. They do not estimate whether an employer will interview or hire someone.

What is filtered first

The explorer requires the selected canonical role and location to match the structured job record. If a posting states a minimum experience requirement above the number entered, it is excluded. A missing experience requirement is treated as unknown and remains visible.

How the public score is calculated

Resume text is optional and stays in the browser. When provided, the score is the percentage of extracted job terms found in that text. Without it, jobs remain newest-first and display no score. Role, location, and experience are eligibility filters, so they are not counted again as score points.

A job with too little structured detail displays N/A instead of an invented score. The explanation names a few matched and missing terms so the result can be inspected.

Where keywords come from

uHired extracts a short set of statistically prominent terms from each returned job. The public response contains those structured terms, not the full source description. A match means the normalized phrase appears in the resume text; it does not prove proficiency.

How pages are ordered

The server returns ten eligible jobs at a time in newest-first order from the 72-hour window. The browser ranks those ten by resume fit. A later, older page can therefore contain a higher-scoring job; the explorer does not claim to rank every available job globally.

Why results can change

Jobs can age out of the 72-hour window, close at the source, receive corrected metadata, or be deduplicated. A source application link is resolved only after sign-in, so it can become unavailable after a card was returned.