United Kingdom · Research and Development · Mid-Level (2-5 years)

Global Technical Documentation Specialist

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 Technical Documentation Specialist
UK framework levelUsually a coordinator, or early in a professional job

Also advertised as Technical Writer (R&D) · Product Documentation Specialist · Information 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 Global Technical Documentation Specialist

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

You'll be the one translating complex scientific and engineering jargon into clear, usable instructions for our global customers and internal teams. Think of it as being the bridge between the brilliant minds in the lab and the people who actually need to use our cutting-edge products or follow our intricate processes. This isn't just about writing; it's about making sure our research is understood, our products are used correctly, and our innovations are accessible worldwide. You'll own specific documentation projects, making sure they're accurate, on time, and easy to understand.

2What you'd actually use

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

MadCap FlareIntermediate

Creating and editing topics, applying conditions and variables, building DITA maps, and publishing basic outputs (like PDFs and HTML5 help) from existing templates. You'll be living in this tool.

SOLIDWORKS ComposerIntermediate

Manipulating existing 3D models from our engineers to create clear, annotated technical illustrations and exploded views for assembly instructions or product overviews. You won't be creating models from scratch, but you'll make them tell a story.

Visio / SnagitIntermediate

Capturing and annotating screenshots for software documentation (Snagit) and creating basic flowcharts or process diagrams (Visio) to explain complex workflows in a visual way.

Confluence / SharePointIntermediate

Using these platforms for SME review cycles, version control, and sharing drafts with internal teams. You'll be comfortable navigating these spaces and setting up basic pages.

SDL Trados Studio / memoQBasic

Packaging content for translation and re-integrating translated files. You'll understand the concept of Translation Memory (TM) and how it helps us save money and maintain consistency.

Jira / Slack / MS TeamsIntermediate

Managing your assigned documentation tickets in Jira, participating in sprint planning, and communicating status updates or asking quick questions in Slack or Teams. These are our daily comms tools.

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 Structure & Wording	Follows templates and supervisor's instructions. All significant changes reviewed.	Independently designs topic structure and chooses wording within established style guides. Consults senior on complex information architecture questions.	Defines and evolves style guides and information architecture for product lines. Approves structural changes across projects.
Tool & Software Usage	Uses assigned tools (e.g., MadCap Flare) under guidance. Learns basic functionalities.	Independently uses authoring and graphics tools for daily tasks. Can troubleshoot common issues. Proposes minor tool workflow improvements.	Designs and implements advanced tool workflows (e.g., complex conditionalisation, automation scripts). Mentors others on tool best practices.
SME Information Gathering	Participates in SME interviews with supervisor. Documents notes.	Independently conducts SME interviews, asking targeted questions to extract necessary information. Follows up on open items.	Develops strategies for efficient SME engagement. Trains junior writers on effective information gathering techniques.
Project Deadlines & Scope	Works to deadlines set by supervisor. Escalates any potential delays immediately.	Manages own project timelines for assigned documentation, raising potential issues early. Negotiates minor scope adjustments with Product/R&D, with senior oversight.	Defines documentation project timelines and resource needs. Negotiates scope and deadlines with R&D and Product leadership.

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.

Topic Accuracy

Number of factual or procedural errors identified post-publication on your assigned topics.

Target · <2% error rate per manual/project

If a 100-page manual has 2 errors flagged by users or QA after launch, that's a 2% error rate. We're aiming for fewer than that, ideally zero, but let's be realistic.

SME Review Cycle Time

Average time it takes for Subject Matter Experts (SMEs) to review and approve your documentation drafts.

Target · Under 5 business days (from 'Ready for Review' to 'Approved')

You send a draft to an engineer on Monday; they approve it by Friday. That's 5 days. If it drags on for 2 weeks, we need to figure out why, as it impacts our release schedule.

Jira Task Completion Rate

Percentage of documentation-related Jira tickets you're assigned that are completed within the sprint.

Target · 95%+ within sprint

If you have 20 tickets in a sprint and complete 19, that's 95%. This shows you're managing your workload and hitting deadlines.

Content Reuse Rate (Basic)

Percentage of new content that uses existing snippets, variables, or conditional text, reducing redundant writing.

Target · Maintain >20% reuse on new projects

You're writing a new manual, and 25% of its content comes from existing approved topics or variables. This saves time and ensures consistency.

Clarity & Usability

How easy it is for the target audience to understand and act on your documentation, without needing extra help.

Feedback from user testing, customer support teams reporting fewer 'how-to' questions related to your documents, positive comments during product demos, or even just colleagues saying 'that was really clear, thanks!'

SME Relationship Building

Your ability to build rapport with R&D experts, making them more willing to provide timely and accurate information.

SMEs proactively reaching out to you with updates, responding quickly to your queries, positive feedback from managers about your interactions, or even just a sense that you're seen as a helpful partner, not just someone 'chasing documentation'.

Proactive Problem Solving

Your initiative in identifying potential documentation gaps or issues before they become major problems.

You flag an inconsistency in the UI before release, you suggest a better way to structure information for a new feature, or you propose a solution when an engineer's notes are a bit... sparse. Basically, you don't wait to be told everything.

Adherence to Style & Standards

How consistently you apply our established style guides, terminology, and content standards.

Minimal edits from senior team members for style or grammar, consistent use of approved terms (is it 'log in' or 'sign in'?), and your documents fitting seamlessly into our existing content library.

5Would you like it

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

What people enjoy

Making Complex Simple

You get a real kick out of taking a dense, jargon-filled scientific paper or a complicated engineering spec and transforming it into something clear, concise, and genuinely useful for someone else.

You've just finished a new user guide for a complex piece of lab equipment, and a colleague from customer support tells you it's the clearest explanation they've ever seen. That's your fuel.

Contributing to Innovation

You want to be part of bringing groundbreaking research and products to life, knowing your clear documentation helps others understand and use these innovations effectively.

You're writing the manual for a new medical device that could change lives, and you feel a direct connection to that impact, even if you're not in the lab yourself.

Structured Problem Solving

You enjoy the challenge of organising information, designing logical structures, and building systems (like a DITA map or a content reuse strategy) that make sense out of complexity.

You've just restructured an entire section of our online help, making it much easier for users to find what they need. The satisfaction comes from bringing order to chaos.

What frustrates people

Chasing Subject Matter Experts (SMEs) for information, only to get a one-sentence email reply for a feature that took six months to build.
The product UI or API changing *after* the documentation has been finalised and sent for a 12-language translation run, causing costly rework.
Being treated as a 'scribe' or 'proofreader' by R&D teams who don't understand that information architecture and content strategy are complex disciplines.
Receiving 'napkin sketch' diagrams or vague, jargon-filled notes from engineers and being expected to turn them into clear, user-facing instructions.
Discovering that legacy documentation, which you now own, is an unstructured, inconsistent mess with no source files.

What this role does not give you

A perfectly linear, predictable workflow with all information handed to you on a silver platter.
Immediate, high-level strategic influence over product direction (that comes later, with experience).
A quiet, solitary writing environment every single day; you'll be interacting with people constantly.
A role where you can avoid the nitty-gritty details of tool configuration or content management systems.

6Who you work with

This role ensures that critical R&D outputs, from product manuals to experimental protocols, are accurately documented and easily understood. Your work directly impacts product adoption, user satisfaction, and the efficiency of internal R&D processes, especially for our global audience. Get it right, and you save countless hours in support, training, and error correction across the business. Get it wrong, and you risk reputational damage and operational inefficiencies.

Inside the business

R&D Engineers (Hardware, Software, Mechanical)
Research Scientists and Lab Technicians
Product Managers
Quality Assurance Teams
Global Customer Support

Outside the business

End-users of our products
External partners using our research outputs
Translation and localisation agencies

7What you need before you start

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

At least 2 years of experience writing technical documentation for complex products or processes, ideally within a technical or scientific field.
Demonstrable experience with at least one structured authoring tool (e.g., MadCap Flare, Paligo, Oxygen XML Editor). You'll need to hit the ground running with Flare here.
A portfolio or samples of your previous technical writing work that showcase your ability to explain complex topics clearly and concisely.
Experience working directly with Subject Matter Experts (SMEs) to extract technical information.
A good grasp of English grammar, style, and punctuation. We're pretty strict on this.

8What to practise next

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

Advanced CCMS & Information Model Design

Important within 12-18 months. As our R&D output grows, managing content effectively across multiple products and languages becomes a huge challenge. We'll need people who can not only use our Component Content Management System (CCMS) but help design its structure and rules.

Global Information Models · Metadata & Taxonomy Strategy · Content Reuse Metrics & ROI · XML Schema Customisation

This quarter: Take an online course on advanced DITA concepts or CCMS administration (we can help with resources).
Next quarter: Volunteer to help with a small project involving content migration or restructuring within our existing CCMS.
Month 6: Start documenting current content reuse challenges and propose solutions based on advanced CCMS features.
Month 9: Begin to understand the 'why' behind our current information model and identify areas for optimisation.

Quick win: Familiarise yourself with all the advanced features of MadCap Flare or our current CCMS, even if you don't use them daily. Just knowing what's possible is a huge first step.

9Staying current once you are in

What people here do to keep up

Attending industry conferences like LavaCon or the STC Summit (we often sponsor attendance for key team members).
Participating in online communities and forums dedicated to technical communication or specific tools (e.g., MadCap Flare forums).
Taking advanced courses on topics like information architecture, content strategy, or Simplified Technical English.
Reading relevant books and articles on user experience (UX) writing and content design.
Seeking out opportunities to mentor junior colleagues or new hires, even informally—it's a great way to solidify your own knowledge.

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

Critical within 6 months—this is already happening, not future. Our competitors are using tools like GPT to draft reports in 10 minutes that used to take 2 hours. Documentation specialists who figure this out will outproduce their peers significantly.

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

Critical within 6 months—this is already happening, not future. Our competitors are using tools like GPT to draft reports in 10 minutes that used to take 2 hours. Documentation specialists who figure this out will outproduce their peers significantly.

Context windows and token limits
Temperature settings for different tasks
RAG (Retrieval Augmented Generation) architectures
Output validation and hallucination detection
Prompt chaining for complex analysis

What you’ll use

Skills this role draws on

Technical

DITA (Darwin Information Typing Architecture)
Minimalism
Single-Sourcing Strategy
Information Architecture
Localization (L10n) & Internationalization (I18n) Principles

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
Junior Technical Writer / Associate Information Developer
2-3 years
Skills to master
- Mastering a structured authoring tool (like MadCap Flare), understanding DITA basics, learning to work with SMEs, and consistently producing accurate, clear content under supervision.
You're ready to move on when
- Consistently delivering assigned documentation tasks on time and with minimal errors.
- Proactively identifying minor inconsistencies or gaps in existing documentation.
- Building good working relationships with a few key R&D engineers.
- Showing initiative in learning new features of our documentation tools.
2
Technical Support Specialist (with writing focus)
3-4 years
Skills to master
- Deep product knowledge, understanding common user pain points, translating support tickets into documentation needs, and developing strong customer-facing communication skills.
You're ready to move on when
- Actively contributing to internal knowledge bases and external FAQs.
- Identifying trends in support queries that could be solved with better documentation.
- Demonstrating an ability to explain complex technical issues to non-technical users.
- Showing a keen interest in improving overall product usability through clear instructions.
3
R&D Engineer / Scientist (transition)
3-5 years
Skills to master
- Learning technical communication principles (DITA, minimalism), structured authoring tools, and developing a user-centric writing style. Your deep technical knowledge is already there, it's about translating it.
You're ready to move on when
- Volunteering to write internal technical specifications or project reports.
- Recognising the importance of clear documentation in your own R&D work.
- Having a natural ability to explain complex technical concepts to colleagues.
- Expressing a strong desire to focus on communication and information organisation.

11Where this role leads

The long view:Your journey here as a Global Technical Documentation Specialist is just the beginning. We're committed to helping you grow, whether that's becoming a deep technical expert, leading a team, or shaping the future of knowledge management across our R&D organisation. The opportunities are genuinely vast, and we're excited to see where you take it.

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 Global Technical Documentation Specialist 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:

Producing Technical Information for Engineering ActivitiesLevel 3

Applied to your work in Global Technical Documentation Specialist

The objective of this unit is to enable learners to produce accurate and clear technical information for engineering activities. Learners will gain the ability to gather information, produce documentation using appropriate formats and standards, and review it for errors, ensuring effective communication.

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 Global Technical Documentation Specialist

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.

Topic AccuracyNumber of factual or procedural errors identified post-publication on your assigned topics.If a 100-page manual has 2 errors flagged by users or QA after launch, that's a 2% error rate. We're aiming for fewer than that, ideally zero, but let's be realistic.<2% error rate per manual/project
SME Review Cycle TimeAverage time it takes for Subject Matter Experts (SMEs) to review and approve your documentation drafts.You send a draft to an engineer on Monday; they approve it by Friday. That's 5 days. If it drags on for 2 weeks, we need to figure out why, as it impacts our release schedule.Under 5 business days (from 'Ready for Review' to 'Approved')
Jira Task Completion RatePercentage of documentation-related Jira tickets you're assigned that are completed within the sprint.If you have 20 tickets in a sprint and complete 19, that's 95%. This shows you're managing your workload and hitting deadlines.95%+ within sprint
Content Reuse Rate (Basic)Percentage of new content that uses existing snippets, variables, or conditional text, reducing redundant writing.You're writing a new manual, and 25% of its content comes from existing approved topics or variables. This saves time and ensures consistency.Maintain >20% reuse on new projects

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 Global Technical Documentation Specialist to Senior Global Technical Documentation Specialist (L3), and whatever you decide comes after.

Level 3 · in progressAI Fluency→ Senior Global Technical Documentation Specialist (L3)→ your design

Where this takes you

Your journey here as a Global Technical Documentation Specialist is just the beginning. We're committed to helping you grow, whether that's becoming a deep technical expert, leading a team, or shaping the future of knowledge management across our R&D organisation. The opportunities are genuinely vast, and we're excited to see where you take it.

See Your Progress GrowIllustration

Global Technical Documentation Specialist

DITA (Darwin Information Typing Architecture)
Minimalism
Single-Sourcing Strategy
Information Architecture
Localization (L10n) & Internationalization (I18n) Principles

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

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

Senior Global Technical Documentation Specialist (L3)
3-4 years
Owns entire documentation suites for major products, mentors junior writers, and drives process improvements.
- Advanced DITA & Content Reuse: Designing more complex content reuse strategies, including advanced conditionalisation and DITA specialisation.
- Process Optimisation: Identifying bottlenecks in documentation workflows and implementing solutions to improve efficiency.
- Project Leadership: Leading documentation efforts for larger, more complex R&D projects, coordinating with multiple teams.
Lead Information Architect (L4)
4-6 years
Designs the overall structure, reuse strategy, and metadata for entire product families, solving complex publishing challenges.
- Enterprise Information Architecture: Designing taxonomies, ontologies, and content models that span multiple products and departments.
- Advanced CCMS Administration: Configuring and managing the CCMS, including schema customisation, publishing pipelines, and integration with other systems.
- Content Strategy Development: Creating and implementing long-term strategies for content creation, management, and delivery.

Working with AI on the job

Working with AI

Where AI is starting to help

Imagine cutting down on the tedious, repetitive parts of technical writing. That's exactly what AI is starting to do for our team. We're not talking about replacing you, but giving you a seriously powerful co-pilot to speed up your work and let you focus on the really interesting stuff.

In R&D, getting accurate information from complex sources is half the battle. AI tools can now help you sift through dense research papers, analyse code comments, and even suggest clearer ways to phrase technical concepts. It's about working smarter, not harder, and getting our groundbreaking research documented faster and more accurately.

First-Draft Automation

Use AI to analyse developer comments in code repositories (like GitHub) or Jira tickets, generating a structured first draft of API documentation or procedural steps. It's like having a super-fast assistant for those initial, often daunting, blank pages.

Consistency & Clarity Analysis

Run an AI tool across your documentation to quickly identify inconsistent terminology (e.g., 'Log in' vs. 'Sign on'), spot sentences that violate Simplified Technical English rules, and flag overly complex language. This frees you up from tedious proofreading.

SME Prep Accelerator

Feed complex internal research papers, patents, or lengthy engineering specifications into an AI model. It'll generate concise summaries and a list of targeted questions to ask your SME, making those crucial information-gathering interviews much more efficient and less painful for everyone.

Audience-Tuned Rephrasing

Highlight a highly technical paragraph and use AI to instantly generate alternative versions tailored for different audiences. Think 'Novice User,' 'Expert Installer,' or even a 'Marketing Brief.' This helps you adapt your content without starting from scratch.

Common questions

How do you become a Global Technical Documentation Specialist?

Common routes in include Junior Technical Writer / Associate Information Developer (2-3 years), Technical Support Specialist (with writing focus) (3-4 years) and R&D Engineer / Scientist (transition) (3-5 years). Times vary with prior experience.

Where can a Global Technical Documentation Specialist progress to?

This role can lead on to Senior Global Technical Documentation Specialist (L3) (3-4 years) and Lead Information Architect (L4) (4-6 years), depending on the skills you build.

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

Increasingly, Prompt Engineering & LLM Integration. 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 Global Technical Documentation Specialist, 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 8 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 Global Technical Documentation Specialist: 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 3

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 build here—structured authoring, information architecture, working with complex technical data, and managing global content—are highly transferable. You could easily move into similar roles in other highly regulated industries (e.g., aerospace, defence, finance) or any tech company with complex products. Your R&D background will be a huge asset.

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.

Global Technical Documentation Specialist

What's rising in its place

Prompt Engineering & LLM Integration

Skills this role draws on

Technical

How you actually get there, here

Junior Technical Writer / Associate Information Developer

Technical Support Specialist (with writing focus)

R&D Engineer / Scientist (transition)

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

Senior Global Technical Documentation Specialist (L3)

Lead Information Architect (L4)

Where AI is starting to help

First-Draft Automation

Consistency & Clarity Analysis

SME Prep Accelerator

Audience-Tuned Rephrasing

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.