Recruitee mangles CVs because its parser struggles with common formatting quirks. The result: missing details, jumbled sections, and frustrated recruiters chasing clean data. This guide helps you diagnose the problem in 60 seconds and fix your Recruitee parsing errors fast.
TL;DR: Recruitee parsing errors usually come from tables, headers, or unusual fonts in CVs. Remove or simplify these elements before upload. Use a quick decision tree to spot the cause, fix the file manually or with a tool, and prevent future issues by standardising candidate CV submissions.
Quick diagnosis: Which Recruitee parsing error do you have?
Start here to pinpoint the issue fast. Follow this decision tree:
| Symptom | Likely Cause | Quick Check |
|---|---|---|
| Key fields missing (email, phone, name) | Hidden or complex headers | Open CV in Word, check header/footer |
| Sections merged or out of order | Tables or text boxes | Look for tables in CV |
| Strange characters or formatting broken | Non-standard fonts or special characters | Copy text into Notepad, check format |
| CV uploads but no data extracted | PDF scanned image or secured file | Try copy-pasting text from PDF |
| Partial parse, missing dates or job titles | Inconsistent date formats or abbreviations | Check date formats (e.g., Mar 2018) |
If you spot one or more of these, you know what to tackle next.
Root causes of Recruitee CV parsing issues (ranked by frequency)
Tables and text boxes Recruitee's parser flattens tables badly, mixing rows and columns into gibberish. Text boxes behave similarly, hiding content or scrambling it.
Headers and footers Candidate details often sit in headers or footers. Recruitee's parser skips these, losing key contact info.
Scanned PDFs or images If the CV is a scan or image PDF, Recruitee can't extract text, so it shows an empty or incomplete parse.
Non-standard fonts and symbols Fonts like Calibri Light or decorative symbols confuse Recruitee's text extraction, causing missing or garbled characters.
Inconsistent date formats Dates not in a clear format (e.g. "Mar 2018" vs "03/2018") sometimes disappear or jumble.
Password-protected or secured PDFs Any security setting on the PDF blocks parsing altogether.
Unusual file types or corrupted files Recruitee primarily supports .doc, .docx, and PDFs. Anything else risks failure.
Step-by-step fix for Recruitee parsing errors
Check the file type and content Open the CV in Word or Adobe Acrobat. If it's a scanned PDF, ask the candidate for an editable version or convert it with OCR software.
Remove tables and text boxes Convert tables to plain text or remove them. In Word: select table, right-click → Convert to Text. Delete text boxes or move content to body text.
Extract content from headers and footers Copy contact info from headers/footers into the main body of the CV.
Simplify fonts and remove special characters Change fonts to standard ones (Calibri, Arial). Remove emojis or symbols.
Standardise dates Use a consistent DD/MM/YYYY or MMM YYYY format.
Save as clean Word (.docx) or PDF Avoid password protection. Use "Save As" to create a fresh file without hidden metadata.
Test upload in Recruitee If the parse still fails, try copy-pasting text into a new document and save again.
How to prevent Recruitee parsing errors on future submittals
Set clear CV guidelines for candidates Request Word or PDF files without tables, text boxes, or headers/footers for contact details.
Use a CV standardisation step in your process Have recruiters or assistants run CVs through a simple clean-up before upload.
Educate hiring managers on parsing issues Explain why certain formatting looks better for ATS parsing.
Automate file checks where possible Tools like Distill can strip headers, remove tables, and normalise formatting before submission.
Avoid scanned CVs Request editable files or OCR-processed versions.
When to escalate to Distill
If your team spends more than a few minutes fixing each CV, or if you handle 20+ Recruitee submissions weekly, manual fixes aren't scalable.
Distill automates the process: it strips headers, removes tables, cleans fonts, and standardises dates before you submit. This reduces parsing errors dramatically and saves time.
Try it free if you want a quick, repeatable fix without training your team on complex manual clean-ups.
FAQ
Q: Why does Recruitee fail to parse contact details even when they are visible on the CV? A: Contact info often sits in headers or footers that the parser ignores. Copy these details into the CV body to fix it.
Q: Can Recruitee parse scanned PDFs? A: No. It needs selectable text. Use OCR software or ask candidates for editable versions.
Q: What's the best file format for Recruitee? A: Word (.docx) is best, followed by clean PDFs without security settings or scanned images.
Q: How do tables cause problems? A: The parser reads them as continuous text, merging unrelated data. Remove or convert tables to plain text.
Q: Does Distill integrate directly with Recruitee? A: Distill doesn't integrate natively but processes CVs before upload. You upload the cleaned file manually or automate via email workflows.
Fix it in 30 seconds with Distill — it removes tables, headers, photos, and graduation years that confuse Recruitee, leaving a clean CV ready for parsing every time. Try Distill free today.