Make Your CV Achievements Hold Up Under Questioning

Rewriting each achievement as a defensible claim

The purpose of an achievement line is not to impress. It is to give the reader a statement they could check if they picked up the phone. An achievement survives an interview only when you can answer "how do you know?" without pausing to reconstruct the story.

The smallest honest version of a claim states three things: what you were responsible for, what changed after your involvement, and why that change is yours to name rather than the team's in general. Run every line through a single test before it goes on the page — could a former colleague confirm what you did? Does any figure trace back to something you actually saw, not something you heard was true? If the sentence collapses under those questions, it does not belong on the page yet.

The defensible sentence is usually shorter than the impressive one. A responsibility stated clearly beats a result stated vaguely, and the fix is almost always subtraction rather than addition.

A worked example. Here is one achievement carried from a raw note to a line that survives questioning.

The middle row is the trap writers fall into: adding a scale word to a true sentence to make it sound stronger, which makes it weaker. The bottom row is what the reader can actually check. Where a real, sourced figure exists — a number you measured, that a colleague would recognise — it can go in front of that sentence. Where it does not, scope carries the claim instead.

Writing achievements when no numbers exist

Not every piece of good work arrives with a measurement attached. A role can be valuable and still leave no countable outcome on your desk. When that happens, describe the scope rather than inventing a metric: what you were responsible for, how many stakeholders or systems your work touched, and what changed after you were involved.

Scope is quieter than a percentage and far easier to defend, because it describes the shape of the work rather than a result you would struggle to prove. A reader who cannot verify a number will still understand the boundary of what you handled.

Compare the two versions of the same true experience:

There is a specific situation worth naming for a China application. A candidate applying from abroad may have real past work whose numbers come from a market the China recruiter does not recognise, and the hiring department (often technical) and the HR screen may describe the same job in different terms. The practical move is to describe scope in the vocabulary of the role you are applying to, and add a one-line context note only when the market gap is too wide to translate. Leading with responsibility and naming the systems you touched keeps the claim checkable even when the foreign context is unfamiliar.

Estimating a figure you did not measure

It is tempting to place a number next to an achievement even when you never measured it. Before writing that figure, ask one question out loud: can you say where it came from, and would someone who saw the work recognise it? If you can reconstruct the source and name it, the estimate can stay, labelled as an estimate. If you cannot reconstruct the source, cut the number rather than soften it.

A vague qualifier such as "approximately" or "around" does not make an unverifiable claim safe. The softening word suggests honesty while the number stays unsourceable, and in an interview the candidate cannot say how the figure was reached. A shorter, true sentence is stronger than a precise-looking one you cannot defend.

One more distinction matters, and it is the one people skip: the measure, not just the source. The same outcome can be counted two ways — attendance at a session versus people who actually stayed, revenue recognised versus revenue booked — and if your definition is not the one the reader assumes, the figure falls apart under one follow-up question. So before a number goes on the page, be able to state its definition as well as its source: what exactly it counts, and who else would count it the same way. A number whose source and measure you can both state aloud is safe; a number with only one of the two is not.

Keeping confidential results off the page

Some results cannot be shared, and the limit is not a writing problem but a disclosure problem. Before writing anything tied to a previous employer, check what you are permitted to disclose, and describe the work only at a level you are allowed to make public. In a China application this matters more than it might elsewhere, because document and credential checks are part of many processes, and what you write may later be compared against verified records.

A structure you can reuse for confidential work: state the problem type, your role, the method you chose, and the direction the result moved in — then write one plain sentence that further details are subject to a confidentiality obligation and can be discussed live. Do not be vague; vagueness makes the reader doubt the work happened, while a clear boundary reads as professional. Offer the live walkthrough as the alternative, and keep a private note that separates what you may say from what you may not, so you do not slip in an interview.

Where the line sits depends on your contract, your former employer's policy and the nature of the project — a portfolio or a CV grants no permission by itself. If you cannot tell where the disclosure line is, do not guess and do not write the figure to see if anyone notices. Pause and confirm with the former employer's HR or the relevant official channel first. Writing a protected number costs trust, not just a correction.

One portal's view on document volume

The Shanghai International Services Portal's FAQ How detailed should your resume be? describes a recent master's graduate who used AI tools to refine her descriptions and chose an appealing template to produce a full set of materials — a cover page, a cover letter, a three-page resume and a back cover. Employers showed little interest, and she rarely received invitations even for roles matching her qualifications. The page's own diagnosis is that the dense, three-page document overwhelmed recruiters and made her suitability hard to see.

The part worth carrying into this method is the direction the example points: lead with the responsibilities that map to the role, because the example shows what happens when volume buries that match instead of showing it.

Keep the limit of that source in view. It is one student-facing FAQ answer on a municipal services portal, written for people considering study and work in Shanghai — one page's guidance, not a market rule and not a statement about what employers generally require. For an international reader the volume question also meets China-specific steps: applications often run through local recruitment platforms where document length and format differ, a screening call may come from HR before the hiring department reads the page, and a recruiter and a direct employer may each hold a copy. None of that changes the verifiability rule; it only changes who asks "how do you know" first.

For anything touching recognition, visas or work permits, do not treat one portal page — or this article — as the answer. Confirm it with the employer or the relevant official channel, and describe past work only at a level you are cleared to make public.

What to confirm with the employer or the official channel - Does the employer's background check contact former managers who could confirm the figures and scopes I state? - How does the hiring department treat self-reported estimates during interviews, and what evidence may I use to support a claimed result? - Which credentials and records will be verified, so I can match my page to what can actually be checked? - What am I cleared to disclose about past work, and does a translated claim widen what counts as disclosure?