LLM-Resume-Template: a LaTeX skeleton for LLM and Agent engineer resumes
专业的 LaTeX 简历模板，专为大模型与 Agent 算法工程师设计 | Professional LaTeX resume template for LLM & Agent algorithm engineers
At a glance
- What is it?
- The repository ships several .tex resumes, a class file with optional photo support, and a content guide aimed at LLM, Agent, RAG and NLP applicants. The interesting part is not the typography but the instruction to replace every X/Y metric with numbers you can defend.
- Who is it for?
- Adopt it if you are applying for LLM, Agent, RAG or NLP roles and already accept LaTeX, because resume-agent.tex and CONTENT-GUIDE.md force you to state responsibility boundaries and verifiable metrics. Do not adopt it if you need a Word file, a one-page layout, or an actively maintained dependency, since the last push was on 2026-08-12 and there are no releases.
- Can I use it commercially?
- Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
- Is it still maintained?
- Yes. The repository last received commits 34 days ago.
- What is it written in?
- Mainly TeX, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 15, 2026, and from our analysis. They are not legal advice.
DEEP OPEN-SOURCE ANALYSIS
The problem is not layout, it is evidence
Most resume templates solve formatting. This one is aimed at a narrower problem: LLM and Agent job seekers tend to write bullets that name a model, a framework and a percentage, without saying what they personally owned or how the number was measured. The README describes CONTENT-GUIDE.md as covering "证据组织、指标口径与自检方法", which is evidence organisation, metric definitions and self-checking. That is the actual product. The TeX files are the delivery vehicle. The intended audience is stated plainly: candidates for 大模型、Agent、RAG、NLP positions, with the README adding that resume-agent.tex is an anonymised content skeleton rather than a copy of anyone's history. It is a poor fit for a general software engineer applying to a backend team, and a poor fit for anyone who has never written LaTeX, because every content change happens inside .tex source.
What is actually in the repository
The README's file listing shows five .tex entry points and two class files. resume-agent.tex is the two-page A4 Agent and LLM example, anonymous and without a photo. resume-photo.tex is the photo version and is marked as recommended. resume-zh.tex is a full Chinese example without a photo, resume-model.tex is the placeholder template, and resume-en.tex is the English template. resume.cls holds the standard style and resume-photo.cls adds photo support. Supporting files include adongwanai.jpg as a sample avatar, a Makefile, a fontawesome5 directory of icon fonts, and CONTENT-GUIDE.md. There are no releases, so the only version you can pin is a commit on the main branch. The README also pushes readers to fork before editing, on the grounds that a fork keeps your version separate and makes it easier to pull later changes. That is a reasonable workflow for a template, though it means your resume lives in a public repository unless you make the fork private.
Compiling: XeLaTeX, Overleaf, and the Makefile targets
The README gives three routes. Overleaf is listed first: upload the ZIP, then in Menu set the Main document to resume-agent.tex, resume-photo.tex, resume-zh.tex or resume-model.tex, confirm the compiler is XeLaTeX, and recompile. Locally, the commands are xelatex resume-agent.tex run twice, or xelatex resume-photo.tex run twice, with the README noting the second pass is needed "以生成正确的目录和引用". For the Chinese version the Makefile target is make zh. XeLaTeX is not optional here: the class files load CJK text and fontawesome5 icons, and pdfLaTeX will not handle that combination. The photo is swapped by editing line 17 of resume-photo.tex to \ResumePhoto{你的照片文件名.jpg}, and the README says deleting or commenting that line disables the photo. Personal fields differ per template: the photo version uses \ResumeName and \ResumeContacts with \ResumeUrl for the mailto link, while the no-photo versions use \name, \keywords and a \profile block containing \mobile, \email, \university, \degree and \birthday. Mixing the two conventions across files is the most likely first compile error.
The X/Y placeholder rule is the real constraint
The README states that all X/Y metrics in resume-agent.tex must be replaced with real data you can explain and verify. Read together with CONTENT-GUIDE.md, that turns the template into a checklist rather than a form. The structure it demonstrates is job positioning, public evidence, responsibility boundary, key mechanism, verification method, business result. The responsibility boundary item is the one most candidates skip: it forces you to say which part of a system you built and which part your team built. The AI prompt examples go further and ask for real model names such as LLaMA, Qwen and GPT-4, real benchmarks such as MMLU, HumanEval and GSM8K, and plausible improvement ranges of 5% to 20%. That last instruction is the weak point. A template that suggests a range for your numbers is inviting fabrication, and a reviewer who knows the benchmarks will notice a 20% HumanEval jump that has no corresponding training detail. Treat the ranges as a sanity check on your own measurements, not as a target.
Where the template fails you
Nothing in the README describes a one-page mode. The Agent example is explicitly two pages of A4, which is long for a first-round screen at many companies and may be rejected by portals with a page limit. There is no documented way to generate a PDF/A or plain-text variant for application systems that parse resumes, and no accessibility or ATS guidance. The class files are the maintenance surface: if your TeX Live distribution changes font handling or the fontawesome5 package version, you are debugging a .cls file you did not write, and the README does not document rollback or a known-good TeX Live version. The photo version is also a liability in some markets, where including a photograph and a birth date invites bias complaints; the no-photo templates avoid this, and the README does not discuss the trade-off. Finally, the README's repeated requests to star and fork the project are noise in an otherwise useful document.
Compared with a Markdown-to-PDF pipeline
The obvious alternative is a Markdown resume plus Pandoc or a hosted builder such as RenderCV or a JSON Resume theme. The difference is not output quality, it is the editing model. Markdown pipelines keep content in plain text and let a tool own the layout, so you can regenerate HTML, PDF and plain text from one source. This template inverts that: the layout lives in resume.cls and the content lives inside LaTeX macros, so a change to spacing or section order means editing TeX. In exchange you get precise control over a two-page A4 layout, CJK text, and icon fonts without fighting a converter. If you apply to many companies and want to tailor per role, the Markdown route is faster. If you want one carefully typeset PDF and are comfortable in TeX, this template is the shorter path.
Maintenance, licence and what to check first
The repository is not archived, and the last push was on 2026-08-12, so recent activity exists but there are no tagged releases and no changelog. Upgrading means pulling from main and re-reading CONTENT-GUIDE.md, because that file carries the writing rules and is the part most likely to change. Forking, as the README recommends, is also the cheapest way to avoid merge conflicts in your own resume. On licensing, the situation is inconsistent: the README badge declares CC BY 4.0, while the repository metadata carries no licence field. CC BY 4.0 permits commercial use and modification with attribution, but it is a content licence, not a software licence, and it is unclear how it is meant to apply to resume.cls and resume-photo.cls. If you plan to redistribute the class files or build a paid service on them, confirm the terms with the author rather than relying on the badge. This is not legal advice; a lawyer can tell you whether the badge binds you.
Editorial conclusion
Adopt it if you are applying for LLM, Agent, RAG or NLP roles and already accept LaTeX, because resume-agent.tex and CONTENT-GUIDE.md force you to state responsibility boundaries and verifiable metrics. Do not adopt it if you need a Word file, a one-page layout, or an actively maintained dependency, since the last push was on 2026-08-12 and there are no releases. Before editing, verify that the CC BY 4.0 badge in the README is the licence you are actually bound by, because the repository metadata carries no licence field.
Community notes