Modern Minimal resume template for Google Docs™
No lines or boxes, just white space and quiet slate-blue headings. Looks modern without anything a parser can trip on.
- Parser read 31/31 fields
- 1 page
- US Letter and A4
- Google Docs and Word
- Verdana
What a parser reads from it
Field by field, from the PDF that Google Docs exports.
31/31
fields read correctly from the resume (US Letter), downloaded from Google Docs as a PDF and read by the open-source OpenResume parser (commit 4f8255a) on Oct 5, 2026.
What the parser read
First 30 lines, exactly as extracted.
Maya Lindqvist Denver, CO | (720) 555-0137 | maya.lindqvist@example.com | linkedin.com/in/mayalindqvist SUMMARY Product manager with four years in scheduling and payments software. I work closely with design and engineering, talk to customers every week, and like features that are small enough to ship in a month and measure in the next one. EXPERIENCE Product Manager Mar 2023 – Present Tarrowfield Software Denver, CO • Own scheduling and shift swaps for about 3,000 hourly teams • Cut unfilled shifts by 18% by adding swap requests and reminders after interviewing 40 store managers about why shifts went empty • Run quarterly planning with two engineering teams and a designer • Wrote the team's first product metrics guide, so every launch now ships with a named success measure and a review date Associate Product Manager Jun 2020 – Feb 2023 Ferncastle Payments Denver, CO • Launched saved cards for repeat customers; checkout time fell by a third • Ran 25 A/B tests on the payment page and kept a public log of every result • Handled the product side of a card network change on a fixed deadline Business Analyst Jul 2018 – May 2020 Gorseholt Distribution Aurora, CO • Built weekly order reports in SQL and Excel for 12 warehouse managers • Wrote requirements for a new returns process that reduced manual data entry EDUCATION Pinyon Draw University Boulder, CO Bachelor of Science in Information Systems May 2018 SKILLS Product: Roadmaps, customer interviews, A/B testing Tools: Jira, Figma, Amplitude, SQL, Looker
Field by field
What we wrote, and what the parser put in each field.
| Field | Parser read | Match |
|---|---|---|
| Name | Maya Lindqvist | |
| maya.lindqvist@example.com | ||
| Phone | (720) 555-0137 | |
| Location | Denver, CO | |
| Link | linkedin.com/in/mayalindqvist | |
| Summary | Product manager with four years in scheduling and payments software. I work closely with design and engineering, talk to customers every week, and like features that are small enough to ship in a month and measure in the next one. | |
| Job 1 company | Tarrowfield Software | |
| Job 1 title | Product Manager | |
| Job 1 dates | Mar 2023 – Present | |
| Job 1, bullet 1 | Own scheduling and shift swaps for about 3,000 hourly teams | |
| Job 1, bullet 2 | Cut unfilled shifts by 18% by adding swap requests and reminders after interviewing 40 store managers about why shifts went empty | |
| Job 1, bullet 3 | Run quarterly planning with two engineering teams and a designer | |
| Job 1, bullet 4 | Wrote the team's first product metrics guide, so every launch now ships with a named success measure and a review date | |
| Job 2 company | Ferncastle Payments | |
| Job 2 title | Associate Product Manager | |
| Job 2 dates | Jun 2020 – Feb 2023 | |
| Job 2, bullet 1 | Launched saved cards for repeat customers; checkout time fell by a third | |
| Job 2, bullet 2 | Ran 25 A/B tests on the payment page and kept a public log of every result | |
| Job 2, bullet 3 | Handled the product side of a card network change on a fixed deadline | |
| Job 3 company | Gorseholt Distribution | |
| Job 3 title | Business Analyst | |
| Job 3 dates | Jul 2018 – May 2020 | |
| Job 3, bullet 1 | Built weekly order reports in SQL and Excel for 12 warehouse managers | |
| Job 3, bullet 2 | Wrote requirements for a new returns process that reduced manual data entry | |
| School 1 | Pinyon Draw University | |
| School 1 degree | Bachelor of Science in Information Systems | |
| School 1 dates | May 2018 | |
| School 1 GPA | (empty) | |
| Skills line 1 | Product: Roadmaps, customer interviews, A/B testing | |
| Skills line 2 | Tools: Jira, Figma, Amplitude, SQL, Looker | |
| Skills line 3 | Methods: Scrum, Kanban, jobs to be done |
Shown but not counted
- Denver, CO: no location field for jobs. It's in the extracted text.
- Denver, CO: no location field for jobs. It's in the extracted text.
- Aurora, CO: no location field for jobs. It's in the extracted text.
- Boulder, CO: no location field for schools. It's in the extracted text.
This checks our sample text, read by one open-source parser from the PDF that Google Docs' File > Download > PDF produces. It isn't a score, and it doesn't tell you how Workday, Greenhouse or any other hiring system will read your own resume. Anyone can rerun it: the test repository has the PDF (SHA-256 2ef5233083f8…), the expected values and the raw results. How we test
Specs and editing tips
Everything you need to edit it without breaking the layout.
Specs
- Font
- Verdana, installed on Windows and macOS, so the .docx keeps its look
- Body text
- 10 pt
- Margins
- 0.75 in (Letter), 19 mm (A4)
- Length
- 1 page with the sample content
- Sections
- Summary, Experience, Education, Skills
- Good for
- 2–10 years
- Layout
- One column, no tables, text boxes, images or icons. Dates aligned with a right tab stop.
Editing tips
- Dates stay on the right by themselves. Each heading line has a right-aligned tab stop. Press Tab before the date instead of adding spaces.
- Add a job by copying one. Select a whole entry, heading lines and bullets, copy it and paste it below. The spacing comes with it.
- Ran onto a second page? Set margins to 0.5 in, body text to 10.5 pt and line spacing to single, in that order. More ways to fit one page
- Rename your copy. Recruiters see the file name, so use something like Firstname-Lastname-Resume.
Exporting your finished resume
Two downloads from Google Docs cover almost every application.
File > Download > PDF Document. This is the exact path we test on every release. It gives selectable text with the fonts embedded.
Word
File > Download > Microsoft Word (.docx). Our own .docx files are exported this way, and we check that text and bullets survive. Don't convert a PDF to Word.
Similar templates
Same rules, a different look.
Modern Bold
33/33 fields read
A large teal name and heavy rules under each heading. Stands out in a stack of printouts and still reads cleanly in software.
- 1 page
- Letter + A4
- Docs + Word
Modern Accent
35/35 fields read
One ink-blue accent on headings and rules, with a summary up top. Clean enough for any parser, with a little more personality.
- 1 page
- Letter + A4
- Docs + Word
Plain
33/33 fields read
Nothing but text, left-aligned, in Arial. A safe default for any job when you don't want the layout to be noticed.
- 1 page
- Letter + A4
- Docs + Word
Questions
- Is it really free?
- Yes. No account, no email and no watermark. Copy it, edit it and send it to as many employers as you like. The one thing you can't do is repost the template file itself somewhere else.
- Will it get through an ATS?
- Nobody can promise that, and we don't. What we can show is that an open-source parser reads our sample of this template correctly, field by field, from the PDF Google Docs produces. Workday, Greenhouse and others use their own parsers, and your own content matters as much as the layout. How we test
- Can I use it in Microsoft Word?
- Yes. Download the .docx, or copy to Google Docs and later use File > Download > Microsoft Word. The font is installed on Windows and macOS, so nothing gets swapped.
- Why no photo, icons or two columns?
- Parsers read a page top to bottom. Columns, text boxes and icons are the usual reason a resume comes out scrambled. US employers also generally don't want photos.
- Can my name have accents or non-Latin characters?
- Yes, with one caveat. In our tests the parser read José Álvarez, Mary-Jane Smith, Sean O'Brien and Иван Петров correctly, and the layout didn't move. A Chinese name like 王小明 also kept the page intact, but Google Docs swaps in a Japanese font for those characters and the parser left the name field empty. For US applications, put the romanized name first, like Xiaoming Wang (王小明). Phone numbers outside the US format, like +44 7700 900123, aren't picked up as phone numbers either.