Sample report

A Verichi report, end to end.

Every detail below is fictional and used only to demonstrate the format.

DEMO DATAA fictional candidate used to demonstrate the report. No real candidate information.

Alex Morgan

Senior Software Engineer

CVProfileGitHub
Employment history96%
Technical experience82%
Project evidence76%
Profile consistency91%
84/ 100

Generally consistent

Executive summary

Alex Morgan's employment history is broadly consistent across the supplied sources. Python and AWS experience is supported by multiple sources. One significant architecture leadership claim has limited publicly available evidence and may be worth exploring during interview.

Employment history

CV compared against the supplied professional profile.

CompanyTitleCVProfileStatus
Acme TechnologiesSenior Software Engineer2022 – Present2022 – PresentMatches

Company, title and dates align across both sources.

Northwind LabsSoftware Engineer2019 – 20222019 – 2022Matches

Consistent across sources.

Bright SystemsBackend EngineerJan 2018 – Dec 20182018 – 2019Difference

End dates differ by several months. Often a rounding difference — worth a quick confirmation.

FreelanceContract developer2017 – 2018Not listedNot listed in one source

Present on the CV only. Not listed on the professional profile — this is common and is not treated as a discrepancy.

Technical experience

Missing public GitHub activity is recorded as an absence of evidence, never as evidence against a claim.

SkillCVProfileGitHubConfidence
Python8 yearsListed as a core technologyMultiple public Python repositoriesStrong support

Consistent across all three supplied sources.

AWSListed, 5 yearsListedNo public evidenceSupported by sources

No additional public evidence available. Absence of public repositories is not evidence against the claim.

KubernetesListedListedInfrastructure manifests in two repositoriesStrong support

Public repositories include Kubernetes configuration.

GoNot listedListedOne small public repositoryNo public evidence

Listed on the profile but not on the CV. Minor difference in emphasis rather than a contradiction.

Claims supported by available evidence

  • Eight years of professional Python experience.

    Employment dates on the CV and profile support the timeline, and public repositories show sustained Python activity.

  • Senior Software Engineer at Acme Technologies since 2022.

    Title, company and dates match between the CV and the professional profile.

Claims worth a closer look

Flagged for a conversation, not a conclusion.

Claim

Led the architecture and development of a distributed payments platform processing £50m+ annually.

Why it was flagged

Highly specific senior-level claim with limited corroborating evidence across the supplied sources.

Available evidence

CV
Present
Profile
Not mentioned
GitHub
No relevant public evidence identified

Suggested interview question

Can you walk me through the architecture of the payments platform, including the main services, data flows and scaling challenges?

Claim

Designed a distributed system processing millions of transactions per day.

Why it was flagged

Scale-based claim that is difficult to corroborate from the supplied sources and overlaps with the payments platform claim.

Available evidence

CV
Present
Profile
Not mentioned
GitHub
No relevant public evidence identified

Suggested interview question

Can you describe the system architecture, the biggest scaling bottleneck you encountered and how you solved it?

Claim

Backend Engineer at Bright Systems, Jan 2018 – Dec 2018.

Why it was flagged

End date differs from the professional profile by several months.

Available evidence

CV
Jan 2018 – Dec 2018
Profile
2018 – 2019
GitHub
Not applicable

Suggested interview question

Could you confirm the exact start and end dates of your time at Bright Systems?

Limited public evidence does not mean the claim is false. Many roles produce no public record at all.

Suggested interview questions

Based on the candidate's highest-value claims.

  1. 1Can you walk me through the architecture of the payments platform, including the main services, data flows and scaling challenges?
  2. 2What was the biggest scaling bottleneck you hit, and how did you diagnose it?
  3. 3How have you used AWS day to day in your most recent role?
  4. 4Which parts of the Kubernetes setup did you own directly?
  5. 5Could you confirm the exact dates of your time at Bright Systems?

Ask Verichi

Answers come only from this report, and separate evidence from inference.

Ask Verichi is available on your own candidate reports. Sign in and run an analysis to use it.

Limitations of this analysis

  • Analysis is based only on the sources supplied by the hiring team.
  • Absence of public GitHub activity is not evidence against a claim — many experienced engineers work entirely in private repositories.
  • Verichi is a decision-support tool. It does not determine whether a candidate is telling the truth.

Run this on a real candidate.

Upload a CV, add a profile and a GitHub username, and get the same report in about a minute.

Verify a candidate