DEMO DATAAlex Morgan and all the information shown are fictional. No real candidate was analysed.

Sample report

Sample candidate report

A Verichi report, end to end — Alex Morgan, Senior Software Engineer (sample-cv-alex-morgan.pdf).

See where Alex Morgan's resume, LinkedIn profile and public GitHub work agree, and where they differ. That judgement stays with you.

Language & AI assistance examples

Switch the writing-style example below. Even the most polished example never changes the consistency score.

The resume is formal and the profile is concise. The difference is described plainly and is not treated as a fault.

AI assistance signal
Moderate
Writing style consistency
Low
Generic language
Moderate
Claim specificity
Moderate

Candidates often write differently on a resume and a professional profile. Register differences are supporting context only.

Candidate consistency

Consistency score

ResumeProfileGitHub

Starts at 50. Each finding shows its effect on the score.

Findings
5
Risk warnings
1
Interview questions
3

Area scores

Each area starts at the baseline and applies the same scoring rules to findings tagged for that area.

Employment

46

Starts at 50

  • +6 points. The resume and the LinkedIn information support the same claim, which raises consistency.
  • −10 points. The resume and the LinkedIn information state facts that differ, which lowers consistency. The difference may have an innocent explanation.

Technical

56

Starts at 50

  • +6 points. The resume and the GitHub profile support the same claim, which raises consistency.

Project

50

Starts at 50

No score changes in this area.

Profile consistency

56

Starts at 50

  • +6 points. The resume and the GitHub profile support the same claim, which raises consistency.

Executive summary

Alex Morgan's employment history at Acme Technologies and Northwind Labs aligns across the resume and LinkedIn profile.

End dates at Bright Systems differ by several months between the resume and profile, which is worth confirming during interview.

Python and Kubernetes experience is supported across multiple supplied sources, including public GitHub repositories.

A distributed payments platform leadership claim appears on the resume alone and is worth exploring in conversation.

Employment history

Job titles and dates recorded in each source. Roles appearing in a single source are marked "One source only" and are not treated as inconsistencies.

CompanyResumeLinkedInGitHub
Acme TechnologiesSenior Software Engineer, 2022 to PresentSenior Software Engineer, 2022 to PresentNot shown
Northwind LabsSoftware Engineer, 2019 to 2022Software Engineer, 2019 to 2022Not shown
Bright SystemsBackend Engineer, Jan 2018 to Dec 2018Backend Engineer, 2018 to 2019Not shown
Freelance
One source only
Contract Developer, 2017 to 2018Not shownNot shown

Skills evidence

Skills compared across the resume, LinkedIn information and public GitHub profile. "No public evidence" never changes the score.

SkillResumeLinkedInGitHubConfidence
Python8 years of professional Python backend developmentCore technology: PythonMultiple public Python repositories and service tooling
Strong support
AWSAWS production infrastructure, 5 yearsSkills: AWS, Python, KubernetesNot shown
Strong support
KubernetesKubernetes cluster configuration and service deploymentSkills: AWS, Python, KubernetesInfrastructure manifests in two public Kubernetes repositories
Strong support
GoNot shownNot shownNot shown
No public evidence

Findings

Supported

Claims supported across multiple supplied sources.

  1. Supported

    +6 points. The resume and the LinkedIn information support the same claim, which raises consistency.

    Senior Software Engineer at Acme Technologies since 2022

    Company, title and dates match between the resume and the professional profile.

    • ResumeSenior Software Engineer, Acme Technologies, 2022 to Present
    • LinkedInSenior Software Engineer at Acme Technologies, 2022 to Present
  2. Supported

    +6 points. The resume and the GitHub profile support the same claim, which raises consistency.

    Sustained Python engineering experience

    Both the resume and public GitHub profile show sustained Python work.

    • Resume8 years of professional Python backend development
    • GitHubMultiple public Python repositories and service tooling
  3. Supported

    +6 points. The resume and the GitHub profile support the same claim, which raises consistency.

    Kubernetes infrastructure configuration experience

    Both the resume and public GitHub repositories include Kubernetes manifests.

    • ResumeKubernetes cluster configuration and service deployment
    • GitHubInfrastructure manifests in two public Kubernetes repositories

Differs

Flagged for a conversation, not a conclusion.

  1. Claim

    End date for Backend Engineer role at Bright Systems

    Differs

    Why it was flagged

    The resume and professional profile list end dates several months apart for Bright Systems.

    −10 points. The resume and the LinkedIn information state facts that differ, which lowers consistency. The difference may have an innocent explanation.

    Available evidence

    • ResumeBackend Engineer, Bright Systems, Jan 2018 to Dec 2018
    • LinkedInBackend Engineer at Bright Systems, 2018 to 2019

    Suggested interview question

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

Not evidenced

Present in one supplied source without corroboration elsewhere.

  1. Claim

    Architecture leadership of a distributed payments platform

    Not evidenced

    Why it was flagged

    Only the resume mentions leading a distributed payments platform processing £50m+ annually.

    No effect on the score. Only the resume speaks to this claim, so there is nothing to compare and the score is unchanged. Any missing corroboration appears under risk warnings.

    Available evidence

    • ResumeLed the architecture and development of a distributed payments platform

    Suggested interview question

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

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

Source evidence

SourceSuppliedCharacters readQuotes cited
ResumeYes4,6805
LinkedInYes1,9402
GitHubYes1,1202

Risk warnings

These say what the supplied sources do not show. They do not change the score and are not findings.

  • Only the resume speaks to this claim; no other supplied source confirms or contradicts it.

Language and writing-style signal

A rough, probabilistic estimate based on writing style alone. Many people write this way, and resume templates or editing tools are common. It does not change the score or count as a finding, and it says nothing about whether the candidate is honest.

  • Resume

    Some of the style patterns checked were present.

    • Frequent stock phrases that are common in templated or assisted writing
    • Frequent long dashes
  • LinkedIn

    Few of the style patterns checked were present.

Suggested interview questions

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

    Relates to: Architecture leadership of a distributed payments platform

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

    Relates to: End date for Backend Engineer role at Bright Systems

  3. Which parts of the Kubernetes setup did you own directly?

    Relates to: Kubernetes infrastructure configuration experience

Ask Verichi

Answers come only from this report. Quoted text is evidence. Anything inferred is labelled as inference.

Limitations

  • 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 and does not determine whether a candidate is telling the truth.

Run this on a real candidate.

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

Verify a candidate