Salary & Negotiation

Directional Numbers (2026, Annual Base)

VFX/film TAs typically land a band lower than game TAs at the same experience; big-tech-adjacent studios (engine vendors, platform holders) a band higher, sometimes with meaningful equity on top.

What Moves The Number

• Specialization premium. Shader/graphics-leaning and pipeline/tools-engineering TAs price closer to engineering bands - often 10-25% over generalist TA. Rigging TAs with strong Python are perennially scarce and priced accordingly. Being "the person who can talk to rendering engineers" is worth real money.
• Shipped titles. One shipped game moves you more than two years of unshipped work. It's unfair and it's real.
• The engineering-ladder trick. Some studios can file a TA as a "tools engineer" or "graphics programmer" on the engineering ladder - same work, different band. If your skills support it, it's worth asking which ladder the role sits on. The title on the ladder matters more than the title on your badge.
• Studio size. AAA and platform holders pay top of band with process attached; small indies pay less in cash and more in scope (you'll do everything - that breadth is worth a lot at your next job).
• Remote. Post-2020 norms stuck unevenly: some studios pay location-adjusted, some pay one national band. Always ask which policy applies before you anchor on a number.

Do Your Own Research (One Evening, Honestly)

1. Posted ranges: job posts in transparency states (California, Colorado, New York, Washington) legally include ranges - search comparable roles regardless of where you live; they anchor the market.
2. The GDC State of the Industry survey and community salary sheets (the tech-art community runs periodic anonymous surveys - ask in the Tech-Artists.org Slack or the big TA Discords).
3. Ask people. "What should someone with my portfolio expect at a studio like X?" is a completely normal DM to a senior TA. Most will answer. We've all been the person who didn't know.

The Scripts

Negotiation is a five-sentence conversation that people lose sleep over for a week. The sentences:

When asked for expectations early (deflect - whoever names a number first anchors):

"I'd rather make sure we're a fit first - I'm confident we can land on
something fair if we get there. Can you share the band for the role?"

They almost always share the band. If they insist you go first, give a researched range, top-anchored: "based on posted ranges for similar roles, I'm looking around X-Y."

When the offer arrives (never accept on the call - warmth plus a pause):

"Thank you - I'm genuinely excited about this. I'd like a couple of days
to review the full package. Can I come back to you Thursday?"

The counter (one number, one reason, zero apology):

"I'm excited to accept if we can get base to [number]. Comparable roles
I'm seeing are posted at [range], and given [shipped title / shader
specialization / the pipeline work in my portfolio], I think that's fair.
Everything else in the offer looks great."

Counter 8-12% over the offer, once, and mean it. A researched counter is expected - recruiters budget for it, and the worst realistic outcome is "we can't move on base, but..." which opens the door to the next section. The only way to actually lose is bluffing numbers you can't source or negotiating past a yes.

Beyond Base Salary

If base won't move, these often will - roughly in order of long-term value: signing bonus (easiest yes in the building - it's one-time money), level/title (a "mid" vs "senior" stamp changes every future band), review timing ("can we do a 6-month review with a defined raise path instead?"), remote flexibility, education budget (GDC/SIGGRAPH tickets are cheap for studios and career-compounding for you), and extra PTO. Get whatever is agreed in the offer letter - verbal promises don't survive reorgs.