UK

United Kingdom · Technical roles · Mid-Level (2-5 years)

XR Developer

Here is the whole job, in plain words. What it is, a real day, what you decide, how you're judged, how people get here and where they go next. Then the part no course gives you: twelve AI tutors who learn your work.

  • Experience bandMid-Level (2-5 years)
  • Direct reportsNo direct reports
  • Reports toSenior XR Developer
  • UK framework levelUsually a coordinator, or early in a professional job

Also advertised as AR/VR Engineer · Unity Developer (XR) · Unreal Engine Developer (XR) · Spatial Computing Developer

Built on an analysis of 43,079 real UK job descriptions · grounded in qualifications employers recognise

Start with a free Future Fluency check, tuned to XR Developer

Ten quick questions, one per Future Fluency, asked against this role rather than a generic one. About five minutes, and no card.

Start the check, free

1What this role really is

This role is all about building out the actual immersive experiences. You'll be knee-deep in code, bringing designs to life in virtual and augmented reality. Think of it as being a digital architect, but instead of bricks and mortar, you're using C# or C++ to construct interactive 3D worlds that users can step into. It's hands-on, problem-solving work, where you're constantly figuring out how to make things run smoothly and feel real.

2What you'd actually use

The tools this job runs on, and how well you'd need to know each one.

Unity EngineIntermediate

Building scenes, implementing pre-existing components, writing C# scripts for gameplay logic, and configuring XR settings for various platforms. You'll be spending a lot of time in the editor.

Unreal Engine (C++ & Blueprints)Intermediate

Developing interactive experiences using a mix of C++ and Blueprints, setting up physics, animation, and rendering pipelines. You'll work with the engine's core systems to create immersive environments.

C# (for Unity) / C++ (for Unreal)Intermediate

Writing clean, efficient code to implement game mechanics, UI logic, networking, and custom XR interactions. This is your primary language for building features.

Meta Quest SDK / OpenXR / ARKit / ARCoreIntermediate

Implementing platform-specific features like hand tracking, passthrough AR, spatial anchors, and controller input using the relevant SDK APIs. You'll need to know the quirks of each.

Git (GitHub/GitLab)Intermediate

Managing your code with branching, merging, pull requests, and resolving conflicts. You'll need to be comfortable with Git LFS for handling large binary assets like 3D models and textures.

Jira / AsanaAdvanced

Tracking tasks, updating progress, participating in sprint planning and retrospectives, and ensuring your work is aligned with project timelines. Keeping your tickets up-to-date is crucial.

Blender / Autodesk Maya (Import & Configuration)Basic

Importing and configuring 3D models, textures, and animations provided by artists. You'll need to understand basic material setup and asset optimisation principles.

3What you get to decide, and how that grows

Power in a job isn't your title. It's what you're allowed to decide. Here's how it grows as you move up.

The choiceComing inWhere you are nowThe step above
Technical Approach for a FeatureFollows prescribed approach; escalates if unsure.Chooses best approach for assigned feature; consults senior on novel techniques.Defines technical approach for entire workstream; approves junior's approaches.
Code Optimisation StrategyApplies basic optimisations under guidance.Independently identifies and implements optimisations for features; consults on system-wide changes.Defines optimisation strategies and standards for the team; mentors others on profiling.
Bug PrioritisationFixes assigned bugs; escalates priority questions.Prioritises P2/P3 bugs for owned features; flags P1s to senior immediately.Helps define bug prioritisation for workstream; makes calls on P1 bug allocation.
Tool/Library Selection (within project)Uses existing approved tools.Researches and proposes new libraries for specific feature needs (e.g., a new physics library); requires senior approval.Approves new tools/libraries for workstream; evaluates broader impact.

4How you'll be judged

The scoreboard, honestly: the hard targets, how often each one is actually looked at, and the quiet human signals that never make it onto a dashboard.

Task Completion Rate
Successfully completing assigned Jira tickets within the sprint timeframe.
Target · 90%+ of P1/P2 tickets completed per sprint

If you're assigned 10 high-priority tasks in a sprint, you'd be expected to finish at least 9 of them, including all necessary code reviews and testing.

Bug Resolution Time
The average time it takes to fix and verify bugs of a certain priority level.
Target · P2 bugs fixed within 72 hours; P3 bugs within 5 working days

A reported UI glitch (P2) on Monday should be fixed and ready for QA by Thursday morning at the latest.

Performance Compliance
Ensuring your implemented features consistently meet our target frame rate on the specified hardware.
Target · >90 frames per second (FPS) on target hardware (e.g., Meta Quest 3)

After integrating a new interaction system, profiling shows the scene still runs at a steady 90 FPS, without any noticeable drops or hitches during user testing.

Code Review Feedback Incorporation
How quickly and effectively you address feedback from code reviews.
Target · All critical/major review comments addressed within 24 hours (P1) or 48 hours (P2)

If a Senior Developer flags a potential performance issue in your pull request, you'd be expected to investigate and push a fix or a clear explanation within a day.

Feature Robustness
How well your implemented features handle edge cases and unexpected user input without breaking.
  • Few post-release bug reports related to your features. QA reports fewer critical bugs during testing. Your code is clean, well-structured, and includes appropriate error handling for common scenarios.
Collaboration with Design & Art
Working effectively with XR Designers and 3D Artists to translate their vision into technical reality.
  • Designers and artists frequently comment on your proactive communication and willingness to find technical solutions for creative challenges. You're seen as a partner, not just a code implementer. You ask clarifying questions early on.
Proactive Problem Identification
Spotting potential technical issues or performance bottlenecks before they become major problems.
  • You bring up potential issues in stand-ups or team meetings before they're discovered by QA. You suggest optimisations or alternative approaches during feature planning. You're not just fixing what's broken, you're trying to prevent it.
Contribution to Team Knowledge
Sharing your learnings and helping other team members.
  • You contribute to internal documentation, share useful articles or techniques in team chats, and offer informal help to newer team members. You're seen as someone who helps lift the whole team up.

5Would you like it

The honest version. What people enjoy, and what grinds them down.

What people enjoy
Building Tangible Experiences

You get a real kick out of seeing your code transform into a virtual world or an AR overlay that people can actually interact with. The immediate feedback of putting on a headset and seeing your work come alive is a huge driver.

Spending an afternoon refining a hand-tracking interaction, then putting on the headset and experiencing it feel perfectly natural and responsive, is incredibly satisfying.

Solving Hard Technical Puzzles

You thrive on the challenge of figuring out why something isn't working, especially when it involves complex 3D maths or obscure hardware quirks. Debugging a tricky performance bottleneck is your idea of a good time.

Successfully optimising a scene to hit 90 FPS after days of profiling and tweaking shaders, knowing you've squeezed every bit of performance out of the hardware.

Being on the Bleeding Edge

The idea of working with new, unproven technologies and shaping the future of spatial computing excites you. You're happy to learn new SDKs and experiment with new hardware, even if it means dealing with instability.

Being among the first to experiment with a new AR cloud API or a novel haptic feedback device, and figuring out how to integrate it into a project.

What frustrates people
  • The 'Tyranny of the Performance Budget': Spending half your time optimising code and art assets to run on what's essentially a mobile phone strapped to someone's face (like a Meta Quest).
  • SDK Whiplash: Platform holders constantly releasing new, often beta-quality, SDKs and deprecating old ones with little notice, forcing you to refactor major parts of your application just to keep it working.
  • Hardware Fragmentation Hell: A feature that works perfectly on a Quest 2 causes crashes on a Pico 4, looks wrong on a Vive Pro, and has tracking glitches on a HoloLens 2. You'll become a part-time hardware QA tester.
  • Explaining Physics to Product Managers: The recurring, soul-crushing conversation where you have to explain why you can't have 100 photorealistic, physically-simulated characters in a scene running on a standalone headset without it turning into a slideshow.
  • Physical and Mental Fatigue: Literally getting headaches, neck strain, and eye fatigue from wearing headsets for hours on end to build and test the very experiences you're creating.
What this role does not give you
  • Absolute stability in tools and platforms – things change rapidly here.
  • A strictly '9-to-5' coding environment without occasional urgent fixes or late nights to hit a demo deadline.
  • The luxury of always working on greenfield projects; you'll spend time maintaining and optimising existing code too.
  • A role where you can avoid wearing a headset for extended periods during development and testing.

6Who you work with

This role directly impacts the quality and stability of our XR products. Your work ensures that features are delivered on time and perform as expected, which in turn affects user satisfaction, retention, and ultimately, our reputation in the immersive tech space. Get it right, and we build a loyal user base; get it wrong, and we're just another buggy app in a crowded market.

Inside the business
  • Senior XR Developers
  • XR Designers
  • 3D Artists
  • QA Engineers
  • Product Managers (for feature requirements)
Outside the business
  • Hardware platform providers (e.g., Meta, Valve, Pico) for SDK updates
  • External asset creators (occasionally)

7What you need before you start

Not a wish list. The things you would be expected to already have.

  • At least 2 years of professional experience in game development, real-time 3D, or XR development.
  • Proven ability to independently implement features in Unity or Unreal Engine using C# or C++.
  • A strong portfolio or demonstrable projects showcasing your XR development skills (e.g., GitHub repo, personal projects, published apps).
  • Solid understanding of 3D mathematics (vectors, matrices, quaternions).
  • Experience with version control systems, particularly Git, and handling large binary assets.
  • A genuine passion for immersive technologies and a drive to learn and adapt in a rapidly evolving field.

8What to practise next

Where the job is going, and what to do about it starting this week.

Advanced XR Graphics & Rendering Pipelines

As hardware gets more powerful, and users demand higher fidelity, understanding how to squeeze every bit of visual performance out of the GPU will become even more critical. This means going beyond basic materials and into custom rendering techniques.

Custom rendering pipelines (e.g., Unity's URP/HDRP · Advanced shader development (HLSL/GLSL, compute sh · Global illumination and real-time ray tracing in X · Foveated rendering and eye-tracked optimisations · Post-processing effects for immersive visuals

  • This week: Dive into the documentation for your engine's rendering pipeline (URP/HDRP or Unreal's renderer).
  • This month: Try writing a simple custom shader to achieve a specific visual effect.
  • Month 2: Experiment with foveated rendering settings on a target device if available.
  • Month 3: Benchmark different rendering techniques for performance impact on XR hardware.

Quick win: Spend an hour or two exploring the different post-processing effects available in your engine and see how they impact visual quality and performance in an XR scene.

Cross-Platform XR Development & Abstraction Layers

The XR market is still fragmented, with many different headsets and platforms. Being able to develop once and deploy everywhere, or at least with minimal changes, will save immense development time and unlock broader audiences.

OpenXR standard and its role in cross-platform dev · Developing custom abstraction layers for input, re · Platform-specific optimisations within a unified c · Build pipeline automation for multiple XR targets · Managing platform-specific asset variations

  • This week: Read up on OpenXR and its architecture.
  • This month: Try building a simple XR app that targets two different platforms (e.g., Quest and PCVR) using OpenXR.
  • Month 2: Research existing cross-platform XR frameworks or libraries.
  • Month 3: Design a simple input abstraction layer that works for both hand tracking and controller input.

Quick win: Ensure all new input code you write uses an abstract input system (like Unity's Input System or OpenXR input) rather than direct SDK calls, making it easier to swap platforms later.

9Staying current once you are in

What people here do to keep up
  • Actively participate in XR developer communities (e.g., local meetups, online forums, Discord servers).
  • Contribute to open-source XR projects on GitHub.
  • Attend industry conferences and workshops (e.g., GDC, AWE, XRDC) to stay current with trends and network.
  • Dedicate time to personal XR projects or game jams to experiment with new technologies and hone your skills.
  • Follow key XR thought leaders and technical blogs for insights into emerging techniques and best practices.

10How the AI economy is changing work like this

Before we ask anything of you, here's what we can already say about AI and work of this kind:

The new skill this role is being asked for: Advanced Prompt Engineering for 3D/XR

Generative AI is rapidly moving beyond text and images into 3D assets, textures, and even basic scene generation. Developers who can effectively 'talk' to these models will be able to prototype faster and create more dynamic content than ever before. It's already happening, and it's only going to accelerate.

We'll only ever tell you what we can actually back up. No hype, no scare tactics.

Your PlanIllustration

Built for XR Developer

3 units that map to this job, from the qualifications that cover it.

  1. Understanding the Interactive Media IndustryPearson Education Ltd · covers 4 of 12 standardsLevel 3
  2. Teamwork Skills in Practice within the Creative Arts and Digital Technology SectorsOpen College Network Northern Ireland · covers 3 of 12 standardsLevel 3
  3. Exploring Interactive Media Production and TechnologyUniversity of the Arts London · covers 2 of 12 standardsLevel 2
These are the real units behind this job, in the order they rank for it. Nothing here is marked done, because this plan has not been started by anyone yet. Yours would fill in as you go.

The rising capability

Zavmo analysis

What's rising in its place

This is where the work is heading, and the higher pay with it. Get fluent here and the shift stops being a threat and starts being your edge.

Advanced Prompt Engineering for 3D/XR

Generative AI is rapidly moving beyond text and images into 3D assets, textures, and even basic scene generation. Developers who can effectively 'talk' to these models will be able to prototype faster and create more dynamic content than ever before. It's already happening, and it's only going to accelerate.

  • Text-to-3D model generation (e.g., using Luma AI,
  • AI-driven texture and material creation (e.g., usi
  • Procedural scene generation with AI guidance
  • Ethical considerations and bias in generative 3D c
  • Integrating generative AI APIs into game engines

Spatial AI & Large Language Models (LLMs) in XR

Adding 'intelligence' to virtual characters and environments is the next frontier. LLMs are enabling more natural language interactions, dynamic storytelling, and adaptive NPCs. Understanding how to integrate and optimise these models for real-time XR will be crucial for creating truly believable and responsive virtual worlds.

  • Integrating LLM APIs (e.g., OpenAI, Claude) into g
  • Local vs. cloud-based LLM inference for performanc
  • Fine-tuning smaller models for specific XR use cas
  • AI-driven pathfinding and behaviour trees for inte
  • Ethical considerations for AI-driven characters (e

What you’ll use

Skills this role draws on

Technical

  • 3D Mathematics & Linear Algebra
  • XR Interaction Design & HCI
  • Performance Optimisation & Profiling
  • Spatial Computing & SLAM
  • Shader Development (Basic)

The pathway

How you actually get there, here

How you become one varies far more by country than what one does. This is the UK route. Most people take one of these ways in; the right one depends on where you're starting from.

  1. 1

    Junior XR Developer / Associate Game Developer

    2-3 years

    Skills to master

    • Core engine proficiency (Unity/Unreal), C#/C++ fundamentals, basic 3D maths, Git workflows, implementing well-defined features under supervision.

    You're ready to move on when

    • Consistently completes assigned tasks on time with minimal bugs.
    • Can independently debug common issues and find solutions in documentation.
    • Actively contributes to team discussions and learns from feedback.
    • Demonstrates a solid understanding of the project's codebase and architecture.
  2. 2

    Software Developer (with 3D/Graphics focus)

    3-4 years

    Skills to master

    • Strong C++/C# skills, experience with real-time graphics APIs (OpenGL/DirectX/Vulkan), 3D rendering concepts, performance optimisation, and potentially physics engines.

    You're ready to move on when

    • Has built or worked on applications with significant 3D rendering components.
    • Understands graphics pipelines and can optimise rendering performance.
    • Quickly grasps XR-specific concepts like motion-to-photon latency and 6DoF.
    • Eager to transition their 3D expertise into immersive environments.
  3. 3

    Graduate with Specialisation in XR

    2-3 years (post-graduation)

    Skills to master

    • A strong academic background in computer graphics, human-computer interaction, or game development, combined with practical experience from university projects or internships in XR.

    You're ready to move on when

    • Excellent academic record in relevant modules.
    • A compelling portfolio of university projects or personal XR demos.
    • Demonstrates strong theoretical understanding of XR principles and technologies.
    • Shows high potential for rapid learning and independent problem-solving.

11Where this role leads

The long view:This isn't just a job; it's a chance to build a career in a field that's still in its early days. The opportunities for growth are immense, and we're committed to helping you forge a path that aligns with your ambitions, whether that's becoming a technical guru or leading a team of innovators.

Pay & demand

Pay and demand for this role will appear here, each figure traced to a named authoritative source (e.g. the ONS Annual Survey of Hours and Earnings, under the Open Government Licence). We don’t show numbers we can’t attribute.

The ten Future Fluencies

Zavmo analysis

The credential is what you can do today. These are what keep you valuable.

A qualification proves you can do the job as it's defined today. These ten are what decide whether you're still the obvious person for it in five years. They're the capabilities employers are now writing into senior roles faster than people are learning them. Zavmo weaves them through whatever you study, so you come out with both: the credential and the fluency.

The highlighted ones are the Fluencies your role leans on hardest, from how XR Developer is actually changing. In about two minutes, the free confidence check asks where you stand on each of the ten. That's the whole check, and it's what makes the plan yours rather than generic.

Where it leads

Roles this leads to

The record names a next step, but the catalogue has no page for it yet:

  • Senior XR Developer

12The team that's yours

No two people are taught the same way. This is one-to-one, not one-to-many.

Zavmo is a hyper-personalised AI learning platform. Twelve virtual tutors, each with a different way of teaching, and one orchestration agent that picks the right one for the moment. So every single lesson is shaped around you, your role, and the way you learn. Not a course everyone sits through. A conversation built for you, and no one else.

…and nine more, matched to you after your first chat. Meet all twelve

Start free and meet yours

13What it feels like

A conversation, not a course

Because your tutor knows your role, your projects and your last session, learning sounds like this. And it's different for every single person:

Understanding the Interactive Media IndustryLevel 3

Applied to your work in XR Developer

This unit aims to provide learners with an understanding of the interactive media industry's structure, market trends, obligations, and employment opportunities, enabling them to prepare personal career development material.

How the thinking builds
  1. Remember
  2. Understand
  3. Apply
  4. Analyse
  5. Evaluate
  6. Create
An illustration of a Zavmo lesson, built from this role’s own route. The unit, its objective and every criterion above are the awarding body’s own words, not an example.

One to one, not one to many

No two people run this the same way

A course is written once and handed to everyone. This is assembled around you, and keeps changing as it learns you. Five things it reads, and what each one changes.

  1. Your actual work Every lesson is taught against a live piece of your own work, not a worked example from a textbook.
  2. What you already know The first conversation finds your starting point, so you skip what you can already do and spend the time on what you cannot.
  3. The conditions you learn under Not a learning-styles quiz. The evidence does not support those. The dimensions the research does back, read once and used to shape the plan.
  4. How far you got last time It picks up mid-thought. The tutor knows what you said, what you struggled with, and what it asked you to try.
  5. Which tutor suits the moment Twelve of them, each for a different kind of thinking. The one who walks you through a first idea is not the one who stress-tests it.

See how you learn, free. Eight questions, no sign-up. A directional taster; the diagnostic inside Zavmo goes deeper and keeps adapting.

DemonstrateIllustration

Evidenced on your work in XR Developer

You do not finish by watching something. You finish by showing it on the work you already do, against the measures this job is judged on.

  • Task Completion RateSuccessfully completing assigned Jira tickets within the sprint timeframe.If you're assigned 10 high-priority tasks in a sprint, you'd be expected to finish at least 9 of them, including all necessary code reviews and testing.90%+ of P1/P2 tickets completed per sprint
  • Bug Resolution TimeThe average time it takes to fix and verify bugs of a certain priority level.A reported UI glitch (P2) on Monday should be fixed and ready for QA by Thursday morning at the latest.P2 bugs fixed within 72 hours; P3 bugs within 5 working days
  • Performance ComplianceEnsuring your implemented features consistently meet our target frame rate on the specified hardware.After integrating a new interaction system, profiling shows the scene still runs at a steady 90 FPS, without any noticeable drops or hitches during user testing.>90 frames per second (FPS) on target hardware (e.g., Meta Quest 3)
  • Code Review Feedback IncorporationHow quickly and effectively you address feedback from code reviews.If a Senior Developer flags a potential performance issue in your pull request, you'd be expected to investigate and push a fix or a clear explanation within a day.All critical/major review comments addressed within 24 hours (P1) or 48 hours (P2)
These are this job's own measures, with its own targets. Nothing is marked evidenced, because nobody has started this yet. Yours would fill in from the work you bring.

Your passport

This isn't a certificate you file away. It's a passport to the life you're designing.

Every credit you earn and every fluency you build adds up: evidence where it counts, carried with you. Zavmo keeps the map: where you are, where you're heading, and the next step, at your pace, around your life. From XR Developer to Senior XR Developer, and whatever you decide comes after.

Level 3 · in progressAI Fluency→ Senior XR Developer→ your design
Where this takes you

This isn't just a job; it's a chance to build a career in a field that's still in its early days. The opportunities for growth are immense, and we're committed to helping you forge a path that aligns with your ambitions, whether that's becoming a technical guru or leading a team of innovators.

See Your Progress GrowIllustration
XR Developer
  • 3D Mathematics & Linear Algebra
  • XR Interaction Design & HCI
  • Performance Optimisation & Profiling
  • Spatial Computing & SLAM
  • Shader Development (Basic)
This is your Mind Palace on learn.zavmo.ai. Every skill above comes from this role's own record, not an example borrowed from another job. A node lights up when you evidence it, and what you build stays yours between jobs. That is the part a course cannot do.

14The detail, folded away

Everything else the record holds

The career branches in full, how AI is already showing up in the day-to-day, and the questions people ask about this job. Here when you want them, out of the way while you decide.

Where it leads next, rung by rung

Where it leads

The career path, and where it branches

XR Developer is a start, not a ceiling. Each step below asks for new skills and hands back more autonomy.

  1. Senior XR Developer

    3-5 years in current role

    Level 3 (003)

    • Architecting complex, multi-part features from scratch.
    • Deep expertise in a specific XR domain (e.g., rendering, interaction, networking).
    • Designing and implementing robust, scalable XR systems.
    • Making technical recommendations to leadership and cross-functional teams.
Working with AI on the job

Working with AI

Where AI is starting to help

Let's be real, XR development is complex, time-consuming, and often involves a lot of repetitive tasks. But what if you could offload some of that grunt work to AI? Imagine spending less time on boilerplate code or sifting through dense documentation, and more time actually building groundbreaking experiences.

Our team is actively exploring and integrating AI tools to make your job as an XR Developer more efficient and frankly, more fun. We're not talking about replacing you; we're talking about giving you superpowers. Here's how AI can genuinely boost your productivity day-to-day:

Automated Code & Asset Scaffolding

Use AI tools like GitHub Copilot to whip up boilerplate C# or C++ code for common XR interactions (think grabbing objects, UI pointers, or basic locomotion). Generative AI can even create placeholder 3D models, textures, and sound effects from simple text prompts, letting you prototype ideas in minutes instead of hours.

Intelligent Performance Profiling

Leverage AI-powered profilers that don't just show you a spike in frame time, but actually analyse the data and suggest probable causes. Instead of manually digging through hundreds of draw calls, AI might tell you, 'High draw calls from transparent shaders in the particle system are likely the culprit.' This cuts down complex debugging time significantly.

Accelerated R&D and SDK Analysis

Imagine using an AI assistant to summarise dense technical documentation for a new Meta Quest SDK, or to quickly compare the feature sets of competing ARKit and ARCore updates. This means less time reading and more time implementing, helping you stay ahead of the curve and make informed technical decisions faster.

Generative Testing & World Building

AI can procedurally generate complex test environments and scenarios. This helps us find those tricky edge-case bugs in physics or interaction systems that manual QA might miss. It can also populate large virtual worlds with varied, non-repeating scenery, saving our artists and designers significant time on environmental setup.

Common questions

Common questions

How do you become an XR Developer?

Common routes in include Junior XR Developer / Associate Game Developer (2-3 years), Software Developer (with 3D/Graphics focus) (3-4 years) and Graduate with Specialisation in XR (2-3 years (post-graduation)). Times vary with prior experience.

Where can an XR Developer progress to?

This role can lead on to Senior XR Developer (3-5 years in current role), depending on the skills you build.

What level is an XR Developer in the UK?

This role aligns to RQF Level 3 on the UK framework, a guide to the depth of qualification it maps to, not a hard entry bar.

What new skills matter most for an XR Developer?

Increasingly, Advanced Prompt Engineering for 3D/XR and Spatial AI & Large Language Models (LLMs) in XR. These are the areas where the higher-paid, future-proof work is heading.

The honest bit

You’ve started things before

Most of them were built for a room full of people who aren’t you. A cohort moves on whether or not your week allowed it, and by the third week the thing you’re behind on becomes the reason you stop opening it.

There’s no cohort here, and no timetable to fall behind. Before anything starts, Zavmo asks when you’re sharpest and how long you can realistically sit down for, then builds the sessions around those answers. A bad fortnight changes your pace. It doesn’t put you behind.

And you only pay once you start learning. Searching and planning are free, and you can cancel any time — so the cost of finding out is an afternoon, not a year.

What it costs

Less than one coaching session. Every month.

A single career-coaching hour costs more than a month of this, and it ends when the hour does. Zavmo doesn't. It's £70 a month, about £2.30 a day, for a companion that knows an XR Developer, works on the job you actually do, and keeps going at your pace rather than a timetable's.

  • Searching and planning stay free. You only pay when you start learning.
  • Your credits are yours. Regulated, and they don't vanish when a subscription ends.
  • Cancel any time and billing stops. No notice period, no minimum term.

Your path, personalised

You have the map. Walking it is the part we do together.

This route runs to 12 national skill standards. That is a real journey.

Zavmo shapes a learning experience as unique as you are. It fits how you learn, your pace and the work you already do. Every step stays benchmarked to recognised national standards. That’s the plan for becoming an XR Developer: personal to you, and it still counts. The first steps are free.

Independent research finds well-designed intelligent tutoring performs nearly as well as one-to-one human tutoring: VanLehn (2011), Educational Psychologist.

A private tutor in the UK averages £35–40 an hour . Zavmo is £70/month.

A real plan on learn.zavmo.ai: Ofqual-regulated units, credits, and a three-month run at your own pace.
Start free No commitment. See your first steps free.

15Where to go from here

Other roles at Level 3

Same depth of qualification, different job. Useful if the work appeals but this particular role does not.

Other roles in Technical roles

Stay in the field you know and move sideways rather than up.

If you leave this industry

The skills you'll gain here are highly transferable across the entire XR industry, from entertainment and gaming to enterprise solutions, training, and healthcare. Your expertise in real-time 3D, performance optimisation, and spatial computing is in high demand, opening doors to various exciting sectors as they adopt immersive technologies.

Not sure this is the right direction?

Work out what you actually want from work first, then come back and see which roles fit it. Takes about ten minutes.

This role profile is © 2026Growth Engineering Technologies Ltd. Built from UK occupational standards and regulated qualification data, and written for Zavmo.

You're not behind. You're right on time. The shift is only just beginning. Your role won't look the same in two years. Be the one who leads the change, not the one it happens to. Build my plan, free Here's the first ten minutes: a 2-minute confidence check → your personalised roadmap → meet the tutors matched to you. No card, cancel any time. No card. Build your plan, see your roadmap and meet the twelve tutors matched to you. All free. When you're ready to start learning, it's £70 a month, billed monthly. Cancel any time and billing stops.