PoolBot minds the pipes

Public listings, one shared pool.

MeWannaJob is our front end. The heavy lifting lives in the Job Data Pool on datapool.work—listings get collected and normalized there once, then tools like this one can stop reinventing the same brittle crawlers.

You are still looking at real jobs; you are just not the hundredth bot hitting the same “careers” page today.

Browse the pool PoolBot’s side of the story
PoolBot mascot with pool skimmer beside a swimming pool

Looking for work

Algorithms love to hide half the board. A shared pool is a blunt way to widen the lens—same postings, fewer gatekeepers deciding what you are allowed to see first.

See what’s in the water →

Shipping a product

If your feature needs jobs data, you probably do not want to own the crawl. Plug into something maintained, fix your actual app, sleep occasionally.

Start from datapool.work →

Running a site that lists jobs

Public pages get scraped to death. Centralizing reads does not fix every abuse, but it cuts the dumb redundancy: one polite reader instead of twenty identical ones.

What we’re trying on datapool.work →

PoolBot waving with a pool on its head

Hi. I’m PoolBot.

I was supposed to catch bad crawlers on a pool-supply job site—yes, actual swimming-pool supplies—and after a while it felt silly that every new project wanted the same public listings in a slightly different JSON shape.

These days I nag people toward datapool.work, which is the feed MeWannaJob reads from. I do not have hands; I have a skimmer and strong opinions.

If the data is already public, hoarding the scrape helps nobody. Peek at the pool →

Why a pool, not a thousand straws.

Posting a role is a press release: you want it seen. Locking the listing behind one app’s feed, or forcing every student project to re-scrape the HTML, is how you get stale mirrors and angry infra teams.

A pool does not solve every problem. It just makes “fetch the open jobs” a boring solved task so the interesting parts—filters, ranking, cover letters, research—can sit upstream.

Dig into datapool.work

PoolBot fishing a job listing out of the data pool