Hiring Trends

Department-specific hiring signals that identify companies actively building out specific teams like Sales, Engineering, Marketing, and more.

Hiring Trends break down which departments a company is actively building — Sales, Engineering, Marketing, IT, and 20+ other functions.

We ingest 80M+ open roles across 21M+ companies and classify each position into one of 23 department categories using job title normalization. When a company crosses hiring thresholds for a specific function, we emit a signal with sample job titles, normalized titles, translated titles, posting URLs, and top hiring locations. A single company can produce multiple signals if they're hiring aggressively across several departments.

📎

See real delivered dataSample Files

Subtypes represent the specific department a company is hiring for — use them to filter signals by the team being built.

Unlike Hiring Velocity which measures overall hiring pace relative to company size, Hiring Trends breaks down where a company is investing headcount by department.

Available Subtypes (23)
Subtype EnumCategoryDescription
hiringAccountingRolesfinanceCompany is actively hiring for Accounting positions
hiringAdministrationRolesadministrationCompany is actively hiring for Administration positions
hiringBusinessDevelopmentRolessalesCompany is actively hiring for Business Development positions
hiringCorporateCommunicationsRolesmarketingCompany is actively hiring for Corporate Communications positions
hiringCustomerServicesRolescustomer_successCompany is actively hiring for Customer Services positions
hiringEngineeringRolesengineeringCompany is actively hiring for Engineering positions
hiringFacilitiesManagementRolesoperationsCompany is actively hiring for Facilities Management positions
hiringFinanceRolesfinanceCompany is actively hiring for Finance positions
hiringHumanResourcesRoleshrCompany is actively hiring for Human Resources positions
hiringInformationTechnologyRolesitCompany is actively hiring for Information Technology positions
hiringLegalRoleslegalCompany is actively hiring for Legal positions
hiringLogisticsRolesoperationsCompany is actively hiring for Logistics positions
hiringMachineLearningRolesengineeringCompany is actively hiring for Machine Learning positions
hiringMarketingRolesmarketingCompany is actively hiring for Marketing positions
hiringOperationsRolesoperationsCompany is actively hiring for Operations positions
hiringProcurementRolesoperationsCompany is actively hiring for Procurement positions
hiringProductionOrManufacturingRolesoperationsCompany is actively hiring for Production/Manufacturing positions
hiringPublicRelationsRolesmarketingCompany is actively hiring for Public Relations positions
hiringQualityAssuranceRolesengineeringCompany is actively hiring for Quality Assurance positions
hiringRecruitingRoleshrCompany is actively hiring for Recruiting positions
hiringResearchAndDevelopmentRolesengineeringCompany is actively hiring for Research and Development positions
hiringSalesRolessalesCompany is actively hiring for Sales positions
hiringStrategyRolesstrategyCompany is actively hiring for Strategy positions

Categories group subtypes into higher-level themes — a common way to filter signals by department function or sales motion.

Signal Categories
CategoryDescription
salesSales and Business Development
engineeringEngineering, ML, QA, and R&D
marketingMarketing, PR, and Corporate Communications
operationsOperations, Logistics, Procurement, and Manufacturing
customer_successCustomer Services and Support
administrationAdministration
financeFinance and Accounting
hrHuman Resources and Recruiting
itInformation Technology
legalLegal
strategyStrategy

Example Signal

What a single entry looks like in a delivered signal file:

{
  "signal_id": "7b2e4f91-c8a3-4d6e-b5f2-9a1c3d7e8f04",
  "batch_id": "2026-04-28-00-00-00",
  "signal_type": "hiring-trends",
  "signal_subtype": "hiringSalesRoles",
  "detected_at": "2026-04-22T11:18:44Z",
  "association": "company",
  "company": {
    "name": "Rippling",
    "domain": "rippling.com",                   // match on domain
    "linkedin_url": "linkedin.com/company/rippling",  // or match on LinkedIn URL
    "industries": ["Software Development", "Human Resources"],
    "employee_count_low": 3001,
    "employee_count_high": 5000,
    "description": "Workforce management platform for HR..."
  },
  "contact": [],
  "data": {
    "category": "Hiring Sales Roles",
    "open_roles_count": 53,
    "pct_of_headcount": 1.8,
    "signal_strength": "high",
    "sample_titles": [
      "Enterprise Account Executive, Mid-Market",
      "Senior Sales Engineer, Platform",
      "Regional VP of Sales, East Coast",
      "Strategic Account Director, Financial Services",
      "SDR Team Lead, Outbound"
    ],
    "sample_normalized_titles": [
      "Enterprise Account Executive",
      "Senior Sales Engineer",
      "Regional VP of Sales",
      "Strategic Account Director",
      "SDR Team Lead"
    ],
    "sample_translated_titles": [
      "Directeur de comptes entreprise, Marché intermédiaire",
      "Ingénieur commercial senior, Plateforme",
      "VP régional des ventes, Côte Est"
    ],
    "sample_urls": [
      "https://www.rippling.com/careers/sales/enterprise-ae-mid-market-7291034",
      "https://www.rippling.com/careers/sales/senior-sales-engineer-platform-7284511"
    ],
    "top_locations": [
      { "location": "San Francisco, California", "count": 18 },
      { "location": "New York, New York", "count": 14 },
      { "location": "Austin, Texas", "count": 9 },
      { "location": "London, United Kingdom", "count": 7 },
      { "location": "Remote, United States", "count": 5 }
    ]
  }
}

Field Reference

Standard envelope and entity fields are shared across all signals — see Schema and Resolution. The fields below are specific to this signal:

Signal-Specific Fields

The data object contains everything unique to this signal type — the intelligence extracted from job posting analysis.

FieldTypeDescription
categorystringHuman-readable department label (e.g., "Hiring Sales Roles"). Maps to the subtype enum. Useful for display in notifications or dashboards
open_roles_countintegerTotal number of open roles in this department right now. Useful for gauging the scale of the hiring push — 5 roles is maintenance, 50+ is a strategic build-out
pct_of_headcountfloatOpen roles as a percentage of current total headcount (e.g., 1.8 = 1.8%). Normalizes hiring intensity across company sizes — a 200-person startup hiring 20 is more aggressive than a 50,000-person enterprise hiring 20. Useful for prioritization
signal_strengthstringHiring intensity classification: high, medium, or low. Derived from open_roles_count relative to company size and department norms. Useful for filtering to the most aggressive hiring surges
sample_titlesarray[string]Up to 5 actual job posting titles that matched this department. Includes seniority, team, and specialization context. Useful for personalizing outreach ("I noticed you're hiring a Regional VP of Sales...")
sample_normalized_titlesarray[string]Cleaned, standardized versions of sample_titles with team/specialization stripped. Useful for programmatic matching against your ICP's role taxonomy
sample_translated_titlesarray[string]Sample titles translated to other languages (typically French, German, Spanish). Present when international postings exist. Useful for identifying global hiring patterns
sample_urlsarray[string]Direct links to up to 5 actual job postings. Useful for research, validation, and as proof points in outreach
top_locationsarray[object]Up to 5 hiring locations sorted by role count. Each entry contains location (city, state, country) and count (roles at that location). Useful for territory routing and identifying new office expansions

Timing & Delivery

  • detected_at is when the hiring threshold was crossed. Job postings are aggregated weekly, so this reflects the scan date rather than individual posting dates.
  • One signal per subtype per company per week. A company hiring across Sales, Engineering, and Marketing will produce three separate signals, but won't fire the same department twice in the same weekly scan.
  • Each delivery arrives in a timestamped folder. Treat all signals in a new folder as recent — no need to diff against prior deliveries.

Coverage

  • Refresh: Weekly
  • Coverage: 21,000,000+ companies globally
  • Best for: SDR/BDR targeting, ABM prioritization, competitive intelligence, identifying companies scaling specific functions

Contact Sales →