Technical screening
Technical candidate screening, backed by public evidence.
Verichi compares the languages, frameworks and projects a candidate claims with the public evidence available, so technical hiring teams know what to probe in the interview.
- Claimed technologies matched against public repositories
- Project depth and recency summarized for reviewers
- Missing GitHub never reduces a candidate's score
- Interview questions written for technical interviewers
Built for technical hiring teams
Engineering managers and technical interviewers get a concise view of which claims have supporting public evidence and which are worth a deeper conversation.
GitHub is optional
Plenty of excellent engineers have no public code. Absence of public evidence is recorded as unknown, never as a negative signal, and never affects the score.
Only public information
Verichi reads public profile and repository data only — languages, descriptions, topics, activity dates. No private data, no scraping.
Questions that earn their slot
Each report suggests specific technical questions drawn from the candidate's highest-value claims, so interview time goes further.
Responsible by design
Built with responsible hiring in mind.
Human-in-the-loop
Verichi provides information to support human decision-making. It does not automatically reject candidates.
Evidence-based
Verichi distinguishes between a contradiction and simply having no public evidence.
Transparent
Reports explain why something was flagged.
Privacy-conscious
Only the information necessary for the verification process is used.
Verichi is a decision-support tool. It should not be used as the sole basis for employment decisions. Verichi does not assess candidates on race, gender, age, nationality, religion, disability, sexual orientation or any other protected characteristic, and does not infer them.
Don't just read the CV. Corroborate it.
Walk into the technical interview knowing which claims are supported and which need exploring.