How do you read a job posting as a sales signal?
A job posting is a company paying to tell the world what it's short of, so read the requirements line by line: the tools it names, the team the role joins, who it reports to and how many seats are open. Map each of those to a problem you solve, then write your opener about the problem the hire is meant to fix, not about the posting. No posting proves a purchase is coming, so treat it as a reason to write this week and check whether posting-sourced emails earn more positive replies than the rest of your list.
Updated
What does one job posting actually tell you?
It's the one public document where a company lists its tools, its gaps and its org chart in its own words. Backfills aside, nobody pays to advertise a seat for a problem that's already fixed.
Read for four things (our list, not a study): tool names, seat count and team wording, a brand-new function, and the reporting line.
| Posting element | What it tells you | What it does NOT tell you |
|---|---|---|
| Tool names in requirements | What the team runs or plans to run, and what's missing | Whether they like it, or when it renews |
| Seat count ("3 openings") | A motion being staffed, and roughly how much work it creates | Whether tool budget grew too |
| "First," "new team," "build from scratch" | A function is being created; process and stack are being chosen now | Who decides on the stack |
| Reporting line ("reports to the VP of Sales, who joined in July") | The buyer title, and sometimes that the buyer is new | The buyer's name, usually |
| "Replacing," "backfill," or months of re-listing | Churn or an evergreen posting, not growth | Anything useful for timing |
Hiring is one of six account changes; the other five are in sales trigger events.
Which posting patterns point to which needs?
Our guidance, written for sellers of sales tools. Swap the need column for your category.
| Pattern you see | Likely need (our read) | Who to write to | Skip it when |
|---|---|---|---|
| 2+ SDR/BDR seats at once | Lists, data, sequencing capacity, ramp | The title the role reports to | It's an agency posting, or it's been open 60+ days (our cutoff) |
| First RevOps or Sales Ops hire | Reporting, CRM hygiene, forecasting, stack decisions | Head of Sales or CRO (the hirer), later the ops hire | The company is under ~15 people (our rule; adjust to your deal size) |
| Names your category's tools, not yours | They own the category but not you: a replacement or add-on conversation | Owner of the stack, per the reporting line | The named tool is your partner, or the posting is 60+ days old |
| New VP or Head title plus seats under it | A new leader building a team and choosing process | The new leader, plus the hiring manager | The leader joined more than ~90 days ago (our window) |
Use the two or three rows that fit your product. The "skip it when" column kills the false alarms: evergreen roles, agency copy, backfills.
How do you read a posting in under five minutes?
Read it bottom-up: team and "you will report to" first, then requirements, then nice-to-haves. The top is marketing; the bottom is facts.
Our five-line read:
- Posting date, plus any sign it's a repost.
- Seat count and team wording.
- The requirements block, tools only.
- The reporting line.
- One sentence: "This hire exists because ___."
Can't fill the blank? Not your signal. Close the tab.
Five minutes per posting is our cap; the per-person budget after that is in how much time to research a prospect. Log four columns: account, posting URL, date posted, your one-sentence read.
Worked example: what does this posting say, and what do you send?
You sell verified B2B contact data to small sales teams. The company, the person and the posting are invented, for illustration.
Sales Development Representative (3 openings) Brindlewood Cold Storage, Columbus, OH. Posted 6 days ago. We're building our first dedicated outbound team. You'll report to our VP of Sales, who joined in July, and you'll own 60 to 80 outbound touches a day across email and phone. Requirements: 1+ years in a sales or customer-facing role. Experience with HubSpot Sales Hub. Familiarity with a sequencing tool (Outreach or Salesloft preferred). Nice to have: Experience selling to food distributors or grocers.
Run the five-line read:
| Line | What the posting says | Our read |
|---|---|---|
| Date | 6 days ago, first listing | Fresh |
| Seats and team | 3 openings, "first dedicated outbound team" | New function, staffed from zero |
| Tools | HubSpot Sales Hub, a sequencer, nothing for contact data | The gap is our category |
| Reporting line | VP of Sales, joined in July | New leader inside our ~90-day window; title known, name not yet |
| This hire exists because | They're starting outbound and need people to run it | A list three reps can work from day one |
Our math (house numbers). One rep sends 4 inboxes × 30 sends × 21 sending days = 2,520 emails a month; at 5 touches each, that's 504 new prospects. Three reps need 3 × 504 = 1,512 new contacts a month. Call it 1,500, and put it in the email.
Who gets it. The VP of Sales, found by title (how to find the decision maker). Call her Odette.
The opener (invented; 65 words in the body, under the 80-word mark from how long should a cold email be):
Subject: three SDR seats
Hi Odette, three SDR openings under a VP who joined in July tells me the outbound playbook is being written right now. The posting names HubSpot and a sequencer but nothing for contact data, and three reps at full tilt need roughly 1,500 fresh contacts a month. We supply verified contacts for teams at exactly that stage. Worth 15 minutes before the first rep starts?
Why it lands: the posting gets one clause, the problem gets the rest, the number is checkable, and the ask carries its own deadline. More in cold emails that work. To draft the opener with AI and edit it so a human would send it, see how to write a cold email with AI. If you send it on LinkedIn, read how to use AI for LinkedIn outreach without breaking LinkedIn's rules first.
Where do you find postings for your accounts without paying?
| Source | What it does (per the vendor's help page, read 2026-10-06) | Limit |
|---|---|---|
| LinkedIn job alerts | Daily or weekly alerts by email, app notification or both; a search can be filtered by one or several companies and by date posted (last 24 hours, past week, past month) | 20 alerts per member at once; a search shows up to 1,000 results by default |
| Indeed job alerts | Search by job title, keyword or company, then activate an email alert; daily or weekly; pause or edit under Settings > Communications settings | You must be signed in; no email goes out on days with no new matching jobs |
| Company careers pages | The posting in full | Manual, one page per account |
Twenty alerts is the ceiling, so spend them well. Our guidance: one alert per buyer-side title ("sales development representative"), filtered to the past week, never one per account. Need more? Read whether Sales Navigator is worth it or what Clay is.
When should you skip each source?
- LinkedIn alerts: skip them once you need more than 20 searches.
- Indeed alerts: skip them for international accounts (Indeed says you may be unable to create alerts when searching internationally) and for roles your buyers don't post on Indeed.
- Careers pages: skip them past roughly 25 accounts (our estimate). Above that, the hand check eats your prospecting block.
Can AI read postings for you?
Extraction, yes. Judgment, no. AI pulls tools, seats and reporting lines out of 30 postings fast; it has no idea which matter to you. The "this hire exists because" line stays yours. These prompts are unbenchmarked: run one posting and compare with your own read.
Prompt 1, extraction:
Here is a job posting from [COMPANY]. List, as short bullets: 1) every tool or software named in the requirements or nice-to-haves; 2) the number of openings and whether the text says the team is new, growing or replacing someone; 3) who the role reports to and whether that title is called new; 4) any project, deadline or metric mentioned; 5) the posting date. Then, labeled GUESS, give one sentence on the problem this hire is meant to solve. Do not add anything that is not in the text; write NOT STATED where it is missing. Posting: [PASTE TEXT]
Prompt 2, opener drafts:
Using this extraction from a job posting at [COMPANY], write three opening lines for a cold email from [OUR COMPANY], which helps [BUYER ROLE] with [PROBLEM]. Each line must name one fact from the extraction and the problem it points to, 24 words or fewer, no praise, and never use the words "posting", "job post" or "hiring". Add (GUESS) to any line that leans on the GUESS. Extraction: [PASTE]
Watch for three failures (our list): a nice-to-have promoted to a requirement, an invented reporting line, or a relevance score you never asked for. More prompts in AI prompts for sales prospecting.
How do you know posting-sourced outreach is working?
A posting is not a purchase forecast. We looked for research putting odds on postings turning into deals and found nothing traceable, so we won't invent a figure. Measure it yourself.
- Tag every email with source = posting.
- Compare positive replies, not raw replies. See reply rate vs positive reply rate vs meeting rate.
- Mind sample size (how to A/B test cold emails).
- Lagging check: did the seat get filled within 60 days? Then your growth read was right, sale or not.
Posting accounts fill part of the 504-prospect plan; the calculator estimates sends, replies and meetings.
The sending days, sends per inbox, inboxes per rep and touches per contact on this page are our house assumptions, with one line on why we use each.
Sources
Research and vendor pages accessed October 6, 2026.