Where Oink finds jobs—and what source coverage means

No single job board represents the whole market. A broad board may have volume but fierce competition; a specialist board may have fewer roles but better domain fit; an employer’s own careers system is often the closest thing to the current source of truth. Oink searches across these categories and then ranks the combined result against the user’s profile.

The source catalog changes as providers, parsers, and operator settings change, so this page intentionally avoids a fixed source count. “Supported” also does not mean “guaranteed in every run.” It means Oink has an integration path for that source when it is enabled, reachable, and relevant to the search.

Broad and startup job discovery

The current source mix includes LinkedIn-derived public searches, Hacker News “Who Is Hiring?”, Wellfound, Y Combinator startup jobs, Built In, and Welcome to the Jungle. These sources overlap, but not perfectly: a startup may post directly in a monthly thread, publish through its own ATS, and syndicate a copy to a broad board at different times.

That overlap is why normalization and deduplication matter. Oink aims to keep one useful candidate record while retaining the original posting URL and source identity. The original page remains authoritative; a copied or indexed version can lag after the employer edits or closes the role.

For a manual way to search the monthly thread, see how to search Hacker News “Who Is Hiring?”. Developers who need structured public listings can also read how LinkedIn collection works without a logged-in session, including the operational limits.

Remote, regional, and specialist boards

Remote-focused discovery can include Remote OK, Remotive, We Work Remotely, and curated remote-board feeds. Regional technology sources include Just Join IT, No Fluff Jobs, InfoJobs, and Tecnoempleo. AI, academic, research, international-development, and public-interest coverage can include AI Jobs, EURAXESS, jobs.ac.uk, Academic Positions, Ikerbasque, EURES, UN Careers, ReliefWeb, Impactpool, Devex, and university-specific sources.

These categories solve different recall problems. A “remote” board may be useful for distributed work but still contain country or timezone restrictions. A university page may publish a funded role that never reaches a commercial board. A regional site may expose local language and work-authorization details that an aggregator drops.

If location is the hard constraint, read how to check real remote-job eligibility. A remote label is a clue, not proof that an employer can hire in your country.

Employer career systems and the open web

Many companies publish through applicant-tracking systems such as Greenhouse, Lever, Ashby, or Workable. Open-web discovery can find those employer pages and other public postings by using derived role and keyword phrases. Oink does not send a raw resume to the web-search provider; the privacy policy explains that derived queries may be shared to perform discovery.

Employer pages are valuable because they are closer to the hiring organization, but they are not infallible. A requisition can remain public after an internal change, and a verifier can itself be unavailable. Treat liveness checks as risk reduction, not certification. Before investing in an application, open the original URL and confirm the role, location, and apply flow yourself. The ghost-job checklist gives a two-minute process.

Why a named source might contribute nothing

A source can return zero useful results for several legitimate reasons:

• the search is narrow and the source has no matching new roles;
• the source is rate-limited, blocked, or temporarily unhealthy;
• a quota, cooldown, or cost cap reduces how much is fetched;
• records are duplicates of a better canonical copy;
• roles fail explicit location, seniority, or work-mode constraints;
• the source is enabled globally but does not participate in that particular search path.

Oink’s adaptive source budgeting considers supply, relevance, prior delivery, and health. This makes the source mix dynamic rather than a checklist where every logo must appear every day. Provider or model failures can also reduce enrichment, so not every fetched record is guaranteed to have the same depth of structured detail.

For developers and automation teams

If you need job data rather than a personal shortlist, the operator also publishes nomad-agent Actors on Apify. Those are separate products with their own inputs, limits, run evidence, and billing. Some Oink articles link to those Actors because they expose the collection layer directly; that relationship is disclosed on the About and editorial standards page.

Start with searching multiple job boards through one API call to understand the bundle pattern. Verify each current Actor’s Store documentation before integration: marketplace descriptions and supported sources can change independently of Oink’s consumer pipeline.

For job seekers, the simpler path is how Oink works: define the constraints once, let the available sources feed one ranking pipeline, and inspect the evidence before applying.