Cloud-ID Verified Hiring: Government-ID Identity Plus a Portable AI Interview

What is Cloud-ID verified hiring?

Cloud-ID is CloudHire's verified candidate identity: each Cloud-ID candidate has had their identity verified against a government ID, Aadhaar or PAN in India and an equivalent government ID in other countries, and carries a recorded, AI-scored interview that travels with them between job applications. For businesses, that means every Cloud-ID candidate in a CloudHire search or pipeline is a real, identified person whose interview you can watch before you ever schedule a call. Verified candidates are badged and boosted in CloudHire's rankings, and a single profile pane shows the ID verification, work history, resume, interview video, and score breakdown together.

This guide explains the problem Cloud-ID exists to solve, exactly what is verified today, what is in beta, and what is planned. It is part of the For Businesses guide hub; the product itself is detailed on the Cloud-ID page.

The fake-candidate problem, and why India feels it first

Candidate fraud is no longer an edge case. Remote hiring made it profitable, and generative AI made it cheap. The common patterns every high-volume recruiting team now sees:

• Proxy interviews, where a skilled stand-in takes the technical interview and a different, weaker person shows up on day one
• Fabricated resumes, with invented employers, inflated titles, and years of experience that never happened
• Bait-and-switch onboarding, where the person who joins is not the person who was assessed
• Duplicate and synthetic identities applying to the same role under different names

The India market feels this most acutely. Application volumes are enormous, a single posting can draw thousands of applicants within days, and organized proxy-interview services openly advertise their pass rates. For IT services, BPO, and high-volume sales hiring, teams routinely discover post-offer that the assessed candidate and the joining candidate are different people. Each bad hire costs the salary spent, the seat blocked, the client escalation, and the restarted search. Verification-after-offer is too late; the check has to happen where sourcing and screening happen. That is the design premise of Cloud-ID, and of CloudHire's broader candidate verification stack.

What a Cloud-ID verifies today

Government-ID identity check

The foundation is identity. In India, the candidate's identity is verified against Aadhaar or PAN; elsewhere, against a government-issued ID for their country. This anchors the profile to a real, unique person, which is precisely what a fabricated or duplicate identity cannot supply.

A recorded, scored AI interview the candidate carries with them

On top of identity sits evidence of ability: a recorded AI interview, scored by CloudHire with written reasoning, that belongs to the candidate and moves with them between job applications. Because the interview is recorded under proctoring and attached to a verified identity, it does two jobs at once. It proves the person can actually speak to their claimed experience, and it proves the person speaking is the person the government ID identifies. The interview experience itself, including languages, proctoring checks, and scorecards, is covered in the AI interviews and proctoring guide.

Portability is the quiet advantage for employers. A candidate who verified last month does not need to be re-verified for your role, so your pipeline starts with the trust work already done, and candidates face less repeated friction, which improves response rates to your outreach.

The Cloud-ID profile pane: everything in one drawer

Verification only saves time if you do not have to hunt for it. CloudHire puts the entire evidence trail in a single profile drawer that opens from any candidate row:

• The verified marker confirming the government-ID check
• Work experience with company logos for fast visual scanning
• The candidate's resume
• The interview video with its AI analysis, watchable inline
• Your team's notes on the candidate
• The full ATS score breakdown against your job

A screening decision that used to require an ATS tab, a video platform, a notes doc, and a scoring spreadsheet happens in one pane. The scoring model behind the breakdown is described on the candidate scoring page.

Cloud-ID in search: badges, boosts, and the verified-only filter

Cloud-ID is wired directly into CloudHire's sourcing engine. Search results blend verified and unverified candidates into one ranked list, with Cloud-ID candidates boosted upward; every verified candidate shows a badge on their row; and a "Cloud-ID only" filter restricts results to verified profiles when identity assurance is non-negotiable. You never lose sight of the wider market, you simply see the proven part of it first. How those searches are built, across plain-English, JD-paste, boolean, and manual modes over a 700M+ profile index, is covered in the AI candidate sourcing guide.

In beta: per-job interview policy

Currently in beta, CloudHire lets you set an interview policy per job: accept a candidate's existing Cloud-ID interview, or require a fresh interview taken specifically for this job. Accepting the portable interview minimizes candidate friction and gets you to a shortlist faster; requiring your own guarantees the answers address your exact role and that the recording is recent. Teams typically accept portable interviews for volume roles and require fresh ones for senior or client-facing positions. Because the feature is in beta, expect refinements as it hardens toward general availability.

On the roadmap: provenance and the four-layer Blue Tick

Two Cloud-ID extensions are planned but not yet live, and it is worth being explicit about their status.

Interview provenance display

Provenance will show exactly where a candidate's interview came from: when it was recorded, for which job, and under which policy, so a reviewer can weigh a six-month-old portable interview differently from one recorded yesterday for this exact role.

Four-layer verification and the Blue Tick

The planned top tier stacks four verification layers: education verification, employment confirmed by a named referrer, government ID, and a formal attestation. Candidates who clear all four earn a Blue Tick with a 12-month expiry, so the badge always reflects a recent check rather than a one-time event from years ago.

Why binding identity to the interview is the point

Most verification products check documents. Most interview products assess skills. Fraud lives in the gap between them: a real ID attached to a proxy's interview, or a genuine interview attached to a fabricated resume. Cloud-ID's design closes that gap by binding a government-verified identity to a proctored, recorded, scored interview inside one profile. A proxy service can fake one link in that chain; faking all of them, on camera, against a government identifier, is a different proposition entirely. For markets like India where proxy interviewing is an industry, that binding, not any single check, is the defense.

If you are evaluating CloudHire against incumbent databases in that market, the CloudHire vs Naukri RMS comparison looks specifically at what verification changes about shortlist quality.

What verified hiring changes in practice

The measurable effects show up at three points in the funnel:

• At sourcing, the verified boost and Cloud-ID filter mean the first page of results is already the trustworthy page, so less recruiter time goes to profiles that fall apart on first contact
• At screening, a portable recorded interview replaces the first phone screen for many candidates; you watch a scored answer instead of scheduling a call to hear one
• At offer, the identity established at the top of the funnel is the same identity joining on day one, which is where bait-and-switch losses used to surface

None of this requires changing your process wholesale. Verification rides along inside the same search, pipeline, and interview flow the rest of CloudHire runs, so adopting it is a filter toggle and a policy setting, not a migration.

Getting started with verified hiring

The practical path is simple: source with the Cloud-ID boost on by default, switch to the verified-only filter for roles where identity risk is highest, set your per-job interview policy, and make the profile pane your single screening surface. Case studies from teams running this workflow are on the case studies page. To see Cloud-ID against your own open roles, contact the CloudHire sales team for a live walkthrough.