United Kingdom · Technical roles · Entry Level (0-2 years)

Associate Quantum Software Engineer

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 bandEntry Level (0-2 years)
Direct reportsNo direct reports
Reports toSenior Quantum Software Engineer
UK framework levelUsually someone starting out, or keeping a process running

Also advertised as Junior Quantum Developer · Quantum Research Assistant (Software) · Entry-Level Quantum Programmer

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 Associate Quantum Software Engineer

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 isn't your average software gig. You'll be diving head-first into the wild world of quantum computing, helping us build and test the very first generation of quantum applications. We're talking about a field that's still being invented, so expect a steep learning curve and plenty of 'aha!' moments. You'll be working on real quantum hardware, which is both incredibly exciting and, frankly, a bit temperamental. Your day-to-day will involve translating abstract quantum algorithms into actual code that runs on these machines, then figuring out why it probably didn't do what you expected. It's challenging, it's new, and it's definitely not for everyone, but if you love a puzzle, you'll feel right at home.

2What you'd actually use

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

Python (NumPy, SciPy, Matplotlib)Advanced

You'll use Python for pretty much everything: writing quantum circuits, controlling cloud platforms, analysing experimental data, and creating visualisations. You should be comfortable with data structures, functions, and basic object-oriented programming.

Qiskit or Cirq (one primary SDK)Intermediate

You'll be writing, debugging, and executing quantum circuits using one of these SDKs. You should be able to create quantum registers, apply standard gates, and perform measurements. You'll also need to understand how to use their built-in simulators and connect to real hardware.

IBM Quantum Experience or Amazon BraketBasic

You'll be submitting quantum jobs to these cloud platforms, monitoring their status, and retrieving results. This means understanding how to configure your job, manage credentials, and interpret the output from actual QPUs.

Git & GitHub/GitLabIntermediate

You'll use Git for all your version control. This means branching, committing your changes, creating pull requests, and participating in code reviews. You should be comfortable with basic Git commands and our team's workflow.

Jira & ConfluenceBasic

You'll use Jira to track your tasks and update your progress on projects. Confluence will be where you document your experimental setups, findings, and any new procedures you develop.

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 choice	Coming in	Where you are now	The step above
Quantum Circuit Design	Implements circuits from detailed specifications; escalates any ambiguities or deviations.	Designs specific circuit components within a larger algorithm; consults on overall architecture.	Designs novel quantum algorithms and full circuit architectures; makes key trade-offs on gate count and depth.
Hardware Backend Selection	Uses the pre-selected quantum hardware backend as instructed.	Proposes alternative backends based on performance characteristics; seeks approval from lead.	Selects optimal hardware backends for specific experiments, considering cost and performance; justifies choice to team.
Debugging & Troubleshooting	Identifies basic syntax errors or configuration issues; reports more complex problems with detailed context to supervisor.	Independently diagnoses and resolves most software bugs; collaborates with hardware engineers on hardware-related issues.	Leads complex debugging efforts across software and hardware; develops new diagnostic tools or techniques.
Project Task Prioritisation	Works on tasks as assigned by supervisor; flags any conflicts or blockers immediately.	Prioritises personal tasks within a sprint; helps break down larger project goals into manageable tasks.	Defines and prioritises tasks for a workstream; manages dependencies and allocates resources for junior team members.

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.

Circuit Execution Success Rate

The percentage of quantum circuits you submit to hardware or simulators that run to completion without crashing due to syntax errors or basic configuration issues.

Target · 95%+

Out of 20 circuits submitted last week, 19 ran successfully. One failed due to a missing library import, which you quickly fixed after review.

Code Review Feedback Cycles

The average number of rounds of feedback required on your pull requests before the code is approved for merging.

Target · Max 2 cycles per PR

Your first PR needed 4 rounds of changes. Your last three PRs only needed one round each, showing you're picking things up quickly.

Documentation Contribution

The number of new or updated internal wiki pages, code comments, or experimental logs you contribute.

Target · 2-3 significant contributions monthly

You've added detailed comments to a complex transpilation script and created a new Confluence page explaining how to set up a specific cloud backend.

Task Completion Rate

The percentage of assigned Jira tickets (e.g., 'implement X circuit', 'debug Y script') that you complete within the agreed timeframe.

Target · 85%+

In the last sprint, you completed 7 out of 8 assigned tickets. The one you missed was due to an unexpected hardware issue, which you promptly reported.

Learning Agility & Application

How quickly you grasp new quantum concepts, SDK features, or debugging techniques and then apply them in your work.

You ask insightful questions that show you've thought about the problem. You can explain new concepts in your own words. You're able to independently solve similar problems after being shown once. You actively seek out new information (e.g., reading SDK docs, arXiv papers).

Attention to Detail in Quantum Code

Your ability to write precise quantum circuits and classical control code, catching small errors before they cause larger issues.

Your code often passes initial checks without needing major corrections. You meticulously label qubits and gate operations. You spot subtle errors in other people's example code. You double-check configurations before running expensive hardware jobs.

Proactive Problem Reporting

How quickly and clearly you identify and report issues, whether it's a bug in your code, a problem with the quantum hardware, or an unexpected experimental result.

You don't just say 'it's broken'
you provide specific error messages, steps to reproduce, and what you've already tried. You report issues to the right person or channel promptly. You suggest potential next steps for debugging.

Collaboration & Communication

Your willingness to ask for help when stuck, share your findings, and communicate clearly with your team members.

You actively participate in daily stand-ups, sharing progress and blockers. You ask for help before getting completely stuck for hours. You explain your code and thought process clearly during code reviews. You're receptive to feedback.

5Would you like it

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

What people enjoy

Solving Uncharted Problems

You get a real kick out of tackling problems where there's no existing solution or clear 'right' answer. This shows up when you're happily debugging a quantum circuit that's giving unexpected results, or researching a new paper to find a hint for a tricky implementation.

Spending an afternoon trying to implement a novel error mitigation technique described in a recent arXiv paper, even if it means hitting a few dead ends.

Deep Technical Learning

You're genuinely excited by the prospect of mastering complex technical concepts, whether it's understanding the nuances of quantum error correction or optimising a transpilation routine. You're always looking for the 'why' behind the 'what'.

Voluntarily diving into the Qiskit source code to understand how a specific gate decomposition works, rather than just using it as a black box.

Building Foundational Technology

You're motivated by the idea of contributing to something truly groundbreaking, even if your individual contribution is a small piece of a much larger puzzle. You see the long-term vision and want to be part of building the future.

Feeling a sense of accomplishment when your carefully written quantum circuit successfully runs on a real quantum computer, even if it's just a simple demo.

What frustrates people

The Simulator-to-Hardware Gap: Perfect code in simulation often breaks on noisy hardware.
The Hardware Queue: Waiting hours for a short slot on a quantum computer.
'Is it a bug or is it physics?': Debugging when the problem source is ambiguous.
Non-Deterministic Debugging: Outputs are probabilistic, making bug-finding tricky.
The Hype Translator: Explaining to non-technical people why quantum isn't magic (yet).

What this role does not give you

Predictable, routine tasks with guaranteed outcomes.
Immediate, tangible business impact from every line of code you write.
Working with mature, fully stable, and well-documented technologies.
A quiet, solitary coding environment (you'll be collaborating a lot).

6Who you work with

You'll directly support our core quantum research and development efforts. Your work ensures that the theoretical algorithms designed by our scientists can actually be tested and validated on real quantum hardware. Essentially, you're helping us bridge the gap between whiteboard ideas and practical quantum applications. Without your careful execution and debugging, our more senior team members would be spending their time on basic setup, slowing down our overall progress significantly.

Inside the business

Senior Quantum Software Engineers (your mentors)
Quantum Research Scientists (who design the algorithms)
Hardware Engineers (who maintain the quantum computers)
Technical Leads (who oversee projects)

Outside the business

Quantum Cloud Platform Providers (e.g., IBM, Amazon, Azure)
Academic Collaborators (occasionally, for specific projects)

7What you need before you start

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

Strong foundational programming skills in Python (loops, functions, data structures, basic OOP).
A solid grasp of linear algebra (vectors, matrices, complex numbers) – it's the language of quantum mechanics.
Basic understanding of probability and statistics, especially for interpreting quantum measurement results.
Familiarity with Git for version control; you should know how to commit, pull, and push code.
A genuine, demonstrable interest in quantum computing (e.g., personal projects, online courses, academic exposure).
Ability to learn new technical concepts quickly and apply them in a practical setting.

8What to practise next

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

Advanced Quantum Circuit Optimisation

As quantum hardware improves but remains limited, squeezing maximum performance from every qubit and gate becomes even more critical. Manual optimisation won't scale; you'll need to use advanced transpilation techniques.

Dynamic Decoupling · Pulse-Level Control (Basic) · Hardware-Aware Compilation

This quarter: Read the documentation on advanced transpilation passes in Qiskit or Cirq. Try to apply them to a simple circuit.
Next quarter: Take an online course or tutorial on pulse-level programming concepts, even if it's just theoretical.
Month 6: Experiment with running the same circuit on different hardware backends and analyse how their specific architectures affect performance and noise.

Quick win: Start by identifying one specific circuit in your current work that could benefit from more aggressive optimisation and try to apply a new transpilation pass.

Quantum Error Correction (Practical)

The NISQ era won't last forever. As hardware scales, error correction will become essential for building truly fault-tolerant quantum computers. Understanding how to implement and test basic error correction codes will be a critical skill.

Surface Codes (Conceptual) · Stabiliser Codes · Logical vs. Physical Qubits

This quarter: Read an introductory paper or textbook chapter on quantum error correction (e.g., Nielsen & Chuang, Chapter 10).
Next quarter: Look for open-source implementations of simple error correction codes (e.g., the 3-qubit bit-flip code) and try to implement them yourself in a simulator.
Month 6: Discuss with senior team members how our current hardware might eventually support basic error correction and what the challenges are.

Quick win: Find a simple online tutorial for implementing a basic quantum error detection code (not full correction) and try to code it up.

9Staying current once you are in

What people here do to keep up

Regularly read papers on arXiv.org in quantum information science and quantum computing.
Actively contribute to open-source quantum computing projects (e.g., Qiskit, Cirq, PennyLane).
Attend virtual or in-person quantum computing conferences and workshops (e.g., Qiskit Camp, Q2B).
Participate in quantum hackathons or coding challenges to test and expand your skills.
Take advanced online courses in specific quantum algorithms or hardware architectures.
Join relevant online communities (e.g., Slack channels, Reddit forums) to discuss new developments and problems.

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: Prompt Engineering & LLM Integration (for Quantum)

Essential for future readiness in this role.

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

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.

Prompt Engineering & LLM Integration (for Quantum)

Essential for future readiness in this role.

Context Windows & Token Limits
Temperature Settings
RAG Architectures (Conceptual)
Output Validation & Hallucination Detection

What you’ll use

Skills this role draws on

Technical

Quantum Algorithm Implementation
Quantum Circuit Compilation & Transpilation (Basic)
Noise Modelling & Mitigation (Conceptual)
Hybrid Quantum-Classical Methods (Conceptual)

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
University Graduate (BSc/MSc)
0-1 year post-graduation
Skills to master
- Transitioning from academic projects to production-ready code, understanding version control best practices, effective debugging in a team environment.
You're ready to move on when
- Completed a final year project involving quantum simulation or programming.
- Contributed to a university quantum computing club or research group.
- Strong academic record in relevant quantitative subjects.
2
Software Developer (Career Changer)
1-2 years self-study/bootcamp + 0-1 year professional experience
Skills to master
- Grasping quantum mechanics fundamentals, learning quantum SDKs, adapting software engineering principles to the unique challenges of quantum systems.
You're ready to move on when
- Existing strong Python development skills and clean code habits.
- Completed significant personal projects in quantum computing (e.g., GitHub repo).
- Undertaken online courses or certifications in quantum computing fundamentals.
3
Research Assistant (Quantum Physics)
0-1 year post-RA role
Skills to master
- Moving from theoretical/experimental physics to software development best practices, scaling up code for larger problems, working within a structured software development lifecycle.
You're ready to move on when
- Experience with scientific computing (e.g., MATLAB, Julia, Python for data analysis).
- Deep understanding of quantum mechanics and experimental setups.
- Demonstrable desire to transition into a software-focused role.

11Where this role leads

The long view:This is more than just a job; it's a chance to be part of building something truly revolutionary. The quantum computing field is still in its infancy, and your career path here will be as unique and exciting as the technology itself. We're looking for individuals who are ready to learn, adapt, and help us shape the future of computing.

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 Associate Quantum Software Engineer 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.

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:

Performing Low Level Programming for Engineering SoftwareLevel 3

Applied to your work in Associate Quantum Software Engineer

This unit aims to equip learners with the ability to perform low level programming for engineering software applications, including developing, testing, and debugging code. Learners will demonstrate the ability to write efficient and optimised code and integrate it with higher-level components. Furthermore, they will understand the principles of low level programming languages and their applications in engineering.

How the thinking builds

Remember
Understand
Apply
Analyse
Evaluate
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.

Your actual work Every lesson is taught against a live piece of your own work, not a worked example from a textbook.
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.
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.
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.
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 Associate Quantum Software Engineer

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.

Circuit Execution Success RateThe percentage of quantum circuits you submit to hardware or simulators that run to completion without crashing due to syntax errors or basic configuration issues.Out of 20 circuits submitted last week, 19 ran successfully. One failed due to a missing library import, which you quickly fixed after review.95%+
Code Review Feedback CyclesThe average number of rounds of feedback required on your pull requests before the code is approved for merging.Your first PR needed 4 rounds of changes. Your last three PRs only needed one round each, showing you're picking things up quickly.Max 2 cycles per PR
Documentation ContributionThe number of new or updated internal wiki pages, code comments, or experimental logs you contribute.You've added detailed comments to a complex transpilation script and created a new Confluence page explaining how to set up a specific cloud backend.2-3 significant contributions monthly
Task Completion RateThe percentage of assigned Jira tickets (e.g., 'implement X circuit', 'debug Y script') that you complete within the agreed timeframe.In the last sprint, you completed 7 out of 8 assigned tickets. The one you missed was due to an unexpected hardware issue, which you promptly reported.85%+

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 Associate Quantum Software Engineer to Quantum Software Engineer (Level 2), and whatever you decide comes after.

Level 2 · in progressAI Fluency→ Quantum Software Engineer (Level 2)→ your design

Where this takes you

This is more than just a job; it's a chance to be part of building something truly revolutionary. The quantum computing field is still in its infancy, and your career path here will be as unique and exciting as the technology itself. We're looking for individuals who are ready to learn, adapt, and help us shape the future of computing.

See Your Progress GrowIllustration

Associate Quantum Software Engineer

Quantum Algorithm Implementation
Quantum Circuit Compilation & Transpilation (Basic)
Noise Modelling & Mitigation (Conceptual)
Hybrid Quantum-Classical Methods (Conceptual)

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

Associate Quantum Software Engineer is a start, not a ceiling. Each step below asks for new skills and hands back more autonomy.

Quantum Software Engineer (Level 2)
2-3 years in the Associate role
You'll move from executing defined tasks to taking ownership of complete quantum software components and independently analysing experimental results. You'll start to propose solutions rather than just implement them.
- Advanced Quantum Algorithm Implementation: Implementing more complex algorithms from scratch.
- Cross-Platform Proficiency: Comfortably working across multiple quantum SDKs and cloud platforms.
- Basic Performance Optimisation: Identifying and improving the efficiency of quantum circuits and classical control code.

Working with AI on the job

Working with AI

Where AI is starting to help

Let's be honest, quantum software engineering is tough. It's complex, it's fiddly, and there's a lot of boilerplate code and repetitive tasks. But what if you could offload some of that grunt work to AI? Imagine spending more time on the truly hard, interesting quantum physics and less on the mundane.

We're embedding AI tools into our daily workflow to help our engineers be more productive. For an Associate Quantum Software Engineer, this means you'll learn how to use these tools from day one, helping you get up to speed faster and contribute more effectively. It's not about replacing you; it's about making you a quantum software superhero.

Classical Code Scaffolding

Use AI code assistants (like GitHub Copilot) to quickly generate the Python 'wrapper' code you need for data loading, pre-processing, and results visualisation. This lets you focus your brainpower on the core quantum algorithm itself, rather than boilerplate.

Basic Noise Pattern Analysis

Even at an Associate level, you can use simple AI/ML scripts to help you spot recurring error patterns in experimental data from a QPU. It's about getting a head start on understanding the hardware's quirks, rather than manually sifting through reams of numbers.

arXiv Research Summariser

Let an LLM-based agent monitor arXiv.org for new papers that match your specific research interests (e.g., 'VQE optimisation'). It'll give you daily one-paragraph summaries, saving you hours of manual scanning and helping you stay on top of this incredibly fast-moving field.

Documentation & Translation Drafts

After you've implemented a new quantum circuit, use an AI tool to generate the initial draft of your technical documentation in Confluence. You can even get it to create a simplified, high-level explanation for when you need to present to non-technical folks. It's a massive time-saver for a necessary task.

Common questions

How do you become an Associate Quantum Software Engineer?

Common routes in include University Graduate (BSc/MSc) (0-1 year post-graduation), Software Developer (Career Changer) (1-2 years self-study/bootcamp + 0-1 year professional experience) and Research Assistant (Quantum Physics) (0-1 year post-RA role). Times vary with prior experience.

Where can an Associate Quantum Software Engineer progress to?

This role can lead on to Quantum Software Engineer (Level 2) (2-3 years in the Associate role), depending on the skills you build.

What level is an Associate Quantum Software Engineer in the UK?

This role aligns to RQF Level 2 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 Associate Quantum Software Engineer?

Increasingly, Prompt Engineering & LLM Integration (for Quantum). 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 Associate Quantum Software Engineer, 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 1 national skill standard. 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 Associate Quantum Software Engineer: 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 Zavmo curriculum screen: a three-month plan built for a customer support lead, five Ofqual-regulated units and a hundred and ninety-six credits. — 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 2

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 within the emerging quantum technology sector. You could move into quantum hardware engineering (if you develop a deeper understanding of physics), quantum research science, or even roles focused on quantum cybersecurity or financial modelling. The core programming, abstract problem-solving, and cutting-edge technical skills are also valuable in broader advanced R&D roles in AI, scientific computing, or high-performance computing.

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.

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.

Associate Quantum Software Engineer

What's rising in its place

Prompt Engineering & LLM Integration (for Quantum)

Skills this role draws on

Technical

How you actually get there, here

University Graduate (BSc/MSc)

Software Developer (Career Changer)

Research Assistant (Quantum Physics)

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

Roles this leads to

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

A conversation, not a course

No two people run this the same way

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

Everything else the record holds

The career path, and where it branches

Quantum Software Engineer (Level 2)

Where AI is starting to help

Classical Code Scaffolding

Basic Noise Pattern Analysis

arXiv Research Summariser

Documentation & Translation Drafts

Common questions

You’ve started things before

Less than one coaching session. Every month.

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