How to Improve CV Parsing Results – A Sprint CV Tutorial

Summarize this post with AI

When dealing with consultants’ CVs, one common issue is the variety of formats they may come in. Whether consultants use predefined templates, build their CVs from scratch, or follow personal formatting preferences, importing these CVs into Sprint CV can sometimes be tricky. The parser may struggle with inconsistent formats, leading to missing or incorrectly categorized information, among other issues. In this blog post, we’ll discuss some of the most common problems you may encounter when importing CVs into Sprint CV, and how to improve your CV parsing results.

1. How to Improve CV Parsing Results – uncommon CV Formats

Consultants often submit their CVs in various formats. These could range from professionally designed templates to custom formats that suit their personal preferences. This variability can make it difficult for our parser to accurately read and categorize information, especially if the formatting contains mistakes or unconventional structures.

Fix: Use LinkedIn Profiles Instead

A straightforward way to avoid these issues is to use consultants’ LinkedIn profiles. LinkedIn exports come with consistent formatting, which allows the parser to work more accurately. Moreover, consultants tend to keep their LinkedIn profiles updated with their most recent experience, ensuring you’re working with the latest information.

How to Improve CV Parsing Results - Using Linkedin profiles
Using a candidate’s LinkedIn profile can lead to more accurate results

However, some consultants might not grant access to their LinkedIn profiles, or they may not have one. In such cases, there are additional troubleshooting methods to ensure smooth CV imports. They will involve having access to the CV in DOCX format, so that you can edit it. If the CV is in PDF, you can always convert it to DOCX and edit it as well.

Keep in mind that you can create multiple profiles for the same consultant without overwriting the original one. This allows you to upload new CVs to a new profile within the consultant’s profile manager and explore various troubleshooting solutions or translate and update profiles if they are accurate.

2. How to Improve CV Parsing Results – Title Inconsistencies

Titles are key to how our parser organizes information. It uses these titles to identify and classify sections of the CV (e.g., “Summary,” “Professional Experience,” “Education”). However, problems can arise when titles deviate from expected standards.

Common Title Issues:

  • Titles in Another Language: If the CV contains non-English titles, the parser might not recognize them. For example, using “Sumário” (Portuguese) instead of “Summary” could lead to missing information in the imported CV.
How to Improve CV Parsing Results - Issues with titles in another language
A CV with the title of a section in another language can cause issues.
  • Incorrect or Unconventional Titles: Some consultants may use custom section titles that don’t align with industry standards or are vague. For instance, if a consultant writes “Introduction” instead of “Summary,” the parser may skip the section entirely.
How to Improve CV Parsing Results -  different titles.
Users should use “Summary” instead of titles like “Introduction”

This type of problem will often lead to the Summary section being empty at the consultant’s page on Sprint CV:

How to Improve CV Parsing Results - Sprint CV output with wrong titles.
Using titles in another language or incorrect ones can make the parser miss the information.

Fix:

Ensure that consultants use standard titles for sections. If that’s not possible, manually reviewing and editing titles before importing can help the parser categorize sections correctly.

How to Improve CV Parsing Results - Correct version of the titles.
As a good practice, use “Summary” in English.

Afterwards, our parser will import the information accurately, displaying it on the consultant’s dashboard under the Summary section.

How to Improve CV Parsing Results - Correct Sprint CV output.
The parser will get all the information with this guideline.

3. How to Improve CV Parsing Results – Professional Experience

Another issue that commonly arises is how dates are formatted in the consultant’s work history. The parser relies on standard date formats to accurately record periods of employment, but some CVs may omit these or represent them in non-standard ways.

Common Date Issues:

  • Missing Dates: Instead of specifying the start and end dates (e.g., 2016–Present or 2012–2014), some consultants simply list the number of years they have worked in a role. This can cause the parser to either skip these entries or fail to import them correctly.
How to Improve CV Parsing Results - Issues with dates on the Professional Experience.
Sometimes, candidates use the number of years instead of dates.
How to Improve CV Parsing Results - Sprint CV wrong input in the Professional Experience.
Using number of years leads to the parser missing the information.

Fix:

Encourage consultants to use standard date formats for their professional experience. If dates are missing or unclear, manually adding them before importing can ensure complete data capture.

Correct version of the Professional Experience.
Substitute the number of years with dates, as shown here
Correct version of Sprint CV's output of the Professional Experience.
The parser will get all the Professional Experience.

4. How to Improve CV Parsing Results – Order of the Sections

The order in which sections appear in a CV can sometimes confuse the parser. For example, a consultant may include a table of skills with associated years of experience, but if this is positioned incorrectly or formatted in a non-standard way, the parser might mistake it for professional experience, leading to errors.

A table that gives issues.
In this example, the candidate used their skills’ experience.
Output at Sprint CV with issues.
The parser confused the skills with the professional experience.

Fix:

Ensure that the CV follows a logical structure, with standard sections (Summary, Experience, Skills, Education) placed in the expected order. If necessary, rearranging the CV before importing can help the parser accurately interpret the document.

5. How to Improve CV Parsing Results – Language Proficiency

Describing language proficiency is another area where inconsistencies can lead to problems during import. Different CVs may use various descriptors for language skills, making it difficult for the parser to categorize them correctly.

Common Language Problems:

  • Non-standard Descriptions: Some consultants may use informal or non-standard descriptions of their language proficiency, which the parser may not recognize.
Incorrect description of Language levels.
Incorrect description of fluency.
Wrong language output at Sprint CV.
The parser assumes that the user has an elementary level in all languages.

Fix:

Advise consultants to use standard language level descriptors, such as those found on LinkedIn or the Europass framework (e.g., “Native,” “Fluent,” “Intermediate”/ B1, A2, C1, etc.). These standardized terms are easier for the parser to process and categorize correctly.

Correct Language description.
Use the standardized descriptions.

6. Bonus: Changing Training, Education, and Certifications sections

It’s not uncommon for consultants to mix up sections related to training, education, and certifications. When this happens, the parser may incorrectly categorize information or miss it entirely.

Common Issues:

  • Confusion Between Sections: If the consultant lists certifications under education or vice versa, the parser might place the information in the wrong section.

Fix:

If you notice that training, education, or certification entries are miscategorized after importing, manually editing these sections can ensure the correct placement of information.

Converting training to education.
You can change the category when the parser makes an error.

Conclusion

While importing CVs into Sprint CV can sometimes present challenges, especially when dealing with varying formats, following these troubleshooting tips can help minimize issues. Whether you choose to use a consultant’s LinkedIn profile or carefully review and standardize their CV, ensuring consistency will allow the parser to work more effectively. When all else fails, taking the time to manually correct key details can save you from larger problems down the line.

Watch our video tutorial on CV parsing results here:

If you notice another kind of issue when importing CVs, don’t hesitate and reach out to us!

Share this post

You may also like

A consulting company wins three new clients in a quarter. Revenue goes up, and so does the number of CVs to prepare, translate, tailor and keep current. Recruiters spend more time formatting, sales spends more time chasing documents, and the bid team works later every week. CV administration has quietly

Two consultants from the same company are submitted to the same client. One CV is in the current corporate template with a clear skills summary. The other is in a layout from three years ago, with half the detail and a different logo. CV standardisation looks settled on paper and

A large opportunity is announced, and the first question in the room is simple: how many of our consultants could we put forward this week? Nobody knows. CV readiness is one of the few operational numbers most leadership teams cannot see until a deadline forces someone to count. This post