The parser extracted the basic identity and work-history fields, but it did not fully return the core six-field resume set because skills from the sidebar were missing.
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: Multi-column sidebar resume — Priya Sharma · pdf · group: resume-parsing
Input — what we sent
Multi-column sidebar resume — Priya Sharma
A two-column sidebar resume for Priya Sharma, used to test whether parsers can preserve reading order and correctly extract content split across columns.
Why this input is hard
- · multi-column layout handling
- · sidebar content extraction
- · reading-order robustness
- · projects extraction
- · languages and certifications extraction
Output — unretouched
Also checked on this input — same tool, 3 other criteria
Accuracy✗ FailedThe parser truncated responsibility text mid-sentence on the multi-column resume, cutting off the quantified detail after 'cutting costs by.'Multi-column handling✗ FailedOn the two-column sidebar layout, the parser lost the entire right-side sidebar block, so skills, certifications, and languages were not preserved in reading order.Output quality◐ MixedThe two-column output was only moderately usable: core contact and work-history fields were present, but sidebar skills/certifications/languages, projects, and GPA were missing or poorly handled.
Provenance
- Observation
- 1cf56ab8-34c3-4b84-80ce-c5ee89e1d790
- 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: "skima-ai",
scenario: "resume-parsing"
})MCP · mcp.aidemos.com/api/mcp
Free with attribution.
Same input, same check — 4 other tools
measured on Field coverage
Airparser✓ WorkedCovers the six core fields from a two-column resume, including split-header contact info, work experience, education, and skills.Extracta.ai✓ WorkedCovers the expected resume content from both columns, including work experience, education, skills, certifications, and languages.Hireability✗ FailedSix visible contact fields — GivenName, FamilyName, Email, Phone, LinkedIn, and Address — came back empty on the multi-column resume.LlamaParse✓ WorkedThe multi-column output included the core resume fields and the sidebar-specific sections, including name, email, phone, experience, education, skills, certifications, languages, and projects.
This evidence is published in
Real inputs and real outputs, no retouching · every cell queryable via API & MCP · aidemos.com