startup.jobs Extractor
What it is
Original website: startup.jobs
This extractor wraps the published startup-jobs-scraper package and feeds normalized startup.jobs listings into the existing pipeline.
Implementation split:
extractors/startupjobs/src/run.tscallsscrapeStartupJobsViaAlgoliaand maps package records intoCreateJobInput.extractors/startupjobs/src/manifest.tsadapts pipeline settings, emits progress updates, and registers the source for runtime discovery.
Why it exists
startup.jobs adds a startup-focused board to job-ops without introducing another bespoke scraper in this repository.
Using the published package also keeps the integration small and makes it easier to evolve the scraping logic independently from the app.
How to use it
- Open Run jobs and choose Automatic.
- Leave startup.jobs enabled in Sources or toggle it on.
- Set your usual automatic run controls:
searchTermsare sent asquery.- country or city filters are reused as the package
locationoption. - workplace type is passed through as the package
workplaceTypeoption. - run budget path (
jobspyResultsWanted) is reused asrequestedCountper term.
- Start the run and monitor progress in the pipeline progress card.
Defaults and constraints:
- No new credentials are required.
- The integration runs with
enrichDetails: true, so it opens job detail pages for richer records. - Browser binaries are not downloaded automatically with the package. Install them with
npx playwright installbefore using this extractor in a fresh environment. - When Search cities is set, the extractor runs once per city and once per search term.
- Workplace type is a global run filter, not a per-city override.
- Without explicit cities, the selected country is used as the location filter except for broad modes such as
worldwideandusa/ca.
Common problems
startup.jobs does not appear in sources
- Check that the app is running a build that includes the new extractor manifest.
- This source does not require credentials, so it should appear as soon as the updated build is loaded.
Results are broader than expected
- If no city is configured, the extractor uses the selected country when possible and otherwise falls back to a broad search.
- Add Search cities when you want tighter geographic filtering.
Job descriptions are missing
- Detail enrichment depends on Playwright browser binaries being installed locally.
- Run
npx playwright installand retry if the extractor cannot open job detail pages.