The TA Resume & Cv
A CV should make your relevant experience and portfolio easy to find. Lead with the work that fits the role, keep the claims specific, and use the template below as a starting point.
The Rules
- Keep it concise. One page is a useful target for a junior CV. Use more space where relevant experience needs it, rather than cutting useful evidence to meet an arbitrary limit.
- Put your portfolio and code links near the top. Check that they work in the final PDF and lead directly to the relevant work.
- Lead with projects, not education - unless the degree is genuinely your strongest card. "Projects" can mean shipped games, mods, jam entries, or the three portfolio pieces from the portfolio formula.
- Group your skills clearly. Languages, DCCs, and engines or tools are useful categories. List skills you can discuss or demonstrate; stars and percentages rarely explain what you can actually do.
- Keep the layout readable. Use clear headings, consistent type, and enough space between sections. The work should be easier to assess because of the design.
Writing Useful Project Bullets
Describe what you built and what changed as a result. A concrete outcome gives the reviewer more to work with than a list of responsibilities.
| Weak | Strong |
|---|---|
| "Worked on tools for the art team" | "Built a Blender batch exporter (Python/bpy) used by 6 artists - cut prop export time from ~15 min to under 1" |
| "Experienced with shaders" | "Authored the project's master material set; reduced shader permutations 40% during the optimisation pass" |
| "Helped with pipeline" | "Wrote the P4 pre-submit validator that blocks wrongly-named assets - naming violations dropped to zero in two sprints" |
No metric? Estimate honestly ("about an hour a week per artist") or state scale ("used across 300+ assets"). A rough number you can defend in an interview beats a vague claim you can't.
The Keyword Filter, Without Writing Like A Robot
Compare your CV with the job description and use the relevant technical terms where they're accurate. Don't add skills you can't support. A person should still be able to read each sentence naturally.
Export a PDF with selectable text and check its reading order. That makes it easier for people and recruitment systems to read.
"But I Have No Experience"
You can show practical experience before your first paid role. Personal tools, game jams, mods, and collaborative projects all give you work to discuss. Be clear about the context, your contribution, and who used the result.
For a first role, try this order: contact and portfolio links, relevant projects, skills, then education and other useful experience. Keep it factual. You don't need to pad the page to make the work count.
The Template
The template is Markdown, so you can edit it in a text editor and keep changes in Git. Export it to PDF with your preferred editor, then check the text and links.
# Firstname Lastname - Technical Artist portfolio.example.com - github.com/you - you@example.com - City / Remote (TZ) ## Projects **Batch Export Toolkit** - Python, Blender bpy - [github link] - Built a collection-aware FBX batch exporter with per-engine presets; used on a 4-person team, cut export setup from ~15 min to one click - What I'd change next: move preset storage from JSON to scene custom properties **"Riverbed" - stylized water shader** - HLSL, Unreal 5 - [breakdown link] - Authored depth-fade foam + flowmap water as a single master material, 6 artist-facing parameters, runs on Quest 3 within budget (breakdown on site) **Asset Validator** - Python CLI - [github link] - Pre-submit validator: naming, scale, missing LODs; blocks bad assets at the door - zero naming violations since adoption ## Skills - **Code:** Python, HLSL, a little C++ - **DCC:** Blender, Maya (cmds), Houdini (VEX basics) - **Engine & pipeline:** Unreal 5, Unity, Perforce, Git, Jira ## Experience **Freelance / personal pipeline work** - 2025-present - (Same bullet style: verb -> thing -> outcome) ## Education **BA Something, University of Somewhere** - 2024