To make a resume in Google Docs that passes ATS screening, start from a blank page or simple template, set one-inch margins and standard fonts, build single-column sections with plain headers, write bullet lines with keywords, export as a text-based PDF, and test parsing in Workday or Greenhouse before you apply.
Google Docs is one of the fastest ways to build a job-ready resume without paying for design software. The catch: many template gallery layouts look polished on screen yet scramble contact fields, dates, and bullet order when you upload to corporate portals running Workday, Greenhouse, iCIMS, or Lever. This guide walks through every setup decision—margins, fonts, headings, bullets, and PDF export—so your finished file parses cleanly and still reads clearly for recruiters.
Key Takeaways
- Start blank or strip decorative templates down to a single column before you write
- Keep contact info in the document body—not only in the Google Docs header area
- Use Heading styles for section titles so parsers and screen readers map structure
- Export with File → Download → PDF Document; avoid browser print-to-PDF shortcuts
- Test the PDF in Workday, Greenhouse, or an ATS checker before every serious upload
Why Google Docs works for ATS-safe resumes
Corporate recruiters receive thousands of applications through applicant tracking systems. Those platforms extract plain text from your upload and map it into fields—name, phone, employer, dates, degree. Google Docs outputs standard document structure that parsers handle well when you avoid layout tricks:
- Free access with any Google account—no subscription required to start applying
- Real-time collaboration if a career coach or CPRW reviews your draft
- Version history so you can recover a clean copy after a bad paste from LinkedIn
- Native PDF export that preserves selectable text when settings stay simple
- Cross-device editing from laptop, tablet, or phone before a deadline
Google's own documentation confirms PDF downloads preserve document text for sharing and printing. See Google Docs help on downloading files as PDF for the official export path—File → Download → PDF Document—not screenshots or third-party converters that flatten fonts.
The limitation is not Google Docs itself but how candidates format inside it. Multi-column templates, skill percentage bars, and icons from the gallery photograph well on social media yet fail silently in Taleo and SuccessFactors. Building with parser rules in mind from line one saves a reformatting weekend later.
Key Takeaway: Google Docs is ATS-compatible when formatting stays plain—treat design restraint as a feature, not a compromise.
Step 1: Start from blank or pick a simple template
Open Google Docs and choose your starting point:
- Blank document: maximum control; best when you already know section order and want zero cleanup
- Template gallery: File → New → From template gallery → Resumes—pick the plainest layout with one column and no graphics
- Duplicate a master: keep one master resume in Drive; copy it per application and tailor keywords without rebuilding structure
If you select a template, delete elements parsers hate before you type a single bullet:
- Table-based contact rows split across cells
- Side-by-side columns for skills and experience
- Progress bars, star ratings, or chart objects for skill levels
- Text boxes or drawing objects floating over the page
- Profile photo placeholders—US corporate ATS workflows rarely expect images
CareerOneStop, sponsored by the U.S. Department of Labor, recommends clear structure and readable layout in application materials. Their resume guidance stresses matching content to employer needs—your template choice should serve that goal, not showcase design skills. Review CareerOneStop resume resources while you outline sections so you include what US hiring managers expect: contact, summary or headline, experience, education, and skills.
| Starting option | Best for | ATS risk |
|---|---|---|
| Blank document | Full control, career pivots, technical resumes | Lowest when you follow this guide |
| Minimal gallery template | First-time builders who want spacing presets | Low after removing tables and columns |
| Designed gallery template | Visual portfolios—not corporate ATS uploads | High in Workday, iCIMS, and Taleo |
| Pasted from Word or PDF | Migrating an old file quickly | Medium—hidden styles may break sections |
Key Takeaway: spend ten minutes cleaning a template before you write— deleting a table now beats rebuilding after a failed Greenhouse upload.
Step 2: Set margins, fonts, and page layout
Page setup drives whether your resume fits one page and whether parsers read lines in order. In Google Docs, open File → Page setup:
- Margins: 1 inch top, bottom, left, right (default). Avoid 0.5 inch unless you have 10+ years and a second page is already justified
- Page size: Letter (8.5 × 11 in) for US employers; switch to A4 only when applying abroad
- Orientation: Portrait—landscape resumes rarely parse and annoy recruiters printing files
- Font: Arial or Calibri 11 pt body; 14–16 pt bold for your name; 12–14 pt bold for section headers
- Line spacing: 1.0 or 1.15 within entries; add 6–10 pt space after section headers for scanability
Google's editor uses standard paragraph styles. Select Normal text for bullets and Heading 2 for section titles (Experience, Education, Skills). Parsers and accessibility tools rely on those tags more than font size alone. A line typed in 14 pt bold without a Heading style may merge into the previous paragraph when iCIMS extracts text.
Color: black text on white background. Subtle gray for dates is acceptable; neon accents, background fills, and watermark shapes add noise without helping keyword matching. If you copy content from a website or PDF, use Edit → Paste without formatting (Ctrl+Shift+V on Windows, Cmd+Shift+V on Mac) so foreign fonts do not linger invisibly.
For export-specific settings that survive Workday uploads, cross-check Google Docs resume export ATS-safe settings after you finish layout—margin and font choices here should match that checklist before you download the PDF.
Key Takeaway: one-inch margins, Arial 11 pt, and Heading styles form the baseline almost every US corporate ATS expects.
Step 3: Build contact block and section headers
Type structure top to bottom in a single column. Do not put your phone number only in Insert → Headers & footers—Workday and Lever often skip header content on import.
Contact block (first lines of the body):
- Full name on line one, 16–18 pt bold
- Target title or headline on line two (optional but helps keyword matching)
- City, State · phone · professional email · LinkedIn URL on one or two lines
- Portfolio or GitHub only when relevant to the role—plain URLs, no button graphics
Standard section order for US corporate applications:
- Summary or Professional Summary (2–4 lines)
- Experience or Work Experience
- Education
- Skills (grouped: technical, certifications, languages)
- Certifications or Licenses (if not folded into Skills)
Apply Heading 2 to each section title. Under Experience, format each role as:
- Job title | Employer name | City, State | Jan 2022 – Present
- 3–5 bullet lines underneath using the built-in bullet list button
Use consistent month-year dates (Mar 2024 – Aug 2026). Mixed formats—2024, 03/24, March '24—on the same resume confuse parsers mapping employment timelines in SuccessFactors and BambooHR. Spell employer names exactly as they appear on LinkedIn and W-2 forms so background checks align later.
Align with Workday resume format guidance for 2026 even if you apply through Greenhouse—the same plain labels (Experience, Education, Skills) reduce parsing variance across platforms.
Key Takeaway: contact info belongs in the body; section headers should use Google Docs Heading styles, not manual bold alone.
Step 4: Write bullets and skills that ATS can rank
Bullets carry most keyword weight. In Google Docs, click the bullet list icon or type * then space to start a line—do not fake bullets with hyphens and tabs; parsers read those as paragraphs, not list items.
Each strong bullet should include:
- Action verb tied to the skill the posting names
- Method or tool (Salesforce, GAAP, Python, Six Sigma)
- Scale (team size, budget, user count, territory)
- Outcome with a number when possible (%, $, time saved, error rate)
Skills section: group related items instead of a 40-word comma string. Example: Technical: SQL, Tableau, Snowflake · Certifications: PMP, AWS SAA · Languages: Spanish (professional). Mirror exact phrases from the job description where you have evidence in bullets—Greenhouse match scores compare parsed resume text to the posting.
Avoid keyword blocks in white font, invisible text, or repeating the same term fifteen times. Recruiters flag stuffing; some ATS configurations penalize duplicate tokens. One mention in summary plus one in a recent bullet beats ten orphaned repeats in Skills.
Google Docs resume build checklist
- Blank or stripped template—single column, no layout tables
- One-inch margins, Letter size, Arial or Calibri 11 pt
- Contact block in body: name, city, phone, email, LinkedIn
- Heading 2 on Experience, Education, Skills
- Month-year dates consistent on every role
- Real bullet lists—not dashes, tabs, or numbered paragraphs
- Skills grouped with proof in experience bullets
- PDF exported via File → Download → PDF Document
- Text selectable in PDF; filename includes your name and role
Key Takeaway: use Google Docs list formatting for every achievement line—fake bullets are a top reason Lever misorders experience entries.
Before-and-after bullet rewrites in Google Docs
When you make a resume in Google Docs, paste-ready lines from old job descriptions waste space. Rewrite duties into outcomes as you type:
Customer support specialist
- Answered phones and helped customers with problems
- Resolved 45+ Zendesk tickets daily at 94% CSAT; cut average handle time 12% by documenting top fixes in a shared Google Doc playbook for tier-1 agents
Financial analyst
- Responsible for reports and budgeting tasks
- Built monthly variance models in Excel for $18M OPEX portfolio; presented forecast accuracy within 2% to CFO staff and supported SAP cost-center realignment
Project coordinator
- Coordinated meetings and tracked project status
- Ran weekly standups for 3 cross-functional workstreams; delivered 14 releases on schedule by maintaining Smartsheet RAID logs and escalating blockers within 24 hours
HR generalist
- Handled onboarding and employee questions
- Onboarded 120 hires in 2025 through Workday HCM; reduced time-to-productivity 20% by standardizing day-one checklists and benefits orientation slides in Google Drive
Type these directly as bullet lists in Google Docs—do not paste from a formatted PDF or the bullets may split across lines when exported. If sections look merged after paste, follow how to fix broken resume sections after copying from Google Docs before you download the final PDF.
Key Takeaway: write bullets natively in Docs—pasting formatted content is the fastest way to break iCIMS section mapping.
Step 5: Export to PDF without breaking ATS parsing
Your Google Docs resume is not finished until the PDF survives upload. Use the official export path:
- File → Download → PDF Document (.pdf)
- Open the file locally and try to highlight a single word in each section
- Confirm contact lines, dates, and employers appear in reading order
- Rename: FirstName-LastName-Role-Resume.pdf
- Upload to the employer portal or run a parser check before you submit
Avoid these export mistakes:
- Browser Print → Save as PDF (can rasterize or reorder content)
- Third-party "free PDF converter" sites that re-encode fonts
- Sharing a view-only Docs link when the application requires file upload
- Password-protected PDFs—ATS cannot open them
- Scanning a printed copy back to PDF—OCR garbles keywords
Google's support article on downloading Docs as PDF notes that PDF preserves layout for viewers; your job is to keep that layout simple so preserved layout equals preserved parse order. Detailed export toggles live in our ATS-safe Google Docs export guide .
After export, run the PDF through HireFlow's free ATS resume checker to see which fields parsers extract—phone, employers, and dates should populate before you trust a Workday or Greenhouse application.
Key Takeaway: File → Download → PDF Document is the only export path you should use for corporate applications.
Pitfalls that break Google Docs resumes in iCIMS, Lever, and Workday
Platform behavior varies, but the same formatting errors show up repeatedly when candidates build in Google Docs and upload to enterprise ATS:
- Workday: drops contact fields when they sit in tables or document headers; single-column body text parses best
- Greenhouse: handles standard bullets well; struggles with text boxes, floating images, and multi-column sections
- iCIMS: sensitive to pasted Word styles—sections merge and dates attach to wrong employers; use Paste without formatting
- Lever: keyword search across flat text; skill bars and icons do not contribute keywords—plain lists do
- Taleo: mangles table layouts; never use tables for alignment—use tabs sparingly or line breaks only
- SuccessFactors: expects standard labels; creative headers like "Where I've Made Impact" map to uncategorized text buckets
If a portal offers a parsed preview after upload, read every field. Missing phone numbers and scrambled job titles are fixable in Google Docs before you resubmit—do not assume the recruiter sees your designed layout. Many hiring managers never open the PDF; they read the ATS profile built from parsed text.
Copy-paste between Google Docs and employer text fields can strip bullets entirely. Keep a plain-text version of bullets in a separate note if you must paste into long online forms. When sections break after an export, use our broken sections fix guide to rebuild structure without starting over.
Tailor a copy per application: duplicate the Doc, adjust summary keywords, reorder bullets, save a new PDF. Identical generic uploads underperform in Lever pipelines when match scores compare your text to specialized posting language.
Key Takeaway: test uploads per platform behavior—formatting that survives Greenhouse may still lose headers in Workday if contact info sits in the wrong place.
Final review before you apply with your Google Docs resume
Walk through this ten-minute QA pass after you export:
- Search the PDF for three must-have keywords from the posting
- Read the summary aloud—awkward phrasing signals recruiter skim risk
- Confirm every date uses the same month-year pattern
- Click LinkedIn and portfolio URLs from the PDF to verify they resolve
- Check page count—one page for most roles unless depth justifies two
- Run the file through an ATS checker and fix empty parsed fields
Store your master Google Doc in Drive with version history enabled. Label tailored copies by employer and date so you know which PDF a recruiter references six weeks later. Building in Google Docs is fast; discipline in naming and versioning prevents duplicate applications with outdated summaries.
When you are ready to apply at scale, keep one ATS-safe master and branch tailored exports—not forty separate Docs with drifting formats. The master holds proof bullets; each branch adjusts keywords for Workday, Ashby, or Jobvite uploads without redesigning margins and fonts every Sunday night.
Key Takeaway: a short QA pass after PDF export catches parsing failures that hours of writing cannot fix retroactively.
Frequently asked questions
Yes. Google Docs is free with a Google account and includes resume templates under File → New → From template gallery. For ATS uploads, start from a simple template or blank document—avoid multi-column designs with icons, charts, or heavy graphics that break parsing in Workday or iCIMS.
Use Arial, Calibri, Georgia, or Times New Roman at 10–12 pt for body text and 14–16 pt for section headers. Google Docs supports these fonts natively, and corporate ATS platforms parse them reliably. Decorative script or narrow condensed fonts often scramble on import to Taleo or SuccessFactors.
Set one-inch margins on all sides (File → Page setup). Tighter margins squeeze content but can clip text when employers print or when parsers misread edge-aligned contact rows. Half-inch margins are acceptable for two-page technical resumes when every line earns space.
Use File → Download → PDF Document (.pdf). Do not print to PDF through a browser extension—that can rasterize text. Before upload, open the PDF and confirm you can highlight individual words; if not, the file may fail keyword search in Greenhouse or Lever.
Google Docs produces ATS-compatible files when you follow plain formatting rules: single column, standard headers, real bullet characters, no tables for layout, and contact info in the body—not only in the header area. Design-heavy templates from the gallery often fail parsing even when the content is strong.
Either works if the result stays single-column and minimal. Templates save time on spacing but frequently include tables, skill bars, or two-column contact rows. Strip those elements or start blank with one-inch margins and Heading styles for section titles.
Common failures include pasting from Word with hidden formatting, using tab stops instead of bullets, placing phone and email in the document header, multi-column layouts, and exporting through print drivers that flatten text. Copy-paste errors also merge section headers with body lines—fix broken sections before you re-upload.
One page for early-career and most corporate roles; two pages when you have 10+ years of directly relevant experience or deep technical scope employers expect. Google Docs makes it easy to overflow—trim weak bullets instead of shrinking fonts below 10 pt, which recruiters struggle to read on screen.