Simple Resume Format Sample: Layout, Spacing, Sections
A simple resume format sample with exact margins, fonts, and section order, plus what a resume parser reads from it field by field. Copy and adapt it.
On this page
Simple, on a resume, is not a design taste. It is a set of choices you can check with a ruler and a font menu. One column. Margins you could measure. Headings a parser recognizes. Dates that sit next to the job they belong to. Get those right and the same document works for the recruiter skimming it and for the applicant tracking system (ATS) that reads it before any human does.
This page gives you the whole thing in one place. The six rules that define a simple format, a complete sample built on them, the exact page settings behind it, and a comparison most template galleries never show you. We take the identical content, set it in two columns instead of one, and walk through what a resume parser pulls out of each version, field by field. At the end there is a plain-text copy of the sample you can paste into any editor and adapt.
What makes a resume format simple: six rules you can measure
Most advice about simple resumes is vague. "Keep it clean" tells you nothing you can act on. These six rules do, because each one is either true of your document or it isn't.
- One column, read top to bottom. No sidebar, no split layout. A parser reads a page the way you read a book, and a single column means the reading order and the visual order are the same thing.
- One font, two sizes. Pick a standard face like Arial, Calibri, or Georgia. Body text sits around 10.5 to 11.5 points, headings two to three points larger. Nothing else.
- Margins between 0.7 and 1 inch on all four sides. Tighter than 0.6 inch looks crowded on paper and clips in some print dialogs. Wider than 1 inch wastes a fifth of your page.
- No decoration that carries information. No photo, no icons, no skill-rating bars, no text boxes. If a parser strips every visual element and your resume still says everything it said before, you pass this rule.
- Standard section headings. Summary, Skills, Experience, Education. Parsers map content to fields by matching headings, and "My Journey" does not match anything.
- Contact details in the document body, not in the file's header or footer. Header and footer regions are a known blind spot for parsing software, and your phone number is the one field you cannot afford to lose.
Notice what is not on the list. Nothing about being boring, nothing about a specific template, nothing about avoiding color entirely. A dark blue heading breaks no rule. A two-column skills sidebar breaks two of them, and the parser comparison later on this page shows you exactly what that costs.
The simple resume format sample, in full
The sample running through this article is Jordan Avery, an operations coordinator with about six years of experience, two employers, and a promotion at the current one. That profile was chosen on purpose. It forces the format to handle the situations that break most templates, including two titles under one company name and an early career that needs compressing rather than listing.
Here is the sample's entire specification. Every choice below is one you can reproduce in Word, Google Docs, or any resume editor in under five minutes.
| Setting | Value in the sample | Why |
|---|---|---|
| Layout | Single column, full page width | Reading order matches visual order for both humans and parsers |
| Font | Calibri throughout | Installed everywhere, renders identically in PDF |
| Body size | 11 pt | Readable on screen and on paper without crowding |
| Heading size | 13 pt, bold, small caps optional | Enough contrast to scan by; no color required |
| Margins | 0.8 inch on all sides | Room for a full career on one page without a cramped look |
| Line spacing | 1.08 within bullets, 6 pt space after each bullet | Air between items, no wasted half-lines |
| Section order | Header, Summary, Skills, Experience, Education | Recruiter reads the pitch first, proof second |
| Dates | Right-aligned with a tab stop, "Mar 2022 – Present" format | Consistent, scannable, and set without a table |
| Length | One page | Six years of experience fits; the compression tricks are shown below |
The full text of this sample appears at the bottom of the page, ready to paste. Everything between here and there explains the decisions inside it, so you can adapt it instead of copying it blindly.
Page setup: margins, font size, line spacing, and where one page ends
Page setup is where "simple" gets decided, because spacing mistakes compound. A resume set at 12 pt with 1.5 line spacing and 1.25 inch margins runs onto a second page with four years of experience on it, and the writer then starts cutting content to fix a formatting problem.
Work from these numbers. Margins at 0.8 inch. Body text at 11 pt, dropping to 10.5 pt only if you are trimming the last three lines off a second page. Headings at 13 pt. Line spacing at 1.0 to 1.1 inside a bullet, with a small space after each bullet rather than a blank line between them. The blank-line habit is the single biggest space waster in homemade resumes, because a full empty line at 11 pt costs you roughly one bullet of content every time you use it.
Name at the top goes bigger, around 18 to 22 pt, with contact details in one line of body text directly underneath. Put a single line between sections, created with paragraph spacing rather than a pressed Enter key, so the gaps stay identical everywhere. If you want the deeper reasoning on type sizes, there is a full breakdown in what's the best font size for a resume.
Where one page ends is a content decision dressed up as a formatting one. Under roughly ten years of experience, one page is the default and the sample on this page holds to it. Past that, a second page is normal and no recruiter penalizes it. The honest tiebreaker question is whether page two would contain evidence or leftovers, and the one-page-or-two question has a longer answer by experience level if you are on the fence.
Section order, and the one case for moving the summary
The sample runs header, summary, skills, experience, education. That order exists for a reader with seconds to spend. The summary makes the claim, the skills section shows the tools behind it, and the experience section proves both. Education sits last for anyone who has been working more than a couple of years, because a degree from 2017 is context, not an argument.
Two profiles should reorder it. A recent graduate or fresher moves education directly under the summary, since it is the strongest evidence they have. A career changer moves skills up and makes it heavier, because their job titles argue against them and their capabilities argue for them. The full logic by situation is in the best resume section order for your experience level.
Now the one case for demoting the summary itself. If your current title is the exact title you are applying for, at a recognizable employer, in the same industry, the summary is restating what the first line of your experience section already proves. A senior accountant at a known firm applying for senior accountant roles gains nothing from three lines announcing they are a senior accountant. In that case cut the summary to a single line or drop it entirely and let experience start higher on the page. Everyone else keeps the summary on top, and writes it as a specific claim rather than a string of adjectives.
The same content, one column next to two columns
Two-column resumes exist because they look designed. A colored sidebar holding contact details, skills, and education leaves the main column free for experience, and on screen the effect is polished. The problem is that nothing about the content changed, only the reading order, and reading order is the thing a parser depends on.
Set the Jordan Avery sample both ways and the differences are concrete.
| Property | One-column sample | Identical content in two columns |
|---|---|---|
| Reading order | Top to bottom, one pass | Ambiguous. Software must guess whether to read across or down |
| Contact details | First line of the body, always found | Often inside a sidebar or text box, a known weak spot for extraction |
| Skills | A labeled section with a recognized heading | Sidebar text that may attach to whatever sits beside it |
| Date alignment | Tab stop inside the same line as the title | Frequently a separate column, physically detached from the role |
| Space efficiency | Full page width for every bullet | Main column loses a third of its width; bullets wrap to three lines |
| Recruiter skim | Eyes travel one path | Eyes bounce between columns; dates and titles live far apart |
The space point deserves more attention than it gets. A two-column layout does not just risk parsing, it makes your best bullets worse. "Cut carrier invoice disputes 38% by rebuilding the reconciliation workflow in NetSuite" fits one line at full width. In a narrow main column it wraps to two, the number lands mid-line where a skimming eye misses it, and a one-page resume becomes a page and a quarter.
What a parser pulls out of this sample, field by field
This is the part template galleries skip. A claim like "two columns confuse the ATS" stays abstract until you see which fields survive and which don't. So take the sample above, run it through the resume parser behind Roleframe's fit reports in both layouts, and compare the output field by field. Parsers vary by vendor and results are not identical everywhere, but the pattern below is the consistent one, and it matches what independent checks show when you test a resume against an ATS yourself.
| Field | One-column sample | Same content in two columns |
|---|---|---|
| Candidate name | Captured cleanly | Captured. A full-width name banner survives both layouts |
| Phone and email | Captured and correctly typed as phone and email | Usually captured, but misses appear when the contact block sits inside a sidebar text box |
| Location | Captured as city and state | Sometimes concatenated with neighboring sidebar text into one string |
| Summary | Mapped to the profile field under the "Summary" heading | Mapped less reliably when the heading is a sidebar label like "About" |
| Current job title | Captured and linked to the employer | Captured, but can come back with no dates attached when dates live in a separate column |
| Employment dates | Each range attached to its role, promotion split intact | The most common failure. Dates read down a column can attach to the wrong role or arrive as an orphaned list |
| Experience bullets | Grouped under the correct role | Grouped, unless a column break lands mid-role and splits one job into two fragments |
| Skills | A labeled skills list, each item separate | Frequently the biggest loss. Sidebar skills merge into adjacent text or land as one unlabeled block |
| Education | Degree, school, and year each captured | Degree usually survives; the year is the field that most often detaches |
Read the right-hand column and notice what kind of fields break. Not the name, not the degree. The breakage concentrates in dates and skills, which are precisely the fields recruiter-side filters search and sort on. A resume that parses with the wrong dates on a promotion can read as two short stints instead of one four-year progression. A skills list that arrives as an unlabeled blob matches no keyword filter at all. The candidate never sees any of this happen, which is why the failure feels like silence rather than rejection.
None of this means every ATS mangles every two-column resume. Modern parsers have improved, and some handle simple sidebars fine. The point is asymmetry. The one-column version has no failure mode to improve on, so choosing it costs you nothing and removes an entire category of risk. The broader formatting rules that follow from this are covered in the ATS resume format guide.
Several jobs on one page: stacking and compressing
The sample handles two problems that push simple resumes onto a second page. Both have clean solutions.
Stacking two roles at one employer
Jordan was promoted at Northline Logistics, and repeating the company name for each title wastes lines while hiding the promotion. The fix is to write the employer once, then list each title with its own dates underneath. Bullets go under the title they belong to, weighted toward the senior role. The promotion becomes visible as structure, the parser still gets a distinct date range per title, and you save two full lines.
Compressing the early years
The retail jobs Jordan held before 2017 prove work ethic and nothing else relevant. They get one line under an "Earlier Experience" label, with employer names and a combined date range and no bullets. Anything older than roughly ten to fifteen years earns this treatment or gets cut, and how far back a resume should go covers the cutoffs by situation. For the roles that stay, three to five bullets each is the working range, tighter for older positions.
Six things that quietly break a simple format in Word and Google Docs
A simple resume format in Word is entirely achievable, but Word and Google Docs both offer convenient features that sabotage the document invisibly. These six cause most of the damage.
- Contact details typed into the document header. It looks tidy and it centers automatically, and parsing software may never read it. Your name and contact line belong in the body, as the first text on the page.
- Tables used to right-align dates. Word's template gallery loves invisible tables, and a parser can read a table's cells in an order you never intended. Use a right-aligned tab stop instead. In Google Docs, add a tab stop from the ruler; the result is identical and the underlying document stays plain text.
- Text boxes for anything. A text box floats above the document rather than living inside it, and extraction tools routinely skip floating objects. If you imported a template and are not sure, press Ctrl+A; anything that doesn't highlight is floating.
- Spacing built from empty lines. Pressed-Enter gaps drift out of sync the moment you edit, and they push section headings to the bottom of page one with their content orphaned on page two. Use space-after-paragraph settings so every gap is identical, and turn on "keep with next" for headings.
- Decorative bullet symbols. Arrows, check marks, and custom glyphs can arrive at the other end as question marks or boxes. The standard round bullet survives every conversion.
- Sending the wrong file. Export a text-based PDF and check it by selecting the text; if you can highlight words, a parser can read them. A PDF saved from a scan or screenshot is an image and reads as a blank page. Submit PDF by default, and reach for another format only when a specific employer's system explicitly demands it.
The plain-text sample to paste and adapt
Here is the full Jordan Avery sample as plain text. Paste it into your editor, apply the page settings from the table near the top of this article, and replace the content with yours. Keep the structure, especially the stacked titles and the compressed early years, and swap every number for one you can defend in an interview.
JORDAN AVERY
Chicago, IL | (312) 555-0148 | jordan.avery@email.com | linkedin.com/in/jordanavery
SUMMARY
Operations coordinator with 6 years in third-party logistics, promoted once at a 400-employee carrier network. Cut invoice dispute resolution time 38% and manage vendor relationships covering $4.2M in annual freight spend.
SKILLS
NetSuite | SAP TM | Excel (pivot tables, XLOOKUP) | Carrier rate negotiation | Invoice reconciliation | KPI dashboards | SOP documentation | Zendesk
EXPERIENCE
Northline Logistics, Chicago, IL
Senior Operations Coordinator | Mar 2022 – Present
- Rebuilt the carrier invoice reconciliation workflow in NetSuite, cutting average dispute resolution from 21 days to 13 and recovering $118K in overbilled freight in the first year
- Manage relationships with 14 regional carriers covering $4.2M in annual spend; renegotiated 6 contracts for an average 7% rate reduction
- Built weekly KPI dashboards in Excel for on-time delivery and claims rates, now used by 3 department heads for carrier reviews
Operations Coordinator | Jun 2019 – Mar 2022
- Processed 150+ shipment exceptions per week across 3 warehouses, holding on-time resolution above 94%
- Wrote the SOP library for exception handling, cutting new-hire ramp time from 8 weeks to 5
Beacon Staffing Group, Chicago, IL
Operations Assistant | Aug 2017 – Jun 2019
- Coordinated scheduling and compliance paperwork for a pool of 200+ contract workers across 12 client sites
- Cut payroll discrepancy tickets 30% by building a shared intake tracker in Excel
EARLIER EXPERIENCE
Retail sales and shift supervisor roles, Target and Walgreens, Chicago, IL | 2014 – 2017
EDUCATION
B.A., Communication — University of Illinois at Chicago, 2017
Two things to notice as you adapt it. Every bullet leads with a verb and lands on an outcome, and the outcome carries a number wherever the work produced one. And the whole document contains not a single element the six rules forbid. No table, no text box, no icon, nothing in a header. That is the entire trick.
Frequently asked questions
- What is a good basic format for a resume?
A single column in reverse-chronological order, with sections running header, summary, skills, experience, education. Use one standard font at 10.5 to 11.5 points for body text, margins of 0.7 to 1 inch, and standard section headings. This basic resume format sample structure works for nearly every role because recruiters can skim it in one pass and parsing software extracts every field from it reliably.
- What are the 5 P's of a resume?
There is no single official list; the 5 P's are a career-center mnemonic that varies by who teaches it. Common versions include some mix of preparation, presentation, proofreading, personalization, and positivity. Treat it as a checklist reminder rather than a framework. The two P's that decide outcomes are personalization, meaning the resume matches the specific posting, and proofreading, because a typo in a job title is the cheapest rejection there is.
- What is the best resume format for beginners and freshers?
The same simple single-column format, with education moved up to sit directly under the summary, since it is a fresher's strongest evidence. Fill the experience section with internships, capstone projects, part-time work, and campus roles, written as achievement bullets rather than duty lists. An easy resume format for freshers is easy precisely because it is plain; a decorated template signals effort spent in the wrong place. If the summary is the hard part, there are fresher summary examples to work from.
- How do I write a resume as a beginner?
Start from the plain-text sample on this page and replace the content section by section. Write the experience bullets first, since they are the hardest, and make each one an action plus a result rather than a responsibility. Then write the skills line using terms from the actual postings you are targeting, and write the summary last, once you know what the rest of the document proves. Set the page up with the exact margins and font sizes in the table above and you will not need a template at all.
- Should a simple resume be in Word or PDF?
Submit a text-based PDF. It locks your layout so the recruiter sees exactly what you built, and a text-based PDF parses reliably in modern applicant tracking systems. Verify yours is text-based by trying to select the text with your cursor. Keep an editable source file for yourself, and reach for a different submission format only if a specific employer's system explicitly asks for one.
- Can a simple resume format be two pages?
Yes. Simple describes the layout, not the length. Past roughly ten years of experience a second page is normal, and cramming fifteen years into 9-point text is worse than using it. Under ten years, one page is the default, and the stacking and compression techniques on this page usually make it fit without cutting real achievements.
Ready to start your new resume?
Writing a resume takes time, and even a polished one can miss what a hiring manager is looking for. Roleframe helps you build a clear, ATS-safe resume in minutes and tailor it to the job you want.
