Notes from the operator side.

Long-form writing on AI-powered job search, Claude Code skill design, and what the data from 740+ listings actually says. Less marketing, more methodology.

Why am I not getting interviews? When applications go into silence

Silence is not an answer when you get no interviews. What the US hiring data says, and three things you control: where you apply, who you write to, your numbers.

How to track job applications with a tracker you own

The three ways people track a job search compared, and why an open-source tracker that keeps the data in a file you own beats a spreadsheet or a hosted app.

Can an AI agent run your whole job search?

What an AI job search agent can automate (scanning, scoring, tailoring, tracking) and why the decision to apply should stay with you.

How to choose an AI job search agent

AI job search agents read job listings, score them against your CV and draft applications. Seven questions to ask before you pick one, from who sends the application to where your CV goes.

What 740 listings taught me about the AI-era job market

I evaluated 740 listings, applied to 68, and accepted one offer (a Head of Applied AI role). Here is what the numbers say about archetype fit, comp band realities, the tailoring response delta, and the patterns that bite candidates without an explicit rubric.

Why career-ops

I built career-ops to manage my own job search after exiting a 16-year operator role. 740 listings evaluated, one Head of AI offer landed. Then I open-sourced it. Here is what the project is, what it deliberately is not, and why this asymmetry needed a tool on the candidate side.