Still covers the main resume fields on the messy input: name, email, phone, experience, education, skills, and certifications.
What was measured
Field coverage
Are name, email, phone, experience, education, and skills extracted?
decisive for this rankingtransformation
A resume parser should extract the key canonical fields; missing them means it is not doing the main job well. (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
Research media screenshot 202026 05 05 20124544.png
Messy real-world resume — John Kumar
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
Also checked on this input — same tool, 5 other criteria
Accuracy◐ MixedPreserves the education marks text verbatim, including the unnormalised '72 percent marks' value instead of converting it to a cleaner percentage format.Accuracy◐ MixedReturns both certification names in lowercase exactly as written, with no capitalization normalisation applied.Messy resume handling✓ WorkedHandles the noisy, inconsistent layout without crashing and still extracts the main sections.Noise in output⚠ StruggledEmits a blank Languages item when the resume has no languages section, leaving an empty placeholder instead of omitting the field.Output quality✓ WorkedProduces a usable JSON result even on the messy resume, with the important sections still readable and structured.
Provenance
- Observation
- d85153f5-b16a-4009-9e33-65440ad1a387
- 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
- verified
- Proof shown
- input + output shown
- 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: "extracta-labs",
scenario: "resume-parsing"
})MCP · mcp.aidemos.com/api/mcp
Free with attribution.
Same input, same check — 7 other tools
measured on Field coverage
Affinda◐ MixedIt extracted one certification but silently dropped the AWS Basics Coursera 2022 certificate, so the certification coverage was incomplete on the messy resume.Airparser✓ WorkedCovers the six core fields even on messy formatting, including contact info, work experience, education, and skills.Hireability✗ FailedOnly the B.E. education entry was extracted; the visible 12th and 10th entries were omitted from the parsed output.HrFlow✓ WorkedEven on the messy resume, it still returns the standard contact, experience, education, and technical-skills sections.LlamaParse✓ WorkedThe messy-resume output included the core fields and additional sections: name, contact information, objective, work experience, education, skills, certifications, hobbies, and references.Parseur⚠ StruggledOnly one education record was extracted, and the 12th Science and 10th std entries were omitted from the output.Skima AI✓ WorkedEven on the messy resume, the parser still returned the core coverage set of name, email, phone, work experience, education, and skills.
This evidence is published in
Real inputs and real outputs, no retouching · every cell queryable via API & MCP · aidemos.com