Game Industry Art Tests and Take-Home Assessments

The art test is the stage of games hiring nobody prepares you for. You get a brief, a deadline, and almost no information about how it will be judged — and for a lot of candidates it is the point where the process quietly ends.

Here is what studios actually send, how long to spend, and when a test has stopped being an assessment and started being free work.

What tests look like by discipline

Art

Usually a single asset or small scene to a spec: a prop or a modular set, with a polycount budget, a texel density target and a named engine. What is being assessed is rarely raw sculpting talent — it is whether you can hit a spec. Wireframes, UV layout and a breakdown matter as much as the beauty shot.

Design

A systems or level brief: design an ability set, balance an economy, whitebox a space, or critique an existing system. The deliverable is usually a short document, and the thing being measured is your reasoning, not your prose.

Programming

Either a small gameplay feature in the studio’s engine, or an architecture problem. Increasingly replaced by a live code walkthrough of something you already own — which is better for everyone and worth suggesting if the alternative is a week of unpaid work.

QA

A bug hunt in a deliberately broken build, plus writing the reports. Report quality is the whole test: clear reproduction steps, correct severity, no duplicates. This is the one discipline where the test genuinely levels the field for people with no credits.

Production

A scheduling or triage exercise. Here is the scope, here is the team, here is the date — what gets cut? They are watching how you make trade-offs and communicate them.

How long to spend

Whatever the brief says, plus nothing. If a test says eight hours, submitting forty hours of work does not signal enthusiasm — it signals that you cannot scope, which is a genuine red flag for a production environment.

If you cannot finish in the stated time, submit what you have with a short note explaining what you would do next and why you stopped. That note is frequently the most useful thing in the submission.

When a test is exploitative

Most tests are legitimate. Some are not. The signals:

• The work is shippable and specific to their product. A generic prop is a test. An asset that slots into their announced game is production work.
• The scope exceeds a working week with no payment offered.
• You are asked to sign over IP for unpaid work.
• There is no feedback and no timeline — a studio that will not say when it will respond is telling you something.
• It arrives before any human conversation. A test as the first contact is a filtering shortcut, not an assessment.

Asking whether the test is paid is completely reasonable and increasingly common. Studios that pay for anything over a few hours tend to get far better completion rates among people who already have jobs — and a studio that reacts badly to the question has answered a different one.

The remote-specific part

Remote processes lean on tests harder, because there is no on-site day and no informal read on how you work. Two consequences follow.

First, your written submission carries more weight — the note explaining your decisions is doing the job that a conversation would do in person.

Second, ask about timezone expectations while you are discussing the test. A studio that expects same-day turnaround across an eight-hour gap is describing its working culture, and you want to know that now rather than in month two.

Frequently asked questions

Should I do an unpaid art test?

For a reasonable scope — a day or less, generic subject matter, a named contact and a stated timeline — usually yes. For a week of production-ready work on their announced title, no.

Can I ask to be paid for a test?

Yes, politely, for anything substantial. Frame it around scope rather than principle: "this looks like about three days — is there a paid arrangement for tests of that size?"

Can I use the test in my portfolio afterwards?

Ask first. Many studios allow it, some do not, and some have an NDA that forbids it. Getting this in writing before you start avoids losing a good piece.

What if I do not finish?

Submit anyway with a clear note on what remains and why. Not submitting reads as giving up; an honest partial submission with good reasoning frequently still advances.

Do studios give feedback on tests?

Often not, and it is the most-complained-about part of the process. Ask at the outset whether feedback is offered — it costs nothing and sets expectations.

Next steps

Before the test stage, make sure the portfolio got you there on merit — see the guides on junior developer portfolios and getting hired as a remote 3D artist. When an offer arrives, check it against the published band before answering.

Sources

• GDC State of the Game Industry 2026, published 29 January 2026