Technical resume template for Google Docs™
Grouped technical skills first, then experience and projects with the numbers engineers look for. A sans-serif cousin of Jake's.
- Parser read 35/35 fields
- 1 page
- US Letter and A4
- Google Docs and Word
- Arial
What a parser reads from it
Field by field, from the PDF that Google Docs exports.
35/35
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.
Kevin Osei Seattle, WA | (206) 555-0159 | kevin.osei@example.com | linkedin.com/in/kevinosei | github.com/kevinosei TECHNICAL SKILLS Languages: Go, Python, TypeScript, SQL Infrastructure: AWS, Kubernetes, Terraform, Docker Data: PostgreSQL, Redis, Kafka Practices: Code review, on-call, observability EXPERIENCE Software Engineer II Mar 2023 – Present Tarnhollow Logistics Seattle, WA • Lead the shipment events service in Go, handling about 40 million events a day from 300 warehouses • Moved the service from a single database to partitioned PostgreSQL tables, cutting p95 write latency from 220 ms to 35 ms • Wrote the team's on-call runbook and alert rules; pages per week dropped from 14 to 4 after the first quarter • Mentor two junior engineers and review about 15 pull requests a week • Added tracing to four shipment services, so finding a failing step takes minutes instead of hours Software Engineer Jul 2021 – Feb 2023 Brindlewood Freight Systems Bellevue, WA • Built the carrier rate API in Python and FastAPI, used by the pricing team to quote about 9,000 loads a day • Set up Terraform for the team's AWS accounts, replacing hand-made resources and shortening new environment setup from two days to an hour • Added contract tests between four services, catching breaking changes before deploys • Took part in the on-call rotation and wrote six incident reviews PROJECTS Queue Lens | Go, open source 2024 • A small web tool that shows Kafka consumer lag by team and topic, with about 600 stars on GitHub Trailhead Weather | TypeScript, React Native 2022 • A phone app that combines forecasts and trail reports for hikers; about 2,000 monthly users EDUCATION Alderhaven University Tacoma, WA
Field by field
What we wrote, and what the parser put in each field.
| Field | Parser read | Match |
|---|---|---|
| Name | Kevin Osei | |
| kevin.osei@example.com | ||
| Phone | (206) 555-0159 | |
| Location | Seattle, WA | |
| Link | linkedin.com/in/kevinosei | |
| Summary | (empty) | |
| Job 1 company | Tarnhollow Logistics | |
| Job 1 title | Software Engineer II | |
| Job 1 dates | Mar 2023 – Present | |
| Job 1, bullet 1 | Lead the shipment events service in Go, handling about 40 million events a day from 300 warehouses | |
| Job 1, bullet 2 | Moved the service from a single database to partitioned PostgreSQL tables, cutting p95 write latency from 220 ms to 35 ms | |
| Job 1, bullet 3 | Wrote the team's on-call runbook and alert rules; pages per week dropped from 14 to 4 after the first quarter | |
| Job 1, bullet 4 | Mentor two junior engineers and review about 15 pull requests a week | |
| Job 1, bullet 5 | Added tracing to four shipment services, so finding a failing step takes minutes instead of hours | |
| Job 2 company | Brindlewood Freight Systems | |
| Job 2 title | Software Engineer | |
| Job 2 dates | Jul 2021 – Feb 2023 | |
| Job 2, bullet 1 | Built the carrier rate API in Python and FastAPI, used by the pricing team to quote about 9,000 loads a day | |
| Job 2, bullet 2 | Set up Terraform for the team's AWS accounts, replacing hand-made resources and shortening new environment setup from two days to an hour | |
| Job 2, bullet 3 | Added contract tests between four services, catching breaking changes before deploys | |
| Job 2, bullet 4 | Took part in the on-call rotation and wrote six incident reviews | |
| School 1 | Alderhaven University | |
| School 1 degree | Bachelor of Science in Computer Science | |
| School 1 dates | Jun 2021 | |
| School 1 GPA | (empty) | |
| Project 1 | Queue Lens | Go, open source | |
| Project 1 dates | 2024 | |
| Project 1, bullet 1 | A small web tool that shows Kafka consumer lag by team and topic, with about 600 stars on GitHub | |
| Project 2 | Trailhead Weather | TypeScript, React Native | |
| Project 2 dates | 2022 | |
| Project 2, bullet 1 | A phone app that combines forecasts and trail reports for hikers; about 2,000 monthly users | |
| Skills line 1 | Languages: Go, Python, TypeScript, SQL | |
| Skills line 2 | Infrastructure: AWS, Kubernetes, Terraform, Docker | |
| Skills line 3 | Data: PostgreSQL, Redis, Kafka | |
| Skills line 4 | Practices: Code review, on-call, observability |
Shown but not counted
- github.com/kevinosei: parser keeps one URL. It's in the extracted text.
- Seattle, WA: no location field for jobs. It's in the extracted text.
- Bellevue, WA: no location field for jobs. It's in the extracted text.
- Tacoma, WA: 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 ead6d788fb7c…), 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
- Arial, installed on Windows and macOS, so the .docx keeps its look
- Body text
- 10.5 pt, bullets 10 pt
- Margins
- 0.6 in (Letter), 15 mm (A4)
- Length
- 1 page with the sample content
- Sections
- Technical Skills, Experience, Projects, Education
- Good for
- 0–8 years in tech
- 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.
Jake's
46/46 fields read
The Jake's Resume layout rebuilt for Google Docs and Word. Dense, centered, made for tech internships and new-grad roles.
- 1 page
- Letter + A4
- Docs + Word
Compact
36/36 fields read
Half-inch margins and tight spacing for people with more experience than one page normally holds.
- 1 page
- Letter + A4
- Docs + Word
Skills-first
33/33 fields read
Summary and skills come before work history. Useful when you're changing careers or coming back after a gap.
- 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.