ResuAssist

Parsing Engine

Uses Textkernel for resume parsing

Supported Formats

Key Quirks

• Strips headers and footers from uploaded documents
• Ignores text embedded inside images entirely
• Multi-column layouts may get scrambled during parsing
• Prefers PDF format for most reliable parsing results

Tips

• Use a single-column layout for best compatibility
• Stick to standard section headings (Experience, Education, Skills)
• Avoid tables, text boxes, and embedded graphics
• Ensure all text is selectable, not rendered as an image

Parsing Engine

Proprietary parser

Supported Formats

Key Quirks

• Often requires manual re-entry of parsed fields by the applicant
• Keyword matching is strict and literal -- synonyms may be missed
• Uses AI-based screening in addition to keyword filters
• Prefers DOCX; may struggle with complex or image-heavy PDFs

Tips

• Match the exact job title from the posting in your resume
• Use standard date formats (MM/YYYY) throughout
• Avoid creative formatting, graphics, or unusual fonts
• Spell out abbreviations at least once before using the short form

Parsing Engine

Proprietary + Daxtra integration

Supported Formats

Key Quirks

• Strong keyword matching algorithm with high precision
• Parses contact information (phone, email, address) reliably
• Struggles with non-standard or heavily designed layouts
• Supports a wide range of file formats including RTF and TXT

Tips

• Include full URLs for your LinkedIn profile and portfolio
• Use keyword-rich professional summaries at the top of your resume
• Avoid abbreviations -- spell out terms in full for better matching
• Keep the layout simple and linear for optimal parsing accuracy

Parsing Engine

Proprietary Oracle parser

Supported Formats

Key Quirks

• Very strict formatting requirements -- deviations cause parsing errors
• Dates must follow an exact format or they may be misread
• Often loses or strips formatting during the upload process
• One of the oldest and least forgiving ATS parsers in use

Tips

• Use plain, minimal formatting with no design flourishes
• Spell out acronyms at least once (e.g., 'Search Engine Optimization (SEO)')
• Use standard section titles: Experience, Education, Skills, Summary
• Avoid headers, footers, page numbers, and watermarks

Parsing Engine

Own parser + Sovren

Supported Formats

Key Quirks

• Better at handling modern resume formats than older ATS systems
• Integrates with a Chrome extension for candidate sourcing
• Combines ATS and CRM functionality in a single platform
• More lenient with formatting but still prefers clean layouts

Tips

• A clean, well-structured PDF works best with Lever
• Keep your resume to 1-2 pages for optimal parsing
• Use reverse chronological order for experience sections
• Include your LinkedIn URL in the contact section

Parsing Engine

Basic built-in parser

Supported Formats

Key Quirks

• Simpler parsing engine compared to enterprise-grade ATS tools
• Keyword matching is less sophisticated -- relies on exact matches
• Primarily designed for HR management, with ATS as an added feature
• May miss contextual keywords that are not explicit matches

Tips

• Focus on exact keyword matches from the job description
• Use industry-standard terminology rather than creative titles
• Keep formatting straightforward -- simple bullets and headings
• Include a dedicated Skills section with specific tool and technology names

Parsing Engine

Built-in AI-powered parser

Supported Formats

Key Quirks

• AI-powered scoring considers context, not just exact keyword matches
• Supports synonym matching -- recognizes related terms automatically
• Modern parser that handles varied formatting better than legacy systems
• Candidate profiles are enriched with data from multiple sources

Tips

• Strong keyword coverage across your resume matters more than stuffing
• Include your LinkedIn profile URL in the contact information
• Use natural language -- the AI parser understands context and synonyms
• Quantify achievements with specific numbers, percentages, and metrics