Guides
Use your existing CV as a starting point, then turn roles, projects, education, and achievements into a structured skill graph with depth and evidence.
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.
A CV already contains the ingredients of a graph:
That makes it the fastest starting point for most professionals.
But a CV also creates four common distortions:
| CV Pattern | What Gets Lost |
|---|---|
| Chronological structure | Skills that span multiple roles stay fragmented |
| Job-title bias | Capability is mistaken for title history |
| Tool-heavy bullets | Skills stay buried under software names |
| Limited space | Important evidence gets compressed or removed |
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.
Open your CV and go role by role.
For each position, ask:
Do not copy bullets word for word. Translate them into skill language.
Example:
| CV Bullet | Better Skill Extraction |
|---|---|
| Built dashboards in Tableau for weekly reporting | analytics, dashboard design, stakeholder reporting |
| Led migration from monolith to microservices | system design, service decomposition, migration planning |
| Worked with product and design to launch onboarding flow | cross-functional collaboration, product delivery, user onboarding |
This is the first major shift: move from activities to capabilities.
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:
Examples:
| CV Term | Keep or Translate? | Better Skill Node |
|---|---|---|
| Excel | Translate | analysis, financial modeling, reporting |
| Jira | Translate | planning, project coordination |
| Docker | Usually translate | containerization, deployment workflow |
| Kubernetes | Often keep | Kubernetes, orchestration, platform operations |
| Figma | Sometimes keep | interface design, prototyping, design systems |
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.
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:
The right grouping is the one that makes future decisions easier. If the domains help you see strengths and gaps quickly, they are working.
A CV usually implies experience, but it rarely defines depth clearly. A skill graph should.
Use a simple, consistent scale such as:
| Depth | Meaning |
|---|---|
| Exposure | You have studied it or used it in a limited context |
| Working | You can apply it with some support or within familiar patterns |
| Proficient | You can own outcomes independently |
| Expert | You can handle edge cases, teach others, and shape strategy |
Now score each skill based on the evidence in your CV.
Here are better depth questions than "How long have I done this?":
Years of exposure do not automatically create depth. Repeated ownership does.
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:
For each important skill, attach evidence from the CV such as:
Example:
| Skill | Depth | Evidence |
|---|---|---|
| API design | Proficient | Designed and shipped three customer-facing APIs with pagination, auth, and versioning |
| Stakeholder communication | Working | Led weekly launch reviews with product, support, and engineering |
| SQL | Working | Built recurring funnel analysis and self-serve reporting for ops team |
Without evidence, a graph is just a reorganized self-assessment. With evidence, it becomes a decision tool.
CVs are optimized for relevance, not completeness. That means important skills are often missing even when they are real.
Common examples:
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:
Your graph should reflect capability, not just what fit on one or two pages.
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:
This is where the graph becomes more useful than the CV. A CV is a static narrative. A graph helps you make choices:
If you need examples of graph structures by role, see Skill Graph Examples and Skill Graph for Engineers.
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:
That is the right workflow:
The graph should not be "Work Experience, Education, Skills." It should be domains, skill nodes, depth, and evidence.
Tool overload makes the graph noisy and harder to use.
A senior title does not prove expert depth across every skill involved in the role.
Projects, certifications, public writing, and side work often provide the clearest proof.
Start with 15-30 skills. You can expand later if needed.
Building from a CV works especially well when:
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.
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.
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.
Build the base graph from your real experience first. Then compare it against the target role and create a role-specific view or emphasis.
Yes. Students can extract skills from coursework, projects, internships, and research. Career changers can surface transferable skills that a standard CV often hides.