How the match score is calculated
The tool extracts up to 60 keywords from the job description — technical skills, tools, soft skills, named-entity bigrams — weighted by frequency and the strength of phrases like "must have", "required", "experience with". Each keyword counts more if it appears in the JD multiple times.
Your resume is then scanned for those keywords (case-insensitive, with simple plural / suffix handling). The score is the weighted-fraction of JD keywords you cover.
Tailoring strategy
- Don't keyword-stuff. Add only keywords you genuinely match — recruiters skim within 10 seconds and notice padding.
- Match the JD's wording. If the JD says "PostgreSQL" and your resume says "Postgres", spell it out as "PostgreSQL" once so the ATS keyword filter catches it.
- Reorder, don't just add. Move the most-relevant role to the top of your Experience section for this application.
- Quantify. "Built a Redis caching layer that cut p95 latency by 38%" beats "Worked with Redis" every time.
What this tool doesn't do
It can't read culture fit, seniority signals, or visa requirements. It scores keyword overlap — necessary, but not sufficient. Use it as a sanity-check, not as the only step.
FAQ
Why doesn't this fetch the JD from a URL?
Browser CORS rules forbid cross-origin fetches, and major job sites (LinkedIn, Indeed, Naukri) block scraping. Pasting the JD text is the most reliable path and avoids any legal grey area.
Where does my resume go?
Nowhere. The resume is parsed entirely in your browser. The page makes no upload calls — open DevTools → Network if you'd like to verify.
What's a "weighted" keyword?
A keyword that appears multiple times in the JD, or that appears near phrases like "must have" / "required", counts for more in the match score than a one-off mention.
Can I tailor for two JDs at once?
Open this page in a second tab. Each tab is independent.