Why a shared job index matters more than another bot

Every job Projobly scrapes ends up in a shared, deduplicated index. The same role posted on LinkedIn, Indeed, and the company's career page resolves to one record with multiple sources, and a continuous timeline of when it was first seen and when it disappeared.

Why bother - **Cost.** The expensive part of scraping isn't HTTP — it's the LLM extraction we run on arbitrary career pages. Doing it once and reusing the result across users is the only way to make breadth affordable. - **Trust.** A platform that visibly knows the industry — counts, trends, recent postings — is one we'd trust to act on our behalf. A platform that runs an opaque search and tells us "we found stuff" is one we wouldn't. - **History.** Knowing when a role was first posted, when it disappeared, and how often similar roles recur is genuinely useful intelligence. Not for marketing — for you.

What we don't do with it - We don't sell it to recruiters. - We don't share resumes across the index. - We don't tell company A that candidate X applied at company B.

The index is the substrate. The bot is the product on top. Both matter — but most of the value is in the substrate.