Quick rules
Build the “portal version” as a simple DOCX-first resume (then export PDF if needed).
- One column. No tables, text boxes, icons, or graphics.
- Contact info in the document body (not header/footer).
- Standard headings: Summary, Experience, Education, Skills.
- Keep formatting simple: bold is fine; avoid fancy shapes and “designed” templates.
Why DOCX? Many ATS workflows parse DOCX reliably. Keep a clean DOCX handy even if you prefer to share a PDF for networking.
Copy/paste template
Template (replace brackets)
FIRST LAST City, State | (555) 555-5555 | name@email.com | linkedin.com/in/username | portfolio.com SUMMARY [Target role title] with [X] years in [domain]. Strengths: [skill], [skill], [skill]. Known for [proof: metric/impact]. SKILLS Tools: [Tool], [Tool], [Tool] Methods: [Method], [Method] Domains: [Domain keyword], [Domain keyword] EXPERIENCE Job Title — Company, City, State Month YYYY – Month YYYY (or Present) - [Action verb] + [what you did] + [tool/method] + [metric] + [why it mattered]. - [Action verb] + [scope: users/revenue/team size] + [result]. Job Title — Company, City, State Month YYYY – Month YYYY - [Action verb] + [what] + [metric] + [result]. EDUCATION Degree, School — City, State Month YYYY (or Year) PROJECTS (optional) Project Name — Tech/Tools - What you built + outcome (metric if possible). CERTIFICATIONS (optional) Certification — Issuer (Year) ADDITIONAL (optional) Work authorization: [US Citizen / etc.] Languages: [Language — level]
Section options (choose what fits)
If you’re entry-level
Put Projects higher (often right after Skills) and include class projects if they match the job.
If you’re mid/senior
Keep Skills short and let Experience bullets carry keywords + proof metrics.
If you have publications (rare for resumes)
Include a short Selected Publications section only if relevant to the role; otherwise use a CV.
Before you upload (QA checklist)
Fast QA
- Paste test: copy/paste into Notepad—order stays correct.
- No columns, tables, text boxes, icons, images, headers/footers for critical info.
- Standard headings: Summary, Experience, Education, Skills.
- Dates are consistent (Month YYYY – Month YYYY).
- You have a DOCX version and a text-based PDF version ready.
Sources
- MIT CAPD: “Make your resume ATS-friendly” (avoid tables/text boxes/graphics; simple formatting). View source
- Greenhouse Support: “Supported formats for resumes…” (accepted DOC/DOCX/PDF/RTF/TXT for candidate uploads). View source
- Greenhouse Support: “Unsuccessful resume parse” (common formatting issues: columns, tables, headers/footers, text boxes). View source