The messy-resume output was the richest and cleanest among the tested tools, with all 3 education entries, all 14 skills, both certifications, hobbies, and a boolean references field.
What was measured
Output quality
Is the parsed result clean, complete, and usable overall?
decisive for this rankingtransformation
The whole point is usable structured extraction; clean, complete, usable output is the core measure of success. (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 image.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, 4 other criteria
Accuracy✓ WorkedOn the messy resume, the name, email, phone, location, and objective statement were extracted correctly.Accuracy◐ 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%.Field coverage✓ WorkedThe messy-resume output included the core fields and additional sections: name, contact information, objective, work experience, education, skills, certifications, hobbies, and references.Messy resume handling✓ WorkedThe parser degraded gracefully on the messy resume, handling missing section headers and mixed date formats while still producing structured output.
Provenance
- Observation
- c2f3f2c8-8c18-40fc-8445-b9e12f157210
- 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: "llamaparse",
scenario: "resume-parsing"
})MCP · mcp.aidemos.com/api/mcp
Free with attribution.
Same input, same check — 5 other tools
measured on Output quality
Airparser◐ MixedProduces usable JSON from noisy text, but the skills section collapses into one long string and one education record keeps an unnormalized marks value.Extracta.ai✓ WorkedProduces a usable JSON result even on the messy resume, with the important sections still readable and structured.HrFlow◐ MixedThe messy-resume output is moderate overall: contact and basic structure survive, but the result is incomplete for soft skills, certifications, and task detail.Parseur⚠ StruggledSkills were returned as one unstructured, space-separated string with no array structure or delimiters, making them hard to split programmatically.Skima AI⚠ StruggledThe messy-resume output degraded sharply: responsibilities became a run-on string, skills collapsed into one concatenated line, and references/certifications/hobbies were missing.
This evidence is published in
Real inputs and real outputs, no retouching · every cell queryable via API & MCP · aidemos.com