Guide
Read Job Postings as Evidence of a Question Worth Asking
Track changes in role descriptions without treating advertised positions as confirmed hires, team size or a guaranteed product roadmap.
What can a job posting tell a reporter?
A job posting documents what an employer publicly says it is seeking at a particular time. Its responsibilities, required experience and reporting relationships can suggest questions about how an organization operates. It does not prove that the role was filled, that the budget remains approved or that a listed project will ship.
Start with the employer's own careers page and preserve the dated listing. Aggregators can help discovery, but duplicates and older copies complicate comparisons. Use the job identifier when available; a changed title alone does not necessarily identify a new role.
Track descriptions, not just counts
Raw counts are easy to overread. One role can appear in several locations, listings can be refreshed, and a removed page may mean many things. Define what you count and retain enough information to reproduce it.
| Tracking field | Why it matters |
|---|---|
| Employer and source URL | Establish whose description this is |
| Job identifier and title | Match versions and reduce duplicates |
| First and last observed dates | Describe your observation window honestly |
| Location and employment type | Avoid collapsing different arrangements |
| Responsibilities and requirements | Identify the specific language of interest |
| Changed passage | Separate an actual revision from a new interpretation |
| Confirmation needed | Ask whether the role and described work are current |
“First observed” is safer than “posted” when you do not have a reliable posting date. A disappearance is an observation, not evidence of a hiring freeze. Respect access restrictions and site terms when collecting listings.
Ask about the operating problem
Suppose a hypothetical logistics company advertises a role focused on reconciling warehouse data across acquired businesses. That supports a question about integration work. It does not establish that an acquisition failed or that a new data product is imminent.
Compare the wording with company disclosures and earlier descriptions. Ask the company what the role is intended to do and whether the responsibilities describe new work. Interview an independent operator about the general challenges, clearly separating their experience from knowledge of this company.
A useful article might explain why post-acquisition reporting needs consistent definitions, using the listing as a documented starting point and other evidence for the substantive explanation. Avoid assigning undisclosed strategy to an employer from a few keywords.
Keep an evidence threshold for publication
Publish a narrow observation when the wording itself matters and you can show it in context. Hold a larger strategic claim until corroboration exists. If you cannot establish whether two listings represent distinct positions, do not add them together as confirmed headcount.
Pair the posting log with earnings-call questions or a human-source interview. Each source should do the job it can support, rather than lend borrowed certainty to the others.
Keep reading