How to Build a Skill Graph from a CV

If you already have a CV, you are closer to a useful skill graph than you think.

Most people do not start from a blank page. They start from a document that already contains years of work history, projects, education, certifications, and achievements. The problem is that a CV is optimized for chronology, not capability. It tells the story of where you have been, but it does not clearly map what you can do.

This guide shows how to use a CV as raw material for a skill graph. The goal is not to recreate your CV inside another format. The goal is to convert experience into a connected map of skills, depth, and evidence that is actually useful for growth planning, job targeting, and stronger applications.

If you are starting from scratch, read How to Build a Skill Graph first. If you want to compare formats, see Skill Graph vs Resume.

Why Start with a CV?

A CV already contains the ingredients of a graph:

• roles and responsibilities
• outcomes and achievements
• technologies and methods
• education and certifications
• projects, writing, and extracurricular work

That makes it the fastest starting point for most professionals.

But a CV also creates four common distortions:

A skill graph fixes those distortions by reorganizing your profile around what you can do, how deeply you can do it, and what evidence supports it.

Step 1: Pull Skills Out of Each Role

Open your CV and go role by role.

For each position, ask:

1. What capabilities did this role actually require?
2. Which of those capabilities did I own directly?
3. Which repeated across multiple roles?

Do not copy bullets word for word. Translate them into skill language.

Example:

This is the first major shift: move from activities to capabilities.

Step 2: Convert Tool Names Into Real Skills

Many CVs are overloaded with tools. That is understandable because recruiters often scan for tool familiarity. But a skill graph needs the underlying capability, not just the software label.

Here is the rule:

• If the tool is only a vehicle, map to the broader skill.
• If the tool itself requires meaningful depth, keep it as a skill node.

Examples:

This matters because skill graphs should help you reason about adjacent capability. Someone who can only say "Tableau" reveals less than someone whose graph shows analysis, stakeholder reporting, and dashboard design.

Step 3: Group Skills by Domain

Once you have extracted raw skills from all sections of the CV, group them into 3-6 domains. These domains become the top-level structure of the graph.

Examples:

For a software engineer

• Backend
• Frontend
• Infrastructure
• Delivery
• Communication

For a recruiter

• Sourcing
• Screening
• Stakeholder management
• Process operations
• Employer branding

For a master's student or early-career candidate

• Core coursework
• Projects
• Research
• Communication
• Career readiness

The right grouping is the one that makes future decisions easier. If the domains help you see strengths and gaps quickly, they are working.

Step 4: Add Depth, Not Just Presence

A CV usually implies experience, but it rarely defines depth clearly. A skill graph should.

Use a simple, consistent scale such as:

Now score each skill based on the evidence in your CV.

Here are better depth questions than "How long have I done this?":

• Did I own the decisions, or just execute within an existing pattern?
• Did I apply this skill once, or repeatedly across contexts?
• Could I explain the tradeoffs to someone else?
• Do I have outcomes that prove real capability?

Years of exposure do not automatically create depth. Repeated ownership does.

Step 5: Attach Evidence to Each Important Skill

This is where the graph becomes significantly more valuable than the CV.

A CV might say:

Improved onboarding conversion by 18%.

That is useful, but isolated. In a skill graph, the same result can support multiple nodes:

• experimentation
• growth strategy
• onboarding design
• cross-functional delivery

For each important skill, attach evidence from the CV such as:

• shipped projects
• measurable results
• promotions and expanded ownership
• certifications
• research output
• talks, writing, or mentoring

Example:

Without evidence, a graph is just a reorganized self-assessment. With evidence, it becomes a decision tool.

Step 6: Fill the Gaps Your CV Hides

CVs are optimized for relevance, not completeness. That means important skills are often missing even when they are real.

Common examples:

• mentoring and coaching
• hiring and interviewing
• architecture review
• debugging and incident response
• technical writing
• stakeholder alignment
• self-directed learning and side projects

This is why you should not stop at the CV text itself. Use it as a base layer, then add what was compressed out.

Check these sources:

• LinkedIn recommendations
• portfolio projects
• GitHub activity
• internal documents you can describe safely
• certifications and coursework
• presentation decks or workshop material

Your graph should reflect capability, not just what fit on one or two pages.

Step 7: Compare the Graph Against Your Target Role

Once the graph exists, it becomes much easier to reason about career direction.

Take 3-5 job descriptions for the role you want next. Extract the repeated skills, then compare them against your graph.

Look for three categories:

1. Missing skills: not represented in your graph yet.
2. Depth gaps: present, but not at the level the role seems to demand.
3. Evidence gaps: you likely have the skill, but not enough proof to make it credible.

This is where the graph becomes more useful than the CV. A CV is a static narrative. A graph helps you make choices:

• what to learn next
• what proof to create
• what to emphasize in future applications

If you need examples of graph structures by role, see Skill Graph Examples and Skill Graph for Engineers.

Step 8: Use the Graph to Improve the CV Again

The relationship goes both ways.

Your CV helps you create the graph. Then the graph helps you write a much stronger CV.

Once your graph is clear, you can:

• write more specific bullets
• prioritize the skills most relevant to the target role
• remove low-signal tool clutter
• support stronger claims with clearer evidence

That is the right workflow:

1. Use the CV to initialize the graph.
2. Use the graph to clarify skills, depth, and evidence.
3. Rewrite the CV from that clearer source of truth.

Common Mistakes

Copying sections directly instead of translating them

The graph should not be "Work Experience, Education, Skills." It should be domains, skill nodes, depth, and evidence.

Treating every tool as its own skill

Tool overload makes the graph noisy and harder to use.

Confusing seniority with depth

A senior title does not prove expert depth across every skill involved in the role.

Ignoring non-work evidence

Projects, certifications, public writing, and side work often provide the clearest proof.

Building too large too early

Start with 15-30 skills. You can expand later if needed.

When a CV Is the Best Starting Point

Building from a CV works especially well when:

• you are mid-career and have several roles to synthesize
• you are preparing for a job search
• you want to sharpen a weak or generic CV
• you need a fast first draft of your graph

If you have strong public project evidence, GitHub may be an equally strong starting point. In that case, read How to Build a Skill Graph from GitHub.

If you want to turn your existing experience into a structured graph quickly, the Skill Graph Generator is the fastest place to start.

FAQ

Can a CV produce a complete skill graph?

Usually not by itself. It gives you a strong first draft, but you will almost always need to add missing evidence, hidden responsibilities, and skills that were compressed for space.

What if my CV is weak or out of date?

That is fine. Use whatever is there as raw material. Even a weak CV usually contains enough history to extract your first 15-20 skill nodes.

Should I build the graph from my current CV or tailor it to a target role first?

Build the base graph from your real experience first. Then compare it against the target role and create a role-specific view or emphasis.

Is this useful for students and career changers too?

Yes. Students can extract skills from coursework, projects, internships, and research. Career changers can surface transferable skills that a standard CV often hides.