What a CV actually is
A CV is a one-page, factual summary of what you can do, what you have made and where you learned it — written for a specific job, not for everyone. In games it has one purpose: to get someone to open your portfolio link, and then to survive the check that happens after they like your work.
Take a CV apart
Below is a CV built for someone finishing a Level 3 course with no paid games experience — the position you are in. Switch the role to see how the same structure carries completely different evidence. Tap any section of the CV to find out what a studio does with it.
Spot the stronger line
Both options say roughly the same thing. One of them survives a twenty-second read. Pick the stronger.
Rules that hold, and myths that do not
Some of this contradicts general careers advice you may have been given. Games hiring is its own thing, and where they conflict, follow the games-specific version.
Do
- Put your portfolio link in the header, as a plain readable address, not hidden at the bottom
- Put projects above education — what you have made matters more than where you studied
- Name software and {{engine|engines}} exactly: “Unreal Engine 5”, “Blender”, “Substance Painter”, “C#”
- State your own contribution on every team project, in specific terms
- Use numbers where they exist — team size, asset count, jam length, poly budgets
- Keep one consistent look with your portfolio and profiles
- Save and send as PDF, named Firstname-Lastname-CV.pdf
Do not
- Include a photo, your date of birth, your full address or your marital status — UK studios do not want them
- Use skill rating bars or star ratings; nobody knows what four stars in Maya means
- Write “references available on request” — it wastes a line everyone assumes anyway
- Claim software you cannot use in front of someone. It is tested at interview
- List “socialising, music, films” under interests. Use that space for {{jam|game jams}}, communities and personal projects
- Use a novelty email address, or one you no longer check daily
- Send a Word file, which reformats itself on someone else's machine
Where to read more
All UK-focused and free. The first two are the ones to use while writing; the rest are for working out which role you are aiming at.
Before you write yours
You will build your own CV in class. Bring the answers to these, because you cannot write a good CV from memory — the specifics are what make it work, and the specifics are what you will not remember.
When you have the answers, the CV Builder is where you write yours: a first version with no help, a check of what it gets wrong, then a rebuilt one you can print.