Writing a résumé in Markdown gets you clean, portable structure for free. But formatting it well — so it reads fast for humans and parses cleanly for machines — is where applications are won or lost. This guide covers the tactical details: how to structure bullets, order sections, place keywords, and avoid the formatting traps that trip up applicant tracking systems.
New to Markdown résumés? Start with our complete guide to writing a résumé in Markdown, then come back for the formatting details.
How ATS Parsers Read Your Résumé
Most mid-to-large companies run résumés through an applicant tracking system (ATS) before a human sees them. The ATS extracts text, maps it to fields (name, experience, skills), and scores it against the job description. Anything it can’t parse cleanly gets garbled or dropped.
Here’s the good news: Markdown is naturally ATS-friendly. When you export Markdown to PDF, you get standard headings, plain paragraphs, and simple bulleted lists — precisely the structure parsers handle best. The formats that break ATS parsing are the ones Markdown doesn’t produce:
- Multi-column layouts
- Text inside tables or text boxes
- Information in headers/footers
- Graphics, icons, and skill “rating bars”
By writing in Markdown, you avoid these by default. The job is simply to not reintroduce them.
Structuring Bullets That Perform
The experience section is where a résumé is really read. Format every bullet with a consistent pattern:
Action verb + task + measurable result.
- Reduced CI pipeline runtime **65%** by parallelizing test suites and caching dependencies.A few rules that make bullets land:
- Lead with a strong verb. Led, built, cut, grew, owned, shipped — not responsible for or helped with.
- Bold the number. Wrapping metrics in
**asterisks**makes them the first thing the eye catches. Every template in our résumé library does this deliberately. - One idea per bullet. If a bullet has two “and”s, split it.
- Three to five bullets per role. More recent roles get more; older roles get fewer.
If a bullet has no number, ask what you can measure: time saved, percentage improved, volume handled, revenue touched.
The Right Section Order
Order signals priority. A reverse-chronological résumé — the format ATS systems expect — flows like this:
- Name and contact (as a single H1 plus a contact line)
- Summary — two or three sentences
- Experience — most recent first
- Skills — grouped by category
- Education
- Optional — projects, certifications, publications, portfolio
Some fields flip this. A licensed professional leads with credentials — see the registered nurse or pharmacist templates, where licensure appears near the top. A designer surfaces a portfolio link early. Match the order to what your field screens for first.
Placing Keywords Without Stuffing
ATS scoring rewards résumés that echo the language of the job posting. To place keywords naturally:
- Mirror the job’s exact terms. If the posting says “demand generation,” use that phrase, not a synonym.
- Put hard skills in a grouped Skills section. This is the cleanest place for an ATS to find them:
## Skills
- **Languages:** TypeScript, Go, Python, SQL
- **Infrastructure:** AWS, Docker, Kubernetes, Terraform- Reinforce keywords in context. A skill mentioned in a bullet (“designed a GraphQL gateway”) carries more weight than one that only appears in a list.
- Don’t keyword-stuff. Hidden white text or a wall of unrelated terms gets flagged and reads as desperate to humans.
Formatting Mistakes to Avoid
Even in Markdown, a few habits can hurt you:
Fancy characters in headings. Keep section titles conventional — Experience, Skills, Education. Creative labels like “Where I’ve Made Magic” confuse both parsers and busy recruiters.
Overusing tables. Markdown tables render beautifully, but ATS parsers can scramble tabular data. Reserve tables for genuine matrices, never for your core experience.
Dense walls of text. A summary paragraph is fine; a five-line bullet is not. White space is a feature.
Inconsistent date formats. Pick one style (Jan 2021 – Present) and use it everywhere. Parsers and readers both rely on the pattern.
Skipping the preview. Always check the live preview before exporting — it’s exactly what your PDF will contain.
Export Settings That Keep It Clean
When you convert your Markdown to PDF:
- Choose “Default” margins in your browser’s print dialog.
- Deselect headers and footers so the page URL and date don’t print.
- Keep it to one page unless you’re a senior candidate.
- Export to DOCX instead when a portal specifically requires an editable Word document — some older ATS platforms prefer it.
Put It Into Practice
The fastest way to apply all of this is to start from a template already formatted for your role, then swap in your own experience:
Browse the full Markdown résumé template library, pick your profession, and edit it right in your browser. Good formatting is mostly consistency — and Markdown gives you most of it for free.