Covers the expected resume content from both columns, including work experience, education, skills, certifications, and languages.

✓ Worked🧾 artifact-verifiedinput + output shownTest date not recordedExtracta.ai
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
Input file 1 — as supplied
Research media image.png
Research media image.png
Input file 2 — as supplied
parseur-input2-priya-sharma-multicolumnresume-0e443ffc95c3.pdf
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
research-media-extracta-ai-20output2-c32b71b0b786.txt
Loading file...
Provenance
Observation
9d73e6da-0cca-4520-88b0-d45d6c6882b7
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 — 4 other tools
measured on Field coverage
Real inputs and real outputs, no retouching · every cell queryable via API & MCP · aidemos.com