On the poorly formatted resume, the parser still recovered the main structure instead of failing outright, including contact data, experience, education, skills, and hobbies.
What was measured
Messy resume handling
Does it degrade gracefully on poorly formatted input?
decisive for this rankingtransformation
Resumes are often inconsistent or poorly formatted, so graceful handling of messy input is a core capability. (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
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
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, 3 other criteria
Accuracy✗ FailedThe second employer name was merged with the role title, returning 'Junior Developer XYZ InfoTech' instead of just 'XYZ InfoTech'.Field coverage✗ FailedOnly the B.E. education entry was extracted; the visible 12th and 10th entries were omitted from the parsed output.Noise in output✗ FailedThe certification field merged three content types — certifications, skills, and references — into one extracted value instead of separating them.
Provenance
- Observation
- e8f31662-b9b9-4b8e-8b89-b56d3b4f574d
- 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 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: "hireability",
scenario: "resume-parsing"
})MCP · mcp.aidemos.com/api/mcp
Free with attribution.
Same input, same check — 9 other tools
measured on Messy resume handling
Affinda✓ WorkedThe parser handled the messy resume gracefully, still extracting the main identity, work history, education entries, skills, objective, and hobbies despite non-standard dates and raw dash-style bullets.Airparser◐ MixedParses a poorly formatted resume, but degrades into non-machine-readable skill output rather than a structured array.CVParserPro⚠ StruggledOn the messy resume, the parser collapsed the education section to 1 extracted entry and dropped the 10th- and 12th-standard records.Extracta.ai✓ WorkedHandles the noisy, inconsistent layout without crashing and still extracts the main sections.HrFlow◐ MixedIt parses a poorly formatted resume without crashing, but degrades by dropping soft skills, omitting certifications, and losing most task bullets.LlamaParse✓ WorkedThe parser degraded gracefully on the messy resume, handling missing section headers and mixed date formats while still producing structured output.OpenResume✗ FailedOn a poorly formatted resume without bold uppercase section headers, the parser degrades badly: core sections are misassigned or empty instead of being recovered gracefully.Parseur✓ WorkedThe parser still accepted a highly inconsistent resume with missing headers and mixed date formats, and it continued parsing through the messy structure.Skima AI⚠ StruggledThe tool accepted the messy file, but it degraded badly in structure by merging bullets into a run-on responsibility line instead of preserving clean formatting.
This evidence is published in
Real inputs and real outputs, no retouching · every cell queryable via API & MCP · aidemos.com