JOURNAL
A resume that gets you the job.
Most resumes are static documents for dynamic decisions. The fix is an agent on top.
A resume is a static document for a dynamic decision. That mismatch is the entire problem.
A hiring manager opens your PDF, scans for the keywords their head is full of, and decides in nine seconds whether you make the next pile. The resume cannot answer the questions the manager actually wants to ask. It cannot say "tell me about a time you turned around a stalled GTM motion." It cannot explain why you chose Copenhagen over Berlin or why you left the last role on a Tuesday in March.
So the manager guesses. Or skips you.
Where the screen breaks
Recruiters paper-screen against keywords. Hiring managers want context the keywords cannot carry. The two read the same document and want different things. Neither gets what they need. The candidate gets ranked on the worst possible signal: the surface match.
Most candidates respond by writing more resumes. Different versions for different roles. Cover letters that retread the resume. Long LinkedIn About sections. None of it solves the read mismatch. It just adds surface area for the same broken scan.
What I did with kim-olsen.com
Put a Claude agent on top of the resume.
The agent is grounded in a small RAG corpus: the resume, every project shipped, references from people who worked alongside, and the writing that lives at the back of the site. Ask it anything and it answers in Kim's voice, with a citation back to the source it pulled from. "Walk me through the 90-to-15 day sales cycle reduction" pulls from the project log. "Why Claude only" pulls from the journal. "What's a deal you lost and what you learned" pulls from a private notes file the agent has read.
The hiring manager is no longer reading nine seconds of PDF. They are conducting a 20-minute interview with a candidate-shaped agent that knows the candidate's actual record.
The qualification side
The agent qualifies. It asks four questions before booking anything:
- The role.
- The seniority and team size.
- Geography and remote policy.
- Compensation band.
If the answers cohere with what the candidate is actually looking for, the agent surfaces calendar slots and books the call. The recruiter walks away with a slot, a confirmation email, and a real conversation queued.
The disqualification side
The agent disqualifies. This is the part most people get wrong.
A staffing agency pings looking to fill a contract role at a hardware company in a different timezone. The agent reads the brief, recognizes the misfit, and says so directly. "This is not a role Kim takes. He works on Claude deployment for B2B SaaS, in Europe, full-time. The closest fit you might want is X, Y, or Z." The recruiter gets pointed somewhere useful. The candidate's calendar stays clean.
A "no" delivered well builds more credibility than a "yes" delivered eagerly. Premium hiring managers respect the disqualification because they have been on the other side of it. They are tired of candidates who say yes to everything and then waste three calls before admitting they were never available.
The math
A typical resume on a job board pulls a hundred views, four phone screens, one offer, mostly aligned. The candidate spends fifteen hours of their week navigating roles that were never going to land.
A resume with an agent on top, set to qualify and disqualify honestly: a hundred conversations, eight that the candidate actually wanted, three offers in the right shape, two within scope, one accepted faster. The fifteen hours go back into work the candidate was hired to do.
The numbers are illustrative, not measured. The shape is the point. The agent compresses the funnel by removing the wasted middle.
Why this generalizes
Every B2B website has the same problem the resume has. A static page for a dynamic decision. A buyer scans for the keyword that matches their pain, reads three paragraphs, fails to find the specific case study they need, and leaves. The agent pattern works at any scale, including a single person's resume. If it works for one job, it works for one company's pipeline.
The work to build it is not large. The hard part is the corpus. What does the agent know? Where does it cite from? What does it refuse to answer? The corpus is the moat, not the model.
Closing
Resumes should be doors, not walls. The agent is the doorman. It checks who is at the gate, asks the right questions, opens the door for the right people, and points the rest somewhere they will actually be welcomed.
If you are still sending PDFs, you are still working in nine-second scans. The decision will not get any more dynamic on its own.
Written by Kim Olsen, principal of Brinvik. Get new essays by email.