A guide to hiring augmented reality designers
Augmented reality puts digital objects into the space around a person, seen through a phone, a tablet or a headset. A sofa appears in the living room. A step-by-step guide floats beside a machine. A character stands on a desk. Making that feel natural is a design job, and it is quite different from designing a flat screen. This guide explains what augmented reality designers do, how the role differs from nearby roles and how to set up the work so it goes smoothly.
What an AR designer works on
The first area is space. The designer decides where an object appears, how big it is and how it behaves when someone walks around it or leans in. The second is placement. People need to find a floor or a table, see that the app has found it and put the object down with confidence. The third is light and look: shadows, reflections and colour that help the object fit the room. The fourth is input, such as taps, drags, pinches or hand tracking. The last is guidance, meaning the short hints and safety notes that help a first-time user. A few designers cover every part, while most are strongest in one, so tell us which part you need most.
AR designer or someone else?
An AR designer plans the experience in the room. A VR developer writes code for headset apps, and a Unity developer builds in one of the engines that many AR projects use. A UI/UX designer works on app and website screens, which counts for the menus around an AR view but not for how an object sits on a table. A game designer plans rules and levels. A graphic designer makes brand visuals. Come to this page when your question is how the experience should feel in a real place.
Who owns which decision
- The designer owns the layout, the placement flow, the gestures and the hints, and records each choice.
- The developer builds it and reports what is slow or risky on a real device.
- The 3D artist makes the models and textures, working to a size and cost the designer sets.
- The product owner sets the order of work and what gets cut.
If two people overlap, still give each decision a single owner. A debate about how big a virtual chair should look ends faster when everyone knows who decides.
Questions to answer first
- The device your users have: phone, tablet, headset or a mix.
- The place of use, such as a shop, a home, a factory floor or outdoors.
- The part you need first: the concept, the placement flow, the look of the objects or the testing.
- Where the 3D models come from, and who checks that they are light enough.
- Who has the final word when the designer and the developer disagree.
How to read an AR portfolio
A demo video can look smooth because it was filmed in one good room. Ask to see the work running on a device, or ask the designer to talk you through it live. Good portfolios show the first minute of use, what happens when tracking is lost and how the design changed after testing. Treat portfolios made only of rendered mock-ups with care, because they show a wish and not a working experience. Ask for the reasoning behind each choice, since it predicts the next one.
Questions for the interview
- How do you help a first-time user find a surface and place an object?
- An object looks too small in a bright room. What do you check, and what do you change first?
- What do you do when tracking is lost halfway through a task?
- How do you brief a 3D artist so the models stay light enough for a phone?
- Describe an idea you dropped after testing it somewhere real. What made you let it go?
Good answers name a real project, say what went wrong and describe the fix. Be wary of anyone whose tests all went well.
Set a short paid task
Hand each finalist a short brief close to your real project. Three good options are a one-page plan for placing one product in a room, a flow for the first thirty seconds of use, or a list of things that could go wrong in poor light, each with a fix. Pay for the work. Then judge the writing, how well the idea suits your users and how the person deals with questions about the room and the device.
Fit the person to the stage
Early on, look for someone who sketches an experience fast and drops weak parts without fuss. During production, a careful note-taker who keeps developers and artists in step is worth more. After launch, the useful skill is reading user feedback and smoothing rough spots. Titles vary a lot from team to team, so ask what the person actually owned.
Access and routine
Open the design files, the project board and the newest test builds to your designer, and keep access limited to what the work needs. Your files and accounts should stay under your company name. During the first month, meet weekly and try the build together on a real device. Later, a brief weekly note and a monthly look at the design notes are enough. Use one fixed update format so the notes are easy to compare.
The designer, the developer and the 3D artist
A developer who joins early makes AR design easier. Have them try a rough version on a real phone before the design is final, so slow or unstable ideas show up while changes are cheap. Ask the 3D artist what the models need from the design, such as a fixed height or a limit on detail. A short weekly session in an ordinary room, with everyone trying the build, keeps the team looking at the same thing.
Common mistakes
- Designing only in a bright studio with an empty floor.
- Asking people to do too much before they see anything on the screen.
- Using heavy models that make the phone hot and the picture jumpy.
- Hiding safety notes, so people forget to look around them.
- Handing a contractor the ownership of design files or project accounts.
Also need someone to write the code? Look at our pages for a VR developer and a Unity developer.















