The messy parse can bleed location text into a task item, prepending 'Pune' to one extracted responsibility.

◐ Mixedinput onlyTest date not recordedHrFlow
What was measured
Noise in output

Does it add incorrect or hallucinated fields?

decisive for this rankingtransformation

Incorrect or hallucinated fields mean the resume parser is not producing reliable structured data, which is central to the job. (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
parseur-input3-john-kumar-messyresume-75275a848042.pdf
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.
Provenance
Observation
88d0b110-6c68-48a4-be94-bb032e62ab16
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
observed
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: "hrflow",
  scenario: "resume-parsing"
})
MCP · mcp.aidemos.com/api/mcp
Free with attribution.
Same input, same check — 5 other tools
measured on Noise in output
Real inputs and real outputs, no retouching · every cell queryable via API & MCP · aidemos.com