CV and interview don’t match? How to clarify the difference
A narrower interview account can reflect vague CV wording, a summary error or a real conflict; clarify which one before recording exaggeration.
· 9 min read

The CV says “led the rollout of our HR system”. In the interview, the applicant describes writing staff instructions and answering questions. Colleagues chose and configured the software.
That is narrower than you expected, but “led the rollout” may have meant leading employee communications. Before writing “possible exaggeration”, find out which responsibility the applicant was claiming.
Compare the original words and clarify the difference that matters to the job. Broad wording needs a more precise account. An error in your summary needs a correction. Two incompatible claims need an explanation and, where material, verification.
What should you do when an interview answer does not match the CV?
Compare the original CV with the original answer. “Led the rollout” leaves the responsibility broad. “I chose the software” makes a specific claim to examine against a later account of who selected it.
Find the source of the disputed claim. The applicant may have said “helped introduce the system” while a recruiter note or AI summary said “set up the system”. In that case, correct the summary before asking the person to defend words they never used.
| What differs? | What to ask or check |
|---|---|
| A broad verb such as led, owned or supported. | Which responsibility was theirs, and how was the work divided? |
| Two dates. | What event does each date describe: selection, joining, launch or another milestone? |
| The applicant and a colleague are both described as making the same decision. | Which decision did they make, and which needed approval? |
| A claim found only in your summary. | Correct it against the original source before asking the applicant to defend it. |
For a People Operations vacancy, employee communications may be the relevant experience. For a systems administrator, you still need configuration evidence. Clarification should make the account more precise, not pressure the applicant into claiming the more senior role.
Questions that clarify what a candidate actually did
Ask how the team divided the work, then follow a problem the candidate describes. This sample exchange shows how the questions can develop:
You: “Which part of the rollout were you responsible for?”
Candidate: “Our People lead chose the system. The administrator set it up. I checked employee details, wrote the launch emails and answered the questions that came back.”
You: “What was one problem employees raised?”
Candidate: “People on shift weren't seeing the announcement. I asked their managers to explain it during handover, then checked who still hadn't activated an account.”
You: “What did you do about the accounts that were still inactive?”
Candidate: “Two employees said they hadn't received an invitation, so I asked the administrator to resend it. Another had the invitation but got an error when opening it. I sent that problem to IT and told the employee I was waiting for an update.”
You now have a specific contribution: the applicant found two missing invitations and a separate access error, then sent each to the appropriate colleague. The original broad claim has become assessable work.
The repair outcome is still unknown. Ask about it only if it matters to the decision. Let the applicant describe what happened; “Was it a login error?” would supply a possible cause.
Distinguish seeking approval from waiting for instructions
“I needed my manager's approval” doesn't necessarily mean “I waited for my manager to tell me what to do.”
Ask “What had you worked out before asking your manager, and what did you need them to decide?” They may have brought a complaint, a diagnosis or a proposed response. Each describes a different contribution.
A person who identified missed announcements and proposed shift briefings may have exercised useful judgement without authority to approve the plan. A person who passed on the complaint may have played a different, legitimate role. Compare that responsibility with the vacancy rather than treating approval authority as a universal measure of seniority.
For the sample exchange, a useful note is: “Checked why accounts remained inactive. Asked the administrator to resend missing invitations and referred a reported access error to IT. Final activation and repair outcomes were not established.”
Mark a question the interview never reached not assessed. An incomplete answer needs a different note describing what is still unclear. Neither justifies claiming that the applicant failed to investigate.
Keep the clarified account accurate in the interview notes
Write the applicant's explanation in the notes before giving your view. For example: “Wrote staff instructions and answered questions; a colleague set up the software.” The next interviewer can then see what you are judging.
Screened provides the interview transcript alongside its summaries and assessment. Use the transcript to check an important responsibility claim, then write the brief in terms the candidate actually used. “Handled the employee rollout” should not become “configured the platform” during the handover.
You can also check your understanding aloud:
“You checked staff details and handled employee communications. Your colleague set up the system, and your People lead chose it. Is that right?”
GitLab's interviewing guidance recommends letting candidates correct the interviewer's understanding. Update the notes when they do.
If the candidate says both “I chose the system” and “I joined after it was selected,” ask about the apparent conflict:
Earlier you described choosing the system, but you also mentioned joining after it was selected. Can you help me understand the sequence?
Let the applicant explain without offering a convenient resolution. In a separate example, they might answer:
I joined after the company chose the software. I compared implementation partners and recommended the one we used. My CV should have said that, not that I selected the system.
That explains the distinction and acknowledges the inaccurate wording. Record both rather than silently treating the original CV as correct. Assess the clarified responsibility against the job; independently verify a material claim through your approved process where needed.
If the account remains incompatible, save the two statements, the explanation offered and the specific fact requiring a check. Repeating the question more forcefully does not establish which account is true.
How do you check achievement percentages on a CV?
First establish what was counted. Account activation is not necessarily completion of onboarding. Ask “What did the report count as complete, and how many people were included?” Then establish the period and whether the figures follow the same employees or compare different groups.
Ask what the applicant changed and what colleagues changed. Reminders, repaired logins and ordinary progress over time could all contribute. “I handled the reminders; IT repaired the login” gives you a clearer account than an unsupported claim to have caused the entire increase.
A reasonable answer is:
“More employees activated their accounts after we changed the messages and fixed the login problems. I handled the messages. I don't know how much of the improvement came from that change alone.”
Example: what does “improved completion by 30%” mean?
Suppose the report counts account activations, which rise from 50 to 65 in a group of 100 employees. That is 15 more activations, or a 30% increase relative to the original 50. It does not establish that all those employees completed onboarding.
The activation rate rose from 50% to 65%: 15 percentage points, not 30 points. Neither description proves the new messages caused the improvement. The figures follow the same employees over time, so ask how much progress was expected anyway and what else helped them finish.
Keep the scope of the role in mind. A junior applicant may know which staff replied and which invitations failed without seeing company-wide results. Ask about those observable checks rather than rewarding the person who supplies the biggest, least-supported percentage.
Choose the next check once the contribution is clear
Once the responsibility is clear, return to the hiring decision. For a communications-focused People Operations job, the employee messaging work may be the relevant evidence. A colleague having configured the software is not automatically another concern to investigate.
Choose any next check for the question still open. Verification can examine a material employment or qualification claim. A writing exercise can show how the person communicates now; it cannot establish who led the historical project.
For the People Operations role, a short writing exercise may be the next useful check. Give the applicant an invented access problem, explain that IT is investigating without a repair time and state that starters will not be penalised for missing the deadline because of the fault. Ask for an employee update.
The response should preserve those facts. “You can log in tomorrow” invents a repair time; “IT knows” omits the reassurance employees need. Agree the time, permitted tools and adjustments beforehand. This tests current writing, not the truth of the earlier project story.
Do not request confidential employer documents as an informal proof test. An applicant declining to share customer files or internal screenshots has not thereby disproved their experience. Explain the information you need and use an appropriate route.
Record the candidate's explanation and the remaining uncertainty precisely. Not remembering an exact number is different from giving incompatible accounts of who made a decision. Leave an unresolved issue unresolved until the evidence supports a firmer conclusion.
Correct the next interviewer's starting point
Correct the brief the next interviewer will read. A clarification buried at the bottom of the notes will not help if the first line still says “possible exaggeration.”
Compare three possible notes:
| Finding | Useful note |
|---|---|
| The broad claim was clarified. | Led employee communications and checked staff details. Software selection and configuration belonged to colleagues. No conflict established on those facts. |
| Your summary overstated the role. | The original answer described coordinating the rollout, not configuring the system. Corrected the brief; configuration experience remains unassessed. |
| A specific conflict remains. | CV states personal responsibility for selecting the system; the interview places selection before the applicant joined. Candidate's explanation recorded; the authorised reviewer is checking the sequence. |
Record any exercise separately from the historical claim: “Produced an accurate employee update without promising a repair time. We have not tested their employee-data checking.” That keeps the work observed today distinct from the experience described in the interview.
End with a precise finding: relevant communications experience, configuration experience still unassessed, or a specific claim awaiting verification. Those lead to different next steps. “Possible exaggeration” leaves the next interviewer with a suspicion instead of a question they can resolve.


