Turn Your AI Coding CLI Into a Job-Search Pipeline

Job hunting means juggling spreadsheets, tweaking resumes for every posting, and losing track of which company you applied to three weeks ago. Career-ops turns any AI coding assistant into a structured job-search system that evaluates postings, tailors CVs, and tracks applications—all locally, no third-party platforms required.

The job-search spreadsheet problem

Most technical job searches follow the same chaotic pattern: scan listings on multiple job boards, copy-paste URLs into a spreadsheet, manually score each posting against your background, edit your resume for the hundredth time, then forget which version you sent where. The evaluation is ad-hoc, the resume editing is repetitive, and the tracking falls apart after the first dozen applications.

Career-ops addresses this by scoring each listing against a five-dimension rubric plus a holistic 1–5 global score. It generates ATS-optimized PDF resumes tailored per role directly from job descriptions and your CV, then stores everything locally so you always know the state of your pipeline.

What career-ops actually does

Under the hood, career-ops is implemented as markdown-based skill files that run inside AI coding CLIs via the Agent Skill Standard. It acts as a local multi-agent system controlled from your terminal—one agent evaluates job listings, another generates tailored resumes, a third tracks application status. You feed it a job description, it returns a scored assessment and a matching PDF resume, no web dashboard required.

The workflow eliminates manual drudgery while keeping humans in control. You decide which postings to pursue; the tool handles the scoring logic and document generation.

The developer's own journey: 700+ applications

The creator, known as u/Beach-Independent on Reddit, built career-ops with Claude Code to manage their own job search. They used it across more than 700 applications, generated over 100 tailored CVs, and landed a Head of Applied AI position. Then they open-sourced the entire workflow.

That's not a guaranteed outcome—job searching is still hard, and AI doesn't solve standing out in a crowded market. But it is proof-of-concept that the system can scale to hundreds of applications without collapsing into spreadsheet chaos.

JobOps and the competitive landscape

Career-ops isn't the only tool tackling this pain point. JobOps, a competing self-hosted job-search cockpit, offers similar capabilities: scraping listings, ranking them, tailoring resumes, and tracking applications. The fact that multiple developers have independently built overlapping solutions signals that this is a real, persistent problem worth solving in different ways.

JobOps and career-ops represent different design philosophies—one emphasizes a cockpit interface, the other leans into CLI workflows—but both are serious attempts to reduce the manual overhead of modern job hunting.

Community forks and token efficiency

Open-source projects evolve through community iteration. One fork cut token usage by 85% and improved scalability, addressing perceived inefficiencies in the original implementation. That's how open source works—developers use career-ops in production and refine it for their own workflows.

Rapid traction: 65k stars in four months

Career-ops crossed 65,000 stars roughly four months after its first commit and hit #1 on GitHub Trending. That momentum doesn't mean the project is finished—it has open issues, including Windows compatibility—but it indicates many developers face this problem and want a better solution than spreadsheets.

What this tool won't do

Career-ops won't land you a job. It won't write cover letters that guarantee callbacks or outsmart ATS systems that have already screened you out. It reduces the manual drudgery of scoring postings, tailoring resumes, and tracking applications, but humans stay in control of strategy, outreach, and follow-up.

Job searching is still job searching. This tool just makes the operational side less tedious.

Getting started with career-ops

Check the GitHub repo, review the documentation at career-ops.org, and understand the Agent Skill Standard workflow before diving in. If you're actively job hunting or anticipating a search, career-ops is worth a look—especially if you're already comfortable with AI coding CLIs and want to automate the parts of the process that don't require human judgment.