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

Technical Writer

Here is the whole job, in plain words. What it is, 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.

Start my Technical Writer plan, free

Free to start: a plan built for this role, and a Future Fluency module to try first. No card.

Keep this job description

Where should we send it?

One email: what AI is changing in this job, and where to start free. With a link back here. Nothing else follows unless you confirm your address.

Upskilling a team in this role? Talk to us

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

Also advertised as Technical Author · Documentation Specialist · Content Developer (R&D)

Built on 43,079 real UK job descriptions we analysed · grounded in qualifications employers recognise

Two short quizzes about you

1From this job to a course

The qualifications matched to this job

Cambridge OCR Level 3 Cambridge Technical Certificate in Applied Science Cambridge OCR · Level 3 · covers 1 of 2 standards

Cambridge OCR Level 3 Cambridge Technical Foundation Diploma in Applied Science Cambridge OCR · Level 3 · covers 1 of 2 standards

GQA PAA\VQ-SET Level 2 Certificate in Laboratory Technical Skills GQA Qualifications Limited · Level 2 · covers 1 of 2 standards

AIM Qualifications Level 2 Diploma in Employability Skills AIM Qualifications · Level 2 · covers 1 of 2 standards

Matched from the standards this job is measured against: a suggestion, not an official ruling.

The units you would start with

Scientific analysis and reporting Cambridge OCR Level 3 Cambridge Technical Certificate in Applied Science

Scientific analysis and reporting Cambridge OCR Level 3 Cambridge Technical Foundation Diploma in Applied Science

Routine Laboratory Procedures GQA PAA\VQ-SET Level 2 Certificate in Laboratory Technical Skills

Report Writing AIM Qualifications Level 2 Diploma in Employability Skills

The future skills this job leans on

AI Fluency working with AI as a thinking partner

Data Fluency turning numbers into a decision

Systems Fluency seeing the whole picture

Start my Technical Writer plan, free

Your Plan Illustration

Built for Technical Writer

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

Scientific analysis and reporting Cambridge OCR · covers 1 of 2 standards Level 3
Scientific analysis and reporting Cambridge OCR · covers 1 of 2 standards Level 3
Routine Laboratory Procedures GQA Qualifications Limited · covers 1 of 2 standards Level 2
Report Writing AIM Qualifications · covers 1 of 2 standards Level 2

These are the real units behind this job, in the order they rank for it. Nothing here is marked done, because this plan has not been started by anyone yet. Yours would fill in as you go.

2AI and this work

Will AI change your work as a Technical Writer?

Nobody can say exactly how. Here is what this job is being asked for next, and where to start.

The new skills this role is being asked for

Prompt Engineering & LLM Integration
Interactive & Multimedia Documentation

Why each one is rising

The future skills this job leans on

AI Fluencyworking with AI as a thinking partner
Data Fluencyturning numbers into a decision
Systems Fluencyseeing the whole picture

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

What happens when you start

Next, a free account. We build your Technical Writer plan as you set up, starting with a Future Fluency module on using AI in your job. No card.

Your first Future Fluency module is free. After that, your AI tutor is £70 a month.

Start my Technical Writer plan, free Ready to pay? Subscribe for £70 a month

3What this role really is

A technical writer turns complex scientific and engineering work into clear, usable documentation. The job means working closely with researchers and engineers, understanding their projects, and producing guides that others can follow, whether that's a new joiner, another team, or a patent examiner.

4What you'd actually use

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

MadCap Flare Intermediate

Creating and publishing topic-based content for user manuals, internal guides, and online help systems. You'll be applying conditional tags and variables for basic single-sourcing.

Confluence Intermediate

Creating, editing, and organising pages within existing R&D knowledge spaces. You'll use macros (like TOCs, info panels) and follow established templates for team wikis and internal process docs.

Git (GitHub/GitLab) Intermediate

Cloning documentation repositories, committing your changes to existing branches, and creating pull requests with clear descriptions. You'll follow our established branching strategies for documentation.

Lucidchart / Visio Intermediate

Creating simple to moderately complex flowcharts, process maps, and system diagrams using standard shape libraries and templates to visually explain R&D workflows or system architectures.

Zotero / EndNote Intermediate

Collecting and organising references for research papers and internal reports. You'll insert formatted citations and bibliographies into your documents using the word processor plugin.

LaTeX Basic

Editing existing `.tex` files to update content for scientific papers or reports. You'll be able to write basic mathematical formulas and create simple tables within LaTeX documents.

Jira Intermediate

Viewing tickets assigned for documentation tasks, updating their status, adding comments, and attaching draft documents. You'll also write effective user stories for your own doc tasks.

5What 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 & Organisation (within a document)	Follows established templates and outlines; seeks approval for any deviations.	Independently designs logical content structures for new documents; consults with Senior Technical Writer on complex information architecture challenges.	Defines and evolves content structure standards for entire documentation suites; mentors others on best practices.
Information Gathering Strategy (SME Interviews)	Uses provided interview templates; relies on supervisor to identify key SMEs.	Develops tailored interview questions based on project brief; identifies relevant SMEs and schedules meetings independently.	Coaches junior writers on effective SME wrangling techniques; designs strategies for capturing 'tribal knowledge' across teams.
Tool & Software Usage (within established stack)	Uses designated tools (e.g., MadCap Flare, Confluence) for specific tasks as instructed.	Chooses appropriate tools from the approved stack for a given task (e.g., Flare for manuals, Confluence for internal wikis); explores new features within existing tools.	Evaluates new tools for potential adoption; defines best practices for tool usage across the team; troubleshoots complex tool-related issues.
Project Timelines & Scope	Adheres strictly to assigned timelines; escalates any potential delays immediately.	Manages own project timelines for assigned documentation tasks; proactively communicates potential delays and proposes solutions to Senior Technical Writer.	Negotiates documentation timelines with R&D project leads; identifies and mitigates scope creep; manages multiple concurrent documentation projects.

6How you'll be judged

The scoreboard, and what is not on it. The hard targets, how often each is actually looked at, and the quiet signals that never reach a dashboard.

First Draft Accuracy

The percentage of your content that gets accepted by the Subject Matter Expert (SME) in the first review round, with minimal changes needed.

Target · <10% of content requires significant rework after first SME review

You submit a draft for a new experimental protocol, and the lead scientist only suggests a few minor wording tweaks, not structural changes or factual corrections. That's a win.

Time-to-Publish (Routine Updates)

How quickly you can get routine documentation updates (e.g., minor changes to an existing guide) published after receiving the request.

Target · Routine updates published within 48 hours of request

A researcher flags a typo or a small process change in a Confluence page. You fix it, get a quick sign-off, and publish it within a day.

User Feedback Score

The average rating or 'helpful' score your published articles receive from internal users.

Target · Achieve an average of 4/5 stars or >80% 'Helpful' rating on published articles

Your guide on setting up a new simulation environment consistently gets positive feedback, with comments like 'finally, a guide that actually works!'.

Documentation Completion Rate

The percentage of assigned documentation tasks or projects that you complete and publish by their agreed-upon deadlines.

Target · 90% of assigned documentation tasks completed on schedule

You committed to having the API documentation for the new internal data processing library ready by month-end, and it's live by the 28th.

Clarity and Scannability

How easy your documentation is to read, understand, and navigate, especially for someone new to the topic. Are people finding what they need quickly?

SMEs comment on how 'easy to follow' your guides are. New joiners mention your docs as a key resource. Low number of follow-up questions to SMEs after they've read your work. Use of clear headings, bullet points, and visuals.

Proactive Information Gathering

Your ability to actively seek out information from busy researchers, anticipating their needs and ensuring you're not just waiting for them to tell you what to write.

You're attending relevant project meetings even when not explicitly invited. You're asking insightful questions that uncover hidden details. You're building relationships with key SMEs who trust you to come to them early.

Adherence to Style & Standards

How well your documentation follows our internal style guides, templates, and information architecture principles, ensuring consistency across all R&D content.

Peer reviews consistently show few style guide violations. Your documents fit seamlessly into our existing knowledge base structure. You're using conditional text and variables correctly for reuse.

Problem-Solving & Adaptability

Your knack for figuring things out when information is incomplete or when the underlying technology changes, and your ability to adjust your approach.

You're not just reporting problems
you're suggesting solutions for missing information. You can quickly adapt a document when a technical spec changes mid-way through writing. You're comfortable documenting a 'moving target' to a reasonable degree.

7Would you like it

Both sides. What people enjoy, and what grinds them down.

What people enjoy

Solving Puzzles & Clarifying Complexity

You'll spend your days taking incredibly complex, often abstract, R&D concepts and breaking them down into understandable, actionable steps. It's like being a detective, piecing together clues from code, conversations, and experiments to form a coherent narrative. The satisfaction comes from turning chaos into order.

Taking a 50-page research paper on a new algorithm and turning it into a 5-page internal guide with clear steps and examples that a junior engineer can follow.

Enabling Others' Success

Your work directly helps our scientists and engineers be more productive. You'll get a real kick out of knowing your documentation has saved someone hours, prevented a costly error, or helped a new colleague get started quickly. You're an unsung hero, making sure the R&D engine runs smoothly.

Receiving an email from a researcher thanking you because your new troubleshooting guide helped them fix an issue in minutes, rather than days.

Continuous Learning & Growth

You'll constantly be exposed to new scientific discoveries, engineering methodologies, and internal tools. Every project is a chance to learn something new, diving deep into different domains within R&D. If you love intellectual stimulation and expanding your knowledge base, you'll find plenty of it here.

Spending a week learning the basics of quantum computing to document a new simulation framework, then moving on to understanding a novel chemical synthesis process.

What frustrates people

The 'Knowledge Curse': Trying to extract clear explanations from brilliant SMEs who are so deep in their field they can no longer explain it to a beginner.
Documenting a Moving Target: Being asked to document a process or tool while it's still being actively designed, leading to constant rewrites and wasted effort.
The Last Mile Problem: Being treated as the final checkbox in a project, handed a complex system with an impossible deadline and no prior context.
Fighting for a Seat at the Table: The constant struggle to be included in early design and planning meetings to understand the 'why,' not just the 'what.'
Archaeological Digs: Discovering the existing 'documentation' is a wasteland of conflicting wiki pages, outdated Word documents on a shared drive, and cryptic notes in a lab book.
The 'Just Write It Down' Fallacy: Stakeholders who believe technical writing is simply typing what an SME says, underestimating the work of structuring, clarifying, and validating information.

What this role does not give you

A perfectly stable, unchanging environment where processes are set in stone.
The opportunity to lead a team or manage people (at this level, anyway).
A role where you're always the first person consulted on strategic decisions.
A quiet, isolated corner where you can just write without interruption (SME wrangling is real!).

8Who you work with

Your work directly impacts the efficiency and effectiveness of our entire R&D department. Clear documentation means fewer errors in experiments, faster adoption of new internal tools, and a smoother onboarding experience for everyone. Honestly, it's about making sure our brilliant minds don't waste time figuring out how to use something, but rather focus on what they do best: research and development.

Inside the business

Research Scientists (your primary source of information)
Software Engineers (for internal tools and APIs)
Product Managers (who define what needs documenting)
Quality Assurance Testers (who validate our processes)
Other Technical Writers (for peer reviews and collaboration)

9What you need before you start

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

A proven track record of 2-5 years in technical writing, preferably within a scientific, engineering, or similarly complex technical domain.
Demonstrable experience in interviewing Subject Matter Experts and translating complex information into clear, user-friendly documentation.
Solid understanding of version control concepts (like Git) and experience using at least one modern component content management system (CCMS) or authoring tool (e.g., MadCap Flare, Paligo, Oxygen XML).
A portfolio of writing samples that showcases your ability to explain complex technical topics clearly and concisely.
A genuine curiosity for how things work, especially in the realm of science and technology.

10What to practise next

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

Advanced MadCap Flare/CCMS Usage

As our R&D projects grow in complexity, so does the need for sophisticated content reuse and multi-channel publishing. You'll need to go beyond basic templates.

Advanced Single-Sourcing Strategies · Skins & Master Pages Customisation · Troubleshooting Build Errors · Integrating with External Systems · Optimising for Search & SEO

This week: Explore the advanced features in Flare's online help or community forums. Pick one feature you haven't used and try it out.
This month: Take on a project that requires more complex conditional text or variable usage than you're used to.
Month 2: Shadow a Senior Technical Writer on a project involving custom skin development or advanced single-sourcing.
Month 3: Propose an improvement to our current Flare project setup that uses a more advanced feature.

Quick win: Experiment with creating a new variable or conditional tag in a test project to see how it works. It's a small step, but it builds confidence.

Documentation CI/CD (Continuous Integration/Continuous Deployment)

Just like software, documentation needs to be updated and deployed rapidly. Automating our documentation builds and releases ensures consistency and speed, reducing 'doc debt'.

Git Hooks & Workflows · Basic Scripting (e.g., Python, Bash) · Build Tools & Static Site Generators · Deployment Pipelines (e.g., GitHub Actions, GitLab CI) · Automated Testing for Docs

This week: Read an introductory article on 'Docs-as-Code CI/CD' to get a general understanding of the concepts.
This month: Find a simple open-source documentation project on GitHub that uses a static site generator and try to build it locally.
Month 2: Experiment with a simple GitHub Action to run a spell check on a Markdown file in a test repository.
Month 3: Discuss with a Senior Technical Writer or Engineer how we could automate a small part of our current documentation build process.

Quick win: Set up a local Markdown linter (e.g., markdownlint) and integrate it into your text editor. It's a tiny step towards automated quality checks.

11Staying current once you are in

What people here do to keep up

Regularly reading industry blogs and publications (e.g., STC Intercom, Write the Docs community) to stay on top of trends.
Attending webinars or online courses on new authoring tools, AI in documentation, or specific R&D domains (e.g., a 'crash course' in bioinformatics if you're documenting a related project).
Participating in internal 'lunch and learn' sessions where R&D teams present their work, helping you broaden your knowledge base.
Contributing to open-source documentation projects to hone your Docs-as-Code skills and collaborate with a wider community.

12The rising capability

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

Honestly, competitors are already using large language models (LLMs) to draft reports in minutes that used to take hours. Writers who figure this out will outproduce their peers significantly. It's not about being replaced; it's about being augmented.

Context Windows & Token Limits
Temperature Settings for Different Tasks
RAG (Retrieval Augmented Generation) Architectures
Output Validation & Hallucination Detection
Prompt Chaining for Complex Analysis

Interactive & Multimedia Documentation

Static text documents, while essential, aren't always the most effective way to explain complex R&D processes, especially for visual learners. Interactive guides, short video tutorials, and embedded simulations are becoming more expected.

Video Scripting & Storyboarding
Basic Screen Recording & Editing
Interactive Walkthrough Tools
Accessibility for Multimedia
Measuring Engagement

13What you’ll use

What you’ll use

Skills this role draws on

Technical

Information Architecture (IA)
Docs-as-Code Principles
DITA (Darwin Information Typing Architecture) Concepts
Minimalism in Technical Writing
API Documentation (Internal R&D APIs)

14The pathway

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
Associate Technical Writer (L1) at Zavmo
1-2 years
Skills to master
- Mastering our internal style guide and templates, effectively using our core authoring tools (Flare, Confluence), basic SME interviewing, and consistently delivering accurate, small-scale documentation updates.
You're ready to move on when
- Consistently produces error-free documentation that meets quality standards.
- Can independently complete routine documentation tasks without constant supervision.
- Proactively identifies and suggests minor improvements to existing documentation.
- Demonstrates a strong understanding of our R&D processes and terminology.
2
Technical Writer from a related industry (e.g., Software, Manufacturing)
Direct entry (0-6 months ramp-up)
Skills to master
- Adapting to the specific complexities of R&D documentation, learning our internal scientific and engineering jargon, quickly understanding our unique R&D workflows, and building rapport with our researchers.
You're ready to move on when
- Quickly grasps new technical concepts unique to our R&D domain.
- Successfully translates previous technical writing experience to new R&D projects.
- Establishes effective working relationships with R&D SMEs.
- Demonstrates initiative in learning our internal systems and processes.
3
Researcher/Engineer with strong writing skills
Direct entry (0-9 months ramp-up)
Skills to master
- Learning the specific methodologies of technical communication (e.g., information architecture, topic-based authoring), mastering our documentation tools, and developing a user-centric approach to content creation (rather than just academic reporting).
You're ready to move on when
- Shows a natural aptitude for explaining complex technical topics clearly to non-experts.
- Quickly picks up new documentation tools and workflows.
- Demonstrates a desire to structure information for usability, not just completeness.
- Actively seeks feedback on their writing and applies it effectively.

15Where this role leads

The long view: This work can lead to a role managing documentation for a whole department, or to specialising deeply as a principal technical writer shaping content strategy.

16Pay and demand

ONS's coding index maps “Technical Writer” to more than one occupation, so there is no one median to quote. Rather than pick, here is each one it could be, with its own figure:

IT business analysts, architects and systems designers £60,288 a year
Authors, writers and translators £39,459 a year

ONS Annual Survey of Hours and Earnings, from the April 2025 survey, about six months old when published, as ASHE always is, under the Open Government Licence.

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 Writer is actually changing.

How you would learn this

One to one, on the work you already do

A tutor sets the task against your own job and marks the reasoning, at your pace. There is no cohort to fall behind.

A lesson from Scientific analysis and reporting, worked against Technical Writer.

Scientific analysis and reporting Level 3

Applied to your work in Technical Writer

The objective of this unit is to enable learners to understand the principles of scientific analysis, apply relevant techniques to interpret data, evaluate its validity, and produce professional scientific reports, while adhering to ethical considerations and quality control procedures.

How the thinking builds

1 Remember
2 Understand
3 Apply
4 Analyse
5 Evaluate
6 Create

An illustration of a Zavmo lesson, built from this role’s own route. The unit, its objective and every criterion above are the awarding body’s own words, not an example.

It is £70 a month, billed monthly. Your free first module is Future Fluency, and you can cancel any time.

Start my Technical Writer plan, free

See Your Progress Grow Illustration

Technical Writer

Information Architecture (IA)
Docs-as-Code Principles
DITA (Darwin Information Typing Architecture) Concepts
Minimalism in Technical Writing
API Documentation (Internal R&D APIs)

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.

17The 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 Writer is a start, not a ceiling. Each step below asks for new skills and hands back more autonomy.

Senior Technical Writer (L3)
3-5 years in current role

You'll move from owning individual documents to owning entire documentation suites for major R&D projects. You'll also start mentoring junior writers and improving our documentation processes.
- Advanced Information Architecture Designing complex IA for multi-product documentation or large knowledge bases.
- Documentation Project Leadership Leading the documentation efforts for significant R&D programmes.
- Content Strategy Contribution Helping to shape the overall approach to how we manage and deliver R&D knowledge.
- Advanced Single-Sourcing Implementing sophisticated content reuse strategies across different outputs and product versions.

Working with AI on the job

Working with AI

Where AI is starting to help

Imagine cutting down on the tedious parts of technical writing, freeing you up to focus on the really interesting, complex stuff. That's what AI can do for you here. We're not talking about replacing writers, but about supercharging your productivity.

In R&D, getting clear, accurate information from busy experts is half the battle. AI tools can help you prepare for those conversations, draft initial content, and even translate dense scientific jargon into something everyone can understand. It's about working smarter, not harder.

First Draft Generation

Feed an AI model internal lab notes, code comments, or meeting transcripts, and it'll give you a structured first draft of a standard operating procedure (SOP) or an internal tool guide. You'll then refine it, ensuring accuracy and our unique voice.

Research Summarisation

Got a stack of lengthy academic papers, patent documents, or competitor research? Pop them into an AI. It'll extract the key findings, methodologies, and prior art, giving you a concise summary for your initial analysis and background research.

Jargon Translation & Style Editing

Instantly rephrase dense, academic text into clear, simple language that adheres to our company style guide. You can even generate different versions for different audiences – say, an expert vs. a novice – with a few clicks.

SME Interview Prep

Provide an AI with a project brief and technical specifications. It can then generate a comprehensive list of targeted, insightful questions to ask a Subject Matter Expert, making sure you don't miss any critical details during your interviews.

Common questions

How do you become a Technical Writer?

Common routes in include Associate Technical Writer at Zavmo (1-2 years), Technical Writer from a related industry (e.g., Software, Manufacturing) (Direct entry (0-6 months ramp-up)) and Researcher/Engineer with strong writing skills (Direct entry (0-9 months ramp-up)). Times vary with prior experience.

Where can a Technical Writer progress to?

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

What new skills matter most for a Technical Writer?

Increasingly, Prompt Engineering & LLM Integration and Interactive & Multimedia Documentation. These are the skills our record of this role lists as growing.

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. Start my Technical Writer plan, free What happens next: a free account, then we build your plan as you set up. 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 Writer

Where should we send it?

Two short quizzes about you

Will AI change your work as a Technical Writer?

What's rising in its place

Prompt Engineering & LLM Integration

Interactive & Multimedia Documentation

Skills this role draws on

Technical

How you actually get there, here

Associate Technical Writer (L1) at Zavmo