News for hackers. Stuff that matters.

Show HN: Jobsearch – unified CLI for scraping job boards

https://github.com/jozefRudy/job_search

Author here. Got tired of checking Upwork, NoFluffJobs, eFinancialCareers, LinkedIn and HN threads separately, so I built a CLI that scrapes them into a local SQLite DB and lets me browse everything in one web UI with filters and semantic search.

Details:

- Scraping via real browser over CDP (your own logged-in session, no API keys)

- Embeddings run locally (nomic-embed-text via fastembed), stored in Lance

- Rust backend, SolidJS frontend embedded in binary, single static executable

Works for my use case (Europe-based contractor). It's my first rust project, decided to do local CLI, it's helpful for me (more providers will be added, feel free to contribute).

( 6 comments | 5 points | on HN )
Re:Show HN: Jobsearch – unified CLI for scraping job boards by panpawka on Wednesday July 29, 2026 @09:07AM (#49097028)
Whoa, need to check it!
Re:Show HN: Jobsearch – unified CLI for scraping job boards by QuantFantom on Wednesday July 29, 2026 @09:30AM (#49097278)
Give it a try - happy to hear feedback, especially which job boards you'd want added.
Re:Show HN: Jobsearch – unified CLI for scraping job boards by bbxx1 on Wednesday July 29, 2026 @09:27AM (#49097238)
nice tool
Re:Show HN: Jobsearch – unified CLI for scraping job boards by QuantFantom on Wednesday July 29, 2026 @09:30AM (#49097272)
Thanks, let me know if you hit any issues using it.
Re:Show HN: Jobsearch – unified CLI for scraping job boards by vasanthrb on Thursday July 30, 2026 @06:35AM (#49108059)
Interesting choice to require users to already be logged into the browser. Was that primarily to avoid dealing with authentication flows and anti-bot measures?
Re:Show HN: Jobsearch – unified CLI for scraping job boards by QuantFantom on Thursday July 30, 2026 @02:25PM (#49113743)
Yes. Usually if you use some website (e.g. linkedin), you are logged in. So this does not add any complexity for a user (since he already uses linkedin). At the same time, why would I complicate this and deal with login separately from user workflow. So, i would say it is practical choice. Also, obviously when user is logged-in it helps with anti-bot measures (since user might be asked to click a square or something, so he does that in his usual browser).

Alternative is it do it separately from user flow (in different browser, and solve whole new set of complexities, for no real gain), e.g. in headless browser (which sucks for anti-bot).

I am not really into catch your tail game of anti-bot measures, which are not static but evolve in time. If I tap into what user actually does, I have won a game, no need to re-do it forever.