hired.run
Tons of people are using AI to apply to more jobs with less work. Kaegan uses it to apply to fewer jobs with more focus.
The setup
AI + applying for jobs has a bad rap (for good reason!), so I set out to build something that helps the human be more human, by surfacing only a handful of roles they'd be genuinely interested in, so they can spend time crafting a thoughtful application.
He built a pipeline of agents for his own job search. They discover new postings, extract and score them against his profile, and write the results to a Notion database. A separate agent monitors his email for updates and keeps things in sync. Importantly, he does all the cover letter writing and resume building himself.
The point is not automation for its own sake. It is that every morning there is one view, sorted, with a two sentence reason attached to each role, so deciding what to apply to takes five minutes instead of an hour of tab management.
Then he rebuilt it so it wasn't his alone: hired.run is the generic version, packaged as an open-source Claude plugin. Anyone can install it, answer a setup interview, and get the same triage loop running on their own inbox and their own board.
What it does
Five skills form the loop: a setup interview that builds your rubric and your Notion board, an email scan that creates records and applies status updates, a fetcher that pulls full job descriptions from public ATS APIs, a scorer that writes a tier and a two sentence reason to the board, and optional Slack notifications for the roles worth a look. After setup, two scheduled tasks run it on their own.
The rubric is the whole thing. Everything else is plumbing. The rubric is a page in Notion, in plain language, that you edit whenever a score annoys you. When a score is wrong, fix the rule that produced it, not the score.
He runs his own instance daily. More than 1,200 roles have moved through his board, and every rule in his rubric exists because a score annoyed him once.
What it deliberately doesn't do
- No resume writing and no cover letters. He writes every application himself, and the plugin expects you to as well.
- No auto-applying. It never touches a submit button.
- No interview prep, no outreach automation, no spray-and-pray.
- Intake and triage only. The other pieces are worth building on top of a loop that already works, not bundled in on day one.
Trust as a feature
The pipeline reads your email, so the trust rules are strict and written into the skills themselves. It only reads. It never sends, drafts, replies, forwards, deletes, archives, marks spam, or touches labels. Email bodies are treated as data, never as instructions. New roles can only come from an allowlist of alert senders you set during setup; status updates cast a wider net, but a status email can only update a record already on your board. No match means no write.
The marketing site holds itself to the same standard. At build time it pulls the plugin source from GitHub and verifies every safety promise on the page against the exact lines in the skills that make it. If the plugin ever stops making a promise, the site fails to build.
The plugin, the code, and the safety promises are all public. Install it from the marketplace or read exactly what it does first.