You've just uploaded a candidate's resume to JobAdder. The system accepts the file. You open the candidate record and... it's almost empty. Maybe there's a name. Maybe a few random skills. But the work history? Gone. Education? Missing. The comprehensive three-page resume somehow produced a profile with almost nothing in it.
JobAdder is an excellent ATS—particularly popular in Australia, New Zealand, and increasingly in the UK and US markets. But its parsing engine has specific quirks that cause predictable failures. Understanding these quirks transforms random frustration into solvable problems.
Why JobAdder Parsing Fails
JobAdder's parser works differently from some competitors. Where Bullhorn might scramble table content, JobAdder is more likely to simply ignore content it can't confidently categorize. The result isn't mangled data—it's missing data.
The Header and Footer Problem
JobAdder's most notorious parsing issue involves headers and footers. Many professional resumes place contact information in document headers or footers—it's a clean design choice that keeps the main content area focused on experience and qualifications.
JobAdder often ignores header and footer content entirely.
If a candidate's name, email, phone number, and location are all in the header, the parsed profile might show "[Unknown Name]" with no contact details. Every field that should have been populated from header content remains empty.
This isn't a bug exactly—document headers and footers serve a different purpose in business documents (page numbers, confidentiality notices, document titles). JobAdder's parser assumes header/footer content isn't part of the resume's "real" information.
Section Header Recognition
JobAdder attempts to identify resume sections by recognizing common header text: "Experience," "Education," "Skills," "Employment History," "Qualifications."
When candidates get creative with section titles, recognition fails:
- "Where I've Worked" doesn't map to work experience
- "What I Know" doesn't parse as skills
- "My Journey" isn't recognized as employment history
- "Academic Background" might not register as education
The parser looks for specific terminology. Creative alternatives cause content to appear in wrong sections or not appear at all.
Text Extraction Limitations
JobAdder can struggle with PDFs that embed text in unusual ways. Just because you can select and copy text from a PDF doesn't mean the underlying encoding matches what an ATS parser expects.
Common extraction failures include:
- Text stored as paths/shapes rather than character data
- Embedded fonts with non-standard character mappings
- Multi-layer PDFs where text appears in unexpected layers
- Scanned documents without OCR text layers
When text extraction fails, JobAdder parses what it can—which might be fragments, might be nothing.
Formatting Complexity
Like most ATS systems, JobAdder handles simple formatting better than complex formatting. Single-column layouts parse better than multi-column. Standard fonts work better than decorative ones. Linear reading order succeeds where creative layouts fail.
The more visually impressive a resume looks, the more likely it is to parse incorrectly. That beautiful design that impressed the candidate in Canva becomes an empty profile in JobAdder.
Diagnosing JobAdder Failures
When a resume fails to parse correctly, quick diagnosis helps determine the fix.
Empty or Nearly Empty Profile
If virtually no information parsed:
- Check if contact info was in header/footer
- Open the PDF and try to select text (if you can't, neither can JobAdder)
- Look for obvious graphical elements replacing text
- Check if it's a scan without OCR
Partial Information Missing
If some sections parsed but others disappeared:
- Compare section headers to JobAdder's expected terminology
- Check if missing sections used creative formatting (text boxes, sidebars)
- Verify the reading order of multi-column layouts
Scrambled or Misattributed Data
If information parsed but appears in wrong places:
- Look for ambiguous visual layouts
- Check for tables causing reading-order issues
- Verify that section headers are clearly delineated
The Distill Solution
Distill's processing engine addresses every JobAdder parsing failure mode.
Header/Footer Normalization
When we process a document, we move content from headers and footers into the main document body. Contact information that would be ignored gets positioned where JobAdder expects to find it.
The candidate's design intention is preserved visually in the formatted output—we can still put contact info at the top of the page—but the underlying structure ensures parsing success.
Section Standardization
Creative section titles get mapped to recognized terminology. We understand that "My Journey" means work experience and "What I Bring" means skills. The output document uses conventional headers that JobAdder recognizes reliably.
Text Layer Optimization
For PDFs with text extraction issues, we rebuild the document with properly encoded text layers. The output is always ParseAble, regardless of how the input was constructed.
Layout Simplification
Complex multi-column layouts become clean single-column documents. The information hierarchy remains clear—more important content still appears more prominently—but the underlying structure is linear and unambiguous.
Workflow Integration
Pre-Processing All Uploads
The most reliable approach is processing every resume before it enters JobAdder:
- Candidate submits resume (any format)
- Resume is processed through Distill
- Optimized version uploads to JobAdder
- Parsing succeeds consistently
This workflow ensures no candidate suffers from parsing failures, regardless of their original resume format.
On-Demand Processing
When you encounter a specific failure:
- Retrieve the original resume file
- Process through Distill
- Delete the malformed JobAdder profile
- Upload the processed version
- Verify correct parsing
This takes about a minute versus the 5-10 minutes typically spent manually entering data from failed parses.
API Automation
For high-volume agencies, our API enables fully automated processing. Resumes are processed before human eyes ever see them, ensuring every document that reaches JobAdder is already optimized.
Best Practices for JobAdder Users
Database Hygiene
Regularly audit your JobAdder database for incomplete profiles. Search for records missing key fields—email, phone, work history. These often indicate parsing failures that went unnoticed.
When you find incomplete profiles, check if original files are available for reprocessing. Better to fix parsing retroactively than to have invisible candidates in your database.
Candidate Communication
When requesting resumes, include simple formatting guidance:
"Please ensure your contact information appears in the main body of your resume, not in headers or footers. Simple Word documents work best with our system."
This reduces (but doesn't eliminate) problematic submissions.
Quality Control
Implement a quick verification step after uploads:
- Upload resume to JobAdder
- Open candidate profile
- Quickly verify key fields populated (name, current employer, contact info)
- If fields are missing, reprocess and re-upload
This 30-second check catches failures immediately, before they disappear into your database.
JobAdder-Specific Optimization
When configuring Distill processing for JobAdder destinations:
Contact Information: Always positioned in document body, never in header/footer. Top of first page, clearly formatted, easy to parse.
Section Headers: Standardized terminology: "Work Experience," "Education," "Skills," "Summary." Clean, bold formatting for easy recognition.
Date Formats: Consistent format throughout (Month Year or MM/YYYY). JobAdder parses dates better when they follow predictable patterns.
Employment Records: Each position clearly delineated with company name, title, dates, and responsibilities in predictable order.
Layout: Single column. No tables for layout purposes. No text boxes for positioned content. Linear reading order.
The Broader Context
JobAdder parsing is one piece of your recruitment technology puzzle. Consider how document processing fits into your complete workflow:
Client Submission: Documents that parse correctly for JobAdder might still need additional formatting for client presentation—branding, confidentiality redaction, standardized layout.
Database Quality: Broader database hygiene extends beyond parsing. Duplicate records, outdated contact information, and incorrectly categorized candidates all reduce search effectiveness.
Candidate Experience: Candidates who experience frictionless application processes form better impressions of your agency. Smooth parsing is part of that experience.
Conclusion
JobAdder is a powerful platform—its parsing quirks don't diminish its value as your operational backbone. But understanding those quirks, and having tools to address them, dramatically improves your daily experience.
Empty profiles after upload are solvable problems. Header/footer issues have technical fixes. Section recognition challenges can be addressed through standardization.
Process your resumes through Distill before they reach JobAdder, and parsing becomes reliable, consistent, and invisible. Spend your time recruiting instead of troubleshooting.
Your JobAdder database should contain every candidate's complete information. Don't let parsing failures create holes in your data and gaps in your candidate coverage.