Requests point back to this page
Automated requests identify as JobWatcherBot/1.0 (+https://jobwatcher.io/crawler). The linked page provides public information and contact details; the contact email is not embedded in the User-Agent.
Crawler transparency
A small, identifiable crawler for public job listings
Job Watcher checks official employer career pages and their applicant-tracking system endpoints so people can discover relevant open roles and follow the original listing.
Direct career-source monitoring
The crawler checks public job lists and job-detail pages published by employers or by ATS providers acting as their recruitment infrastructure. It is not used to build a general-purpose copy of a recruiting site.
What Job Watcher produces
The service turns public vacancy information into compact job metadata and derived matching signals, then sends users back to the original source.
Metadata
Structured vacancy facts
Job title, employer, location, canonical link, posting identifiers, and publication state. Raw job-page content is not exposed to users.
Analysis
Search and fit signals
Job descriptions are processed internally to produce normalized locations, role and seniority signals, duplicate detection, availability checks, and profile-specific relevance analysis.
Output
Links to original listings
Users receive concise alerts and links. Job Watcher does not sell vacancy content or present itself as the employer or ATS operator.
Conservative access practices
Source health matters more than scan speed. Requests stay bounded and reuse prior work wherever possible.
Public-source access
Job Watcher checks publicly available job listings and directs users back to their original sources. Access is source-specific, bounded, and subject to manual opt-out requests from website operators.
Low-rate, scheduled checks
Checks use conservative request rates, bounded pagination and concurrency, cached results, retry backoff, and provider-specific cooldowns.
No technical bypass
Job Watcher does not rotate proxies to evade controls, solve access challenges, bypass authentication, or work around blocks. A challenge or denial is treated as a signal to stop or defer access.
Questions or opt-out
Website operators can ask for access to stop for a domain, ATS tenant, or specific path. Requests are reviewed and applied manually.
Include the affected domain or URL and enough context to verify that the request comes from the site operator.
solovtsov71@icloud.com