The Hiring Tell: your job posts are positioning documents, and buyers are reading them

The scene I'm in this week

Monday morning, a $47M fintech outside Charlotte. PE-backed, payments infrastructure for mid-market lenders. In the room: the CEO, the CRO, and a head of people who looked like she'd been arguing with somebody all weekend.

They'd lost a candidate the week before. Final round, senior solutions engineer, the kind of hire that takes four months to replace. On his way out he told the recruiter the job post and the website felt like two different companies and he couldn't tell which one he'd be joining.

The head of people put both on the screen. The homepage spoke to a lender's COO about a problem she has every day. The job post described a platform for modern financial services teams and then listed fourteen integrations. Same company, same week, two different businesses.

I asked how many open roles they had. Nine. I asked who reads a req before it goes live. Long pause. Legal reads them. Nobody else does.

Nine documents describing his company, published on his own domain, pushed out to LinkedIn, Indeed, and two aggregators he'd never heard of, written by seven different hiring managers and approved by a lawyer for risk.

Then the CRO said the thing that ended the meeting early. A prospect had quoted their careers page back to him on a call in June. Not the homepage. The careers page.

Naming what's actually broken

In poker, a tell is the thing you do without meaning to that shows your hand. Your job posts are that. I call it the Hiring Tell.

Reqs get written fast, by people close to the actual work, under a deadline, with no framework and no review. That makes them the most honest public description of your company. Honest and on-message are different things, and the gap between them is where this gets expensive.

Two things leak at once, in opposite directions.

The first leak is the boilerplate. That "About [Company]" paragraph at the bottom of every req is usually the oldest paragraph your company owns. Written once, before your last repositioning, copied from role to role for years because copying it is faster than writing a new one. It's now the most syndicated sentence about your business, and it describes a company you stopped being.

The second leak runs the other way. Somewhere in your open roles, a hiring manager wrote a real paragraph about what your customer is actually dealing with, because a candidate can't do the job without understanding the problem. That paragraph is frequently sharper than anything on your homepage. Nobody who owns your message has read that either.

This is Solution-Centric Marketing with an HR login. The req opens with the company, the funding round, the growth rate, the perks, the tech stack. The customer shows up on line forty, if she shows up at all.

This is just truth: your hiring managers didn't drift off-message. There was no message to drift from, and they had a seat to fill by Friday.

Why is this worse in 2026 than it's ever been?

Job posts used to be a low-stakes surface. Two things changed that, and they changed it at the same time.

AI dropped the cost of writing a req to roughly zero. A hiring manager now generates a full job description in forty seconds and posts it the same afternoon. Volume went up and perspective stayed flat, which is the pattern everywhere right now. Worse, a model with no context about your company writes toward the category average, so your reqs and your competitor's reqs come out of the same machine sounding like siblings.

The second change matters more. Job postings are structured, crawlable, syndicated data. One req lands on your careers page, your applicant tracking system's public board, LinkedIn, Indeed, Glassdoor, and a handful of aggregators. To a retrieval system, that reads as five or six separate places describing your company.

HubSpot's AI Search Visibility research in May 2026 found that brands referenced positively across four or more independent sources are 2.8 times more likely to appear in ChatGPT responses than brands mentioned only on their own website. That multiplier is the whole game, and it runs in both directions. Consistent sources compound you. Four sources telling four versions of your story build consensus around nothing, and the engine resolves you into whatever's most common, which is your category's average language.

This is the same failure I wrote about in "What is message drift, and how do you keep brand messaging consistent across channels?" The careers surface is where drift is worst, because it's the only channel with a dozen authors and no editor.

How do you tell if your job posts are describing a company you no longer are?

Three tests. All of them take less than an hour, and you don't need to open a project or hire anyone to run them.

1. 1The Three-Req Read. Pull your three most recent job posts from three different departments. Read only the first paragraph of each, out loud, back to back. Out loud matters. You'll hear whether they describe the same company, the same buyer, and the same problem, and you'll hear it in about ninety seconds.
2. 2The Boilerplate Date. Find the "About us" paragraph at the bottom of your reqs and figure out when it was last edited. Then set it next to your current homepage headline. Most companies I do this with find a paragraph two positioning cycles old, live on five job boards, describing a company that stopped existing eighteen months ago.
3. 3The Source Count. Open a fresh session in ChatGPT or Perplexity. Ask what your company does and who it's for, then ask it to show its sources. Count how many are job boards, applicant tracking pages, Glassdoor, or LinkedIn company profiles, versus pages your marketing team actually wrote. That ratio is your answer, and for most $5M-$75M companies it's higher than the founder expects.

Test three is the one that changes the room. Founders brace for the engine to get them wrong. Watching it get them right, accurately quoting a description of the company from three years ago, is a different feeling.

What do I see across 100+ B2B companies?

The median founder-led company in the $5M-$75M range has six to twelve reqs live at any moment and exactly zero of them reviewed by anyone accountable for the message. Legal reviews them for risk. Finance reviews the band. Nobody reviews the story.

Nine boilerplates in ten predate the current homepage. Fewer than one in ten job posts name the customer's problem anywhere in the opening paragraph. The perks section is almost always longer than the customer section, which tells you what the company thinks the candidate cares about and gets it backwards.

Here's the part that surprises people. Roughly a third of the time, the sharpest description of the customer's problem anywhere in the business is sitting in a req. It hides in sales engineering, customer success, and implementation roles, because those hiring managers know a candidate who misunderstands the customer will fail in month two. They write the truth out of self-interest.

“What's wrong with CMOs these days. JDs literally read out what's expected from a CMO yet they unashamedly mention role reports...”

... anonymous marketer, r/marketing, 2026

Read what that marketer is doing. He's treating a job description as a statement of what a company actually believes, and he's right to. Candidates read reqs that way. Competitors read them that way. Buyers who are doing diligence read them that way. The engines now read them that way at scale, which is the same surface problem I described in "The Manual Majority: why AI learns your company from your docs, not your homepage." Documentation is your biggest surface. Job posts are your most syndicated one.

A real example

A VC-backed B2B SaaS company, $29M in revenue, supply chain visibility software for mid-market manufacturers. They came to me because ChatGPT kept describing them with language they'd retired in 2023. Their assumption was that the model was stale and would catch up on its own.

We ran the Source Count on the first call. The answer came back citing their Greenhouse board and a job aggregator ahead of their own marketing site. They had eleven open reqs. Every one of them carried the same eighty-word boilerplate written at seed stage, back when the pitch was helping teams work smarter. They'd repositioned twice since then and never touched it.

We built the Magnetic Messaging Framework first, because there was nothing for a hiring manager to write from. Then the work took one afternoon. One new ninety-word company paragraph. One required opening line for every req, naming who the team serves and what problem they're solving, before a single responsibility gets listed. Both pushed to all eleven live posts and into the applicant tracking system template so every future role inherits them by default.

Ten weeks later we re-ran ten category questions. Their 2023 language came back in seven of ten before, and in one of ten after. The head of people told me final-round candidates started opening interviews by talking about the customer's problem instead of asking what the product does. And in the quarter that followed, a rep closed a deal where the buyer said the careers page was the thing that convinced her they understood her world.

Eleven job posts. One afternoon. The framework upstream of it took real work, and the careers surface itself was the cheapest fix on the board.

What this means for you

You don't need a careers page project. You need to stop treating the pages you publish under HR's name as somebody else's positioning. Three things worth doing this week:

1. 1Run the Three-Req Read today. Fifteen minutes, three first paragraphs, out loud. You'll know within ninety seconds whether you have a Hiring Tell.
2. 2Rewrite the boilerplate once. Ninety words: who you serve, which problem you attack, what you believe about it. Push it to every live req and into your applicant tracking system template so it propagates without anyone remembering to do it.
3. 3Go mine your reqs before you rewrite them. Read every open role's description of the customer's problem and find the one sentence that's better than your homepage. It's in there more often than not. Take it and use it where buyers can see it.

All three of those hold only if there's something upstream for a hiring manager to write from, which is where this actually breaks. The fix is a Magnetic Messaging Framework (MMF), a documented strategic narrative built on four anchors: category design, villain framing, an old-way / new-way contrast, and a promised-land outcome. Category design is the anchor doing the work here, because it settles the one sentence every author in your company inherits about what business you're in. This matters for a practical reason. A req gets written by whoever needs the hire, at whatever hour they need it, and they'll reach for the nearest available words. Written narrative means the nearest available words are yours, so the eleventh hiring manager describes the same company as your homepage does, and every job board you syndicate to starts voting for the same story instead of splitting the ballot.

PitchKitchen builds Magnetic Messaging Frameworks for founder-led B2B companies in the $5M-$75M range. I'm Greg Rosner, founder of PitchKitchen and author of Story Craft for Disruptors, and I'd bet a hiring manager at your company wrote a better sentence about your customer this year than your homepage did. Go find it. Does that make sense?