Job boards match on title, so you get every “Senior Backend Engineer” in Europe — including the ones paying half your floor, the on-site-only ones, and the four that are reposts of a role you already dismissed in May.
This routine reads the posting itself against your floor, your city and your remote rule. And because it remembers every role it has shown you, it can lead with the thing a board can't see: what changed about a job you already know.
A board treats each posting as a new event with no history. joris keeps a ledger of what it showed you and what you did about it — so when a job reappears, it doesn't say “new match”. It says what moved.
Remote, right stack, no salary anywhere in the posting.
Shown to you“Not without a number — I'm not doing three rounds to find out.”
Reason recordedSame text, new date, new board. Nothing you cared about had changed.
Held back · silentPosting edited to add €85–95k. That's the one fact that changes your answer.
Surfaced as an updateThat's the sentence that wastes your evening. Keyword matching can't catch it, because the keyword is right there in the headline and the contradiction is four hundred words down.
Your rules are prose, not checkboxes — “€85k minimum, fully remote or Lisbon, no on-call rotation, not agencies” — and each posting is read against them end to end. When a posting is ambiguous, you get an amber flag instead of a false positive.
Which makes “Open to work” a bad idea and recruiter inboxes a worse one. This is a private document that arrives, and nothing else happens.
Those match your title and location only — they can't read a posting. joris checks each new role against your real deal-breakers (salary, remote, seniority, company type) and tells you why each passed or failed, so the shortlist is already vetted.
Yes. When you save or dismiss a role, joris remembers, so each run leads with genuinely new postings and changes instead of re-surfacing yesterday's. That “what changed since yesterday” view is the point.
It reads the live web rather than plugging into one board's API, so it isn't limited to a single site. Name the roles and criteria; it checks the postings that are actually out there.
Yes — because it remembers what it's shown you, it flags when a role you're tracking discloses salary, reposts, or closes, not just when something brand-new appears.
No — it finds and vets the roles worth your time and tells you why. Applying, and the judgement that goes with it, stays yours. Think of it as the research assistant, not an auto-applier.
People who run this routine tend to add one of these within a fortnight.
Portal alerts dump every listing. This one checks each against your hard must-haves — lift, budget, outdoor space, wa...
Explore →Different job, different document. Tell us the output you'd want waiting for you and we'll build the template.
Ask us →Tenders in your sector. Grant calls with your eligibility. Freelance briefs above a day rate. Anything where the listings repeat and only the updates matter — describe it and we'll design the output template.
Write your floor, your city and your rules in a sentence. The first digest reads every posting against them — and from then on it only interrupts you when something actually changed.
Start free