RemoteStack's match score ranks jobs by how well the role fits your actual career, not by keyword overlap. It works in three steps: it keeps jobs in departments that suit you, scores a job higher when its role matches your current title, past roles or target roles, and lowers the score when the job's seniority does not fit your years of experience.
Below is what the score measures, why keyword matching alone fails, what the score does not do, and how to use it. You get a match score on every job once you create a free profile.
What the Match Score Actually Measures
The match score is a number from 0 to 100. Jobs with higher scores appear first in your feed. Lower scores get pushed down. But the number itself matters less than what feeds into it.
The system looks at five core signals:
| Signal | Weight | What It Checks |
|---|---|---|
| Job title match | 20% | Your preferred role vs. actual listing title |
| Skills overlap | 35% | Skills on your profile vs. skills in the job description |
| Experience level | 20% | Years of experience and seniority requirements |
| Timezone fit | 15% | Overlap between your timezone and company working hours |
| Company preferences | 10% | Company size, industry, remote culture signals |
Each signal gets scored independently. Then they combine into your match score. No black box. No mystery weighting that changes without explanation.
Let's break each one down.
Job Title Match
This is the simplest signal. If you say you want "Product Designer" jobs, the system looks for titles containing "Product Designer", "Product Design", "UX Designer", "UI Designer", "Design Lead", and similar variations. It uses synonym mapping, not exact string matching.
A job titled "Product Designer" gets a 100. A job titled "Creative Director" gets a 0 unless your preferences include creative director roles. Simple.
Skills Overlap (The Heavy Lifter)
This is where most job boards fail. They check if your resume mentions "Python" and the job mentions "Python". That's it. RemoteStack goes deeper.
The system reads the full job description and extracts required skills, preferred skills, and nice-to-haves. Then it compares them against your profile skills. But it also checks for related skills. If you have "React" and the job asks for "React.js", that's a match. If you have "SQL" and the job wants "PostgreSQL", that's a partial match.
Skills overlap accounts for 35% of your score because it's the strongest predictor of whether you'll get an interview. A high skills match means your application won't get auto-rejected by an ATS. If you want to optimize your profile for this, check out our guide on ATS Optimization for Remote Jobs 2026.
Experience Level
The system detects the seniority level from the job description. "5+ years experience", "Senior Engineer", "Lead" all signal senior roles. "Entry level", "Junior", "0-2 years" signal junior roles.
If you're a junior developer and the job asks for 8 years of experience, your experience score drops. Hard. No point applying to jobs you're underqualified for. The reverse is also true. A senior engineer applying to junior roles gets a lower score too, because you'd be bored and overqualified.
Timezone Fit
Remote doesn't mean "any timezone works". Many remote companies have core hours. A company in San Francisco might expect you to be available from 9 AM to 1 PM Pacific. If you're in Tokyo, that's 2 AM to 6 AM.
The match score checks your timezone against the company's location and any stated working hours. If the job says "must overlap with EST 4 hours daily", the system calculates your overlap. No overlap? Score drops. Full overlap? Score stays high.
This matters more than most people think. The Owl Labs remote work study found that timezone misalignment is the second biggest challenge for remote workers after loneliness. RemoteStack accounts for it before you apply.
Company Preferences
Not every remote job fits your preferences. Maybe you only want startups. Maybe you prefer companies with 500+ employees. Maybe you want fully remote companies, not hybrid "remote-friendly" roles.
The system reads company size, industry tags, and remote culture signals from the job listing and the company's public data. If you prefer startups and the company is a 10,000-person enterprise, the score adjusts. If you want a strong remote culture and the company has an open-source remote handbook (like GitLab's Remote Work report), that's a positive signal.