Is exaggerating on your CV illegal? Where the line is

What did the Elizabeth Holmes documentary change about CV honesty?

Nothing about the law changed when "You Can See Everything" opened — but the conversation did. The Elizabeth Holmes documentary has just posted one of the biggest opening weekends a documentary has ever had, and for the past few days the internet has been arguing about where confident storytelling ends and fraud begins. Holmes was convicted of defrauding investors over claims her blood-testing technology couldn't support. That's a corporate fraud case, not a CV case. But the question the film has dropped into group chats and LinkedIn feeds is precisely the one job seekers ask quietly: how much can I inflate before it counts as lying?

The reason the comparison lands is that the mechanism is the same, only the stakes differ. A claim is made to obtain something of value. The claim outruns the evidence. Then somebody asks a follow-up question and the gap shows. On a CV, that moment is small and survivable right up until it isn't — a hiring manager asking "walk me through how you got that 40%" is doing the same work as a journalist asking to see the machine run. Nobody sends you to prison for a padded bullet point. They just stop the process, and you never find out why.

Here's the bridge for anyone actually job hunting this month. Your CV is a set of claims made to obtain a salary, a title, sometimes a visa — and most people genuinely can't see what theirs claims, because they built it in pieces over eight years. That's the gap worth closing before a recruiter closes it for you. A free CV analysis scores impact and ownership alongside clarity and structure, experience, tech stack and ATS compatibility, which shows you where the document makes a loud noise with nothing underneath it. Strong and verifiable beats inflated every time, and it usually reads better too.

Is exaggerating on your CV illegal?

In most cases, no — padding a CV is not a crime in itself in the US, the UK, India or Israel. It crosses into illegality in four specific situations: you forge a document (a degree certificate, a payslip, a reference letter); you claim a regulated licence you don't hold, such as nursing registration, a medical or legal practising certificate, or a trade ticket; you make a false statement on a government or federal employment form, which is a federal crime in the US; or your false representation is used to obtain money or property, which is fraud by false representation under the UK's Fraud Act 2006, carrying a maximum of ten years.

The far more common consequence is commercial, and it arrives much faster. Offers get rescinded during screening with no explanation. Employees get dismissed for misrepresentation, sometimes years in, because CV fraud is treated as a breach of trust rather than a performance issue — and "dismissed for falsifying your application" is a sentence that follows you through every future reference call. In India, where background verification is a standard step before joining, a discrepancy flagged by the screening vendor can get your candidature withdrawn after you've already resigned from your current job. That timing is what ruins people, not courtrooms.

So use a stricter line than the legal one, because the legal line is the wrong tool. My test has three questions: Is this sentence literally true as written? Could a named third party — a former manager, a registrar, a dashboard, an invoice — confirm it? Would I say it unchanged to the person who actually managed that work? If a bullet fails any one of those, it isn't strong framing, it's exposure. And here's the contrarian half: most CVs I see fail in the opposite direction. They lie by omission, burying genuine ownership under vague verbs because the writer was afraid of sounding boastful. Underselling costs more interviews than overselling.

Which CV claims actually get verified?

Four things get verified against records: employment dates, job titles, degrees and professional licences. Everything else — your metrics, your tool fluency, your described scope — gets tested in conversation rather than documented. That split should drive how you write. Hard-verified claims need to be exactly right, down to the month, because a screening report that shows "candidate stated Senior Analyst, employer confirmed Analyst" reads as a lie even when you were doing the senior work. Soft-tested claims need to be defensible, meaning you can explain the method, the baseline and your own contribution without reaching for a number you invented to fill the line.

How that verification happens varies by market, and it pays to know yours. In India, pre-joining background verification is near-universal for corporate and IT roles: expect your offer letters, relieving letters and salary documents to be checked, and your employment history to be cross-referenced against provident fund records tied to your UAN. In the UK and US, previous employers often confirm only dates, title and sometimes eligibility for rehire — which is why hiring teams lean on backchannel references instead. In Israeli hi-tech, where one or two mutual connections separate most candidates from most hiring managers, the informal call is the background check, and it asks far better questions than a form.

Degrees deserve a paragraph of their own, because the most frequently caught CV lie is the unfinished qualification written as a finished one. University registrars and screening vendors confirm awards directly, and the answer is binary: awarded or not. Write it straight instead. List the institution, the field and the years you studied, and state the status plainly — "coursework completed, degree not awarded" or simply the modules and the period, with no degree claimed. Nobody has ever rejected a strong candidate for an honest unfinished degree. Plenty of strong candidates have been rejected for a one-word upgrade from "studied" to "BSc".

What do background checks and reference calls really catch?

Background checks catch structural lies, not stylistic ones. They reliably surface employers that never employed you, dates that don't line up, titles that don't match payroll, degrees that were never awarded and licences that lapsed or never existed. They almost never catch an inflated percentage, because no report contains your old dashboard. That's the asymmetry worth understanding: the formal check protects the employer against fabricated identity and credentials, while the hiring manager's curiosity protects them against fabricated impact. Two different filters, two different failure modes — and the second one is where most well-meaning candidates come unstuck in the room.

The mechanics are duller than people fear. You give written consent, a vendor contacts the sources, and the output is a report of confirmations and discrepancies. The wording matters enormously. A start date out by a few weeks is a clarification; employers expect memory to be imperfect. An employer that has no record of you is a stop. Reference calls, meanwhile, have narrowed in many large organisations to dates, title and rehire eligibility, which is exactly why hiring teams go sideways instead — a quick message to someone who worked alongside you. That informal route asks the question no form asks: what did this person actually own?

Then the interview finishes the job. Any invented number dies on the second or third follow-up, because real numbers come with a baseline, a timeframe, a method and a boundary around your contribution, and fabricated ones come with a shrug. This is also where AI-assisted CVs get people into trouble, since a chat model will cheerfully insert a plausible-sounding metric you never earned. If you've had a model rewrite your CV, run the line-by-line check for invented numbers and titles before you apply — the fabrications are usually the most impressive-sounding sentences in the document.

How do you quantify achievements honestly without underselling?

Replace invented precision with verifiable scope. Use numbers you can actually source — the ones sitting in dashboards, invoices, ticket counts, headcount, budget lines, release notes — and when you only have an estimate, say so in the sentence with "roughly" or "approximately". Then draw a boundary around your own contribution: "led", "co-owned with one other engineer", "contributed the migration workstream". Honest attribution reads as senior, not modest. The candidates who sound most credible in interviews are the ones who name their slice of a big result rather than claiming the whole thing, because that's how people who've genuinely shipped things talk about shipping things.

Three rewrites show the pattern. "Increased revenue by 300%" becomes "grew a small product line from roughly ₹30 lakh to ₹1.2 crore in annual revenue over 14 months, as one of two product owners" — bigger claim, fully defensible. "Expert in Kubernetes" becomes "ran our staging and production clusters for two years, including the migration off VMs and the on-call rotation" — which survives a technical screen that "expert" does not. "Managed a large team" becomes "managed six analysts directly, plus two contractors through a nine-month reporting rebuild". Specifics don't shrink your CV. They make it stop sounding like everybody else's.

The hard part is seeing your own document clearly, since you know what you meant. That's the use case for automated feedback: a score out of 100 with category scores for experience, tech stack, impact and ownership, clarity and structure, and ATS compatibility, plus a visual layout analysis — free, in a couple of minutes. The paid Full Analysis at $3.99 adds the fix list, your blind spots and a blunt "why you might be rejected" read, which is the section that catches bullets making claims you can't back. If you'd rather start clean, the chat-based CV builder rewrites from your real history across six ATS-friendly templates.

Frequently asked questions