Why pre-screen virtual reality designers before the portfolio review
A capture of a virtual environment tells you nothing about what it feels like to stand in it. Frame drops, forced camera movement and interactions above shoulder height all read fine on video and make people uncomfortable in minutes. Designers worth hiring have watched someone take a headset off early and changed the design. A short screen asks about that person and what was done afterwards.
What actually matters when screening Virtual Reality Designer candidates
- 01
Portfolio
Ask for shipped VR builds on Quest, SteamVR, or PSVR2: probe their role in locomotion schemes, spatial UI, onboarding flows, and any published playtest or store metrics.
- 02
Craft and rationale
Test craft reasoning: why diegetic menus over floating panels, how they set affordances at arm's reach, frame budget trade-offs, and comfort choices like vignetting or snap turn.
- 03
Feedback and iteration
Probe how playtesting in-headset changed their designs: SUS or simulator sickness scores, observed flailing or hesitation, iteration cycles in Unity or Unreal blueprints.
- 04
Working with the brief
Judge collaboration with engineers, technical artists, and clients on scope: interpreting briefs for training sims, retail, or games under hardware and budget constraints.
Pre-screening questions to ask Virtual Reality Designer 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.
Experiences shipped
3 questions01What virtual reality projects have you worked on, and what was your role?
Listen forExperiences that shipped to real users, with the platform named and their own contribution distinguished.
Concept work and videos only, or contribution to a team project not separated out.
02Do you have a portfolio of work that shows your design experience?
Listen forWork that can be tried in a headset rather than only watched, with build files or store links provided.
Portfolio consisting entirely of rendered video, or nothing anyone can actually put on and use.
03Can you describe a project where you had to work to a tight deadline?
Listen forScope reduced deliberately with quality protected on the parts that affect comfort and performance.
Frame rate sacrificed to hit a deadline, or scope managed by cutting testing entirely.
Comfort designed
3 questions04What are the key considerations when designing for virtual reality?
Listen forComfort, frame rate and scale raised first, with a clear understanding of what causes discomfort.
Answers focused on visual fidelity, with comfort and performance not mentioned at all.
05What factors matter most in the user experience of a virtual environment?
Listen forPresence, reach and physical comfort considered, including how long someone can reasonably stay in it.
Session length not considered, or interactions designed above shoulder height for extended periods.
06How do you approach solving design challenges specific to this medium?
Listen forLocomotion and interaction solved with options offered, and the trade-offs of each approach explained.
Flat interface conventions transferred directly, or one locomotion method imposed on everyone.
Can build and test
4 questions07What experience do you have with the design and development tools for this medium?
Listen forPrototyping done in engine, so ideas are experienced in a headset rather than judged on a screen.
Designs produced only as flat documents, or no ability to build a testable prototype.
08What is your experience with three-dimensional modelling and animation?
Listen forAsset creation with polygon and draw call budgets respected, since performance directly affects comfort.
Assets built with no performance budget, or optimisation treated as someone else's problem.
09Do you have experience with scripting for interactive experiences?
Listen forEnough scripting to prototype interactions independently without waiting on an engineer for every test.
Every interaction requiring engineering support, or no ability to test an idea themselves.
10Can you explain your process for testing and debugging these applications?
Listen forFrame timing monitored on target hardware, with performance problems diagnosed rather than tolerated.
Testing done only on a high-end machine, or frame rate drops accepted as normal.
Users in a headset
2 questions11Do you have experience with user research and usability testing in this medium?
Listen forTesting with people new to headsets, with comfort and confusion both observed and acted on.
Testing done only with colleagues, or first-time users never observed putting a headset on.
12Can you discuss a time you received and implemented feedback on your design work?
Listen forA specific change made because of what testing showed, described without defensiveness.
Feedback acknowledged but never acted on, or design decisions defended against user evidence.
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 headset-ready builds they can name, explaining their exact contribution to locomotion, hand-tracking interactions, and measured retention or comfort outcomes.
Craft and rationale
25%5Justifies each interaction decision against presence, reach envelopes, and a 72 or 90 Hz frame budget rather than aesthetic preference alone.
Feedback and iteration
25%5Cites specific in-headset test findings that reversed an early design, with before and after builds and reduced discomfort or task failure.
Working with the brief
15%5Translates vague briefs into greyboxed prototypes and interaction specs quickly, negotiating scope against device limits and engineering effort.
Forced camera movement reads fine on video and makes people uncomfortable in minutes. A one-way video screen asks who took the headset off.
Try it on HirevireScreening FAQ
Process basics
How long should a pre-screening round for this role take?
Fifteen minutes across eight to ten questions, answered async, alongside a portfolio. Enough to establish shipped work, test comfort thinking, and check whether they observed real users.
Should they be able to build as well as design?
Enough to prototype in a headset. A designer who works only in flat mockups cannot judge scale, comfort or reach, all of which only become apparent when you stand inside the scene.
Evaluating answers
What is the strongest signal when screening this role?
Someone who felt unwell in their experience. Designers who test with real users have that story and the change they made. Anyone whose testing found no comfort issues has tested with colleagues.
How do I judge their comfort thinking?
Ask how they handle locomotion. Real answers cover the trade-offs between teleport and smooth movement and offer options. Anyone treating comfort as a settings menu has not designed for it.
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
