Account Intelligence
What a Job Posting Tells You About a Company's Problems
Adriaan ten Boosch
Read Time
6
mins
Last Updated
A company writes down everything it cannot currently do, in detail, and posts it on its careers page for anyone to read. That is what a job posting is. Most sales teams skim it for a contact name. The ones getting meetings read it for the problem.
Read correctly, one posting tells you four things:
What the company cannot do well enough right now. The gap.
Which part of the organization owns it. The buying unit.
How urgent it is. Visible in seniority and how many roles are open.
What a fix has to look like from their side. Visible in the responsibilities and the named tools.
That is more actionable, more specific, and more company-specific than most intent data. Generic intent tells you somebody at the account showed up. A job posting tells you what they are trying to fix and who will own it.
Last updated: June 2026
Why this signal is underused (and the fair reason)
Most reps do not read postings this way, and it is not because they are incurious. Reading a posting for the gap takes a method and time most BDRs do not have against an 80-account list. So they pull the hiring manager's name, write "I see you're hiring," and move on. The signal is sitting right there, and the workflow does not give them room to use it. That is the honest reason it goes to waste, and it is fixable upstream.
Why a posting beats a topic surge
A company posts a role when it has decided to spend money on a problem. That sits between "we feel the pain" and "the budget is approved." It is one of the clearest buying signals a company produces without meaning to.
Set it next to intent. Intent says someone at the company read about a topic category. A posting says the company decided the problem is real enough to hire for, scoped the gap, named the owning team, and described the experience needed to fix it. "We're hiring a VP of Sales Ops to own ABM infrastructure and territory allocation across EMEA" is a play, a buying unit, a scope, and a rough timeline in one sentence.
The one limit is freshness. A posting runs 30 to 90 days, then vanishes from most tools. The timing edge is real but short.
Five things hidden in every posting
The gap. The responsibilities are a list of things nobody is currently doing well enough. Read them as problem statements. "Own the ABM target list and keep it aligned with Sales" means the list is misaligned and unowned today.
The buying unit. Reporting line and team tell you who owns the problem. An FP&A role under the CFO means Finance owns it. A RevOps role under the CRO means the Sales org is driving.
Urgency. Seniority plus headcount. A VP-level hire means it reached the executive team. Several roles in one function in a short window means the gap is outgrowing the team. Senior plus multiple equals urgent.
Current state. "Experience with [tool]" tells you what they run. "Comfortable building without established playbooks" tells you they start from scratch. "Replacing a departing leader" tells you a transition opened the window.
Timeline. "Immediate start" or "priority hire" means it is already costing them. A role open three months means the problem is harder than expected, or the budget is shaky.
A teardown
This is the article's worked example: one posting, decoded. The posting below is illustrative, written to show the method, not a real company.
"Director of Revenue Operations. You will own our account prioritization model and align territory allocation between Sales and Marketing. You'll work with leadership to define what 'good pipeline' means and build the data to measure it. Experience with ABM tools (Demandbase or 6sense) required. Comfortable building from scratch in a scaling environment."
Decoded:
Gap: prioritization is not working, Sales and Marketing are not aligned on targets, "good pipeline" is undefined, the data does not measure it.
Buying unit: RevOps under the CRO. The CRO owns the budget.
Urgency: a Director-level "build from scratch" hire. It reached the CRO's desk and there is no incumbent system to displace.
Current state: they already have ABM tooling that is not delivering. They are not buying another tool. They are hiring someone to make the existing output mean something.
The play: this is not a tool gap, it is an intelligence gap. They have intent and ABM infrastructure and no shared conviction about which accounts and why. The play: show how a GTM intelligence layer gives the incoming Director a working model on day one instead of six months of build.
The opener that falls out of it: "You posted the RevOps Director role to own prioritization and align Sales and Marketing. Most people hired into that spend their first six months building the model before it produces anything. Some teams hand them one that already works." Compare the weak version, which uses the same posting and learns nothing from it: "Saw you're hiring in RevOps, we should talk." Same input, no decode, no reason to reply.
Diagnostic: is this you?
This matters for any team selling into more than one buying unit, where the right message changes by account. You have the problem if your reps personalize from postings with "I see you're hiring" and stop there. You have it if nobody on the team can turn a job description into a buying unit and a play. You do not have it if you run one play into one persona and every account's pain is the same.
The artefact: the posting decoder
Five fields, each extracted from the posting, with a rule for when to act:
Field | Pull from | Act when |
|---|---|---|
The gap | Responsibilities, read as problems | The gap maps to a pain you solve |
Buying unit | Reporting line + team | It's a unit your play targets |
Urgency | Seniority + count + days open | Senior, or multiple roles, or fresh |
Current state | Requirements, named tools | They have adjacent tooling that isn't enough |
Play match | The four above, combined | All four point one direction |
One posting is a hypothesis. The decoder turns it into an action only when the fields line up. Three postings in a function in 60 days, or a posting plus a matching exec change, is a pattern worth acting on now.
What it costs to ignore it
The cost is timing. A posting is a 30-to-90-day window into a budget that is forming. Miss it and you reach the account after the role is filled, the model is half-built, and the buying unit has already framed the problem in someone else's language. Reps reading postings as contact lists are leaving the most time-sensitive signal a company emits sitting in plain sight, and competing later, on worse terms, for the same account.
FAQ
Why are job postings useful as sales signals?
A posting is a decision. The company decided the problem is worth hiring for, scoped the gap, named the owning team, and described the fix. That is more specific, more timely, and more company-specific than most intent data.
How do you decode a job description into a play?
Read the responsibilities as problem statements. Each line is something not done well enough today. Identify the gap, the team that owns it, and the urgency, then match the gap to the play that addresses it in that buying unit.
How current are job-posting signals?
A posting goes live when a hire is decided, usually weeks after the problem was recognized at leadership level, and runs 30 to 90 days. Act within 30 days of posting for the strongest timing edge.
Should BDRs read job postings?
Yes, with a method. Without one, you get "I see you're hiring." With the decoder, you get an opener tied to the gap, the buying unit, and the play. The difference is the interpretation layer, not the BDR.
Close
Most teams treat postings as a place to find names. The teams getting replies treat them as the most detailed public account a company will ever give of what is broken inside it. A job description is not a task list. It is a problem, named, scoped, and owned. Read it that way.
Rembrandt reads it that way at scale. It watches postings, exec moves, and filings across your whole territory, decodes each into a gap, a buying unit, and a play, and surfaces the account while the window is still open. Your reps stop scraping names and start opening the right door with the evidence already in hand. See it run on your accounts.
