Loading page...Загружаем страницу...正在加载页面...
AtlasRepo

I built a self-hosted gig watcher so I stop refreshing job boards — it only pings me on new matches

Description and use

GigWatch is a self‑hosted job feed watcher that notifies only about new, relevant gigs, eliminating the need to refresh multiple job boards manually.

Problem

Freelancers waste time refreshing job boards and see stale listings, missing fast‑filled high‑pay gigs.

Outcome

GigWatch reduces manual effort by eliminating repeated refreshes, filters out stale listings, and notifies the user only when a genuinely new, relevant gig appears.

Workflow

  • Fetch live listings from each configured source
  • Score each listing against profile keywords and title
  • Deduplicate against local state file of previously shown listings
  • Alert for new matches above score floor via console, email or Slack

Evidence

Freelancers lose real money to latency. The best remote gigs get filled in the first few hours — the "Senior Backend Engineer, $120k, fully remote" posting is usually taken before you finish your second coffee.

Source

GigWatch does one loop, on a timer you control (default 15 min): 1. Fetch 2. Score 3. Dedup 4. Alert

Source

It pulls from free, keyless job endpoints (Remotive, We Work Remotely, RemoteOK, Jobicy, Hacker News, plus any RSS feed you point it at). No API keys.

Source

The dedup step is the whole point. A job board shows you the same 300 listings forever; GigWatch shows you a listing exactly once, and only if it matches your profile.

Source

  • Record date: 2026-10-13T20:56:04.251Z