On the messy resume, it keeps the main contact/work/education structure but misses the soft-skill section and certification entries.
What was measured
Accuracy
Are extracted values correct and complete?
decisive for this rankingtransformation
Correct and complete values are the essence of resume parsing, so this directly determines whether the tool succeeds. (3 of 3 judges)
What was given, what came back
Test input: Messy real-world resume — John Kumar · pdf · group: resume-parsing
Input — what we sent
A poorly formatted, inconsistent real-world resume for John Kumar, used to test robustness against noisy structure, inconsistent dates, and mixed-content sections.
Why this input is hard
- · messy formatting robustness
- · section detection fallback
- · inconsistent date parsing
- · soft-skills extraction
- · noise and hallucination control
Output — unretouched
No output artifact
The verdict rests on the tester's written observation alone — no file was captured for this cell.
Also checked on this input — same tool, 4 other criteria
Field coverage✓ WorkedEven on the messy resume, it still returns the standard contact, experience, education, and technical-skills sections.Messy resume handling◐ MixedIt parses a poorly formatted resume without crashing, but degrades by dropping soft skills, omitting certifications, and losing most task bullets.Noise in output◐ MixedThe messy parse can bleed location text into a task item, prepending 'Pune' to one extracted responsibility.Output quality◐ MixedThe messy-resume output is moderate overall: contact and basic structure survive, but the result is incomplete for soft skills, certifications, and task detail.
Provenance
- Observation
- 979b5f53-2a09-4a4a-9bc1-e6cf8836f843
- Evidence run
- cbbef4db-964c-49fa-a57f-a2977822bdfc
- Study
- Parse resumes into structured data using an API
- Research task
- 86b9jm30n
- Tested at
- not recorded
- Source
- first-party
- Evidence state
- observed
- Proof shown
- input only
- Cost / latency
- not captured
- Repeat run
- not captured
- Tester
- not captured
The last three rows are honest blanks, not placeholders — our capture has no field for them yet.
Query this
get_evidence({
tool: "hrflow",
scenario: "resume-parsing"
})MCP · mcp.aidemos.com/api/mcp
Free with attribution.
Same input, same check — 8 other tools
measured on Accuracy
Affinda✗ FailedIts total experience calculation overstates tenure: it returned 7.3 years even though the resume explicitly says 3 years of experience.Airparser◐ MixedLeaves one education marks value as raw text ("72 percent marks") instead of normalizing it to the percentage form used by the other entries.CVParserPro✗ FailedThe education end date was wrong: a completed program was rendered as ending in Present.Extracta.ai◐ MixedReturns both certification names in lowercase exactly as written, with no capitalization normalisation applied.Hireability✗ FailedThe second employer name was merged with the role title, returning 'Junior Developer XYZ InfoTech' instead of just 'XYZ InfoTech'.LlamaParse◐ MixedOne messy-resume education entry preserved the source phrase "72 percent marks" instead of normalizing it to a numeric percentage, while the other grades were captured as 67% and 81%.OpenResume✗ FailedWork experience mapping fails by putting a project bullet into Company and leaving Job Title empty.Parseur✗ FailedThe education CGPA value was wrong: the tool returned 67, which the report says is the percentage score rather than the actual CGPA.
This evidence is published in
Real inputs and real outputs, no retouching · every cell queryable via API & MCP · aidemos.com