The Resume Said “Sales Manager.” The Call Revealed They'd Never Spoken to a Client. How Many of Your Hires Have This Gap?
I want to tell you about a pattern that should make every TA leader uncomfortable.
In production data across thousands of AI-led assessment calls, we kept seeing the same three conflicts emerge. Not occasionally. Consistently. Across roles, cities, and candidate profiles.
But before I share the data, think about your own recent hires.
How many times has a candidate cleared every interview round, accepted the offer, started the job, and then you discovered within the first month that something fundamental was off? The salary expectation was different from what they indicated. They weren't really in the city they claimed. Their "sales experience" was actually internal operations with no client-facing work.
You've seen this. Every TA leader has. And every time, the same question comes up: "How did we miss this?"
You missed it because resumes are marketing documents. Candidates present the best version of their experience. Job titles get inflated. Skills get listed that were used once in a training. Locations reflect aspirations, not current reality. And salary expectations stay hidden until the offer stage, when it's too late and you've invested weeks of recruiter and hiring manager time.
Your current process is designed to discover these conflicts at the worst possible moment: after you've already committed.
Here's what we found when the conversation happened in the first 7 minutes instead of the last interview round.
Salary mismatches. Across candidates who disclosed compensation expectations during the AI assessment call, the vast majority quoted numbers significantly above the role's range. This information would typically surface only during offer negotiation, after weeks of investment. In the first assessment call, it surfaced immediately.
Location gaps. Candidates confirmed during the call that they were in a different city than their resume stated. Some disclosed relocation plans that hadn't been acted on. The resume said one city. The candidate was in another and "planning to move." Without a live conversation, this would have been caught at onboarding. Or worse, after.
Experience inflation. Candidates who listed "sales" described purely operational or internal roles with no client-facing element. The title said one thing. The actual work was something else entirely. A resume parser would have passed them. A keyword matcher would have passed them. A structured conversation with probing caught the gap.
I'm not sharing this to sell you a product. I'm sharing this because this is the hiring leak that nobody measures.
Every mismatch that surfaces late has a cost. Recruiter hours on a candidate who was never going to accept the offer. Hiring manager time in interviews. Scheduling coordination. Weeks of effort on a candidate whose salary expectation was 40% above your range, and you only found out at the offer stage. And the biggest cost of all: the better-fit candidate who was available at the same time but didn't get attention because the pipeline was clogged with candidates who looked right on paper but weren't right in reality.
The resume is not going away. But treating it as the source of truth is costing you more than you think. Every month you delay adding a verification layer to your first-touch process, you're advancing candidates who will fail later and rejecting candidates whose resumes undersold their actual capability.
This is one of the core problems Gia solves. Not by replacing the resume, but by verifying it in the first conversation. Before your recruiters invest a single hour.
