On 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.
What was measured
Multi-column handling
Does it correctly parse two-column sidebar layouts?
decisive for this rankingtransformation
Many resumes use two-column layouts, and failing on them breaks real-world extraction quality. (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.'Field coverage◐ MixedThe 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.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
- 138b0a76-2a81-4a72-9bb1-a3a5bc425e98
- 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 — 9 other tools
measured on Multi-column handling
Affinda✓ WorkedThe parser preserved the two-column layout well enough to extract left-column work experience and right-sidebar education, certifications, skills, and languages on first upload.Airparser✓ WorkedCorrectly parses the two-column layout, extracting left-column experience and the right-sidebar sections without losing them.CVParserPro✓ WorkedThe two-column sidebar resume was parsed without layout configuration, and content from both columns was retained well enough to extract the sidebar languages and the main work history.Extracta.ai✓ WorkedCorrectly parses a two-column sidebar layout without requiring any layout configuration.Hireability✗ FailedThe two-column sidebar layout was misread as a job-order record, so the parser returned Title, PositionTitle, and MinimumEducationLevel instead of a candidate profile.HrFlow◐ MixedIt can read a two-column/sidebar resume without crashing and pull content from both columns, but the parse is not perfectly layout-stable.LlamaParse✓ WorkedThe parser handled the two-column sidebar layout correctly and preserved content from both columns rather than dropping the right sidebar.OpenResume✗ FailedOn a two-column sidebar resume, it loses reading order in work experience and duplicates 'Software Engineer — ML' into both Company and Job Title.Parseur✓ WorkedThe two-column sidebar resume was parsed correctly after template setup, so the layout did not prevent extraction of the intended fields.
This evidence is published in
Real inputs and real outputs, no retouching · every cell queryable via API & MCP · aidemos.com