Research transparency
Research methodology
How to interpret Pika Resume’s aggregate diagnostic-scan research—and what the data cannot tell you.
Last reviewed: September 12, 2026
Methodology in one sentence
Pika Resume publishes aggregate patterns from successful, self-selected Pika ATS diagnostic scans—not unique people or documents—using the proprietary rubric in effect when each scan ran; the findings do not measure employer ATS decisions, applications, callbacks, interviews, or hires.
Dataset and scope
The State of Resumes report uses aggregate results from successful Pika ATS diagnostic scans. A successful scan is an eligible completed result with a positive 1–100 score that is neither deleted nor watermarked. Zero-score and out-of-range results are excluded. The live report displays the successful-scan count, covered dates, update time, Pika scoring threshold, and minimum sample rule.
The sample is self-selected. It is not designed to represent every job seeker, occupation, country, employer, applicant tracking system, or successful application, and it cannot estimate an employer screening or rejection rate.
Unit of analysis and repeat scans
One eligible successful scan row is one observation. It is not one unique person, resume document, job application, or hiring outcome. Repeat scans and variants of a document or job description may therefore appear more than once in the aggregate count.
For a signed-in user, Pika may reuse a result when the same file and job description are checked again within 24 hours. A later repeat or a changed file or job description can produce another countable scan. The public aggregate does not deduplicate people or documents across the full study period.
Full-history and recent-profile samples
Headline scores, score distributions, and time-series counts use all eligible successful scans. The section-failure and checks-passed profiles use the most recent eligible successful scans, capped at 10,000. The profile is recent and non-random; the sample size printed for each profile or section is its denominator. The checks-passed profile further requires all eight canonical Pika checks.
What the score measures
Pika Resume applies its own diagnostic rubric to parsing and formatting, section structure, contact details, work experience, education, skills and keywords, projects and certifications, impact, grammar, and consistency. The resulting 0–100 score and ATS-ready threshold are Pika Resume product measures—not a score or pass decision returned by an employer or commercial applicant tracking system. You can apply that rubric to your own document with the free ATS resume checker.
Aggregation and privacy
Public findings are reported as aggregates. Resume text, names, contact details, files, and other identifiable content are not published in the report. Rates, averages, and profile cuts below the displayed minimum sample are withheld; time-series scan-volume counts may remain visible below that floor. For data-handling details, read the privacy policy.
Important limitations
- The dataset contains self-selected successful scans, not a random population sample.
- Scan counts can include repeats and are not counts of unique people, documents, or applications.
- A higher Pika score does not prove that an employer will parse, rank, shortlist, or interview a candidate.
- The study does not measure job applications, recruiter decisions, callbacks, interviews, or hires.
- Historical results do not store a comparable scoring-version series. Each score reflects the Pika rubric used when that scan ran, so monthly and quarterly score trends are product telemetry—not evidence that resume quality or the labour market changed.
- Aggregate patterns describe the observed dataset and should not be treated as causal findings.
Questions and reproducibility
For a methodology question, a dated data cut, or a suspected error, email support@pikaresume.com. Include the statistic, the page URL, and how you intend to use it.
See the editorial policy for sourcing standards and the corrections policy for the public error-reporting process.