Resume Template in LaTeX: Best Classes + ATS Reality (2026)

LaTeX is the only resume tool where users actively enjoy using it. Ask a PhD candidate, a software engineer, or a quant what they build their resume in, and half will say LaTeX with the same energy normal people reserve for their favorite pizza place. The typography beats Word and Google Docs. The source lives in git. And when a senior engineer opens the PDF, they can tell within a second that whoever wrote this is comfortable with tools.

The problem: the person reading it is often a recruiter's ATS, not a PhD advisor. Applicant tracking systems were built for DOCX first, PDF second, and "whatever pdflatex spits out" dead last. Your LaTeX resume can look spectacular in the browser preview, then get parsed into word salad by Workday the moment it lands in the pipeline.

This guide gives you the five free LaTeX templates worth knowing, the Overleaf workflow that skips the local-install headache, an honest comparison with Word and Google Docs, and the ATS workaround that keeps LaTeX useful without getting you filtered out of every Fortune 500 application.

Is LaTeX Good for a Resume? The Short Answer

Yes for academic CVs, tech roles where the hiring manager cares, and anyone whose resume will be read by a human first. Mostly no for mass-applying to corporate ATS pipelines.

The split is clean. LaTeX wins where typography and version control matter, and where the first reader is a human with opinions about kerning. Word and Google Docs win where the first reader is a parser built on 2010-era NLP that panics at anything fancier than Arial 11.

Why LaTeX Is Still the Resume Tool for Tech and Academia

Three real reasons it stays the standard in certain fields.

1. Typography is better than any WYSIWYG alternative. LaTeX handles line breaks, kerning, and spacing the way a professional typesetter would. A good LaTeX resume looks like a book page; a good Word resume looks like a Word document.
2. Version control. Your resume is plain text. It lives in git. You can diff a change, roll back a bad edit, branch for job-specific variants, and see your entire resume history. Try doing that with a .docx.
3. Academic CV requirements. Tenure-track applications, fellowship applications, and many PhD program applications expect LaTeX-typeset CVs with bibliographies managed by BibTeX. It is functionally mandatory in these contexts, not optional.

Where LaTeX is not the right tool: anyone mass-applying to corporate jobs that route through Workday, Taleo, Greenhouse, Lever, or iCIMS. Those pipelines prefer Word-shaped documents, and LaTeX PDFs often break at the parser even when they look perfect to your eyes.

5 Best Free LaTeX Resume Templates

All five are free, open-source, and available on Overleaf or GitHub. Scored on ATS-friendliness because that is where LaTeX templates differ most.

Default pick for most tech readers: Jake's Resume. Single column, Computer Modern, information-dense, parser-friendly, MIT-licensed. It's the default recommendation on r/cscareerquestions and r/EngineeringResumes and turns up in most university CS career guides. If you're in CS and can't decide, use it and move on; the template is not what decides whether you get interviews. Full breakdown of it below.

If you are writing an academic CV with publications, talks, and teaching, use ModernCV or a department-specific template. If you are in the EU, Europass is often expected explicitly on the posting.

Jake's Resume: Who Made It, What's In It, Where to Get It

Jake Gutierrez published the template on GitHub on 28 August 2020 under the MIT license. The repository is github.com/jakegut/resume. Older links and the Overleaf listing still point at jakeryang/resume, which is the same repository under his previous username; GitHub forwards it. There's one .tex file and a compiled PDF. That's the whole project.

It gets described as the most-forked resume template on GitHub, including by an earlier version of this article. That's wrong, and the numbers are one API call away. Here is what the GitHub REST API returned on 20 August 2026 for the templates in this guide, plus RenderCV and sb2nov/resume for scale.

Awesome-CV has roughly eight times the forks. What Jake's has instead is recommendation share: it's the answer people give on r/cscareerquestions and r/EngineeringResumes when someone asks what to use. For a resume template that is the more useful signal, because the people recommending it are the ones who got interviews with it.

The uncomfortable part of the same table: the last push to jakegut/resume was 10 August 2024, and the Overleaf listing has not moved since publication. Nobody is maintaining this. For a single-page document that compiles in about two seconds against a standard TeX distribution, unmaintained doesn't really matter. Just don't let a paid tool sell you "actively maintained" as the reason to use their copy of it.

To open it: go to overleaf.com/latex/templates/jakes-resume and click "Open as Template". It copies into your account, and you never touch GitHub or install a TeX distribution. The free Overleaf plan handles it comfortably; a one-page resume is nowhere near the 10-second compile timeout that the free tier enforces.

The next question is always whether a Word version exists. It doesn't. Search for one and the first page of results is mostly vendors: Etsy listings selling a .docx recreation, template shops, and browser builders that regenerate the same layout behind a signup. All of it is third-party work on an MIT-licensed file, which is legal for them and optional for you. The design is a single column, bold role on the left, dates right-aligned, bullets underneath, no tables. Rebuilding that in Word by hand is faster than shopping for a copy of it.

AltaCV: When You Want More Visual Polish

AltaCV (by liantze) is the LaTeX template asked about most after Jake's Resume. It supports a two-column sidebar layout that gets closer to a Canva-style design while staying in pure LaTeX. The catch: only the single-column variant is ATS-safe. The default two-column setup gets parsed as one continuous row by most ATS, mixing your skills sidebar into your job titles and breaking section ordering.

If you go with AltaCV: stick to the single-column variant, use Computer Modern or Lato, and run the copy-paste-into-plain-text test before submitting. Save the two-column version for situations where you know a human reads the PDF directly (recruiter emails, portfolio links, conference networking PDFs). For Workday-style pipelines, single-column AltaCV or Jake's Resume are the safer picks.

If you want a one-column ATS-safe resume without compiling LaTeX, our Resume Builder produces the same parser-friendly PDF output without the Overleaf round-trip. You keep LaTeX for the academic CV, use this for the corporate applications.

How to Compile a LaTeX Resume (The Overleaf Workflow)

Skip the local TeX install debate. Overleaf runs in the browser, compiles on their servers, and the free tier is enough for a resume. Here is the minimum-friction workflow.

1. Create an Overleaf account (free tier works). overleaf.com.
2. Open the template you picked. For Jake's: overleaf.com/latex/templates/jakes-resume. Click "Open as Template" and it copies into your account.
3. Replace the placeholder content. Name, contact, education, experience, projects, skills. The comments in the .tex file tell you exactly where each section starts.
4. Recompile (the green button) and preview on the right. Overleaf recompiles in about 2 seconds for a one-page resume.
5. Download PDF when you are happy with it. Click Download > PDF.
6. Test ATS compatibility: open the downloaded PDF, select all (Ctrl+A or Cmd+A), copy, paste into a plain text editor. If the sections come out in the wrong order or words are merged together, the ATS will have the same problem. MIT and most career services centers recommend this test.

If you want the .tex source in git, check the plan first: Overleaf lists Git and GitHub sync as a premium feature, so the free plan won't push your resume repo. The workaround costs nothing. Keep the repo on GitHub, edit locally, and open Overleaf only to compile. Or install TeX Live once and skip the browser entirely. Overkill for most people, but it means your resume lives in your dotfiles forever.

LaTeX vs Google Docs vs Word for Resumes

Honest trade-off table. Nobody wins at everything.

The honest call: for most job applications in 2026, Word or Google Docs is the safer default. For tech roles where the hiring manager is a senior engineer who will read the PDF themselves, LaTeX is a signal. For academic CVs, LaTeX is almost required. The decision is about who the first reader is: machine or human.

The ATS Problem: Why LaTeX PDFs Fail Parsing

LaTeX PDFs fail ATS for specific, boring, fixable reasons. If you understand the causes, you can write a LaTeX resume that passes cleanly.

• Two-column layouts. ATS parses left-to-right, top-to-bottom, across the full page width. A two-column layout gets read as one wide row, mixing your skills list into your job titles. Deedy-Resume is the canonical offender here.
• Custom and non-standard fonts. If your template uses a font that is not embedded or not one of the Adobe base 14, some PDF text extractors render it as boxes or swap to a fallback that shifts layout.
• Ligatures and micro-typography. LaTeX's finest feature (fi, fl, ffl ligatures rendered as single glyphs) sometimes decodes back to text as "fi" merged into one character that parsers do not split properly.
• Math-mode text. If you use math mode for anything other than actual math (some people do it to get italic text or specific symbols), parsers can fail to extract it as readable text.
• Floats, figures, and tables. Same issue as columns. ATS reads tables inconsistently; stick to bullet lists wherever possible.
• Section headers as images or custom commands. If your \section{} command is customized to output as a styled box, parsers may miss the section label entirely and not know where experience ends and education begins.

Jobshinobi's 2026 LaTeX-ATS guide runs actual Jobscan tests on popular templates and reports: Jake's Resume passes at 85–95% match when keywords are present. Deedy passes at 40–60% because of the two-column issue. Custom-designed templates with heavy styling can go below 30%.

ATS-Safe LaTeX Workflow

The honest answer for tech job seekers who want LaTeX but also want to pass parsers.

1. Use a single-column template. Jake's Resume, Awesome-CV single-column variant, or a stripped-down ModernCV. Drop any template that uses two columns, sidebars, or floating sidebars.
2. Stick to standard fonts. Computer Modern (LaTeX default) is fine. Lato, Source Sans Pro, Roboto all work. Avoid obscure fonts that may not embed cleanly.
3. Test every template by copy-paste into a plain text editor before you ever submit it. If the order is wrong or text is jumbled, the ATS will fail the same way.
4. Use the Jobscan-style keyword match test. Paste your PDF text into a free ATS parser and see what the system extracts. Iterate on the template until the text comes out clean.
5. For mission-critical corporate applications, keep a parallel .docx version. Convert via pandoc or by copying the content into a Google Docs resume template. Submit the .docx to ATS, keep the LaTeX for direct human readers (recruiter emails, portfolio links, academic CVs).

The tailoring step matters more than the format. Whatever tool you use, Mirrai's Job Matcher takes your resume and a job description and shows you which keywords you are missing, regardless of whether the file came out of Overleaf, Word, or anywhere else.

AI-Powered LaTeX Builders: New in 2026

By 2026 there is a real category of AI-powered LaTeX builders: web tools that take plain-text input and generate LaTeX code styled like Jake's Resume or AltaCV. They lower the barrier for anyone who wants LaTeX-quality output without learning the syntax.

What they actually do: feed your writing into a pre-existing LaTeX template (almost always a Jake's-style or AltaCV-style layout), compile to PDF. The template is not new — it is the same MIT-licensed code that has been free on Overleaf since 2019. What the AI adds is the writing assistance and the compile step, not the underlying layout.

The tool that actually got traction in this category isn't an AI wrapper. RenderCV takes a YAML file with your content and renders it to LaTeX and PDF, and since launching in June 2023 it has collected 17,400 GitHub stars, six times what Jake's Resume gathered in six years. Same trade as the AI builders, without the subscription or the chat window: you write the content, the tool owns the layout. MIT-licensed, runs on your machine, and the output is a single-column PDF that parses cleanly.

Where they help: if LaTeX syntax feels intimidating but you want the typography. Where they do not: the resulting PDF still has the same two-column-vs-ATS problem if the chosen template is two-column. An AI wrapper does not fix the parser issue.

If your goal is ATS-safe PDF output without compiling LaTeX at all, Mirrai's Resume Builder generates one-column parseable PDF from your content directly. The typography is not Computer Modern, but the ATS parsing is reliable across Workday, Greenhouse, and Lever.

FAQ

Related: Notion resume guide (for the block-based crowd), Canva resume templates (for the visual crowd), the ATS-friendly resume template breakdown, and the full ATS resume guide.

Keep LaTeX for the resume where you know a human reads it. For the corporate ATS pipeline, Mirrai's Resume Builder produces a one-column parseable PDF from your content without the compile-debug loop. Use the right tool for the right reader.