Landing pages sell the dream. Changelogs show what already shipped. But a competitor's job postings reveal what they're about to build — three to nine months before it hits a changelog or a press release. Here's how to read the one page they forget to sanitize.
Founders spend hours reverse-engineering competitor landing pages and diffing their pricing tables. Both are worth doing. But both share the same flaw: they're written by marketers, edited for persuasion, and describe a product that already exists.
There's a page on almost every competitor's site that gets none of that treatment. It's written by a hiring manager who needs a specific human to fill a specific gap, and who has zero incentive to be vague about it. It's the careers page.
A job posting is a company telling you, in plain language, what it can't do yet and is spending real money to fix. You hire ahead of building. That makes the careers page the most forward-looking document a competitor publishes — and one of the few that leaks strategy before the strategy is announced.
This is the espionage companion to reading changelogs. A changelog is a confession about the past. A job posting is a confession about the future.
Why job postings leak more than the rest of the site
Three structural reasons the careers page is honest when the rest of the site isn't:
It's written to attract, not to convert. A hiring manager's job is to get the right candidate to apply, and the right candidate will not apply to fluff. So the posting has to be specific: the actual stack, the actual team structure, the actual problem the role exists to solve. Specificity that a marketing page would sand off, a job description depends on.
It's forward-looking by necessity. Nobody posts a role for work that's already finished. Every open req is a bet on something the company intends to do in the next two or three quarters. Read a batch of postings and you're reading a rough draft of the roadmap.
Nobody guards it. Marketing reviews the homepage. Legal reviews the pricing page. Almost no one treats the careers page as competitive surface area, so it ships raw. The "about the role" paragraph often describes the target customer and the core problem in plainer terms than the homepage does — because the recruiter is trying to make the mission legible to an engineer, not to a buyer.
The six tells
You're not reading a job posting to fill it. You're reading it for what it admits. Six patterns to watch for.
1. The Title Tell — the role itself
The single most information-dense field is the job title, because a first of any role marks a strategic threshold.
A company's first enterprise account executive means it's moving upmarket. Self-serve and SMB are about to get less attention.
A first developer advocate or DX engineer signals a platform or API play — they want other people building on top of them.
A first compliance, security, or "Head of Trust" hire means they're chasing regulated or enterprise buyers who ask for SOC 2 and won't sign without it.
A first "Head of [function]" where there used to be none means they're formalizing something they used to improvise. That function is now a priority.
Firsts matter more than backfills. One new title can redraw a company's entire go-to-market.
2. The Stack Tell — the technology listed
The requirements section is an architecture disclosure. Engineers can't hide the stack in a JD, because the whole point is to filter for people who know it.
New infrastructure in the requirements — a streaming system, a new database, a specific ML framework — is a re-platforming or a new capability in progress. Wanting real-time streaming experience means real-time features are coming.
Repeated language about "performance at scale," "reliability," or "reducing latency" is a tell that they're hitting limits. That's double-edged: it validates that the market is big enough to strain them, and it flags a weakness you can win on right now while they're busy fixing plumbing.
A cluster of LLM / applied-ML roles is the obvious one, but read the specifics — retrieval, evaluation, and fine-tuning roles imply very different bets.
3. The Volume & Velocity Tell — how many, how fast
Counting is underrated. The rate of hiring says as much as the roles.
A sudden burst across go-to-market — sales, marketing, success all at once — usually means they just raised, often weeks before the funding is announced. GTM hiring is the first thing that thaws after a round closes.
A freeze — postings pulled, roles going stale for months, a shrinking board — points to runway pressure or a missed plan. A competitor in a freeze is a competitor whose roadmap just got shorter.
The same role reposted every few months is a retention tell. If they can't keep a position filled, something internal is broken, and that instability eventually reaches customers.
4. The Language Tell — how the description is written
Read the prose, not just the bullets.
The "about the role" paragraph frequently states the target customer and the core problem more plainly than the homepage. Recruiters translate the mission for candidates, and translation strips the spin.
The "you'll work on" bullets are a miniature roadmap. Each one is a project someone decided was worth a headcount.
A required "X years in [industry]" tells you the buyer persona they're now targeting. When a horizontal tool starts demanding fintech or healthcare experience, it's picking a vertical.
5. The Location & Structure Tell — where and how
A first hire on the ground in a new region is geographic expansion. They're planting a flag before they announce the market.
A shift from contractor to full-time on a given function signals a bet graduating from experiment to commitment. The reverse — converting FTE work to contract — signals the opposite.
6. The Absence Tell — what they're not hiring for
The hardest one to see and often the most valuable: the roles that should exist and don't.
Rapid growth with no support or customer-success hiring is a service gap. Their customers are getting stretched thin, and that's a wedge — you compete on the experience they're neglecting.
A whole function nobody owns is a function nobody is improving. If no one's title touches onboarding, onboarding is bad, and you already know where to aim your demo.
Turning tells into moves
A signal you don't act on is a screenshot rotting in a folder. Each tell maps to a decision:
- They're hiring enterprise sales → they'll deprioritize the low end. Own self-serve and SMB while they chase logos upmarket.
- They're hiring for a specific integration → don't build the same one and arrive second. Build the adjacent one they haven't staffed, or ship the same one faster while it's still a job posting and not a feature.
- They're staffing up reliability and "scale" → they're distracted and possibly wobbly. Push on stability and trust in your own positioning while they're heads-down on plumbing.
- They froze hiring → their roadmap just contracted. The feature you were racing them on may not ship this year. Reassess whether you still need to.
- They're not hiring support → make service and responsiveness a front-and-center part of your pitch, because it's the thing they've decided not to invest in.
Where to actually look
The careers page is the start, not the whole picture. Public sources, most to least useful:
- The applicant-tracking board. Most companies run on Greenhouse, Ashby, or Lever, and those boards live at predictable public URLs. They're usually more complete and more current than the pretty careers page, and they timestamp roles.
- LinkedIn Jobs, filtered to the company, which sometimes surfaces roles the site doesn't feature and shows rough posting dates.
- Startup job boards (Wellfound, YC's list) for earlier-stage competitors.
- Aggregators to catch cross-posts and reposts.
The trick isn't finding one posting. It's watching the set change.
The catch: read clusters, not posts
Everything above comes with the warning that runs through this blog — a loud signal isn't automatically a real one. A single job posting is the definition of a false positive.
Job listings are especially noisy:
- Aspirational reqs get posted and never filled. A role can sit open for a year because it was a nice-to-have, not a commitment.
- Reposts and evergreen pipelines ("we're always looking for great engineers") mean nothing about current strategy.
- Backfills look like expansion. Someone left; they're replacing them. That's not a new bet, it's a patched hole.
- Agencies post on behalf of companies, sometimes garbling the details.
The discipline is the same one that separates a real market signal from an echo chamber: never read a single posting as strategy. Read the cluster. One enterprise AE is noise. Three enterprise AEs, a first solutions engineer, and a compliance hire — in the same quarter — is a company telling you exactly where it's going.
The snapshot is worthless; the diff is everything
Here's the part that decides whether any of this works.
A careers page you looked at once is a photograph of a moving thing. The strategy isn't in the snapshot — it's in the change between snapshots. The competitor who had two open roles in March and eleven in June didn't tell you anything in March. The delta told you everything in June.
Which means the real work isn't reading a job posting. It's checking regularly, capturing the state each time, and comparing — so a new enterprise role or a quiet hiring freeze registers as a change instead of disappearing into a page you glanced at once and forgot. Do that by hand across five competitors and you'll manage it for about three weeks before it becomes the chore you skip.
That's the whole game with competitive signal, and it's why one-off research decays the moment you close the tab. The careers page is the roadmap your competitors forget to hide. The only question is whether you're set up to notice when it changes.