Resume parsing is a core feature in PyjamaHR, enabling you to quickly extract candidate information from uploaded CVs and streamline your hiring process. However, users sometimes encounter errors such as "Resume not found," missing candidate details, or failed uploads—especially when importing from job boards like Naukri, LinkedIn, or Indeed. This guide provides a comprehensive, actionable approach to diagnosing and resolving parsing errors, ensuring your candidate data is always complete and accessible.

Resume parsing in PyjamaHR automatically extracts structured candidate data (name, email, education, experience, etc.) from uploaded CVs, whether added manually, via Chrome extension, or imported from job boards. Parsed data powers features like keyword search, resume match scoring, and candidate comparison.

When and Why Use Resume Parsing?
- Bulk candidate uploads (e.g., from Naukri, LinkedIn, Indeed)
- Manual candidate addition for direct applications or referrals
- Automated candidate screening and search

Integration with Other Features:
- Keyword Search: Relies on parsed data for accurate results
- Resume Match Score: Requires successful parsing to calculate fit
- Candidate Comparison & Data Export: Only works with parsed fields

Business Impact:
- Faster shortlisting and screening
- Reduced manual data entry
- Improved candidate experience

Screenshot Callout:
- Show the "Upload Resume" button and progress indicator.

Note:
- If the resume is missing on the job board, parsing will fail and you’ll see "Resume not found".

Screenshot Callout:
- Bulk upload dialog and upload summary with error indicators.

Do:
- Share problematic resumes with support for faster resolution.
- Use screen recordings or screenshots when reporting issues.
- Check the "Rejected" pipeline for missing candidates.

Don’t:
- Upload image-only PDFs or scanned documents (these cannot be parsed).
- Expect parsing to work with resumes missing key sections (name, email, etc.).
- Rely on job board imports if the resume is not attached.

Cause:
- Resume file was not attached during import (common with LinkedIn/Indeed).
- Candidate profile on job board lacks a downloadable CV.

Solution:
- Ask the candidate to send their resume directly.
- Manually upload the resume via the candidate profile.

Cause:
- Resume format is non-standard or fields are not clearly labeled.
- Email address is improperly formatted (e.g., no space after numbering).

Solution:
- Edit the resume to ensure clear section headers and proper email formatting.
- Re-upload the corrected resume.

Cause:
- Some files are corrupted, password-protected, or in unsupported formats.
- Large batch uploads may take longer; some files may time out.

Solution:
- Check the upload summary for failed files.
- Re-upload failed resumes individually after checking formatting.

Cause:
- Parsing failed, so candidate profile was not created.
- Candidate is in the "Rejected" pipeline or filtered out.

Solution:
- Check all pipelines, including "Rejected".
- Search by email ID to locate the candidate.
- Re-import or manually add the candidate if missing.

Cause:
- Resume parsing failed, so keywords are not indexed.
- Resume format issues prevent extraction of relevant data.

Solution:
- Re-upload the resume in a standard format.
- Ensure key information is present and clearly labeled.

Cause:
- Candidate profile was not created due to parsing failure.
- Candidate was deleted or moved to a different pipeline.

Solution:
- Re-upload the resume.
- Check all pipelines for the candidate.

What to Provide:
- The problematic resume file(s)
- Screenshots or screen recordings of the error
- Job ID or candidate profile link

1. Why does PyjamaHR show "Resume not found" after importing from LinkedIn/Indeed?
Because the candidate profile on the job board did not include an attached resume. You must upload the resume manually.

2. Why are some candidate details (email, education, etc.) missing after upload?
The resume format may be non-standard, or key fields are not clearly labeled. Edit and re-upload the resume.

3. Can I upload scanned or image-only PDFs?
No. Only text-based PDFs, DOC, or DOCX files can be parsed.

4. Why do some resumes upload but parsing fails for others in the same batch?
Some files may be corrupted, password-protected, or in unsupported formats.

5. How do I fix "Job candidate not found" when rejecting or moving a candidate?
Check if the candidate profile exists and is in the correct pipeline. Re-upload if missing.

6. Why is keyword search not working for certain candidates?
Parsing failed for those resumes, so keywords were not indexed. Re-upload with a standard format.

7. What should I do if parsing is slow or stuck on "parsing in progress"?
Large batches may take time. If stuck for over 30 minutes, contact support with the affected files.

8. How do I ensure resumes are parsed correctly?
Use simple, text-based formats with clear section headers and proper email formatting.

9. Can I edit parsed candidate details if something is wrong?
Yes, you can manually edit candidate profiles after upload.

10. What if I see blank candidate profiles after import?
Parsing likely failed. Re-upload the resume after checking formatting.

11. Why are some candidates missing from the Talent Pool after import?
Parsing failed or candidates are in the "Rejected" pipeline. Check all pipelines and re-import if needed.

12. What if I see "parsing failed" but the resume looks fine?
Share the resume with support for further investigation.

Recommended Articles:
- Importing Candidates from Naukri
- Importing Candidates from Indeed
- Troubleshooting Chrome Extension Issues

Still need help?
Contact PyjamaHR Support with the problematic resume, error screenshots, and job/candidate details for priority assistance.

By following this guide, you can resolve most resume parsing errors in PyjamaHR and ensure your hiring workflow remains smooth and efficient.