Overleaf makes LaTeX CV creation accessible to anyone with a browser and a free account. The challenge is not the editor itself, it is knowing which of the hundreds of available templates will pass an ATS scan and which will scramble your application before a human ever reads it. This guide covers both the academic and professional template stacks, gives you a step-by-step workflow for first-time users, and ends with the ATS testing step that almost every other Overleaf guide skips.
What Is Overleaf and Why Use It for Your CV
Overleaf is a cloud-based LaTeX editor that runs entirely in your browser. You do not need to install TeX Live, MiKTeX, or any local LaTeX distribution. Open a browser, create a free account, and you are compiling documents in seconds.
LaTeX has been the standard document preparation system in academia, mathematics, computer science, and engineering for decades. It produces typographically precise PDFs with consistent spacing, clean font rendering, and precise control over every layout element. For CVs and resumes, those properties translate to documents that look professional without any design software.
Who Should Use Overleaf for a CV
- Academics and researchers who need publications, grants, conference presentations, and teaching sections formatted consistently
- Computer science and engineering students who want the typographic quality and template ecosystem that LaTeX provides
- PhD candidates and postdocs applying to academic positions that expect a formal academic CV format
- Software engineers who want a clean, text-heavy resume that performs well in ATS screening
Overleaf Free vs. Paid
The free Overleaf plan covers everything most CV users need: unlimited projects, access to all public templates, PDF compilation, and PDF download. The paid tiers add real-time collaboration (useful for academic advisors reviewing a CV) and version history. For solo CV work, the free tier is fully sufficient.
Academic CV vs. Professional Resume on Overleaf
These are two distinct document types with different purposes, lengths, and section requirements. Confusing them is a common mistake.
| Dimension | Academic CV | Professional Resume |
|---|---|---|
| Length | No limit; grows with career (2 to 20+ pages) | 1 to 2 pages maximum |
| Core sections | Publications, conferences, grants, teaching, research interests, referees | Work experience, skills, education, summary |
| Purpose | Faculty positions, postdocs, fellowships, research grants | Industry jobs, corporate roles, technical positions |
| Date conventions | All dates listed; publication dates critical | Work history dates listed; gaps visible |
| ATS exposure | Low (mostly human review in academia) | High (industry applications are routed through parsers by default) |
| Overleaf template match | Academic CV, Clean Academic CV, Minimal Academic CV | Jake's Resume, Awesome-CV, ATS Friendly Technical Resume |
The most important practical distinction: if you are applying to industry roles, do not use an academic CV template. The multi-page format with publications and referees looks unusual to corporate hiring managers and may trigger ATS length penalties. Likewise, if you are applying for a faculty position, a two-page industry resume is insufficient.
See how your resume scores against the job
We optimize it for ATS automatically, no manual fixes, and show your match score in seconds.
Best Overleaf CV Templates by Category
The table below rates each popular template on ATS risk, since that is the most consequential technical factor for anyone applying to industry roles.
| Template Name | Best For | ATS Risk | Style | Overleaf Link |
|---|---|---|---|---|
| Academic CV (Trey Hunner) | Faculty, postdocs, PhD students | Low | Single-column, traditional | overleaf.com/gallery/tagged/cv |
| Clean Academic CV | Researchers, early-career academics | Low | Minimal, single-column | overleaf.com/gallery/tagged/cv |
| Minimal Academic CV | Postdoc applications, grants | Low | Plain, maximum readability | overleaf.com/gallery/tagged/cv |
| Jake's Resume | Software engineers, CS students | Low | Single-column, ATS-optimized | overleaf.com/latex/templates/jakes-resume/syzfjbzwjncs |
| Awesome-CV | Tech professionals, engineers | Medium | Modern, minimal color accents | overleaf.com/latex/templates/awesome-cv/dfnvtnhzhhbm |
| ATS Friendly Technical Resume | Engineers applying to corporate roles | Low | Single-column, no icons | overleaf.com/gallery/tagged/cv |
| Friggeri CV | Design portfolios, creative roles | High | Two-column, graphic sidebar | overleaf.com/latex/templates/friggeri-cv/hmnchbfmbrdz |
| Modern Simple ATS Friendly LaTeX CV | All industry roles | Low | Clean, professional, single-column | overleaf.com/gallery/tagged/cv |
Academic Templates: What Each Includes
Academic CV (Trey Hunner): The most-used academic template on Overleaf. Structured for a complete academic record: education, publications (with BibTeX integration), presentations, teaching experience, grants, and referees. Works without modification for faculty applications.
Clean Academic CV: A lighter version suited to early-career researchers who have a shorter publication list. Easier to customize for different disciplines. The section order can be rearranged by moving LaTeX blocks without rewriting commands.
Minimal Academic CV: The most stripped-down option. Prioritizes white space and readability over typographic complexity. Good for fellowship applications that ask for a concise CV.
Professional Templates: Jake's Resume and Alternatives
Jake's Resume: The most widely used professional resume template on Overleaf, and the one most often recommended in software engineering communities. Single-column layout, standard section headings (Education, Experience, Projects, Technical Skills), no icons, no columns, no graphics. Compiles to a PDF that passes every major ATS scanner. The go-to template for software engineering applications at tech companies.
Awesome-CV: A widely used template with subtle color accents (a thin colored header bar). The ATS risk is medium because the color header can occasionally confuse parsers, but the body text is single-column and standard. Safe for most tech roles; use Jake's Resume if you want to minimize risk entirely.
ATS Compatibility Guide for Overleaf Templates
Industry applications are routed through an applicant tracking system by default, and the share of employers doing so is quoted so widely and sourced so poorly that we will not repeat a number for it here. What matters for Overleaf users is mechanical and not statistical: ATS compatibility depends entirely on how the LaTeX template structures its output PDF.
What Makes an Overleaf Template ATS-Friendly
- Single-column layout: ATS parsers read documents top-to-bottom, left-to-right in a single text stream. Two-column templates split your content into two streams; the ATS often reads column one in full, then column two, garbling your work history.
- No icons or symbol packages: FontAwesome icons, phone symbols, envelope icons, and similar decorative elements are parsed as random characters or skipped entirely. Your contact information can become unreadable.
- Standard section headings: ATS systems are trained to recognize "Work Experience," "Education," "Skills." Non-standard headings like "Where I've Been" or "What I Know" may cause sections to be misclassified.
- Standard fonts via pdflatex: Templates that compile with pdflatex and use system fonts (Arial, Times New Roman, Calibri) produce clean text extraction. Templates that embed fonts as images or use exotic font packages can cause parsing failures.
- No tables for layout: Tables used to create multi-column layouts scramble text extraction. Tables used for data (publication lists, skills grids) are a gray area and should be tested.
High-ATS-Risk Overleaf Templates to Avoid for Industry Jobs
- Friggeri CV (graphic sidebar, two columns)
- Any template with a colored left-sidebar containing contact info
- Templates that use FontAwesome icons for section headers or contact details
- Templates with a photo or headshot placeholder in the header
- Templates that use
\begin{tabular}for the main layout structure
The Copy-Paste Test
After compiling your Overleaf template to PDF, open the PDF in Adobe Reader or Chrome and try to copy-paste the content into a plain text document. If the text comes out in the correct order with no garbled characters, the template will likely pass ATS parsing. If the columns are interleaved or contact info appears as symbols, it will fail.
The Single-Column Overleaf Resume, as Copy-Paste Source
Every other guide to Overleaf resume templates shows you screenshots and sends you to a gallery. That is fine until the template you liked has been renamed, restructured, or filled with packages you now have to debug. The document below is the whole thing: a complete, compilable, single-column LaTeX resume with no external template dependency. Paste it into a blank Overleaf project, hit recompile, and you have a working ATS-safe resume you fully control.
Minimal ATS-safe resume (paste into a blank Overleaf project)
\documentclass[letterpaper,11pt]{article}
\usepackage[margin=0.75in]{geometry}
\usepackage{enumitem}
\usepackage[hidelinks]{hyperref}
\usepackage{titlesec}
% Single column, no icon packages, no fontawesome, no tabular layout.
\pagestyle{empty}
\setlist[itemize]{leftmargin=*, topsep=2pt, itemsep=1pt}
\titleformat{\section}{\large\bfseries\uppercase}{}{0em}{}[\titlerule]
\titlespacing{\section}{0pt}{10pt}{6pt}
\begin{document}
% --- Contact block: plain text, in the body, never a header/footer ---
\begin{center}
{\LARGE \textbf{JORDAN AVERY}}\\[3pt]
Austin, TX $|$ (512) 555-0142 $|$ jordan.avery@email.com $|$
linkedin.com/in/jordanavery
\end{center}
\section{Professional Summary}
Backend engineer with six years building payment infrastructure.
Reduced transaction failure rate from 2.1\% to 0.4\% across a service
handling 40 million monthly requests.
\section{Experience}
\textbf{Senior Backend Engineer} \hfill Jan 2023 -- Present\\
\textit{Northwind Payments, Austin, TX}
\begin{itemize}
\item Rebuilt the retry pipeline, cutting failed transactions 81\%.
\item Led migration of 14 services to a shared auth layer.
\item Mentored four engineers; three promoted within 18 months.
\end{itemize}
\textbf{Backend Engineer} \hfill Jun 2020 -- Dec 2022\\
\textit{Cedarline Software, Austin, TX}
\begin{itemize}
\item Shipped the billing API now serving 1,200 business accounts.
\item Cut p99 latency from 840ms to 190ms via query restructuring.
\end{itemize}
\section{Education}
\textbf{B.S. Computer Science} \hfill 2020\\
\textit{University of Texas at Austin}
\section{Technical Skills}
Python, Go, PostgreSQL, Redis, Kafka, Docker, Kubernetes, AWS,
Terraform, REST API design, distributed systems
\end{document}
Five deliberate choices in that file are the entire reason it parses. There is no \begin{tabular} anywhere, so nothing creates a hidden column structure. There is no icon package, so your phone number is characters rather than a glyph. The contact block sits in the document body rather than in a header, so extraction reaches it. Section names are the conventional uppercase words, so classification succeeds. And \hfill handles date alignment, which is the job most templates hand to a two-column table and thereby break.
If Overleaf reports an error on first compile, it is almost always a missing package rather than a mistake in the document. Overleaf installs the four used here by default, so a clean paste should build on the first try.
Turning it into an academic CV
The same skeleton becomes a CV with three changes, and none of them touches the structural rules above. Drop the summary, since a CV does not open with a pitch. Reorder the sections to education first, then publications, presentations, teaching, grants, service. Then remove the length discipline: a resume is compressed to fit, a CV is complete by design and grows for as long as your record does.
For publications specifically, add \usepackage{natbib} and pull entries from a .bib file rather than typing them. BibTeX is the single strongest argument for writing an academic CV in LaTeX at all: the citation formatting stays consistent across hundreds of entries, and switching between required styles is one line rather than an afternoon.
How a Parser Actually Reads Your Compiled LaTeX PDF
LaTeX has an unusual reputation in resume advice. It is described either as the most ATS-safe format available or as a guaranteed rejection, and both claims are made confidently. Neither is right, because the format is not what gets read. The compiled PDF is, and LaTeX can produce PDFs at both extremes.
Here is what our own pipeline does with the file, which is close enough to what an employer's parser does to be useful:
| Stage | What happens | What breaks it in a LaTeX document |
|---|---|---|
| Text extraction | Characters are pulled out of the PDF's text layer. | XeLaTeX or LuaLaTeX with an exotic font whose glyphs lack a clean Unicode mapping. The page looks flawless and copies out as gibberish. |
| Reading order | Extracted characters become one linear stream. | Any two-column construction, including multicol, a minipage pair, or a tabular used for layout. Content survives; sequence does not. |
| Section classification | Headings are matched to known section types. | Renamed sections. Templates fond of "Odyssey" or "Toolbox" instead of Experience and Skills leave the content unlabeled. |
| Field parsing | Titles, employers and dates are separated inside each entry. | Dates placed in a right-hand column rather than inline. The date detaches from its role and can attach to the wrong one. |
| Scoring | Content is compared against one job description. | Nothing LaTeX-specific. By this point the format no longer matters, only whether the earlier stages preserved your content. |
The practical consequence is that the compiler you choose carries real risk. pdflatex with standard fonts produces the most reliably extractable text layer. XeLaTeX and LuaLaTeX exist precisely to give you fonts that pdflatex cannot use, which is a feature for a thesis and a liability for a resume. The template above compiles with pdflatex for that reason.
Our score itself combines a language-model assessment of fit with deterministic checks for exact skill matches, job title, management level, education and certifications, measured against one job description at a time. Note what is not in that list: the tool you wrote the document in. No parser rewards or penalizes LaTeX as such. It only ever sees the PDF.
How to Use an Overleaf CV Template: Step-by-Step
For users new to Overleaf, the workflow below takes you from zero to a compiled PDF in under 30 minutes.
- Create a free Overleaf account at overleaf.com. Your email address is sufficient; no payment information is required for the free tier.
- Browse the CV gallery. Go to overleaf.com/gallery/tagged/cv. Filter by most popular to see the templates with the largest user bases.
- Click "Open as Template." This creates a personal copy of the template in your Overleaf account. You are not editing the original; changes affect only your copy.
-
Edit the .tex file. The main file (usually
main.texorcv.tex) contains your content. Replace placeholder text with your own. Section commands like\section{Work Experience}define the structure. - Compile. Click the green "Recompile" button (or press Ctrl+Enter). The PDF preview updates on the right. Compilation errors appear in the log panel below; most are caused by special characters (%, &, $, #) that must be escaped in LaTeX as \%, \&, \$, \#.
- Download the PDF. Click the download icon next to the PDF preview. This is the file you submit.
- Test ATS compatibility. Upload the PDF to Resume Optimizer Pro's free ATS checker to verify that the text is parsed correctly before submitting.
Customizing Your Overleaf CV Without Being a LaTeX Expert
LaTeX has a reputation for complexity, but CV customization rarely requires advanced LaTeX knowledge. Most changes are straightforward text edits.
Safe Edits for Beginners
- Replacing text: Find the placeholder text (usually in the .tex file) and overwrite it with yours. Name, email, job titles, company names, and bullet points are all plain text replacements.
- Adding a bullet point: Most templates use
\iteminside anitemizeor similar environment. Copy an existing line, paste it below, and edit the text. - Removing a section: Comment it out by adding % at the start of each line in that section block, or delete the block entirely.
- Adding a new section: Copy an existing
\section{}block and rename it. The structure repeats consistently across well-built templates.
Edits to Avoid Without LaTeX Experience
- Changing column definitions in the document class or preamble
- Modifying font packages or font size declarations
- Changing the page geometry (margins) beyond simple
\geometry{margin=0.75in}adjustments - Adding custom package imports unless the template documentation mentions them
Quick Fix: Special Characters That Break Compilation
These characters must be escaped in LaTeX body text:
| Character | Escaped version |
|---|---|
| % (percent) | \% |
| & (ampersand) | \& |
| $ (dollar) | \$ |
| # (hash) | \# |
| _ (underscore outside math mode) | \_ |
After Export: Testing ATS Compatibility
Downloading a PDF from Overleaf is not the last step if you are applying to industry roles. The PDF needs to pass ATS parsing before it reaches a recruiter's inbox.
Resume Optimizer Pro's free ATS checker parses your uploaded PDF and shows you exactly how the system reads your document: which sections are identified correctly, which keywords are extracted, and where formatting issues cause data loss. For Overleaf users, the most common findings are:
- Contact information parsed as a single unstructured string (common with icon-heavy headers)
- Skills section merged with work experience (common with two-column templates)
- Bullet points stripped of their content due to custom list environments
- Email address or LinkedIn URL appearing as garbled text due to FontAwesome icon rendering
If the checker finds parsing issues, the fix is to switch to a single-column, icon-free template (Jake's Resume or ATS Friendly Technical Resume on Overleaf) rather than trying to patch the problematic template.
Frequently Asked Questions
\item line and editing it. Where people get stuck is structural change, such as removing a section that a template defined with a custom command, because deleting half of a command pair produces an error that names a line nowhere near the actual problem. Two habits prevent most of that pain: recompile after every small change so you always know which edit broke the build, and change one thing at a time.