Pick a clean, single-column layout for a Documentation Writer. Use reverse-chronological order so your latest docs and tools appear first. That layout reads well and most ATS parse it reliably.
Keep it short. One page works if you have under 10 years of direct writing experience. Use two pages only when you have many relevant projects, standards, or publications to show.
Use simple, ATS-friendly fonts like Calibri, Arial, Georgia, or Garamond. Set body text to 10–12pt and headers to 14–16pt. Keep line spacing around 1.0–1.15 and add clear margins to create white space.
Use clear section headings such as Summary, Experience, Projects, Tools, and Education. List tools and formats you use, like Markdown, DITA, XML, Git, and CMS, in a short bullet list.
Avoid complex columns, images, text boxes, and unusual fonts. Those elements often break ATS parsing and make your document hard to scan. Use bold and italics sparingly to guide the reader.
Common mistakes include long dense paragraphs, inconsistent spacing, and unclear dates. Also avoid generic headers like "Responsibilities" without achievements. Show measurable outcomes like reduced support tickets or faster onboarding time when possible.
Keep language concise and use action verbs. Start bullets with verbs like "wrote," "structured," "reduced," and "standardized." Use consistent date formats and align text with left justification for easy scanning.