Findable Is Not Chosen — and That Résumé Won't Save You

Findable Is Not Chosen — and That Résumé Won't Save You

Thirteen applications since mid-August. Thirteen polite silences.

Every one had a tailored CV. Every one had a cover letter mapped line by line to the job description. By the rules hiring used to run on, that candidate did everything right.

If your inbox looks the same, so did you.

You're findable. Findable is not chosen. The rules are the problem — and sitting still won't fix them. The rest of this piece is what to do instead, in order, starting today.

Your résumé is priced at zero. Here's why.

A résumé was never proof. It was a proxy. "Ten years at X" stood in for "can do the work." A degree stood in for "learned the theory."

Proxies only hold while they're expensive to counterfeit. Both broke the moment a plausible CV for any role became a forty-second task. Every candidate generates one now. Every candidate looks perfect on paper. Hiring managers know it — so they discount the document to zero and hunt for the one thing a prompt can't fake: something you built, in public, with a trail.

I spent this month taking notes while hiring managers explained why they picked the person they picked. Not one mentioned a degree, a certificate, or a years count. All of them described something the candidate had built or fixed.

Your résumé still does one job: it gets you past the ATS filter. That's all "findable" means. Treating the filter as the decision is the mistake.

Action 1 (today, 30 minutes): Audit your last 10 applications. If all you sent was a CV and a cover letter, you sent nothing a prompt couldn't produce. Stop tweaking the document. Start building the evidence.

The three probes behind every AI interview question

Every interview question about AI is a wrapper. Unwrap it and you find one of three probes:

• Experiment like a scientist — hypothesis, test, accept the result, move fast. Sounds like: "How would you automate this?"
• Stay close to the work — you can name which step of the workflow is broken, and which steps AI can actually improve. Sounds like: "Walk me through a process you rebuilt with AI. What didn't work?"
• Stay curious — you ask the customer the right questions before building anything. Depth, not breadth. Sounds like: "What did the customer actually need, and how did you find out?"

What a fail sounds like, and what a pass sounds like:

• Experiment. Fail: names a model and a prompt. Pass: "I don't know yet — here's how I'd find out, and how fast."
• Proximity. Fail: "I've used AI to improve workflows." Pass: names the step that breaks, then the step you actually automated — and why they weren't the same one.
• Curiosity. Fail: proposes the chatbot. Pass: went and asked the customer where the process loses them, before building anything.

Notice what isn't probed: knowing the most models. Fluency is table stakes, and it's spreading so fast it stops being a differentiator before you finish listing it.

Action 2 (this week): Write your three answers out loud. One experiment, one broken workflow step with names and numbers, one customer question you asked before building. If any of them still sounds like the "fail" column, that's your drill list.

Build a portfolio of process — the five artefacts that get you chosen

Chosen candidates don't show up with a better résumé. They show up with a portfolio of process. Five artefacts kept coming up in my notes:

1. One workflow you rebuilt with AI. Manual before, AI after, named and scoped. Yours — not a tutorial's.
2. A public write-up of it. A post, a blog, a repo README. Anywhere a hiring manager finds it before the interview.
3. A failure log. The automations that didn't work, and why. The most under-supplied artefact in hiring right now — and the most reliable signal of a scientist's mindset.
4. A technical deep-dive. Not "I use Claude Code." How the agent loop works. What your MCP server exposes. Where the tokens go.
5. A day in the life with agents. Which agents, which tasks, what you still do by hand and why. Video is best — it proves communication skill in the same footage.

The same pattern runs under all five: you walked into a process, found the broken step, fixed it with AI, and explained it to the team. That is the job now, whatever the title says.

Action 3 (this month, one artefact per week):

• Week 1: pick one workflow from your current or last job and rebuild a piece of it with AI. Small is fine. Real is required.
• Week 2: publish the write-up. A failure log is the most under-supplied artefact in hiring right now — so include what broke.
• Week 3: write the deep-dive. If you can't explain where the tokens go, learn it, then write it.
• Week 4: record one video walkthrough. Post it. Posting is how you prove the knowledge in your head exists outside it.

Interviews changed on both sides of the table

Candidates moved first. They record every interview, feed the transcript to an LLM, and ask where they were vague and what a stronger answer would have sounded like. Then they drill the weak answers before the next round. If you aren't doing this, the person you're competing with is.

Interviewers went the other way from what most candidates expect: deeper, not shallower. The coding round is less about syntax and more about one question — "show me how you'd do this with AI, and where you'd stop trusting it."

The strongest answer in my notes ran like this:

"This is my domain. Here's the workflow, here's the step I automated, here's the agent that does it, here's what I'd change next, and here's how I'd hand it to the team."

Now read the CV-bullet version: "Experienced with LLMs and agentic workflows."

One of these earns a second call.

Action 4 (every interview, from the next one on): Record it (where legal), transcribe it, and run one prompt: where was I vague, and what would a stronger answer have sounded like? Drill the weak spots before the next round. Fifteen minutes per interview. Your competition is already doing it.

The uncomfortable part

AI is opening roles faster than most people expected. For a lot of people it's the social elevator they've been waiting on — a way to skip the credential queue and be judged on the work itself.

Good news, with one catch: the elevator only stops for people who put the work where it can be seen.

So here's the sequence. Stop rewriting the CV. Build one workflow. Publish the write-up — failures included. Record your interviews and drill the weak answers. Four actions, and not one of them is "apply to more jobs."

Findable is the ATS. Chosen is the evidence.

Which artefact are you shipping first?