What competitor job postings can—and cannot—tell you

A job posting proves that a company publicly advertised a role under stated conditions. A persistent cluster of related roles can support a hypothesis about investment, capability, geography, or go-to-market motion. It does not prove approved headcount, a filled team, product timing, or strategic success.

What this guide covers

• the fields worth collecting from jobs pages;
• the difference between a vacancy and a role cluster;
• a corroboration ladder for stronger hypotheses;
• a review template that preserves alternative explanations.

Capture the role as evidence

Careers pages from companies such as Cursor, Anthropic, OpenAI, and Intercom can change frequently. For a useful record, store:

• job title and function;
• seniority;
• location and remote condition;
• team or product named;
• responsibilities and required capabilities;
• customer, market, regulation, or partner language;
• first and last observed dates;
• posting URL or stable identifier;
• whether the role is new, changed, closed, or reposted.

Do not infer a hire from a removed posting. It may have been filled, paused, canceled, duplicated, or moved to another system.

Separate five signal types

Capability build

Several engineering, product, design, or research roles share a specific capability or product area.

Supported statement: the company is publicly recruiting for that capability.

Unknown: whether the team already exists, the initiative's budget, launch date, and priority.

Go-to-market motion

Clusters in enterprise sales, partnerships, solutions, forward-deployed work, customer success, or a vertical may indicate investment in how the product is sold and implemented.

Unknown: pipeline quality, quota attainment, or whether the motion is new rather than replacement hiring.

Geographic expansion

Multiple roles in a new region, especially across sales, support, legal, and infrastructure, can support an expansion hypothesis.

Unknown: office commitment, market entry timing, and commercial performance.

Governance and readiness

Security, privacy, compliance, reliability, procurement, or government roles can indicate work on enterprise or regulated-market requirements.

Unknown: certification status, control scope, and product availability. Verify those on trust and product sources.

Operating pressure or replacement

Repeated senior roles, reposting, or a sudden large cluster may reflect growth, reorganization, turnover, backlog, or recruiting-process changes. Public jobs alone cannot select the explanation.

Look for clusters, duration, and novelty

One role is weak evidence. Score the pattern:

“Stronger” still means a stronger public investment hypothesis—not proof of the private strategy.

Corroborate before escalating

For a capability hypothesis, inspect:

1. changelog and documentation for shipping movement;
2. homepage and product pages for positioning;
3. pricing for availability or packaging;
4. partner pages for ecosystem motion;
5. trust/security pages for readiness;
6. your customer/deal evidence for market relevance.

For a geographic hypothesis, add legal entity, data-region, language, currency, partner, and local hiring sources where appropriate and lawful.

Avoid five bad conclusions

• “The role disappeared, so it was filled.”
• “Five openings mean five net-new employees.”
• “A vertical salesperson proves a vertical product launch.”
• “A security role proves a certification.”
• “More postings than a competitor means faster growth.”

Different companies use different recruiting systems and disclosure policies. Raw counts are not directly comparable without coverage and persistence controls.

Role-cluster review

# Job signal: [Company] — [cluster]

Observed window:
Primary careers URL:
Stable role IDs captured: yes / no

## Roles
| Title | Function | Location | First seen | Last seen |
|---|---|---|---|---|

## Shared language/capability

## Supported observation
[What the postings directly establish]

## Hypotheses
1.
2.
3.

## Corroboration
- product/changelog:
- pricing/docs:
- partner/trust:

## Unknowns

## Decision to review
Owner:
Decision:
Follow-up date:

Use the EXVIV company directory to identify careers-source coverage and the market map to define a comparable peer set. The monitoring guide explains review states, while Evidence Compare keeps the final record attached to sources.

Related EXVIV research

• Public signals that reveal competitive strategy
• How to read a competitor changelog

Sources and further reading

• Cursor careers
• Anthropic careers
• OpenAI careers
• Intercom careers

Method note

Job postings are public recruiting claims, not employee records. Do not collect applicant personal data or infer protected characteristics. Preserve alternative explanations and require cross-source evidence before making a strategic conclusion.