Start Here
Here's a suggested route into technical art, with links to the guides and projects for each stage. Treat the timings as a starting point. Your experience, available time, and interests will change the pace.
Before You Commit
Find Out If This Is Your Job
Technical art may suit you if you enjoy making things look good and helping people work more efficiently. You don't need to start as an expert in art or programming. Curiosity, patience, and a willingness to learn both are useful foundations. Read the role guide and specialisations page, then try a small task that interests you.
The Path
Get Comfortable With Python
Start with files, paths, strings, dictionaries, loops, and functions. These are the parts of Python you'll reuse in DCC tools and pipeline scripts. Aim to finish a small script that solves a real task; that gives you something concrete to test and improve.
Pick A DCC And Automate It
Choose one 3D package and learn its scripting API. Blender is an accessible starting point; Maya and Houdini may be more relevant to the work you want to do. Pick based on that goal and spend time using the package before trying to automate it. Learn the basics of version control alongside it.
Get Engine Literate
Practise importing assets, building materials, and investigating performance in an engine. Unreal's pipeline and performance guides give you a starting point. If you're aiming for Unity roles, use that engine for the exercises. Many concepts carry across, but the APIs and workflows differ.
Choose A Specialisation And Build Something
Pick an area you'd like to explore further: shaders, procedural content, pipeline, or rigging. A tool, a shader, and a pipeline script can make a useful starter portfolio, though the mix should suit the role. The project briefs give you a problem, constraints, and checks for the finished result.
Apply Like A TA: Systematically
Keep a record of applications and use what you learn to improve the next one. Make your CV and portfolio easy to read, lead with relevant work, and practise explaining your decisions. Rejections are part of the process; they don't always tell you much about the quality of your work.
Your First Few Months
Learn how the studio's pipeline works before proposing changes. Spend time with artists and engineers, ask about unfamiliar terms, and start with a small improvement you can test safely. That context will help you choose more useful work as you settle in.
For example, a starter portfolio could include a Blender naming tool, a dissolve shader with a clear breakdown, and a Python script with tests. Together they show how you build, explain, and check your work. A degree or a polished reel can add context, but neither replaces that evidence.
Everything In This Section
Building A Portfolio
Choose useful projects, explain how they work, and show the decisions behind them. Includes a starter mix of a tool, a shader, and a pipeline script.
-> CareerThe TA Resume & Cv
Lead with relevant work and make the portfolio link easy to find. Includes a template you can adapt.
-> CareerInterview Prep & Question Bank
Practise explaining Python, maths, shaders, pipelines, and team decisions. Each example answer walks through the reasoning.
-> CareerSalary & Negotiation
How to research comparable roles, understand an offer, and prepare for the salary conversation.
-> CareerStudio Survival Guide
Settling into a studio, understanding its pipeline, working across teams, and managing your workload.
-> CareerVersion Control For TAs
Perforce and Git for code and art assets. Covers daily commands, binary files, and recovering from common mistakes.
->