Resumen del proceso. quick roadmap
For urgent prep, the designer should pick one 2D project and define an MVI. The designer must build a 2–3 minute transparent AR demo video and a one-page interaction map. Practice a 30s elevator, a 2–3 minute demo, and three mock interviews. Run a small test and cite 2–4 KPIs in the case page.
Quick pause: focus on the core interaction first.
-
Pick a 2D project and define an MVI (minimum viable interaction). One sentence to frame scope.
-
Create a spatial interaction map that shows nodes, triggers, and failure states. Use visuals.
-
Prototype to the right fidelity: Figma plus transparent AR video for speed, Unity or WebXR for metrics.
-
Run a small test (5 remote users or 10 lab sessions) and capture KPIs: task completion, spatial drop-off, comfort. Record numbers visibly.
-
Build a Notion case page with hero summary, artifacts, metrics, trade-offs, and a 2–3 minute demo. Make it scannable.
-
Practice six trade-off stories and rehearse three mock interviews: recruiter screen, design exercise, and deep dive.
Step 1: choose the right project and define the MVI
Designers should begin with a single 2D project that has a clear physical analogue. Good choices include checkout flows, object inspection, or navigation tasks. Pick work that maps to a real spatial action. That keeps scope tight.
The MVI should isolate one spatial decision. Example: move a product preview into world space. Keep core task time under 90 seconds.
Limit scope to one primary interaction. This makes prototypes reproducible and demos tight.
Set measurable success criteria up front. Pick 2–4 KPIs that match study goals. Core metrics often include task completion, time-on-task, and spatial drop-off. Add comfort measures when relevant, like a short motion-sickness scale or SUS.
Label primary versus secondary KPIs. This keeps small-sample tests focused and results interpretable.
Example MVI: transform a mobile try-on into a world-anchored AR preview. Validate scale and placement within 72 hours.
Timeline rule: if an interview is within 72 hours, do a Figma plus transparent AR video walkthrough. If you have 1–14 days, make a WebXR or Spark AR prototype.
Step 2: map the 3D interaction space and document decisions
Create an interaction map that shows spatial nodes, user entry points, and fallback states. Include environmental assumptions.
Maps must show triggers and edge cases. For every trigger, document expected sensor input and the fallback behavior.
Add a short gesture lexicon. Define what a swipe, pinch, or gaze does in world-space.
Add a small table with device assumptions: phone AR, glasses, or headset, and the expected DoF (3DoF vs 6DoF). Make this explicit for reviewers.
Document the main trade-offs. For example, choose world-locked anchors for stability at the cost of initial calibration time.
Key artifact: a single-page interaction map with nodes, triggers, and 3 failure states. This convinces hiring managers more than a long video.
Step 3: prototype fast, with clear fidelity choices
Choose the prototype method to match the goal. Do not build a Unity prototype if the goal is primarily to signal to recruiters.
If the aim is to test concept or user flow, use Figma plus a transparent AR video. That workflow takes 1–3 days.
If the aim is to measure behavior, pick the right platform for the needed fidelity. WebXR can deliver instrumented, shareable prototypes faster.
WebXR often takes about 1–3 weeks for a cross-device build with basic telemetry. Unity fits headset-grade tests but requires more ramp-up and engineering effort.
Unity typically requires 2–8+ weeks depending on scope. Plan for dev cost and test logistics.
For moderate signal, use Spark AR or Lens Studio. Those are good for phone-based AR lenses in 3–10 days.
Rule of thumb: For a recruiter screen, a crisp 2–3 minute demo beats a buggy interactive build.
Prototype recipes by timeline
-
48–72 hour MVI: Figma flows → interaction map → transparent AR walkthrough video → Notion page.
-
1–2 week build: Spark AR or WebXR prototype with simple interactions and a 5-user remote test.
-
2–4 week build: Unity headset prototype with analytics, 10-user lab test, and motion-sickness survey.
Decide by goal, time, device, and need for metrics. Goal: validate idea quickly or prove metrics? Time: days or weeks? Device: phone AR or headset VR? Metrics: qualitative feedback or instrumented telemetry?
Choose tools to match those answers. Each option trades speed for fidelity and metrics.
Below is a practical comparison table with typical times and trade-offs.
| Tool |
Best for |
Fidelity |
Typical time-to-deliver |
Pros |
Cons |
Metrics possible |
| Figma + Transparent AR video |
Quick concept demo |
Low |
1–3 days |
Fast, no dev, clear visuals |
Not interactive, limited telemetry |
Qualitative feedback, video timing |
| Spark AR / Lens Studio |
Phone AR interactions |
Mid |
3–10 days |
Platform reach, quick interactivity |
Platform limits, not headset-ready |
Basic events, engagement metrics |
| WebXR (A-Frame/Three.js) |
Cross-device prototypes |
Mid |
5–14 days |
Accessible, shareable links |
Browser/device variance |
Event logs, heatmaps |
| Unity + XR Interaction Toolkit |
Instrumented headset tests |
High |
2–8+ weeks |
Full interactivity, analytics |
Longer ramp, dev cost |
Task completion, drop-off, comfort |
1. Pick 2D project
2. Define MVI & KPIs
3. Interaction map
4. Prototype
5. Test & metrics
Time vs Signal: 48–72 hrs = low fidelity, quick signal. 1–4 weeks = measurable signal.
Step 4: build the portfolio page and prioritize artifacts
The case page must be scannable. Start with a one-line hero problem and a one-line impact. Keep both sentences short.
Follow with role, constraints, research highlights, and the interaction map. Add the prototype link and a short demo video.
Include a clear metrics section with numbers. Example: "5 participants, 80% task completion, 25% spatial drop-off." Use real numbers.
Show trade-offs with context. For example: "chose on-device SLAM to preserve privacy at higher CPU cost." Make that sentence bold.
Provide a short section on accessibility and privacy. Mention ADA and CCPA if data collection occurred.
Step 5: run quick tests and capture meaningful KPIs
For a credible case study, run a small test. Remote tests may use 5 participants. Lab tests often use 10 participants.
Collect at least these metrics: task completion, time-on-task, spatial drop-off points, and motion-sickness incidence. Log events whenever possible.
Use short surveys such as SUS and a simple motion-sickness scale. Note that many UX labs adapted VR comfort metrics in the 2010s.
Log events in Unity or WebXR if possible. If not, use timestamped video overlays and manual coding.
Step 6: demo scripts and interview prep focused on product trade-offs
Interviewers want product thinking. They want concise demos and explicit trade-offs.
Provide three scripts: 30s elevator, 2–3 minute demo, and 10–15 minute deep dive. Each script should hit metrics and trade-offs.
2–3 minute demo template:
- 00:00–00:15. One-sentence problem and role.
- 00:15–01:30. Show the interaction map and a live demo of the primary interaction.
- 01:30–02:00. Present KPIs and one trade-off sentence.
Emphasize the decision sentence. Use: “We chose X because it maximized Y while minimizing Z.”
Practice six trade-off stories. Map each story to STAR with explicit constraints and metric outcomes.
Mock interview playbook
Round 1: Recruiter screen. Practice a 30s elevator and a short demo link. Keep the demo under 2 minutes.
Round 2: Design exercise. Practice spatial whiteboard prompts and sketch interaction maps in 20 minutes.
Round 3: Deep dive. Prepare to discuss instrumentation, SLAM trade-offs, and accessibility choices with an engineer and PM.
Role-play prompts: engineer asks about latency. The PM asks about shipping versus measurement priorities.
Common errors that ruin a spatial portfolio
Uploading 2D work without spatial translation. That confuses reviewers. Design must show spatial decisions.
Focusing on tech stack instead of product decisions. Recruiters want impact, not just libraries used. Show metric outcomes.
Demos that cannot be reproduced. If the reviewer cannot run the demo, they skip assessment. Make reproducible links.
Missing interaction maps and edge-case handling. Spatial products fail at edges. Document those cases.
Over-polishing visuals without measuring outcomes. Appearance without data weakens credibility.
Warning: This method does not apply to roles that are purely CG art or shader engineering. For those, visual fidelity and artist reels matter more than interaction maps.
When this approach won’t work and alternatives
If the role is strictly visual effects, an interaction-focused portfolio will under-sell the candidate. Visual reels matter more for that hiring track.
If a position demands deep engine-level expertise in rendering, prioritize longer Unity or Unreal demos and technical write-ups. Show engine-level metrics and shaders.
If the company only hires for mobile UI and prohibits spatial features, keep mobile work front and center. Tailor the portfolio to the job.
Alternative: for art roles, build a reel and include one annotated interaction map to show spatial awareness.
Quick pause: pivot the portfolio to match the role.
Repair, iterate, and fast-track a rejected portfolio
Top causes of rejection: no spatial artifacts, no metrics, and nonreproducible demos. Fix those first.
Quick fixes in 48–72 hours: add an interaction map, record a 2–3 minute transparent AR demo, and append one metrics line. This often moves the needle quickly.
Medium fixes in 1–2 weeks: release a WebXR or Spark AR prototype, run a 5-person test, and add results. Use those numbers in the case page.
Long fixes in 3–6 weeks: instrument Unity builds, run lab tests, and rewrite three case pages to the canonical structure. This is heavier work.
Include a simple outreach script when requesting portfolio feedback from mentors and engineers. Ask for specific feedback items.
Mention organizations and figures during interviews. Cite Meta / Reality Labs, Apple ARKit (2017), and Unity Technologies.
Reference standard groups: SIGGRAPH (annual since 1974), Nielsen Norman Group for UX guidance, and Stanford Virtual Human Interaction Lab for presence research.
Bring up compliance when relevant: ADA, Section 508, CCPA, GDPR, and COPPA. These matter when collecting user data.
If discussing sensor trade-offs, mention latency and motion-to-photon as product constraints. Call out numbers when available.
- Hero problem + one-line impact
- Role & constraints
- MVI & KPIs
- Interaction map (image + alt text)
- Prototype links (video, WebXR, APK)
- Test plan & raw metrics
- Trade-offs & accessibility
- What I’d do next. Candidates report that a ready template cuts case-page time from ~6–10 hours to ~2–4 hours.
Provide a concrete interaction-spec example:
- Beyond a visual interaction map, include a one-page interaction spec per primary flow with event names, parameters, thresholds, and pass/fail criteria. Example: Event: PlaceProduct → params: anchorPosition(x,y,z), anchorOrientation(yaw,pitch,roll), poseConfidence ∈ [0,1]
- success: user confirms placement within 90s AND distanceToTarget ≤ 20 cm
- failure: timeout > 90s OR poseConfidence < 0.6 for more than 3s. Log events as timestamped JSON: { event: "PlaceProduct", t: 1610000000, poseConfidence: 0.82, distance: 12.3 }. Define derived metrics: Task completion rate = successfulPlacements / totalAttempts
- Spatial drop-off = percent of users who exit flow before first placement
- Placement accuracy = mean(distanceToTarget) ± SD
Including these concrete artifacts, like JSON schemas and thresholds, turns a persuasive demo into a reproducible study. Hiring teams can audit such artifacts.
Repair, iterate, and fast-track a rejected portfolio
(Note: the repeated section was removed in the rewrite to keep content focused and concise.)
Mock-interview checklist and role-play schedule
Create a reusable prep checklist and a timed mock plan with rubrics. Checklist items: share demo link (≤3 min) and interaction map, confirm device assumptions, prepare three trade-off stories mapped to STAR, and have instrumented metrics ready to cite.
Timed mock plan (48–72 hour prep): Day 1. Recruiter mock (15 min) plus feedback (10 min). Day 2. Design exercise simulation (30–40 min) with a 20-minute whiteboard and a 10–15 minute critique. Day 3. Deep-dive with engineer and PM (45–60 min) covering SLAM, latency, telemetry, and accessibility.
Rubric (1–5) criteria: clarity of problem, measurable success criteria, trade-off justification, technical feasibility, and prototype reproducibility. Use recorded role-plays and score each run. Aim for an average ≥4 across criteria before scheduling onsite interviews.
Quick pause: practice until the demo feels natural.
FAQ — practical answers to what people ask
How do I prepare for an AR/VR product designer interview?
Prepare three things first: portfolio artifacts, a reproducible demo, and trade-off stories. Then rehearse. Practice the 2–3 minute demo until it fits the timeline. Prepare six STAR stories that finish with a trade-off sentence. Run three mock interviews with different reviewers. Focus on measurable outcomes and how design choices affected those metrics.
What should be included in an AR/VR product design portfolio?
Include a hero summary, role, interaction map, prototype link or video, metrics, and trade-offs. Then accessibility and privacy notes. Show the interaction map early. Host a short demo video and an accessible prototype link. Make KPIs obvious.
How many projects should I present in my design portfolio?
Minimum: one robust MVI case study plus a recruiter-friendly summary. Optimal shortlisting: two detailed case studies. For senior roles, include three in-depth projects with test data. If interviews are soon, prioritize one high-quality case and one quick demo.
What questions are commonly asked in AR interviews?
Expect product trade-offs, SLAM basics, latency causes, locomotion patterns, accessibility, and metrics instrumentation. Expect cross-functional scenarios. Prepare concise answers that end with a trade-off sentence and a metric. Interviewers look for measurable thinking.
How does augmented reality differ from virtual reality in product design?
AR layers interfaces on the real world. VR creates a full virtual environment. Each imposes different UX constraints. AR needs world anchors, occlusion handling, and privacy planning. VR needs locomotion patterns, spatial audio, and comfort modes.
Where can candidates get fast feedback and credible standards?
Use community reviews from XR meetups, SIGGRAPH, and Nielsen Norman Group resources. Ask an engineer to sanity-check prototypes. Aim to get at least one mentor review and one engineering review before broad applications. Mentioning standards like ISO 9241 adds credibility.
Final checklist and next steps, convert plan into deliverables
72-hour deliverables: Notion case page with hero, interaction map, and a 2–3 minute demo video. 2-week deliverables: second case study with WebXR or Spark AR prototype and a 5-user test with KPIs. 4-week deliverables: Unity instrumented build, 10-user lab test, motion-sickness report, and polished case pages.
Suggested timeline matrix:
- Day 1–3 rapid MVI
- Day 4–10 prototype and test
- Day 11–14 polish and mock interviews
Action now: pick one 2D project, draw a one-page interaction map, and record a 2–3 minute demo.
