Job postings within hours of going up, fetched and filtered on your own machine

Run it when you like. It reads the boards you choose, and a language model reads a posting once for the facts your rules check. What you can't take is dropped with its reason, and the rest reaches you hours old, not days later with a hundred applicants ahead of you.

The tool I run every day for my own search; the public repository comes once it installs cleanly on a fresh machine. One email to confirm, one when it opens, and the address is used for nothing else.

Postings in a week of my own search4,915
LocationOn-site or out of area1,584
KeywordsNone from my stack1,239
ModelJudged not relevant544
FreshnessOld or 100+ applicants371
LanguageNot one I read299
BlocklistA company I blocked218
FingerprintRepost153
Hiring scopeRemote, other countries only142
ModelCitizenship or clearance62
ReadPage unreadable7
ModelPay under my floor4
6 more reasons142 held, 444 dropped586
8 more reasons142 held, 1,114 dropped1,256
DigestSent, grouped by board292Half under 2 hours old when found, 96% under a day
The age is how old a posting was when a run found it, over the sent postings that carried a precise time, at about a dozen runs a day.

The local app, sheet by sheet

What it dropped, and why

In a week, PostingWatch checks 4,915 new postings for me and sends me 292. Here are nine of the others, one per reason.

From the dashboardNine of the 4,915 postings in a week

  1. Mid-Senior Frontend Engineer (Saudi National)Breezy board · RiyadhModelRequires citizenship
  2. Senior AI EngineerGreenhouse board · KrakówLocationJudged not remote by the model
  3. Developer - Fullstack (REACT/Java/Python)Workday board · Bangalore, IndiaLocationOn my excluded-locations list
  4. Senior Software Engineer (Go - React - TypeScript - Next.js)arc.devLanguageWritten in Spanish
  5. Senior Technical Lead - Java/ReactSmartRecruiters boardKeywords“Java” in the title, a word I excluded
  6. DevOps Engineerremotejobs.org · RemoteKeywordsNo keyword from my stack on the page
  7. Senior Software Engineer (Frontend), Business AccountsAshby board · SydneyFreshnessPosted 6 May, seen 1 October: past my 3-day limit
  8. Software Developer, React Native - Hybridremotefrontendjobs.comFingerprintThe same text as a posting already on record
  9. Software Engineer, Productremotefirstjobs.com · United StatesHiring scopeRemote, but hiring in the United States only. Kept in the dashboard, not sent.
Real postings from the run; company names left out. The dashboard shows them, with the saved text.

A week is the average of two weeks of my runs, ending 2 October 2026; every reason with its exact count is in /llms.txt.

How a posting gets checked

A posting stops at the first check it fails, and that check is its reason in the dashboard, next to its saved text. The ghost check only flags.

  1. Read

    Dropped

    A run opens two browser windows, walks every board in your list, reads each new posting and closes them when it's done. A blocked or empty page is dropped with that reason and kept in the dashboard, so you can open it yourself; a bot wall raises a notification, and each board's health is on the dashboard.

  2. Rules

    Dropped

    Before any model call, grouped by check, not in the order they run:

    • Keywords: a word from your stack on the page, and no stop word in the title, matched as whole words, so Java never catches JavaScript.
    • Location: the board's work-type badge matches yours, the place isn't one you excluded, and a hybrid or on-site role is somewhere you allow. The model's answer can drop a posting here too: judged not remote, or refusing applicants from outside its countries.
    • Freshness: not closed, under 100 applicants, not marked ineligible by the board, and within your age limit.
    • Blocklist: not a company you blocked.
    • Fingerprint: not the text of a posting already on record.
    • Language: one you read.
  3. Model

    Dropped

    A language model reads the posting's title and text once and reports facts, all in one answer:

    • is it a job page
    • is it really remote, and for where
    • what area and main stack it is for
    • does it ask for a language you don't speak
    • does it require citizenship or a clearance
    • is the stated pay under your floor

    The area and stack rule is tuned to my own search, frontend and JavaScript full-stack, in the code rather than the settings for now. No answer means a retry, not a drop.

  4. Hiring scope

    Held

    Then, from the same answer, a remote posting naming one or two countries or regions that leave yours out (your allowed locations, in the settings) is held: out of the digest, shown apart in the dashboard with a geo badge, worth a look when a company might make an exception. Three or more named regions pass, as the table below shows.

  5. Ghost check

    Flagged

    Every posting gets this check, whatever the others said. A posting closed within days of going up, listed again by the same company on the same board, marked reposted or always open, or from an agency or a board hiring for someone else gets a likely-ghost flag in the dashboard and stays where it was.

  6. Digest

    Sent

    What passed goes out in one email or Telegram message, grouped by board, once the run's queue is done. A board that blocked the reader is named in it.

Remote postings, case by case

What the Location and Hiring scope checks do with a posting, for the example settings (a reader in Poland).

Remote postings by case, with the check that decides each and its outcome
The postingCheckOutcome
On-site or hybrid, anywhereLocationDropped
In a place on my excluded list, such as Bangalore, IndiaLocationDropped
Called remote, but the model finds in-person time after hireLocationDropped
Remote, but refusing applicants from outside its countriesLocationDropped
Remote, worldwide, including through an employer of recordHiring scopeSent
Remote, no place namedHiring scopeSent
Remote, naming my country or a region it is in: Poland, the EU, EMEAHiring scopeSent
Remote, naming three or more regions that leave mine out: US, UK, CanadaHiring scopeSent
Remote, naming one or two countries that leave mine out: US onlyHiring scopeHeld

What arrives in your inbox

One email or Telegram message when new postings pass, grouped by the board they came from. Each line has the title, the company, the location and the day it was posted; the exact time, when the board gives one, is in the dashboard.

Example, made-up postings

PostingWatch · 4 new jobs

Greenhouse boards

  • Senior Frontend Engineer, ReactTallwood HealthRemote, Europe · today
  • Staff Engineer, Web PlatformNorthgate FreightRemote, EMEA · yesterday

Ashby boards

  • Frontend Engineer, Design SystemsQuillmarkRemote, worldwide · today

Hacker News: Who is hiring

  • Founding Frontend EngineerBrightline RoboticsRemote, UTC±3 · today
An example digest. The companies and postings are made up; the layout is the real one.

It runs on your machine

Your keys
Model calls go to OpenRouter with your own key, or to a local model through Ollama. The model sees a posting's title and text with your languages and pay floor, and nothing else about you.
Your data
Postings, reasons and settings stay in a SQLite file and a settings file on your disk. There's no account, no telemetry and no server of mine in between.
Your runs
A run is one pass over every board. You start each one yourself, from the dashboard or a terminal, while your machine is awake; there is no schedule. The digest goes out when the run's queue is done.

Questions

What do I need to run it?

At release: download it, run one command, and paste your OpenRouter key. It needs Node.js and a Chromium-based browser, which it opens itself to read the boards, and an email account (a Gmail app password works) or a Telegram bot for the digest. A local model through Ollama works in place of OpenRouter. Runs start by hand; there is no schedule. Windows and macOS support is in progress.

Could it drop a job I'd have wanted?

It can. The posting is then in the dashboard under the check that dropped it, with its saved text, so you can see what the rule or the model made of it and loosen the rule. No answer from the model keeps a posting in the queue for a retry rather than dropping it. My own rules are wide on purpose, so that it errs toward sending: about 3 in 10 of what it sends me are worth applying to, and I take that over a lost posting.

Which boards does it read?

The ones in your settings, one listing page per line. My list has about 30: company career pages on Greenhouse, Lever, Ashby, Workable, SmartRecruiters and Workday, Hacker News, We Work Remotely, Remote OK, Wellfound, Working Nomads, Built In, Y Combinator's boards, arc.dev and more. Another listing page is one more line; a board with unusual markup needs a small reader of its own. A board that shows postings only to signed-in members is read in a browser profile of its own, which you sign into once.

Does it apply to jobs for me?

No. It reads new postings, drops the ones you can't or wouldn't take, and sends you the rest. Deciding what to apply to stays with you.

What does it cost to run?

The code will be open source, and the model calls cost what your provider charges. On my setup a run costs $0.01 to $0.06; the first few cost more, before anything is cached. My OpenRouter key spent about $0.45 a day over about a dozen runs a day, read from the key on 2 October 2026, so about $14 a month at my pace. A local model through Ollama costs nothing beyond your own machine.

When will the code be public?

There's no date, and I won't invent one. It is the tool I run every day for my own search, and the public repository comes once it installs cleanly on a fresh machine. Leave your email above and you'll get one message when it opens.

How is it related to PostingFit?

PostingFit is a separate paid product, still being built, that tailors a resume to one posting. PostingWatch will be open source either way, will be able to hand a posting to it, and works without it.

Get one email when the code is public

PostingWatch will be open source. The form at the top is the whole signup: one address, one confirmation, one email when the repository opens.

Go to the form