RefolkCandidates
DocsApplying

How job matches work

The matches screen is a live feed of open roles, ranked against your profile. Reading it costs nothing: the ranking is arithmetic, not a model call, so you can scan a few hundred postings and spend credits only on the ones you actually want to apply for.

Where the jobs come from

157 companies, read straight from the public board feeds they publish for their own careers pages. It is the same data their careers site renders from, fetched fresh and cached for a few hours. Nothing is scraped and no credentials are involved. When a company moves provider its board simply goes quiet, which reads as “no jobs today” rather than an error.

How ranking works

Four things decide whether a posting is worth your attention, and all four are answerable from text:

  • Is it your job? How much of your target role appears in the posting’s title. Weighted heaviest, because a posting for the wrong job is worthless however well the rest lines up.
  • Is it your level? The seniority in the title against the seniority in your profile.
  • Can you work there? Your locations, and whether the role is remote.
  • Do you have the skills? Your skills against the posting text, where the board gives one.

Match score is not fit score

The number on the matches screen is a ranking heuristic. Its job is to get the right hundred postings in front of you so the expensive scoring can be spent on the right ten. The fit score on an application is a different number, written against the full posting and your whole history, and it is the one to trust. The two are labelled differently for that reason.

Queueing from matches

Select the postings you want and queue them. They land in the same application queue as anything you paste by hand, and the tailoring step reads the posting from its URL. See Tracking applications.

If the feed looks empty

Usually the profile is too thin to rank against, or the target role and locations are narrow enough that nothing clears the bar this week. Broadening the target role is the fastest fix; adding remote is the second.