People treat the CV as a universal document, then wonder why the version that landed interviews in one field goes silent in another. The format that works for a software engineer can read as cluttered and self-promotional to an academic hiring committee, and the academic CV reads as bloated to a startup. The skill isn't writing one perfect CV; it's knowing which parts to change per industry and which to leave alone.

What stays the same everywhere

Start with the constants, because they're easy to lose in the customization panic. Every field rewards evidence over adjectives, clarity over density, and relevance over completeness. A vague claim is weak in finance and in design. An unverifiable result is suspect in nursing and in sales. The fundamentals of a strong CV hold across all of them. Industry adaptation happens on top of that base, not instead of it.

What changes: the proof currency

The biggest variable is what counts as proof in the field. In sales, it's numbers: quota attainment, revenue, growth percentages, with no number left implied. In software, it's shipped systems and scale, the thing built and what it handled. In academia, it's publications and grants, listed in full, where brevity would actually look like inexperience. In skilled trades and healthcare, it's certifications and license numbers placed where they're seen in the first scan, because their absence is disqualifying regardless of the rest.

Using the wrong currency is the classic failure. A salesperson who describes responsibilities instead of numbers looks like they have no numbers. An engineer who lists soft skills before systems looks like they didn't build much. Same person, same career, wrong proof for the audience.

What changes: length and convention

Length is not a universal rule; it's a per-field convention. The startup and most corporate roles want one to two pages and read brevity as confidence. Academia, research, and some senior medical or legal roles expect a multi-page CV and read brevity as a thin record. Applying one field's length norm to another signals you don't know the field, which is its own quiet rejection. When you don't know the convention, look at how people one level above you in that field present themselves and follow that, not a generic template.

What changes: the keyword and ATS layer

Most mid-to-large employers screen with an applicant tracking system before a human reads anything, and the vocabulary it screens for is industry-specific. "Stakeholder management" matters in consulting; "CI/CD" matters in engineering; "patient outcomes" matters in healthcare. The exercise is the same everywhere but the dictionary is not: take the target field's actual job postings and mirror their real terms where they're true of you. A literal cross-field translation of your old CV's keywords is how you become invisible in a new industry.

How to actually adapt without rewriting from scratch

Keep one full master record of everything you've done, then cut a targeted version per application from it. The master is your memory; the sent CV is the argument for this one role in this one field. If your history already lives on LinkedIn, a tool like Postulit can produce the structured base quickly, which makes maintaining a master and cutting field-specific versions far less tedious than editing a Word file each time. The judgment, what proof currency this field rewards, what length it expects, still has to come from you.

There's no universal CV, only a CV well-adapted to a field or a CV that ignored the field. Keep the fundamentals fixed, change the proof currency, length, and vocabulary to match the industry, and the same career can read as a strong fit in places a single static document never could.