What I learned reading 50 companies' job postings

I read job postings for a living. Not because I’m looking for a job, but because a company’s hiring is the most honest document it publishes. A job posting tells you exactly what’s broken, what’s budgeted, and what they need right now. It’s a spec sheet written by people who have a problem, and it’s more current than any vendor database you can buy.

The thesis is simple. When a company posts a role, it is confessing three things: there is a problem, there is money to solve it, and the need exists today. A job ad is a dated, signed statement that a specific gap is real enough to spend salary on. There is no stronger trigger event in outbound than a company putting a role on its careers page.

The trick is reading them the way an engineer reads a spec, not the way a recruiter reads a posting.

The first thing to look for is named tools. When a job description lists Clay, Salesforce, HubSpot, a sequencer like Outreach or Salesloft, and an enrichment vendor, it is confessing its stack. A company’s own hiring ad naming its tools is higher-signal than anything a data provider would sell you, because the company wrote it, and it costs nothing to read. That combination, Clay plus a CRM plus a sequencer plus enrichment, almost always means the same thing: they bought the ingredients and they don’t have a cook. The tools don’t assemble themselves into a revenue machine. Someone has to build the system between them.

The second thing is the build-versus-manage language. The verbs tell you whether the seat is greenfield or legacy. “Architect,” “design and build,” “0 to 1,” “founding” means someone is starting from zero. “Maintain,” “own existing,” “support,” “run” means someone is inheriting a system. These are different problems for different companies, and the words are right there in the ad. A maintain seat at a mature company is not your buyer if you sell build work. A founding seat at a company that just raised is.

The third thing is seniority and stage. A founding or first-of-kind title at a seed or Series A company is a greenfield build. The same title at a Series C company is usually operational debt being backfilled. The words are identical; the work is not. One company posted a “GTM Engineer” role that was actually pre-sales. Another’s GTM Engineer seat was a Series-C RevOps manager job in a current-market label. The title is the marketing. The verbs are the spec.

You can also spot the companies to skip, and skipping is half the value. Agencies reselling services post roles that look like your target but aren’t. Late-stage maintain roles post build-sounding titles that aren’t build work. Pre-sales and enablement seats wear the GTM label because the label is hot right now. Reading the ad carefully filters all of these out for free, before you spend a credit or write an email.

I built a sourcing engine on this premise. It reads public job boards, pulls the descriptions, and decodes them: which roles are trigger roles, which are build versus manage, which companies fit a target profile. The engine exists because reading fifty companies’ job postings by hand taught me that the signal was always there, in the text, public and free. The companies it surfaces are companies whose own hiring has already told me they have the problem I solve.

A job posting is the strongest trigger event there is, because it’s the one signal the company writes about itself. Learn to read it, and you stop guessing who has the problem. They’re telling you.

The strongest trigger in outbound is a company telling you, in writing, what’s broken. I read those documents for a living. Worth a 30-minute look at your stack? → Book a call.