Teamtailor auto-fills candidate profiles from uploaded CVs, and when parsing goes wrong you get half-empty profiles, jumbled sections, and manual re-keying. This guide shows you what breaks Teamtailor's parser and how to fix it.
TL;DR: Teamtailor parsing errors come from tables, hidden formatting, non-standard section headings, and image-based files. Use single-column layouts, standard headings, and clean text-based .docx or PDF files. Distill automates the cleanup if you process CVs at volume.
Quick diagnosis: why Teamtailor parsing fails
| Symptom | Likely cause | Quick check |
|---|---|---|
| Candidate name not extracted | Name in a header table or graphic | Is the name in plain body text? |
| Contact details missing/merged | Phone + email share a line | Are they on separate lines? |
| Sections jumbled or skipped | Non-standard headings or hidden styles | Does it say "My Story" instead of "Work Experience"? |
| Skills lumped together | Bulleted list flattened to a sentence | Are skills a list or a paragraph? |
| Profile mostly empty | Scanned or image-based PDF | Can you select the PDF text? |
What causes Teamtailor parsing errors most often
Tables and multi-column layouts Teamtailor's parser expects a top-to-bottom reading order. Tables and columns scramble it, and the header block — name and contact details — fails first.
Hidden formatting CVs exported from design tools or heavily styled templates carry invisible formatting that derails section mapping even when the CV looks clean.
Non-standard section headings "My Story" and "What I Bring" read nicely, but the parser maps sections by recognising standard headings like "Work Experience" and "Education".
Flattened bullet lists When a skills list arrives as a comma-separated sentence, Teamtailor reads it as one blob instead of separate skills.
Image-based files Scanned PDFs and photographed CVs contain no selectable text. The profile saves mostly empty.
Step-by-step fix for Teamtailor parsing errors
- Flatten the layout. Single column, no tables, name and contact block in plain text at the top.
- Rename creative headings to standard ones: Work Experience, Education, Skills.
- Stack contact details on separate lines, no symbols.
- Restore bullet points for skills and responsibilities.
- Re-save through a fresh .docx to strip hidden formatting from designed CVs.
- Confirm the file is text-based before upload.
- Re-upload and check the profile — name, contact, roles, skills all mapped.
How to prevent Teamtailor parsing errors
- Standardise incoming CVs to a single-column template before upload.
- Watch for design-tool exports; they look polished and parse worst.
- Batch-clean at volume with Distill rather than fixing profiles one by one.
- Keep a quick pre-upload check: columns, headings, contact lines, bullets, file type.
When to automate this
- You process 20+ CVs weekly through Teamtailor.
- Half-empty profiles are creating manual re-keying work.
- You also need candidate data anonymised before sharing shortlists.
Distill flattens layouts, standardises headings, restores structure, and outputs clean files tuned for Teamtailor — before you upload.
FAQ
Q: Why is Teamtailor missing the candidate's name? A: It's in a table, graphic, or styled header. Move it to plain body text.
Q: The CV looks fine but the profile parsed badly. Why? A: Hidden formatting from a design tool or styled template. Paste the content into a fresh .docx and re-upload.
Q: Skills came through as one long string. What happened? A: The list lost its bullets. Restore a proper bulleted list.
Q: Can Teamtailor parse a scanned CV? A: No — there's no selectable text. Convert it to a text-based file first.
Q: Does Distill integrate with Teamtailor? A: No direct integration. It cleans CVs before you upload them.
If Teamtailor keeps producing half-empty profiles, Distill cleans every CV to spec automatically. Try Distill free.