惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

人人都是产品经理
人人都是产品经理
W
WeLiveSecurity
Recorded Future
Recorded Future
P
Privacy & Cybersecurity Law Blog
V
Vulnerabilities – Threatpost
C
Cybersecurity and Infrastructure Security Agency CISA
G
GRAHAM CLULEY
S
Securelist
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
小众软件
小众软件
The Hacker News
The Hacker News
The Cloudflare Blog
D
Darknet – Hacking Tools, Hacker News & Cyber Security
V
V2EX
C
Cisco Blogs
Cisco Talos Blog
Cisco Talos Blog
腾讯CDC
Recent Announcements
Recent Announcements
Jina AI
Jina AI
K
Kaspersky official blog
The GitHub Blog
The GitHub Blog
云风的 BLOG
云风的 BLOG
酷 壳 – CoolShell
酷 壳 – CoolShell
GbyAI
GbyAI
F
Fortinet All Blogs
T
ThreatConnect
S
Schneier on Security
罗磊的独立博客
Y
Y Combinator Blog
C
Check Point Blog
T
The Exploit Database - CXSecurity.com
宝玉的分享
宝玉的分享
aimingoo的专栏
aimingoo的专栏
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
I
Intezer
F
Full Disclosure
T
Troy Hunt's Blog
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
WordPress大学
WordPress大学
Application and Cybersecurity Blog
Application and Cybersecurity Blog
V
V2EX - 技术
C
Comments on: Blog
T
Tenable Blog
Project Zero
Project Zero
H
Help Net Security
A
Arctic Wolf
Google DeepMind News
Google DeepMind News
NISL@THU
NISL@THU
博客园 - 【当耐特】
F
Fox-IT International blog

DEV Community

Cooking an AI Campaign in 5 Minutes with Google Cloud AI APIs Your PM Retrospectives Are Lying to You How I Built a Free, Self-Hosted Pipeline That Auto-Generates Faceless YouTube Shorts TypeScript 54 to 58: The Features That Actually Matter in 2026 95. Fine-Tuning LLMs: Make a General Model Do Your Specific Job What Is a Frontend Developer Roadmap and Why You Need One Google shipped three Gemini "Flash" models. Picking the wrong one could 6 your AI bill Building an MCP server so Claude can query my SaaS analytics directly Google I/O 2026 and the Rise of the AI Ecosystem Your Docker Builds Are Slow Because You're Doing It Wrong (And I Built a Tool to Prove It) How do you verify GitHub contributions without trusting self-reported skills? CV vs Resume: What's the Difference and Which Do You Need? student Devs: Build AI Agents & Compete for $55K in Prizes 🚀 How to Write a Cover Letter That Actually Gets You Interviews Battle-Tested: What Getting Hacked Taught Me About Web & Cyber Security Unda folders za kuandika code >> mkdir src >> cd src >> mkdir controllers database routes services utils >> cd .. Directory: C:\Users\mwaki\microfinance-system Mode LastWriteTime Length Name Code Coverage .NET AI slop debt" is technical debt on fast forward. Nobody's ready. Multi-Head Latent Attention (MLA) Memoria - A Local AI Reading Companion Powered by Gemma 4 Stop Trusting Your Accuracy Score: A Practical Guide to Evaluating Logistic Regression Models Serious Question: Is the Developer Job Actually in Risk Due to AI? published: true tags: #discuss #career #ai #help rav2d: We ported an AV2 video decoder from C to Rust — here's why Your New Domain's First Week of GA4 Is a Lie: 4 Days of Raw Data from a Launch Gemma Guide - Real-Time Spatial Awareness for Blind Users From YAML to AI Agents: Building Smarter DevOps Pipelines with MCP A Field Guide to Human–AI Relations (For the Newly Bewildered Mortal) The AI Agent That Learns While It Works — A Complete Guide to Hermes Agent Inviting collaborators to work on ArchScope ArchScope is an interactive web-based tool that lets you design, visualize, and test system architectures with real-time performance simulations. Github - ArchScope is an interactive web-based tool that lets you Gemma 4: Google's Open-Weight AI Is a Game Changer for Developers Confessions of a Git Beginner: Why the Terminal Stopped Scaring Me Docker 容器化实战:从零到生产部署 🚀 I Built a Full Stack Miro Clone with Real-Time Collaboration using Next.js Building an African Economic Data Pipeline with Python, DuckDB & World Bank API llms.txt vs robots.txt vs ai.txt: The Developer's Cheat Sheet Intigriti Challenge 0526 Writeup Business Logic Flaws: How Attackers Skip Steps in Your App to Get What They Should Never Have Why Vibe Coders Need Boilerplates to Save Time, Tokens, and Build More Secure SaaS Projects Idle Cloud Cost Is the New Egress Cost Quark's Outlines: Python Traceback Objects Ghost in the Stack (Part 1): Why uninitialized variables remember old data Building a High-Performance Local Chess Assistant Extension with WebAssembly Stockfish and Manifest V3 Breaking the Trade-off Between Self-Custody and Intelligent Automation on the Stellar Network I Open-Sourced a Practical Fullstack Interview Preparation Repository (React + Node + System Design) 🚀 How I Started Coding as a Student (Beginner-Friendly Guide) WordPress vs. Ghost: Why Automated Bot Attacks Are Making us think much I tested 4 AI agent-governance tools against an open spec - here's the matrix zkML Inference Proof: What the Receipt Proves, and What the Model Still Does Not I Scored 1000/1000 on AWS Certified AI Practitioner (AIF-C01) Here's Every Resource I Used Go - Struct and Interface Handling JSON Requests in Go Storing Kamal secrets in AWS Secrets Manager and deploying to a cheap Hetzner VPS How I Caught and Fixed an N+1 Query in My Django REST API I got tired of paying $10/month to remove image backgrounds – so I built it for free How to Start Coding as a Student: A Complete Beginner’s Guide 🚀 Storing Kamal secrets in AWS Secrets Manager and deploying to a cheap Hetzner VPS What Are Buffers? Build AI Agents with Hot Dev The Client Onboarding Checklist That Prevents 90% of Project Problems Scalable Treasure Hunts Are a Myth, But We Almost Made One Gemini 3.5 Flash Has a 1M Token Context Window. Here's What You Can Actually Build With It. I built a ultra-polished developer portfolio template using React & Tailwind v4 (with zero-JSX configuration) Gemini CLI Is Dead. Here's the Better Thing That Replaced It Post-quantum cryptography for embedded and IoT: secure boot, TLS and OTA Understanding Optimistic Preloading in Modern Applications Nobody Wants to Read Your Code (And You Don't Want to Read Theirs) A clothing pairing app E2B vs E4B vs 31B Dense: The Practical Guide to Choosing the Right Gemma 4 Model I built an AI app store screenshot generator because Figma made me cry — looking for brutal feedback Hello DEV Community — My Developer Journey Begins Adaptable apps on ChromeOS: a post-mortem The WordPress Paradox: Why It’s Here to Stay (and How to Stop Ruining It) I built a local voice AI that can change to 9 different personalities! UXRay: I Built an AI That Roasts Your UI Like a Senior Designer Would Wyrly DI: Type-safe Dependency Injection for Modern TypeScript The contract is the interface: agent-driven Steampipe Stave in one command Gemma 4's Hidden Superpower: Why Built-in Thinking Tokens Change Everything for Evaluation Tasks ⚡ WordPress Performance: The Real Truth They Don't Tell You A Mobile App Usually Needs an Admin System First Customer Portals Should Remove Repeated Admin Work Episode 4: The Time Loop (Layers & Caching) I Built ContextForge with Gemma 4: A Project Memory Generator for Developers and AI Coding Agents Why shadow DOM beat iframe for inline tooltips HOW TO CREATE USER AND ASSIGN ROLES IN AZURE WITH ENTRA ID When AI Blackmail Goes Viral Episode 3: The Secret Scroll (The Dockerfile) Monte Carlo Simulation for Engineers: Turning Uncertainty Into Numbers The tokens-per-byte trap: character-level 'compression' adds tokens Nobody Reads Your Code Anymore Why I built a collection of 5 free, zero-signup career finance tools for solo builders 🚀 New React Challenge: Instant UI with useOptimistic Resolvendo a Alucinação da IA na Arquitetura de Software com Code Property Graphs e .NET 9 S1 — Clean Backtrace Crashes: How to Diagnose and Fix Them Cómo solucionar el bucle infinito en useEffect con objetos y arrays The Brutal Reality of Running Gemma 4 Locally I made Claude Code refuse to write code unless the ticket scores 80/100 I Fed React's Entire Hooks Transition History to Gemma 4. Here's What It Found That We Missed. Building a Private RAG System: Lessons from a Local-First AI Journal CodePulse AI — Reviving an AI-Powered Repository Intelligence Platform How to Split Video into Segments with FFmpeg (CLI + API)
How to Tailor Your CV to Any Job Posting in 2026
John · 2026-05-23 · via DEV Community

Most job seekers spend more time refreshing their inbox than they do tailoring their CV to the job posting in front of them. That's a mistake that costs more interviews than any skill gap ever could. A generic CV — one that lists everything you've ever done in a neutral, inoffensive order — gets ignored not because you're underqualified, but because you look exactly like every other applicant who didn't bother to customize theirs.

This guide walks through the exact process for tailoring your CV to any job posting, including how Applicant Tracking Systems (ATS) filter candidates before a human even reads a word, how to reframe your real experience without fabricating anything, and how to write bullets that make a hiring manager stop scrolling. By the end, you'll have a repeatable system — one you can do manually when you have the time, or automate with tools like NextCV when you're in a heavy application sprint.


Why Generic CVs Fail: ATS Filters and the 6-Second Scan

Before your CV lands in front of a recruiter, it usually passes through an Applicant Tracking System. ATS software parses your document, scores it against the job description, and — in competitive roles — filters out the bottom 70–80% before any human sees it. This isn't theoretical: large companies with high application volumes rely on these systems heavily, and even mid-sized employers increasingly use tools like Greenhouse, Lever, or Workday to manage their pipeline.

What does an ATS look for? Primarily, keyword matches. If a job description says "cross-functional stakeholder management" and your CV says "worked with different teams," the ATS may score those as a mismatch — even though they describe the same thing. The language gap alone can disqualify you.

Then there's the recruiter scan. Studies consistently show that recruiters spend roughly six seconds on an initial CV pass. They're not reading; they're pattern-matching. They want to see familiar role titles, recognizable company names, and concrete achievements. If your most relevant bullet is buried in the fourth job on page two, they'll miss it.

Tailoring your CV solves both problems. It feeds the ATS the keywords it needs and surfaces your most relevant experience first for the human reader.

Real job posting matched to a tailored CV — this is what effective tailoring looks like in practice


What Tailoring Actually Means (And What It Doesn't)

Let's clear up a misconception: tailoring your CV is not lying. It's not inventing skills you don't have or claiming accomplishments that belong to someone else. Tailoring is reframing — choosing which parts of your real experience to emphasize, and using the employer's own language to describe them.

Think of it this way. You are a three-dimensional person with a varied career. Your CV is a two-dimensional snapshot. Every time you apply to a job, you're deciding which angle to photograph yourself from. The product being photographed doesn't change. The framing does.

Concretely, this means:

  • Reordering bullets so the most relevant responsibilities appear first within each role
  • Swapping synonyms to match the job description's language (e.g., "managed" vs. "led" vs. "directed")
  • Expanding or collapsing sections based on what the role values (a startup cares about your side projects; a bank probably doesn't)
  • Quantifying achievements in the units the industry uses (revenue, headcount, uptime, NPS, conversion rate)
  • Adding or removing optional sections like publications, certifications, or volunteer work depending on their relevance

What tailoring is not: adding skills you can't demonstrate, inflating titles, or padding dates. Those are integrity issues with real consequences.


Step 1: Decode the Job Posting Before You Write a Word

Most candidates read a job posting once, skim the requirements, and start updating their CV. That's too fast. Before you type anything, spend ten minutes dissecting the posting itself.

Extract the Primary Keywords

Go through the posting and highlight every technical skill, tool, methodology, or domain term mentioned. These are your primary keywords. If the job description mentions "Python," "machine learning pipelines," and "MLOps" three times each, those are non-negotiable inclusions. If your experience is relevant, those exact terms should appear in your CV — not paraphrases.

Identify the Implicit Priorities

Job descriptions are not perfectly written documents. They list requirements in approximate order of importance, and they often bury what actually matters in the middle of a long paragraph. Look for verbs like "must," "essential," and "required" versus "preferred" and "nice to have." The must-haves are your core targeting criteria.

Also look at what the role is ultimately responsible for. A "Senior Marketing Manager" post that mentions "you'll own MQL targets and work closely with sales" is really a demand generation role with a seniority title. Your CV should lead with your demand gen experience, not your brand work.

Note the Company's Language Register

Does the posting use formal corporate language or casual startup speak? Does it reference "Objectives and Key Results" or "sprints and retros"? These are cultural signals. Your CV's language register should loosely mirror theirs. A heavily jargon-laden posting signals they want someone already fluent in their world.


Step 2: Audit Your Current CV Against the Posting

Before editing anything, score your existing CV against the target role. This step forces you to identify the gap between what you have and what the job needs — so you can close it deliberately rather than accidentally.

Create a simple two-column list:

Job posting requirement Your CV (as it currently stands)
5+ years Python 6 years Python — matches, check terminology
CI/CD pipeline ownership "contributed to build process" — needs strengthening
Team lead experience Managed 3-person team — buried in bullet 7, needs to surface

This audit takes 15 minutes and gives you a precise editing brief. You know exactly which gaps to address and which bullets need to move up the page.

Deciding What to Cut, Not Just What to Add

Most people approach CV customization as an additive exercise — they add keywords, add a new bullet, add a summary paragraph. But subtraction is equally important. Every line on your CV that isn't relevant to the target role is competing for the reader's attention with lines that are.

If you have seven years of experience and you're applying for a senior role, the work you did in years one and two probably doesn't need three bullets. Cut it to one line or a single descriptive sentence. That space can go to a more recent, more relevant achievement. Similarly, if a section isn't mentioned anywhere in the job description — say, you have a "Volunteer Work" section and the role makes no reference to community involvement — consider removing it for this application. You're not erasing that experience from your life; you're just not including it in this particular snapshot.


Step 3: Rewrite Your Bullets the Right Way

This is where the real work happens. Generic CV bullets follow a pattern that looks like a job description: "Responsible for managing client accounts and ensuring customer satisfaction." Nobody who reads CVs for a living likes this pattern. It describes a duty, not an achievement.

Tailored, high-impact bullets follow a different pattern: Action verb + specific context + measurable result. The goal is to answer the question: "So what happened because of your work?"

Before and After: The Generic Bullet Problem

Here's the same experience written two ways.

Generic (before):

Responsible for managing the company's social media presence across multiple platforms and creating content.

Tailored and achievement-focused (after):

Grew LinkedIn following from 4,200 to 18,000 in 11 months by launching a weekly thought-leadership series targeting mid-market SaaS buyers; contributed directly to a 22% increase in inbound demo requests from LinkedIn.

The second version does several things the first doesn't. It quantifies the outcome. It specifies the channel. It explains the mechanism (thought-leadership series). And it connects the work to a business result (demo requests). If the job posting mentions "B2B LinkedIn content strategy," this bullet is a direct hit.

More Before/After Examples

Project management (generic):

Managed multiple projects simultaneously and ensured they were delivered on time.

Project management (tailored):

Led delivery of four concurrent product launches across a 12-person cross-functional team, hitting all milestones within a compressed 90-day roadmap while reducing scope creep by 30% through weekly stakeholder alignment sessions.


Software engineering (generic):

Worked on backend services and APIs to improve application performance.

Software engineering (tailored):

Re-architected a legacy REST API handling 2M daily requests, reducing average response time from 480ms to 62ms and cutting server costs by $14,000/month by migrating to async processing with Redis queues.


Sales (generic):

Exceeded sales targets and built strong client relationships.

Sales (tailored):

Finished FY2025 at 134% of quota ($2.1M ARR), sourced entirely from outbound prospecting; closed the largest new logo in team history, a $340K enterprise contract that opened a new vertical.

The pattern holds across every field: specific numbers, named tools, real scope, and actual outcomes.


Step 4: Optimize for ATS Without Writing Like a Robot

ATS optimization and human readability are not mutually exclusive, but you have to be intentional about it.

Use the Exact Phrasing from the Job Posting

If the posting says "Agile project management," don't write "scrum-based workflows" and assume the ATS will connect them. Some systems have synonym libraries; many don't. Match the phrasing exactly at least once. You can vary it elsewhere.

Put Keywords in Context, Not in a List

Some candidates add a "Skills" section that's just a comma-separated list of keywords. ATS systems increasingly penalize keyword stuffing in skills sections because it's a known gaming tactic. The safest approach: weave keywords naturally into bullet points where they appear in real context. This reads better for humans and scores better in smarter ATS tools.

Check Your File Format

Most ATS systems parse .docx and .pdf files, but they handle them differently. PDFs generated from a properly formatted Word document usually parse cleanly. PDFs created from graphic design tools (Canva, Adobe Illustrator) often contain text in image layers that ATS cannot read at all. Always use a text-layer PDF.

Avoid Tables, Columns, and Headers/Footers

ATS parsers read linearly. A two-column layout that looks clean to a human eye often becomes scrambled text when an ATS tries to extract it. Keep your layout single-column, use standard section headings ("Experience," "Education," "Skills"), and keep important information out of the document's header and footer areas, which some parsers skip entirely.


Step 5: Quantify Everything You Can

Numbers do cognitive work that adjectives cannot. "Significant improvement" means nothing. "38% improvement in customer retention" means something precise and memorable.

When reviewing your bullets, ask these questions for each achievement:

  • How much? Revenue generated, cost saved, percentage change, headcount managed
  • How many? Clients served, products shipped, issues resolved, campaigns run
  • How fast? Time-to-delivery, cycle time reduction, onboarding speed
  • Compared to what? Prior period, team average, industry benchmark, original target

You won't have numbers for everything. That's normal. When you don't have a precise figure, use a range or qualifier: "reduced churn by roughly 20%," "managed a portfolio of approximately 30 enterprise accounts." Approximate is better than vague.

If the metric genuinely doesn't apply — you're a writer, a designer, or in a role where output is qualitative — describe scope instead: "Authored the company's brand guidelines, now used across a 200-person organization," or "Redesigned the customer onboarding flow, adopted in full by the product team."


NextCV generates a tailored CV, cover letter, and interview cheat sheet from any job posting

The Automated Way: Using AI to Scale Your Tailoring

Everything described above works. It's also time-intensive. Properly tailoring one CV to one posting — auditing, rewriting bullets, checking ATS alignment — takes 45 minutes to an hour when done carefully. If you're running a serious job search and applying to ten roles a week, that's almost a full workday spent on document customization.

This is the problem that tools like NextCV are designed to solve.

The workflow is straightforward: you build your master profile once, adding your full experience, skills, and education. Then, for each job application, you paste the job description. The AI reads the posting, extracts the keywords and priorities, and rewrites your bullets to match — surfacing the most relevant experience, adopting the posting's language, and generating a targeted CV and cover letter together. It also produces an interview cheat sheet based on the role, so the tailoring carries through to your preparation, not just your application.

The key distinction: the AI is working from your real profile. It's not inventing experience; it's doing the same reframing you'd do manually, but in seconds instead of an hour. You still review the output and make judgment calls a tool can't make — whether to include a particular project, how to describe a career transition, whether the tone matches the company culture. The AI handles the mechanical labor; you handle the strategic decisions.

NextCV uses a credit-based model (no subscription required), with packs starting at $3 for 3 credits. Each credit generates a tailored CV, cover letter, and interview cheat sheet for one job posting. Free watermarked previews are available so you can evaluate the output before committing. For an active job search — say, 15 applications in a month — the Job Hunter pack at $9 covers the full sprint.

This isn't about replacing the thinking. It's about removing the bottleneck so that careful tailoring becomes something you do for every application instead of just the ones you have time for.


How to Handle Career Gaps and Non-Linear Histories

One question that comes up constantly: how do you tailor your CV when your background is messy — career gaps, industry pivots, freelance stints, or roles that don't map cleanly onto the job description?

The answer is still reframing, but it requires more deliberate framing at the structural level, not just the bullet level.

Gaps in Employment

Don't hide gaps, but don't apologize for them either. If you took time off to care for a family member, complete a personal project, travel, or recover from burnout, a brief parenthetical is enough: "(Career break, 2024–2025)." Recruiters see this routinely and care far less about it than candidates fear. What they do care about is whether the gap is followed by something relevant. If you did anything during that period — freelance work, online courses, open-source contributions, independent study — list it. It doesn't need to be a formal employer.

Career Pivots

If you're moving between industries or functions, the tailoring burden is higher because your previous titles won't immediately signal relevance. The solution is two-fold: write a short professional summary at the top of your CV that explicitly frames the transition, and lead every bullet with the transferable skill rather than the industry context. "Managed a $4M product budget in retail" becomes a data point for a product role in fintech if you lead with "Budget ownership" and explain the decision-making process, not the retail vertical.

Freelance and Contract Work

Treat each client engagement as its own role, or group short engagements under a single "Freelance [Function]" header with a date range. For each client, apply the same action + context + result structure you'd use for a staff role. The key is specificity — "various clients in marketing and technology" tells a recruiter nothing; "B2B SaaS growth strategy for three Series A companies, including [client name if public]" tells them everything they need to evaluate fit.


Common Tailoring Mistakes to Avoid

Even job seekers who understand the value of customization make the same errors repeatedly.

Over-tailoring to the point of incoherence. There's a difference between emphasizing relevant experience and telling a different story in every application. Your career narrative should remain internally consistent. If you're tailoring toward a product management role, lean into your PM-adjacent work — but don't suddenly omit three years of engineering experience that contextualizes how you think.

Changing the job title on your CV. Don't. Your actual title is verifiable, and misrepresenting it in a background check is a disqualifying event at most companies. You can add clarifying context in parentheses ("Senior Engineer (Tech Lead for Payments Squad)") but the formal title should match your employment record.

Tailoring the CV but not the cover letter. A tailored CV paired with a generic cover letter is a missed opportunity. The cover letter should do a different job — not recapping the CV, but explaining why this role specifically, at this company specifically, is the logical next chapter. That requires real customization.

Forgetting to update the file name. Sending a file called "CV_Generic_v4_FINAL.docx" undermines everything. Name your files clearly: "Jane_Smith_ProductManager_Stripe.pdf." It's a small thing that signals you're organized and specific.


Actionable Takeaways

The system, distilled:

  1. Decode before you write. Extract keywords, identify implicit priorities, and note the company's language register before touching your CV.

  2. Audit the gap. Map your existing CV against the posting to identify exactly what needs to change — don't edit blindly.

  3. Rewrite with action + context + result. Every bullet that can be quantified should be. Every bullet should answer "so what?"

  4. Match the ATS language exactly. Use the posting's terminology at least once, in context, not in a stuffed skills list.

  5. Protect your layout. Single-column, text-layer PDF, standard section headings. The cleanest CV a human can read is also the cleanest one an ATS can parse.

  6. Scale with tools when volume demands it. When you're in an active search, tools like NextCV do the repetitive reframing work so careful tailoring stops being something you skip because you're tired.

The job market in 2026 rewards specificity. Hiring managers are wading through more applications than ever, and the candidates who stand out are the ones who did the work to show — in the posting's own language — that they understand the role and have the evidence to back it up. A tailored CV is that evidence. It takes more time than sending the same document everywhere. It also works.


NextCV is an AI-powered CV builder that tailors your CV, cover letter, and interview prep to each job description. Build your profile once, paste any job posting, and get a targeted application package in seconds. Try it free at nextcv.net.


Related Articles