Wellfound holds a good deal more than job postings. This is an account of what was left out and why, written because a limits section that only lists accidents is not a limits section.
What is on a company page
Funding rounds, investors, perks, team size and — the part that matters here — named founders and employees with their roles. It is a rich page, and it is the page that gets asked about most.
Two reasons, pointing the same way
The first is that Wellfound puts /company/* behind a Cloudflare challenge. That is a control the site placed there deliberately, and treating it as an obstacle to route around is a different activity from reading published listings.
The second would apply even if the page were wide open: it identifies individuals. A dataset about which startups are hiring for what, at what salary, does not become more useful by naming the people who work there — it becomes a different kind of dataset, with a different set of obligations attached. Article 6 GDPR does not exempt data because it was published.
Descriptions are passed through, not mined
Job descriptions are delivered exactly as the company wrote them, in markdown and HTML. Nothing is extracted from them and nothing is derived: no hiring-manager names, no contact details pulled out of the text, no inferred seniority. A description that happens to contain a name contains it because the company published it there.
What ships instead
The company as it appears attached to its own postings: pitch, size band, hiring badges, industries, website, logo and geocoded headquarters, plus every ATS seen across its jobs. That is assembled from the listing surface, which exists so that candidates can find these companies.
What robots.txt says about profiles
wellfound.com/robots.txt, checked on 9 September 2026, disallows /u/ — the user profile path — along with /search and the account surfaces. A site's own machine-readable declaration is the cheapest signal available about what it considers crawler-facing, and here it points the same direction as everything else — reading robots.txt as a specification.
