"Led a team of 10": how to check a team-size claim

Two claims, not one

"Led a team of ten" asserts a number and a relationship, and they fail independently. The number can be right while the relationship is looser than it sounds: ten people worked on the project, one of whom ran standups. The relationship can be right while the number is generous: three direct reports, plus contractors, plus a designer who was matrixed in for a quarter, rounded up.

Separating them changes the question from "is this true" to two answerable ones. How many people were on this team? What was this person's relation to them? Each has its own evidence, and a reviewer who keeps them apart avoids the usual failure, which is discounting a real leadership role because the headcount was soft.

Where a team's size shows up in public

Teams leave a footprint when they ship. Launch and release posts thank contributors by name. Org, about and team pages list who was in a group at a given time, and earlier versions of those pages are often archived; the Wayback Machine's captures of those same pages are the record once the live page has moved on, and how to pull an old snapshot walks through doing that for a title or a start date. Conference talks carry bios and speaker affiliations. Job postings from that period describe the team being hired into, often with its size. Published org charts, annual reports and grant or funding announcements name reporting lines. For technical teams the repository is a census in itself: the people who committed to a project in a date range are countable.

Counting is inexact. A footprint captures the people who were visible, not everyone who was on the payroll, so treat it as a floor and a shape rather than a headcount.

"Led" against "was on"

Evidence for the relationship is different in kind. Look for the verbs other people used: who is described as the lead, the owner, the manager, the point of contact; who is thanked and who does the thanking; who answers on the mailing list; who signs the release; whose name is on the internal document that leaked into a blog post. A single source calling someone "the lead on payments" is worth more than any number of sources confirming they worked on payments.

Write the supported wording, and let silence stay silent

The result to record is a sentence, not a score: "public sources place five named engineers on this project and describe the candidate as its technical lead" tells a hiring panel exactly what it is weighing. Where nothing is public — most teams inside most companies are not public — the finding is unverified, and it must not tilt the decision. Private work is the normal case, not a warning sign, and an evidence-first process that penalizes the absence of evidence is not evidence-first. How to tell if a résumé is exaggerated sets out the same comparison for other kinds of claim.

If a vendor or a third party assembles this check for you, the result is generally a consumer report, and the notice and dispute duties described in what the FCRA requires when a claim fails apply.