Separate resume claims from verified public proof.
Candidate-supplied text is parsed into technical claims, then checked against the selected TrueHire fixture profile. The audit labels each claim by evidence coverage, not confidence in the person.
Audit input
fixture evidenceClaim audit
GitHub evidence onlySupported by public evidence, led by ada-the-builder/next-orbit.
No matching public GitHub evidence was found for this resume claim.
Supported by public evidence, led by ada-the-builder/next-orbit.
Some public evidence matched, but coverage is not strong enough to treat the claim as verified.
Supported by public evidence, led by ada-the-builder/next-orbit.
Supported by public evidence, led by ada-the-builder/next-orbit.
Supported by public evidence, led by ada-the-builder/next-orbit.
Supported by public evidence, led by ada-the-builder/next-orbit.
Follow-up queue
Which design tradeoff in your TypeScript work mattered most?
The resume claims Rust; where can we verify that work?
Which design tradeoff in your Frontend product engineering work mattered most?
Can you share a concrete project or PR that proves your Backend/API engineering experience?
Which design tradeoff in your Testing discipline work mattered most?
Evidence trail
Fairness caveats
claim auditResume text is treated as candidate-supplied claims, not proof.
Unverified means public GitHub evidence did not support the claim; it does not prove the candidate lacks the skill.
Do not use absent public work as a proxy for protected attributes, employment constraints, private-repo work, or non-GitHub ecosystems.