How to verify an AI engineer's GitHub is real
Verifying an AI engineer's GitHub means judging whether the public record — the account, the work published under it, and the identity it asserts — holds together as one person's real output, rather than trusting any single detail on its own.
Sooner or later you will open a profile that looks right and isn't — a portfolio assembled to pass a skim, or an account with a great README and nothing underneath it. Public data can answer part of that question and not all of it. This is the part SensAI answers, and how.
Ajai GeorgeLast updated
How is the legitimacy verdict decided?
A profile is reviewed for whether its public record hangs together as one person's real work. The job is to tell a real engineer with a thin profile apart from a fabricated or AI-generated persona — those two look alike on a surface read, and the difference matters: a quiet engineer with four serious repositories is someone you want to talk to.
The review is deliberately steady rather than creative. The same profile should not read differently depending on the hour.
The outcome gates the rest of the assessment. A profile that does not clear this check cannot present as strong, however well it scores elsewhere.
Common questions about verifying an engineer's GitHub
- How do you verify an AI engineer's GitHub profile is real?
- By reading the public record as a whole rather than trusting any single detail. A profile that looks right in one respect and wrong in three is the case this is built to catch, and no individual indicator decides it on its own.
- Can you tell a fake profile apart from a real engineer with a thin profile?
- That distinction is the specific job of the check. A quiet engineer with four serious repositories and a fabricated persona can look alike on a surface read, and the difference matters enormously — the first is someone worth talking to. The review is framed around telling those two apart rather than around penalising low activity.
- What happens if a candidate applies with a résumé instead of a GitHub profile?
- The check does not run. A résumé carries no public record to read, so there is nothing for this assessment to work from. It is recorded as skipped and displayed that way in the dossier — never silently treated as a pass.
- Does the legitimacy check affect the candidate's score?
- Yes. It gates the rest of the assessment: a profile that does not clear it cannot present as strong, no matter how the other dimensions read. The gate is applied before any score reaches a recruiter.
- Is the interview checked for authenticity as well?
- Where a candidate has completed an interview, their answers are reviewed for signs of an inauthentic response pattern, and the result is attached to the dossier alongside the profile assessment.