job-posting-signalslisted

# Job Posting Signals A job post is a company publicly committing budget to a problem. It's dated, specific, written by someone inside the company, and free to read. For outbound it's one of the highest-quality signals available and it's under-used because it takes slightly more work than filtering a database. Three distinct things a job post tells you, and most people only use the first. ## 1. They're building the function you serve The obvious use. If you sell to sales teams and a company posts two SDR roles, they're investing in outbound and will need tooling around it. Map your product to the roles that imply it: | You sell | They're hiring | |---|---| | Outbound tooling | SDR, BDR, Head of Sales, RevOps | | Analytics | Data analyst, BI, first data hire | | Support software | Support lead, CX manager, first support hire | | Recruiting tools | Recruiter, Head of Talent, TA coordinator | | Marketing tooling | Growth, demand gen, content lead | | Finance software | Controller, FP&A, first finance hire | | Security | Security engineer, compliance, first DevSecOps | **The first hire in a function is the strongest version.** A company hiring its first RevOps person has just decided the problem is real and has nobody with an entrenched tool preference. That's a much better prospect than a company with an established team on a competitor's platform. ## 2. The tech stack, stated openly Job descriptions list required tools far more accurately than any technographic detecti