Why pre-screen 3D modelers before the paid test
A portfolio render is the output of modelling, texturing, lighting and post work, and it hides everything about the mesh underneath. An asset can look excellent and be unusable: dense where it does not need to be, with topology that deforms badly, unwrapped in a way that wastes texture space. None of that is visible in the images, and all of it costs your pipeline time. A short screen asks about the parts that do not appear in a render.
What actually matters when screening 3D Modeler candidates
- 01
Portfolio
Review their reel and turntables: ask which assets they modeled versus textured, polycounts shipped, and whether work went to game engines, film renders, or 3D print.
- 02
Craft and rationale
Probe topology decisions: edge flow for deforming meshes, quad discipline, UV packing and texel density, high to low poly baking, and tools such as Maya, Blender, ZBrush, Substance Painter, Marmoset.
- 03
Feedback and iteration
Test how they absorb art director and technical art notes: silhouette revisions, retopology requests, LOD reductions, and how many iterations a hero asset typically took.
- 04
Working with the brief
Assess how they work from concept sheets, scan data, or CAD references, plus adherence to naming conventions, scene scale, pivot placement, and engine or render pipeline specs.
Pre-screening questions to ask 3D Modeler candidates
12 questions grouped by what they test. Ask the same set in every screen and score answers on a consistent scale, or send them as an async video screen and compare answers side by side.
Their own assets
3 questions01Can you describe a complex modelling project you completed, and what you personally did on it?
Listen forClear separation of modelling, sculpting, retopology, unwrapping and texturing, with what was theirs on each piece in the portfolio.
Presents renders with no breakdown, or claims every stage on work that was clearly a team pipeline.
02Which 3D modelling software are you proficient in?
Listen forA primary package with real depth and an honest level on the others, plus whether they can work in the software your pipeline uses.
Lists every major package as proficient, or would need full retraining to work in your pipeline.
03Can you explain your experience with both hard-surface and organic modelling?
Listen forA stated strength with honest limits, since the two demand different skills, and examples that match the claim rather than covering both thinly.
Claims equal strength in both with a portfolio that only demonstrates one.
Topology and budgets
3 questions04How do you ensure your models are efficiently built and well structured?
Listen forEdge flow, clean quads where deformation matters, and density concentrated where it is seen, described as decisions rather than habits.
Topology not mentioned at all, or density applied uniformly regardless of what the asset needs.
05How do you approach optimising models for game engines or real-time environments?
Listen forPolygon budgets worked to, with levels of detail and baking described, and a case where they had to cut an asset down significantly.
No experience of a budget, or optimisation described as something the engineering team handles afterwards.
06How familiar are you with texture mapping and shading?
Listen forUnwrapping decisions explained with texture space used deliberately, plus real physically based material workflow rather than tweaking values.
Automatic unwrapping accepted without review, or materials built by adjusting sliders with no understanding of the model behind them.
Handling revisions
3 questions07What strategies do you use for handling feedback and revisions?
Listen forFiles structured so a change is a change rather than a rebuild, with version discipline that survives round five of notes.
Rebuilds from scratch on significant notes, or has lost work to a versioning mistake with nothing changed since.
08Have you worked on a project where the deadline moved up unexpectedly?
Listen forWhat they cut to hold the date, with the compromise flagged to the client or lead rather than delivered quietly.
Deadlines absorbed by working through the night, or quality reduced without telling anyone.
09Have you had to troubleshoot issues with a 3D model? How did you approach it?
Listen forA specific problem such as shading artefacts or a mesh that would not deform, traced to a cause rather than fixed by smoothing over it.
Problems resolved by remodelling the area, with no diagnosis of what caused the artefact.
Fitting the pipeline
3 questions10Are you familiar with game engine workflows such as physically based textures and levels of detail?
Listen forReal pipeline experience with naming conventions, export settings and what the engine team needed from them beyond the mesh.
Delivers files with no naming or scale convention, or has never had an asset rejected by a pipeline.
11Do you typically work on modelling projects individually or as part of a team?
Listen forExperience handing assets to riggers, animators or engineers, with what they learned about what the next person needs.
Works entirely alone with no handover experience, or unaware of what downstream stages require.
12Do you have experience creating models for real-time applications?
Listen forReal-time constraints understood: draw calls, texture memory and how an asset performed once it was actually in the build.
Only offline rendering experience presented as equivalent, or no awareness of runtime performance cost.
How to score responses
Score every candidate on the same four criteria immediately after the screen. At this stage you are shortlisting for panel interviews, not making the final call.
Portfolio
35%5Shows named shipped assets with wireframe turntables, states polygon budgets, and clearly separates their own work from team contributions.
Craft and rationale
25%5Explains clean edge loops around joints, controls texel density deliberately, and diagnoses baking artefacts like skewed normals or ray distance errors.
Feedback and iteration
25%5Describes specific redlines received, reworked topology or proportions without defensiveness, and cites turnaround times per revision round.
Working with the brief
15%5Reads concept art and orthographics accurately, follows studio naming and unit conventions, and flags spec conflicts before modeling begins.
A render hides everything about the mesh underneath, which is the part your pipeline pays for. A one-way video screen asks about topology and budgets before a paid test.
Try it on HirevireScreening FAQ
Process basics
How long should a pre-screening round for a 3D modeler take?
Ten to fifteen minutes across eight to ten questions, answered async. Enough to establish what they modelled versus lit or textured, hear how they think about topology and budgets, and confirm pipeline fit before a paid test.
Should I still run a paid test?
Yes, on a shortlist, and ask for the source file rather than a render. The screen exists so that the tests you pay for are with modelers whose specialism, software and pipeline experience already match what you need.
Evaluating answers
What is the strongest signal when screening a 3D modeler?
Talking about topology unprompted. Modelers who have worked in a real pipeline mention edge flow, deformation and polygon budgets without being asked, because those constraints shape every decision. Candidates who talk only about detail and realism have worked alone.
How do I judge portfolio attribution?
Ask what they did on each piece. Modelling, sculpting, retopology, unwrapping, texturing and lighting are often different people. A modeler who says which of those were theirs is telling you the truth; one who presents every image as wholly their own usually is not.
Go deeper on this role
Sanat has been hiring since 2012 and watching the recruitment industry change up close ever since, and turned that screening process into Hirevire's video screening platform. LinkedIn
