Jobber/docs-site/docs/features/duplicate-jobs.md

id, title, description, sidebar_position

id	title	description	sidebar_position
duplicate-jobs	Duplicate job detection	How JobOps deduplicates cross-source postings and hides repeats after you skip or apply.	8

What it is

JobOps treats the same role reposted on different boards as one opportunity, and remembers when you have already skipped or applied so you do not see it again.

Duplicate detection uses normalized keys:

• Employer + title — strips punctuation, (Remote), trailing city lines, and legal suffixes (Inc., Ltd.) so Acme Inc. / SDET (Remote) matches Acme / SDET.
• Employer + description — when the job description is long enough, the same posting copy under the same company matches even if the title wording differs slightly.

This runs at import time (pipeline) and in the Jobs list (UI).

Why it exists

Job boards repost the same role on LinkedIn, Indeed, QAJobsBoard, and aggregators. Skipping or applying once should mean you do not wade through the same listing again on the next run.

How to use it

You do not configure duplicate detection separately. It is always on for your profile.

When you skip a job

1. Skip from the job detail panel or press s on the Jobs page.
2. JobOps marks that row skipped.
3. Any other Discovered or Ready jobs with the same employer+title (or same employer+description) are auto-skipped.
4. Future pipeline imports that match those keys are not imported.

When you mark applied

1. Mark the job applied from the UI.
2. Duplicate open rows are auto-skipped (not marked applied) so your Applied tab stays clean.
3. Future imports of the same role are suppressed the same way as for skips.

Cross-source import

During a pipeline run, if a new posting matches an existing row by URL, source id, or content fingerprint, JobOps does not create a second row — the import is counted as skipped in run stats.

Jobs list

Open jobs that match a prior skip or apply are hidden from Discovered, Ready, and All tabs so the queue stays fresh. Skipped and applied rows themselves remain visible in their statuses.

Defaults and constraints

• Description matching requires at least 80 characters of normalized text; short or empty descriptions fall back to employer+title only.
• Matching is per profile (ownerProfileId); different login profiles do not share dedup state.
• Dedup does not delete existing rows retroactively when you change skip list or country filters — run discovery again or skip manually for old data.
• Very different titles at the same company (for example SDET vs Product Designer) are not collapsed.

Common problems

I still see the same job from another source

• Titles or employer names may differ enough that normalization does not match (for example a staffing agency name vs the hiring company).
• Add the employer to the Company skip list if it is always noise.
• Skip one row — siblings with matching keys should auto-skip and future imports should stop.

A different role at the same company disappeared

• Employer+title dedup only merges the same normalized title. Different roles at one company should remain separate.
• If two titles normalize to the same string, check for overly generic titles on the board.

Skipped jobs reappear after a pipeline run

• Confirm the skip saved (status skipped in the UI).
• If the repost uses a new employer spelling and a new title and a short description, it may not match — block the employer or country instead.

Related pages

• Orchestrator
• Pipeline Run
• Company skip list
• Blocked countries
• Keyboard Shortcuts