Some resume parsers can struggle with complex tables or text boxes. Greenhouse documents both as possible parsing problems. This is a reason to test a layout, not evidence that every table always fails or that PDF and DOCX store text boxes in the same way.
Why a layout may be ambiguous
Visual alignment does not always establish logical reading order. A parser might interpret neighboring content differently from a person, and implementations differ. W3C’s PDF reading-order guidance explains why document structure deserves its own check.
Keep essential history clear
Avoid relying on a complicated grid to connect job titles, employers, dates and bullets. If extraction mixes those details, try a simple body-text layout. Removing a table’s visible border does not by itself change its underlying structure.
Check rather than diagnose by appearance
Copy text and inspect the actual imported fields when available. A missing summary or date alone does not prove that a text box caused the error. Compare a simplified file and record whether it resolves the observed problem.
- Keep role details visibly and structurally connected
- Check reading order in the exported file
- Compare a simpler version when extraction fails
- Correct application fields before submitting