Sample report
Every detail below is fictional and used only to demonstrate the format.
Switch the writing-style example used in the report section below. Note that even the most polished example is never labelled dishonest, and the consistency score never changes.
The CV is formal and the profile is concise. The difference is described plainly and is explicitly not treated as evidence of dishonesty.
Senior Software Engineer
Generally consistent
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.
CV compared against the supplied professional profile.
| Company | Title | CV | Profile | Status |
|---|---|---|---|---|
| Acme Technologies | Senior Software Engineer | 2022 – Present | 2022 – Present | Matches Company, title and dates align across both sources. |
| Northwind Labs | Software Engineer | 2019 – 2022 | 2019 – 2022 | Matches Consistent across sources. |
| Bright Systems | Backend Engineer | Jan 2018 – Dec 2018 | 2018 – 2019 | Difference End dates differ by several months. Often a rounding difference — worth a quick confirmation. |
| Freelance | Contract developer | 2017 – 2018 | Not listed | Not 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. |
Missing public GitHub activity is recorded as an absence of evidence, never as evidence against a claim.
| Skill | CV | Profile | GitHub | Confidence |
|---|---|---|---|---|
| Python | 8 years | Listed as a core technology | Multiple public Python repositories | Strong support Consistent across all three supplied sources. |
| AWS | Listed, 5 years | Listed | No public evidence | Supported by sources No additional public evidence available. Absence of public repositories is not evidence against the claim. |
| Kubernetes | Listed | Listed | Infrastructure manifests in two repositories | Strong support Public repositories include Kubernetes configuration. |
| Go | Not listed | Listed | One small public repository | No public evidence Listed on the profile but not on the CV. Minor difference in emphasis rather than a contradiction. |
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.
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
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
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
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.
A probabilistic signal describing observable writing characteristics. Supporting context for a conversation — it has no effect on the consistency score.
AI assistance signal
ModerateThe CV is consistently polished with several formulaic achievement statements, while the profile text is far more concise. Taken together these are characteristics worth reviewing rather than an indication of AI use.
Writing style consistency
LowThe professional profile uses a noticeably more informal and concise writing style than the CV.
Generic language
ModerateThe CV uses broad business phrasing in places, while the profile describes the same work in plainer, more specific terms.
Claim specificity
ModerateThe profile supplies concrete detail that the CV states only in general terms.
Register differs between sources
CV bullet points average 19 words in formal third-person phrasing; profile entries average 8 words in first person.
Same work, different specificity
The CV describes “transformative platform modernisation”; the profile names the two services migrated and the database involved.
“Delivered transformative platform modernisation across the organization.”
Broad claim with no named system, scope or measurable outcome in the CV.
Stronger with: The specific services involved, which the profile already names.
Candidates often write differently on a CV and a professional profile. A difference is not evidence of dishonesty.
| Dimension | CV | Profile | Note |
|---|---|---|---|
| Tone and formality | Formal, polished, third person | Informal, first person | A common and legitimate difference between a CV and a professional profile. |
| Specificity | General business outcomes | Named services and databases | The profile is the more specific source here, which supports rather than undermines the claims. |
“Delivered transformative platform modernisation across the organization.”
The scope and the candidate's individual contribution are not stated.
“Which parts of the modernisation did you personally deliver, and what changed as a result?”
AI-assisted writing cannot be reliably established from text alone. This analysis identifies linguistic patterns that may warrant further review; it does not determine authorship, dishonesty or fraud.
Based on the candidate's highest-value claims.
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.
Upload a CV, add a profile and a GitHub username, and get the same report in about a minute.
Verify a candidate