United Kingdom · Research and Development · Entry Level (0-2 years)

Technical Documentation Assistant

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 Technical Documentation Assistant
UK framework levelUsually someone starting out, or keeping a process running

Also advertised as Junior Technical Writer · Documentation Support Specialist · R&D Document Control Assistant

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 Technical Documentation Assistant

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 about writing novels; it's about making sure our groundbreaking scientific work is clearly, accurately, and consistently documented. You'll be the person making sure all the 'i's are dotted and 't's are crossed in our vital R&D documents, learning the ropes from a seasoned team. It's a foundational role, really, where you'll get to see how cutting-edge research gets turned into usable, compliant information.

2What you'd actually use

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

MadCap FlareBasic: You'll be able to open existing projects, edit topics, apply conditional tags, and generate basic outputs from pre-configured targets. Think of it as learning the navigation and basic editing functions.

Updating text in an existing SOP topic, applying a 'Draft' conditional tag, or generating a quick PDF preview for review.

Git (via GitHub/GitLab)Basic: You'll learn to clone repositories, commit your changes to existing branches, and handle basic pull requests, always with guidance from your supervisor.

Saving your updated Flare project files to our Git repository, creating a new branch for your edits, and submitting your changes for review.

ConfluenceIntermediate: You'll be creating and editing pages, applying labels, and using basic macros. You'll understand how space permissions work and how to find information.

Creating meeting notes pages, documenting quick internal processes, or adding links to formal documentation from Flare.

Veeva Vault (or SharePoint)Basic: You'll upload documents, populate metadata fields accurately, and navigate document lifecycles for review and approval processes.

Uploading a finalised PDF of an experimental report, ensuring all required metadata (author, date, version) is correctly entered, and initiating a review workflow.

AcrolinxBasic: You'll run checks on your content and correct basic grammar, style, and terminology issues based on the scorecard feedback it provides.

Running an Acrolinx check on a draft document and making the suggested corrections to improve clarity and consistency before sending it for SME review.

Snagit / CamtasiaBasic: You'll capture and annotate screenshots with basic callouts (e.g., arrows, text boxes). You might record simple screen-capture videos for short procedural explanations.

Taking a screenshot of a new software interface, adding an arrow to highlight a button, and inserting it into a user guide.

Lucidchart / VisioBasic: You'll create basic flowcharts and diagrams, either from a template or a rough sketch provided by a scientist. You'll focus on clarity and adherence to existing visual standards.

Drawing a simple process flow diagram for a lab procedure based on notes from an R&D engineer, ensuring it's easy to follow.

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
Content Changes (Text/Diagrams)	Propose changes to your supervisor; all modifications require explicit approval before implementation. You'll be told exactly what to change.	Independently make routine content updates within established guidelines; consult supervisor on complex or ambiguous changes.	Own content changes for entire workstreams; make technical decisions on content structure and wording; consult leads on strategic implications.
Tool & Process Selection	Use tools and follow processes as instructed. No input on tool selection or process improvement.	Choose appropriate tools/methods for routine tasks from approved list; propose minor process improvements to manager.	Select and implement tools/processes for specific projects; make recommendations for broader adoption; influence team standards.
Project Prioritisation	Work on tasks as assigned by your supervisor. Your workload is managed for you.	Manage your own task queue for assigned projects; escalate conflicts to manager.	Prioritise tasks across multiple projects; negotiate deadlines with stakeholders; resolve minor conflicts independently.
External Communication	No direct communication with external stakeholders or vendors. All external contact is handled by your supervisor.	Communicate with internal cross-functional peers and SMEs; all external communication requires manager's review.	Represent the documentation team in project meetings with internal and external stakeholders; handle vendor communications within project scope.

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.

Document Accuracy Rate

The percentage of your assigned documentation tasks (edits, formatting, updates) that are completed without errors flagged during review.

Target · Achieve >98% accuracy on all tasks after initial training.

If you complete 50 edits in a week and only one has a formatting error or a missed instruction, that's a 98% accuracy rate. We're looking for consistent precision.

Task Completion within SLA

The proportion of routine documentation tasks (e.g., minor content updates, formatting changes) that you finish within the agreed-upon timeframe.

Target · Complete 90% of routine tasks within a 24-hour SLA.

You're asked to update a diagram caption by Tuesday morning. Getting it done by Monday afternoon means you've met the SLA. Missing it means a delay.

Content Reuse Adherence

How often you correctly identify and use existing content snippets or variables instead of creating new, duplicate text.

Target · Correctly use existing content reuse elements in 95% of applicable tasks.

When updating a procedure that mentions a standard safety warning, you correctly insert the pre-approved snippet rather than typing it out again. This saves time and ensures consistency.

Feedback Incorporation Rate

The percentage of feedback points from your supervisor or SMEs that you correctly understand and apply in subsequent revisions.

Target · Successfully incorporate 95% of feedback points on the first revision.

Your supervisor points out 10 areas for improvement in a draft. You address 9 of them perfectly in the next version, hitting 90%.

Proactive Learning & Asking Questions

Your willingness to seek clarification, ask 'why' questions, and actively learn about our R&D processes and documentation standards.

You'll be asking thoughtful questions during team meetings, scheduling 1-on-1s with SMEs to understand context, and bringing up potential issues you've spotted. We'll see you taking notes and referring back to them. It's about showing you're engaged and trying to truly grasp the underlying science and processes, not just follow instructions blindly.

Adherence to Style Guides & Templates

Your consistent application of our established writing style, terminology, and document formatting guidelines.

Your documents will consistently follow our house style guide (e.g., using 'analyse' not 'analyze', correct heading styles, consistent jargon). You won't need constant reminders about basic formatting or grammar rules. Essentially, your work should look like it belongs with the rest of our documentation.

Organisational Skills

How well you manage your assigned tasks, prioritise your workload, and keep your files and projects tidy and accessible.

You'll be able to tell your supervisor the status of your tasks without scrambling. Your project folders will be logically organised, and you'll keep track of your deadlines. This means fewer missed tasks and less time spent searching for things.

Collaboration & Team Fit

Your ability to work effectively with your immediate team and R&D colleagues, contributing positively to our team environment.

You'll respond promptly to requests, offer help when you can, and generally be a good team player. This means being open to feedback, sharing what you've learned, and being easy to work with for both your supervisor and the scientists you support. We're a close-knit team, so fitting in is important.

5Would you like it

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

What people enjoy

Making Sense of Complexity

You'll get a real kick out of taking a jumble of scientific notes or a complex experimental setup and turning it into a clear, step-by-step procedure. That feeling of bringing order to chaos is a big part of the job.

You're handed a rough sketch of a new lab instrument and a few pages of bullet points. Your goal is to turn that into a coherent instruction manual, and you love the challenge of figuring out how all the pieces fit together.

Contributing to Scientific Progress

You'll feel proud knowing that your meticulous documentation helps our scientists conduct better research, publish their findings, and ultimately contribute to new discoveries. You're part of something bigger.

You've just finished tidying up the documentation for a new experimental protocol. Seeing that protocol then used successfully by the lab team, knowing your work made it clearer, gives you a real sense of purpose.

Continuous Learning & Skill Development

This role is a fantastic opportunity to learn about cutting-edge science and develop highly sought-after technical communication skills. If you love soaking up new information and mastering new tools, you'll thrive.

Every week brings a new scientific concept or a new software feature to learn. You're keen to attend workshops, read up on new methodologies, and constantly improve your craft.

What frustrates people

Chasing SMEs: The constant effort to get feedback from brilliant but overloaded scientists.
The 'Scribe' Misconception: Being seen as just a typist rather than someone who adds real value by structuring information.
Repetitive Tasks: Some days will involve a lot of formatting or minor edits, which can feel a bit monotonous.
Legacy Documents: Sometimes you'll be handed old, messy documents with no clear history and asked to 'just update it'.

What this role does not give you

High-level strategic decision-making (that comes later in your career).
Full autonomy over project direction (you'll be guided closely).
A constant stream of brand-new, creative writing tasks (much is updating and refining).

6Who you work with

Your work ensures that all R&D documentation meets our internal quality standards and, crucially, external regulatory requirements. This means our research findings are accurately recorded, our processes are repeatable, and our intellectual property is protected. Essentially, you're building the bedrock of our scientific knowledge base, which underpins everything from patent applications to product development.

Inside the business

Senior Technical Documentation Assistant (your direct manager)
R&D Scientists and Engineers (the folks whose work you'll document)
Quality Assurance Team (they'll review your work for compliance)
Project Managers (they'll need your documentation on time)

Outside the business

Regulatory Bodies (indirectly, through compliant documentation)

7What you need before you start

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

Strong command of written English, including grammar, spelling, and punctuation (British English, naturally).
A genuine interest in science, technology, or research – you don't need a PhD, but curiosity helps immensely.
Basic computer literacy, including familiarity with Microsoft Office Suite (Word, Excel, PowerPoint) or similar tools.
An organised approach to work and a keen eye for detail – you're the person who notices the small things.
A willingness to learn new software and processes quickly, and to ask questions when you're unsure.

8What to practise next

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

Advanced MadCap Flare Features

You'll move beyond basic editing to truly harness Flare's power. This means using more advanced content reuse features and understanding how to troubleshoot minor publishing issues independently.

Creating and managing snippets and variables for m · Working with conditional text sets for different o · Understanding target settings and basic publishing · Using cross-references and indexes effectively. · Basic troubleshooting of build errors.

This week: Review Flare's online help for 'snippets' and 'variables'.
This month: Ask your supervisor for a task that specifically involves creating or modifying snippets.
Month 2: Experiment with creating a new publishing target (e.g., a PDF with specific branding) under supervision.
Month 3: Take a MadCap Flare certification course (if offered by the company or self-funded).

Quick win: Actively look for repetitive text in documents you're editing and suggest to your supervisor that it could be turned into a snippet for future reuse.

Git Branching & Merging

As you become more comfortable with Git, you'll need to understand how to manage your own branches and resolve minor conflicts when collaborating with others. This is fundamental to a docs-as-code workflow.

Understanding different branching strategies (e.g. · Creating, switching, and deleting branches. · Performing basic merges and rebase operations. · Resolving simple merge conflicts independently. · The concept of pull requests and code reviews for

This week: Read up on Git branching fundamentals. There are many great online tutorials.
This month: Practice creating and merging branches in a personal Git repository (e.g., on GitHub).
Month 2: Ask your supervisor for a task where you can work on a dedicated branch and then merge it back.
Month 3: Participate actively in code reviews for documentation, understanding how changes are integrated.

Quick win: Always create a new branch for any significant work, even if it's just for yourself. This builds the habit.

9Staying current once you are in

What people here do to keep up

Joining relevant professional bodies like the Institute of Scientific and Technical Communicators (ISTC) in the UK.
Attending industry webinars and online workshops on technical writing best practices, DITA, or content strategy.
Reading books and articles on minimalism in technical writing and information architecture.
Seeking out opportunities to learn from senior colleagues, asking for mentorship, and taking on challenging tasks.
Building a portfolio of your best writing samples, even if they're from personal projects or academic work.

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 & AI Content Validation

AI is already here, helping us draft content and spot errors. As these tools get smarter, your value will shift from pure content creation to knowing how to effectively 'talk' to AI and, crucially, how to validate its output for accuracy and compliance. This isn't future-gazing; it's happening now.

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 & AI Content Validation

AI is already here, helping us draft content and spot errors. As these tools get smarter, your value will shift from pure content creation to knowing how to effectively 'talk' to AI and, crucially, how to validate its output for accuracy and compliance. This isn't future-gazing; it's happening now.

Crafting clear, specific prompts for AI (e.g., 'wr
Understanding AI limitations and potential for 'ha
Techniques for cross-referencing AI-generated cont
Using AI for summarisation and rephrasing complex
Ethical considerations when using AI in regulated

Basic Data Visualisation for Documentation

Scientists love data, and often the clearest way to explain a complex finding or process is visually. As you progress, being able to create simple, effective charts or graphs directly for documentation will become a significant advantage, reducing reliance on others.

Choosing the right chart type for different data (
Principles of clear and unambiguous data labelling
Using basic tools (like Excel or Google Sheets) to
Integrating visual data into documentation tools l
Understanding when a table is better than a chart,

What you’ll use

Skills this role draws on

Technical

DITA (Darwin Information Typing Architecture) Principles
Docs-as-Code Fundamentals
Minimalism in Technical Writing
Single-Source Publishing Concepts
Information Architecture Basics
Good Documentation Practice (GDP/GxP) Awareness

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
Recent Graduate (English, Science, or Tech)
0-1 year post-graduation
Skills to master
- Foundational technical writing principles, our R&D specific terminology, and proficiency in our core documentation tools (Flare, Git, Veeva Vault).
You're ready to move on when
- Consistently producing accurate, well-formatted documents with minimal supervision.
- Proactively asking clarifying questions and demonstrating a strong grasp of new concepts.
- Successfully managing assigned tasks and meeting deadlines reliably.
2
Administrative Assistant / Document Controller
1-2 years in a document-focused administrative role
Skills to master
- Moving from document management to content creation and editing, understanding technical concepts, and learning authoring tools.
You're ready to move on when
- Demonstrated strong organisational skills and attention to detail in previous roles.
- Expressed a clear interest in understanding technical content and improving communication.
- Proven ability to learn new software quickly and adapt to structured processes.
3
Lab Technician / Research Assistant (with strong writing skills)
1-2 years in a lab setting
Skills to master
- Translating hands-on scientific knowledge into structured, user-friendly documentation, and mastering technical writing tools.
You're ready to move on when
- Exceptional ability to document experimental procedures and results clearly.
- A keen eye for detail and consistency in scientific records.
- A desire to move into a communication-focused role while retaining a connection to science.

11Where this role leads

The long view:This role isn't just a job; it's a launchpad for a rewarding career in technical communication within a fascinating scientific environment. We're looking for someone keen to learn, meticulous in their work, and excited to grow with us.

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 Technical Documentation Assistant 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:

Improve the quality and reliability of scientific or technical activities in the workplaceLevel 3

Applied to your work in Technical Documentation Assistant

This unit aims to provide learners with the skills and knowledge to improve the quality and reliability of scientific or technical activities in the workplace. Learners will be able to implement quality improvement plans, monitor reliability, document changes, implement corrective actions, and evaluate their effectiveness.

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 Technical Documentation Assistant

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.

Document Accuracy RateThe percentage of your assigned documentation tasks (edits, formatting, updates) that are completed without errors flagged during review.If you complete 50 edits in a week and only one has a formatting error or a missed instruction, that's a 98% accuracy rate. We're looking for consistent precision.Achieve >98% accuracy on all tasks after initial training.
Task Completion within SLAThe proportion of routine documentation tasks (e.g., minor content updates, formatting changes) that you finish within the agreed-upon timeframe.You're asked to update a diagram caption by Tuesday morning. Getting it done by Monday afternoon means you've met the SLA. Missing it means a delay.Complete 90% of routine tasks within a 24-hour SLA.
Content Reuse AdherenceHow often you correctly identify and use existing content snippets or variables instead of creating new, duplicate text.When updating a procedure that mentions a standard safety warning, you correctly insert the pre-approved snippet rather than typing it out again. This saves time and ensures consistency.Correctly use existing content reuse elements in 95% of applicable tasks.
Feedback Incorporation RateThe percentage of feedback points from your supervisor or SMEs that you correctly understand and apply in subsequent revisions.Your supervisor points out 10 areas for improvement in a draft. You address 9 of them perfectly in the next version, hitting 90%.Successfully incorporate 95% of feedback points on the first revision.

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 Technical Documentation Assistant to Technical Writer (Level 2), and whatever you decide comes after.

Level 2 · in progressAI Fluency→ Technical Writer (Level 2)→ your design

Where this takes you

This role isn't just a job; it's a launchpad for a rewarding career in technical communication within a fascinating scientific environment. We're looking for someone keen to learn, meticulous in their work, and excited to grow with us.

See Your Progress GrowIllustration

Technical Documentation Assistant

DITA (Darwin Information Typing Architecture) Principles
Docs-as-Code Fundamentals
Minimalism in Technical Writing
Single-Source Publishing Concepts
Information Architecture Basics
Good Documentation Practice (GDP/GxP) Awareness

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

Technical Documentation Assistant is a start, not a ceiling. Each step below asks for new skills and hands back more autonomy.

Technical Writer (Level 2)
2-3 years in the Assistant role
You'll move from executing assigned tasks to independently owning the documentation for specific projects or instruments from start to finish. You'll be making routine decisions on content and structure.
- Independent Authoring: Writing new documents from scratch based on source material and SME interviews.
- Advanced Flare Usage: Using more complex features like snippets, variables, and conditional text independently.
- Basic Information Architecture Design: Proposing and implementing minor structural improvements to documentation sets.
- Mentorship (Informal): Providing guidance and support to new Technical Documentation Assistants.

Working with AI on the job

Working with AI

Where AI is starting to help

Let's be honest, technical documentation can sometimes feel like a grind. But what if you could cut down on the tedious bits and focus more on understanding the science and crafting perfect explanations? That's where AI comes in. We're not talking about robots taking over your job; we're talking about smart tools that make your life easier and your work more efficient.

In our R&D documentation team, we're actively exploring and integrating AI tools to streamline our workflow. For a Technical Documentation Assistant, this means you'll learn how to use these tools to speed up your daily tasks, from drafting initial content to catching inconsistencies. It's about working smarter, not harder, and getting a head start on the future of technical communication.

First-Draft Generation

Imagine feeding raw lab notes or a scientist's bullet points into an AI assistant and getting a structured first draft of an SOP or experiment report back. You'll then refine, validate, and polish it, saving you hours of staring at a blank page. It's like having a very fast, if slightly unpolished, co-writer.

Inconsistency Detection

You'll use AI tools to scan large documents or even our entire documentation repository for inconsistent terminology, conflicting procedural steps, or outdated product names. These are the subtle errors a human might easily miss, but an AI can flag them in seconds, helping you maintain a high level of accuracy.

SME Prep & Research

Before you even chat with a Principal Scientist, you could use AI to summarise their recent papers or internal reports. This means you'll go into meetings better informed, asking deeper, more targeted questions, and getting the information you need faster. Less time researching, more time understanding.

Plain Language Translation

Got a super dense, jargon-filled paragraph from an engineer's notes? You can feed it into an AI model with a prompt like 'Explain this for a new lab technician with a bachelor's degree.' The AI's output gives you a fantastic starting point for creating clear, accessible content, helping you bridge the gap between expert and user.

Common questions

How do you become a Technical Documentation Assistant?

Common routes in include Recent Graduate (English, Science, or Tech) (0-1 year post-graduation), Administrative Assistant / Document Controller (1-2 years in a document-focused administrative role) and Lab Technician / Research Assistant (with strong writing skills) (1-2 years in a lab setting). Times vary with prior experience.

Where can a Technical Documentation Assistant progress to?

This role can lead on to Technical Writer (Level 2) (2-3 years in the Assistant role), depending on the skills you build.

What level is a Technical Documentation Assistant 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 a Technical Documentation Assistant?

Increasingly, Prompt Engineering & AI Content Validation and Basic Data Visualisation for Documentation. 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 a Technical Documentation Assistant, 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 11 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 a Technical Documentation Assistant: 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 Research and Development

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

If you leave this industry

The skills you'll gain here – technical communication, content management, regulatory compliance, and working with complex scientific information – are highly transferable. You could move into documentation roles in other regulated industries (e.g., medical devices, pharmaceuticals), or even into broader content strategy or knowledge management roles in tech companies.

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.

Technical Documentation Assistant

What's rising in its place

Prompt Engineering & AI Content Validation

Basic Data Visualisation for Documentation

Skills this role draws on

Technical

How you actually get there, here

Recent Graduate (English, Science, or Tech)

Administrative Assistant / Document Controller

Lab Technician / Research Assistant (with strong writing skills)

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.

This role isn't just a job; it's a launchpad for a rewarding career in technical communication within a fascinating scientific environment. We're looking for someone keen to learn, meticulous in their work, and excited to grow with us.

Everything else the record holds

The career path, and where it branches

Technical Writer (Level 2)

Where AI is starting to help

First-Draft Generation

Inconsistency Detection

SME Prep & Research

Plain Language Translation

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.