DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to track a new employer by copying its careers URL details with Jobradar

Add a company to config.yaml using the board and slug taken from its careers URL, then scan it.

Who it is forA job seeker who wants to follow an employer that is not in the default list of 56 companies.

The problemThe tracker only watches companies you add, and each company needs the right board type and slug to be read correctly.

The outcomeThe new company appears in your scans and listings, and you can see its scored openings with `./run.sh list`.

What you need first

  • Python 3.11 or newer
  • A Mac, because the scheduled runs use launchd
  • Your resume as a PDF file
  • An LLM API key for an OpenAI-compatible endpoint (the default is xkiro)
  • A Gmail App Password, which needs 2FA turned on for the account first

Steps

  1. Open the company's careers page and note the board type and slug from the URL, using the examples in the README table.
  2. Add an entry such as { name: 'Figma', board: greenhouse, slug: 'figma' } under companies in config.yaml. (inferred, check the README)
  3. Run ./run.sh scan to fetch the new board and score its openings.
  4. Run ./run.sh list to see this week's finds in the terminal.

Prompt for your agent

In the jobradar repo, add <company name> with the correct board and slug to the companies list in config.yaml, then run ./run.sh scan and ./run.sh list. Report the board type and slug used and the number of openings found for that company. Verify that the company name appears in the list output.

Caveat. The README lists the supported boards as Greenhouse, Lever, Ashby, Workable, Workday, and Oracle Recruiting Cloud, so a company on another platform cannot be tracked.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page