The Resume Is Dead. Long Live the Parlei Link.
The brief
A resume is a one-page document optimized to be skimmed in six seconds by someone who isn't paying attention. Time for a different shape.
A resume is a one-page document optimized to be skimmed in six seconds by someone who isn't paying attention.
That sentence isn't overly dramatic. It's a working description of the resume, drawn from how it actually moves through the hiring funnel. A recruiter scans. A keyword filter parses. A hiring manager flips. The reader's attention is shallow, hostile, and brief. The document is engineered to survive that environment.
Maybe it survives. Sometimes it succeeds. But it does not represent the person.
It cannot. A resume has no time, no context, no audience-awareness, no version control, no ability to answer a question. It collapses a multi-dimensional human being into a one-page lossy summary, and then sends that summary into a system designed to barely look at it.
We have known this for thirty years. We use it anyway.
Why it persists
The resume is the artifact the hiring system was built around, and the hiring system holds the gravity that everything else orbits. Applicant tracking systems are designed to ingest resumes. Recruiters are trained to read them. Job boards are structured to surface them. Career advisors charge to optimize them. The artifact is bad and the infrastructure built on top of it is enormous.
Nobody likes resumes. Candidates resent producing them. Recruiters distrust their accuracy. Hiring managers don't read them carefully. The keyword filter at the top of the funnel does its work badly enough that it routinely drops qualified candidates and surfaces unqualified ones, and the entire industry knows this, and the artifact persists.
It persists because the alternative requires changing the protocol, not just the document.
What the resume cannot do
A resume cannot update itself. The version you submitted on Tuesday morning is the version that will be evaluated on Friday afternoon, even if your role changed Wednesday and you launched something Thursday night.
A resume cannot contextualize for the reader. The same document is read by recruiter, hiring manager, executive sponsor, and HR. Each one wants something different. The document delivers the same thing to each.
A resume cannot answer a question. If a hiring manager wonders, on minute two, whether you've ever shipped at scale — there is no path through the document for them to ask. They have to interpret the bullet points and guess.
A resume cannot show different facets to different audiences. A career strategist looks like a different artifact to a CTO than to a CMO. The resume cannot adapt.
A resume cannot include the things it isn't shaped to hold — the talk you gave, the post that went around, the side project that became a category, the Slack channel where you became known as the person to ask about a thing. The page is too small. The format is too rigid.
So we file all of that elsewhere — LinkedIn, a personal site, a portfolio, a Substack, a Notion page, a press kit — and then we send the resume anyway, because that's what the system asks for. The candidate maintains six artifacts to support one document.
The ATS problem
Both sides hate the ATS. Both sides feed it anyway.
Candidates game it — keyword stuffing, formatting tricks, parallel resume versions for parallel roles, AI-rewriting tools that promise to translate the candidate's life into the dialect the parser expects.
Recruiters distrust its output. They know the top of the funnel is broken. They know the keyword filter rejects strong candidates with non-traditional language and surfaces weak ones who optimized harder. So they go around it — sourcing on LinkedIn, asking for referrals, pulling from networks the ATS will never see.
The system, in other words, has already partially routed around the resume. The ATS is the formal channel. The actual hiring happens in the informal one.
What's missing is a sovereign artifact for the informal channel. Something the candidate maintains, controls, updates, and points at. Something that doesn't have to survive a keyword filter, because the click that brought the visitor was an intentional one.
Pull, not push
The resume is pushed. You write it, you save it, you send it. Every recipient gets the same artifact regardless of why they're reading.
A Parlei link is pulled. The visitor declares context — I'm hiring for a senior role — and the response shapes itself around that.
This is the protocol shift. It's small in description and large in consequence.
In a push model, the candidate is responsible for predicting every audience and producing one document that compromises across all of them. The result is the document we have: skimmable, generic, lossy.
In a pull model, the candidate maintains one source of truth, and the visitor's declared intent shapes the slice they see. The recruiter sees fit-for-role evidence. The reference-checker sees confirmation paths. The journalist sees press kit. The colleague sees what's been happening lately. The investor sees the operator profile.
One link. One source of truth. Many responses.
The resume tries to anticipate every reader and ends up serving none of them well. The Parlei link doesn't anticipate. It asks.
The standard objections
"Recruiters still need a PDF."
Yes — and a Parlei link provides one on demand, but also invites a conversation about your background, with context and a brief dropped in your email.
"ATS won't accept a link."
Some don't. Increasingly, many do. The personal-website field already exists in most modern ATS schemas. The protocol shift is at the threshold, not on the horizon. Pointing that field at a Parlei link instead of a stale homepage is a one-keystroke change with compounding consequences.
"I already have a website."
A website is a brochure. It speaks at the visitor. A Parlei link is a host. It speaks with the visitor. The two are not substitutes for each other; one is a generation older than the other.
"This is just a fancy landing page."
A landing page is a marketing surface optimized for conversion against a single goal. A Parlei link is identity infrastructure that recognizes whichever audience showed up and routes accordingly. The difference is the same as the difference between a billboard and a business card from a maître d'.
"Will recruiters actually use it?"
The recruiters who care about evidence will. The recruiters who only care about keyword density will continue to do their jobs the way they've always done them, until the funnel is bypassed entirely by candidates who route their best opportunities through the informal channel — which, as established, is where the actual hiring already happens.
What dies, what lives
The resume isn't dying because of AI. It is dying because we finally have something that makes better connections.
The piece of paper had its run. It served the era of fax machines, paper files, and assistants who screened mail stacked in a physical pile. The infrastructure that depends on it has outlived the artifact's usefulness by a wide margin.
What replaces it is not another document. It is a different shape — a sovereign, audience-aware, version-controlled artifact that the candidate owns and the visitor declares into.
A resume is what you send when you don't know who's reading. A Parlei link is what you share when you don't have to guess.
The first form persists for a little longer because the system around it persists. The second form is already here, already working, already routing intentional clicks the resume could never see.
The protocol shift is at the threshold.