A frontend developer and a data analyst are both "in tech." Their CVs should look almost nothing alike.
The frontend dev needs a portfolio link near the top, a short list of frameworks (React, Vue, maybe Svelte), and bullet points that talk about pixels, load times, and shipped features. The data analyst needs SQL dialects, dashboards they actually built, and numbers that show business impact: revenue lifted, hours saved, churn predicted. Same industry label. Two completely different documents.
Most candidates miss this. They write one CV, change the job title at the top, and apply to 80 roles across four industries. Then they wonder why nothing lands. This guide is the hub for fixing that. It explains why a single CV fails across fields, what each industry actually scans for, and where to go deeper for your specific role.
Why the same CV everywhere fails
Recruiters in different industries are not looking at the same things. A finance recruiter spends most of their first scan on credentials, certifications, and named institutions. A startup hiring manager skips all of that and looks for shipped products and traction numbers. A design lead barely reads the page. They click the portfolio link.
If you send the finance CV to the startup, you look slow and bureaucratic. If you send the startup CV to the bank, you look unserious. The content might be 80% the same underneath, but the framing, the order of sections, and the vocabulary need to change. We unpack the mechanics in why the same resume fails across fields.
What industries actually look for
Every field has its own scan pattern. A few examples, distilled from years of recruiter feedback:
- Tech: Stack list near the top, GitHub or portfolio link, bullets focused on shipped features and measurable performance. One page if you have under five years of experience.
- Finance: Education and certifications in a prominent block (CFA, CPA, ACCA), named employers, deal sizes, AUM, P&L responsibility. Two pages is normal.
- Design: Portfolio link is the headline. The CV itself is short, with a clear visual hierarchy. Tools (Figma, Webflow, After Effects) get a small block, not a wall.
- Healthcare: Licenses, board certifications, hospitals or clinics you worked at, patient volumes, specialties. Long-form is expected.
- Sales: Quota numbers, attainment percentages, deal sizes, sales cycles, named accounts. Two pages with hard numbers beats five pages of soft phrases.
- Consulting / Strategy: Top schools, named firms, structured bullets that follow situation-action-result, industries covered.
The through-line: every industry has a currency. Finance pays attention to numbers and prestige. Tech pays attention to what you shipped. Design pays attention to what you made. Healthcare pays attention to where you trained and who you treated. Figure out the currency before you write the bullets.
Tech roles deserve their own CV per role
Inside tech, the differences are sharper than people think. Lumping every engineering CV into one template is how good engineers get filtered out.
- Frontend: emphasize UI work, performance budgets, accessibility, design systems. See frontend developer CV.
- Backend: emphasize APIs, scale, latency, databases, on-call experience. See backend developer CV.
- Full-stack: show range without looking generic. The trap is listing everything and signaling nothing. The fix is one or two end-to-end features per company, described in depth. See full-stack developer CV.
- Mobile: App Store and Play Store links, MAUs, crash rates, native vs cross-platform. See mobile developer CV.
- Data engineer: pipeline scale, SLAs, data volume, the tools you wired together. See data engineer CV.
- Data analyst: SQL, dashboards, questions you answered, business decisions you influenced. See data analyst CV.
- Data scientist / ML: focus on impact, not a tool list. A model that lifted retention 4% beats a 20-line skills section. See data scientist CV.
If your CV could be sent to a frontend and a data engineer role with no changes, it's too vague to do either justice.
How seniority changes the document
A junior CV and a staff CV in the same role are almost different genres.
Junior CVs lead with education, projects, internships, and any open-source or freelance work. The narrative is "I can learn fast and I've already built things." One page.
Mid-level CVs lead with two or three roles where you owned something end to end. Bullets shift from "helped with" to "led" or "shipped." Still one to two pages.
Senior and staff CVs lead with scope and influence. Team sizes, budgets, systems you designed, decisions you owned, mentorship. The skills list gets shorter because nobody hiring a staff engineer cares which CSS framework you used in 2019.
The trap is sending a senior-style CV for a junior role (it sounds inflated) or a junior-style CV for a senior role (it sounds like you've been coasting). Match the document to the level of the job, not the level you wish you were at.
When to break the conventions
Conventions exist because they help recruiters scan fast. But they cost you when your story is the conventions.
A bootcamp grad applying to a startup that says "we hire for slope, not intercept" should put projects above education. A career switcher from law to product management should open with a short "why product" paragraph, not a chronological list of legal roles. A founder who shut down a company should explain what they learned in two honest lines, not hide it.
The rule: break a convention only when the alternative makes your story clearer, not when it makes you feel cleverer. And remember that most CVs are first read by an ATS, which is conservative by design. If you experiment with layout, keep a clean parsed version too. The mechanics are covered in how applicant tracking systems work.
Picking which version to send
Once you accept that you need several versions, the question becomes maintenance. Most people quit because keeping three or four CVs in sync is painful.
A few principles that work:
- Keep one master document with everything: every role, every bullet, every number. This is your source, not your CV.
- From the master, cut a version for each target industry. Frontend, backend, data, product, design, whatever you're applying to.
- Within each version, tweak the top third for the specific job. The summary, the headline skills, and the first role's bullets do most of the work.
- Re-read the job ad twice before each send. Mirror the vocabulary that already appears there, not the vocabulary you wish was there. The general principles also live in how to write a CV.
If you have a populated LinkedIn profile, the master-and-variants approach gets a lot easier. Postulit reads your LinkedIn once and lets you regenerate a role-targeted CV (frontend, data, product, sales) from the same underlying data, so the master stays in one place and the variants update themselves.
The one-CV-everywhere habit is a slow leak in your job search. Plugging it is the highest-leverage change most candidates can make this month.