What Your CV Needs Before You Import It

A CV tool reads your document, breaks it into sections, and turns each one into structured data it can reshape for any job. That only works if the sections are there to read.

A parser does not guess. If a date is missing, it leaves the field blank. If your job title is buried in a sentence, it may never find it. The cleaner and more complete the CV you import, the less you fix afterward and the more the tool can do for you.

Here is what each section should hold before you import, and what the parser cannot infer when it is missing.

Contact and Personal Info

This is the smallest section and the one people get wrong most often.

Include:

• Full name, on its own line, at the top.
• A professional email address you actually check.
• Phone number with country code if you apply abroad.
• City and country. A full street address is optional and usually skipped.
• One or two links: LinkedIn, a portfolio, GitHub if you are technical.

What the parser cannot infer: it cannot invent your email or guess your location from context. If your name only appears inside a header image or a text box, some parsers miss it entirely. Keep it as plain text at the top.

Avoid putting contact details in the page header or footer. Many parsers read the body first and treat headers as decoration, so the one line you most need read is the one most likely dropped.

Professional Summary

Two or three sentences at the top that say who you are, your strongest proof, and what you are aiming at.

The summary is the one section a tool can rewrite well only if you give it a starting point. It anchors your seniority and field so the rest of the CV is read in context.

What the parser cannot infer: your positioning. It can see you held three backend roles, but it cannot know whether you want to stay backend or move into platform work. A summary states the direction. Without it, the tool has facts but no angle.

If you write nothing else by hand, write this.

Experience

This is the core, and the most structured. Each entry should be a clear block, not a paragraph. A parser looks for four things per role:

• Job title. On its own line, exact. "Senior Backend Engineer", not "I worked as a senior engineer doing backend things".
• Company name. Next to or below the title.
• Dates. Start and end, in a consistent format. Jan 2022 – Mar 2024 or 2022 – 2024. Use "Present" for current roles.
• Achievements. Bullet points, not a wall of text. One accomplishment per line, with a number where you have one.

Weak:

Backend developer at a fintech where I did a lot of work on the payments system and helped the team ship faster over about two years.

Strong:

Backend Engineer — PayFlow (Jan 2022 – Mar 2024)

• Cut checkout latency 35% by reworking the payments queue.
• Led migration of 40 services from REST to gRPC.

What the parser cannot infer: a missing date breaks the timeline. If a role has no end date and is not marked "Present", the tool cannot place it in order or calculate your years of experience. If title and company blur into one sentence, it may tag the whole thing as a single field. Keep the four parts visually distinct.

Order roles newest first. That is the order every reader, human and machine, expects.

Skills

Group them. A flat list of thirty comma-separated words is hard to read and hard to match against a job posting.

Better:

Languages: Python, Go, TypeScript Infrastructure: AWS, Docker, Kubernetes, Terraform Data: PostgreSQL, Redis, Kafka

Grouping does two things. It lets a person scan for the category they care about, and it lets the tool map your skills against the categories a job asks for.

What the parser cannot infer: proficiency and grouping if you do not supply them. It will not know that "Kubernetes" belongs under infrastructure rather than languages unless the structure tells it, and it will not invent skills you did not list. List the real ones plainly. Do not pad with soft skills like "communication" in a technical skills block; keep those for the summary if at all.

Projects

Projects carry weight when your experience is thin, when you changed fields, or when your best work was not a paid job. Treat each like a small experience entry.

Include:

• Project name.
• One line on what it does and your role in it.
• The stack or tools used.
• A link if it is live or public.
• A result if you have one: users, stars, adoption.

What the parser cannot infer: which of your side efforts count as portfolio work. A GitHub link alone in your contact section tells the tool nothing about what is behind it. A named project with a description and a stack is something the tool can surface for the right job. If a project is central to your case, give it a heading, not a footnote.

Certifications and Achievements

The proof layer. Certifications, awards, publications, and formal recognition.

Include, per item:

• The exact name of the certificate or award.
• The issuing body.
• The date, or an expiry if it has one.

Example:

AWS Certified Solutions Architect – Associate, Amazon Web Services, 2024 Runner-up, National Datathon, 2023

What the parser cannot infer: the credibility a name carries. "AWS Certified Solutions Architect" is a keyword a job filter looks for; "cloud certified" is not. Write the full, official title. Skip vague lines like "various online courses" — they add length without signal, and a parser cannot turn them into anything useful.

The Quick Checklist

Before you import, confirm your CV has:

• Full name and a working email as plain text at the top.
• A two-to-three sentence summary.
• Experience as blocks with title, company, dates, and bulleted achievements.
• Skills grouped by category.
• Projects with names, stacks, and links where relevant.
• Certifications with exact names, issuers, and dates.

If all six are there, the import gives you a clean, structured CV the tool can tailor for every application. If they are missing, you spend the first ten minutes after import fixing what the parser could not read.

Import Your CV

Get the CV right once, and the tool does the rest for every job. Import your CV and myCVpath reads each section into structured data you can reshape for any posting — a tailored version per application, drawn only from what is already true in your CV.