our methodology
How We Verify a Remote Tech Job Is Real and Still Open
A job board earns trust through provenance and removal discipline. This is the complete workflow used to turn an employer's public career-board record into a listing—and to remove it when the source closes it.
1. Start with the employer's own board
We maintain a company registry and connect only to public job-board endpoints operated by Greenhouse, Lever, or Ashby. We do not import listings from another aggregator. The original employer URL is retained as the application destination, so candidates can verify the role and apply without creating an account here.
A public endpoint confirms provenance, but it does not make every result relevant. The remaining checks decide whether a posting belongs on this particular board.
2. Verify remote eligibility
The location field must say remote, distributed, anywhere, or another remote marker. We then look for explicit eligibility for the United States, Canada, North America, the Americas, or worldwide. A posting limited to another region is excluded.
When a source says only “remote” and provides no geographic qualifier, the listing is marked as potentially open to both target countries. This is deliberately shown as a normalized interpretation, not a guarantee; the source posting remains authoritative.
3. Keep the role relevant and readable
Role relevance is judged primarily from the title so a broad department label cannot turn unrelated openings into tech jobs. Clear non-software disciplines such as civil, mechanical, petroleum, or naval engineering are excluded. Remaining roles are normalized into categories, employment types, seniority, region labels, and salary bands.
Normalization makes filters usable, but it can occasionally be imperfect. Every detail page therefore links to the original record and the Contact page accepts corrections.
4. Re-check, expire, and disclose
Career boards are checked daily. If a successfully checked employer board no longer returns a previously seen role, the listing is removed. A 90-day age ceiling also prevents unusually stale source records from remaining indefinitely.
Removed job URLs return HTTP 410 Gone rather than pretending the role still exists. If a source is temporarily unavailable, a safety threshold prevents a failed crawl from deleting the entire inventory.
- Source unavailable: preserve the last verified record rather than guessing.
- Source confirms removal: remove the listing and return 410 on its old URL.
- Material data error: correct the normalizer and refresh the affected record.
- Employer removal request: review it against the source and respond through the published contact address.
What automation does—and does not—decide
Automation retrieves public records, applies documented filters, and updates factual fields. It does not evaluate an employer's culture, recommend one company over another, or claim that a candidate is legally eligible. Those decisions require the original posting and, where appropriate, direct confirmation from the employer.
Sources and further reading
continue with live listings
Browse relevant remote jobs
related research