United Kingdom · Technical roles · Director/VP (16-20 years)

Director, Knowledge Platforms

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 bandDirector/VP (16-20 years)
Direct reports5-8 reports
Reports toVP of Engineering Enablement
UK framework levelUsually a director, accountable for a division and its numbers

Also advertised as Head of Knowledge Management Engineering · VP, Engineering Enablement (Knowledge) · Director of Technical Content Strategy

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 Director, Knowledge Platforms

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

Start the check, free

1What this role really is

This role isn't just about managing a team; it's about shaping how our entire engineering organisation finds, shares, and uses critical technical information. You'll own the vision for all our internal knowledge systems, making sure engineers spend less time searching and more time building. Think of it as building the central nervous system for our engineering brain. You'll be the one making the big calls on platforms, strategy, and how we measure success across the board.

2What you'd actually use

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

Knowledge Base Platforms (e.g., Confluence, Notion, Guru)Strategic

Leading platform selection, defining enterprise governance models, managing vendor relationships, and ensuring platform roadmap aligns with business needs. You're making the big 'build vs. buy' decisions.

Search & Indexing (e.g., Elasticsearch, Algolia)Architect

Designing the enterprise search strategy, integrating multiple data sources into a unified index, and approving schema changes. You're defining how engineers find *everything*.

Scripting & Automation (e.g., Python, Workato, Zapier)Strategic

Architecting the data ingestion and integration framework, making build vs. buy decisions for integration tooling, and overseeing automation strategy for content health and workflows. You're setting the direction for how we automate KM.

Analytics & Visualization (e.g., Tableau, Power BI, Google Analytics)Strategic

Defining the KM metrics framework, presenting insights to leadership linking KM performance to business outcomes (e.g., reduced time-to-information, improved onboarding velocity). You're telling the story with data.

Collaboration & Ticketing (e.g., Jira, Slack, MS Teams)Strategic

Defining the end-to-end workflow for how knowledge is created, linked, and consumed across engineering systems (Jira, Slack, GitHub). You're ensuring our tools work together to support knowledge flow.

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
Strategic Roadmap Definition	No involvement.	Propose tactical improvements within existing roadmap.	Lead specific workstreams within the roadmap, make technical recommendations.
Budget Allocation & Spend	No authority.	Suggest tool purchases up to £1K.	Approve project-specific spend up to £5K, recommend larger investments.
Team Hiring & Performance	Provide feedback on candidates for peer roles.	Interview candidates for junior roles, provide performance feedback to manager.	Lead interviews for junior/mid-level roles, mentor mentees, contribute to performance reviews.
Platform Selection & Architecture	Use existing platforms.	Suggest improvements to existing platform configurations.	Design and implement new features or integrations within existing platforms.

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.

Engineering Time-to-Information Reduction

The average time it takes for an engineer to find a specific piece of technical information (e.g., a runbook, API spec, design decision).

Target · Reduce average time by 20% year-over-year across key engineering teams.

If engineers currently spend 10 minutes searching for a specific service's incident response guide, your goal is to get that down to 8 minutes or less, on average, for a significant portion of common queries.

Reduction in Repetitive Support Queries

The percentage decrease in common 'how-to' or 'where-is' questions directed to engineering teams or support channels (e.g., Slack, Jira Service Desk).

Target · Achieve a 25% reduction in identified repetitive queries within 12 months.

If the 'how do I deploy X service?' question pops up 50 times a month, your team's improved documentation and search should bring that down to 37 or fewer, freeing up senior engineers.

Knowledge Platform ROI

The demonstrable return on investment from our knowledge management programmes and platform spend, quantified in saved engineering hours or reduced operational costs.

Target · Deliver a business case showing >£1M annual saving in engineering hours by end of year one.

By making runbooks more accessible, you might save 100 engineers 2 hours each per month, which at an average cost of £80/hour, is a saving of £192,000 annually. You'll build on these types of calculations.

Knowledge Base Content Health Score

A composite score reflecting the freshness, accuracy, and completeness of critical technical documentation.

Target · Maintain an average content health score of 90% across all critical engineering knowledge spaces.

This means less than 10% of our core API documentation is more than 6 months old, has broken links, or is flagged as incomplete by automated tools.

Engineering Leadership Buy-in & Sponsorship

The level to which engineering VPs and Directors actively champion and contribute to knowledge management initiatives, seeing it as a critical enabler.

Regular participation in KM steering committees, allocation of engineering time for documentation efforts, proactive suggestions for KM improvements, and referencing KM success in broader engineering updates. You'll know you're succeeding when they're asking 'how can we help?' not 'why should we bother?'

Organisational Knowledge Culture Shift

The observable change in how engineers perceive and engage with documentation and knowledge sharing—moving from a 'nice-to-have' to a 'must-do'.

Increased voluntary contributions to the knowledge base, engineers proactively updating their team's documentation, positive feedback in internal surveys about knowledge sharing, and new hires reporting a smooth onboarding experience due to accessible information. It's about seeing documentation become part of the engineering DNA.

Strategic Influence on Engineering Tooling

Your ability to influence the selection and integration of broader engineering tools and platforms to ensure they support effective knowledge capture and discovery.

Being consulted early on new tool procurements (e.g., new observability platforms, code repositories), having your recommendations directly impact tool choices, and seeing knowledge management requirements baked into the evaluation criteria for new systems. You're not just reacting
you're shaping the landscape.

5Would you like it

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

What people enjoy

Making a Tangible Impact on Engineer Productivity

You'll get a real buzz from seeing your team's work directly reduce the time engineers spend searching for answers, or hearing positive feedback about how much easier onboarding has become. Your daily work will involve reviewing metrics, talking to engineers, and seeing the 'before and after' of your strategic initiatives.

An engineer tells you they solved a critical production issue 30% faster because of a runbook your team made easily discoverable, or you see a significant dip in 'how-to' questions in a Slack channel after a new knowledge programme launch.

Building and Leading a High-Performing Team

You'll thrive on mentoring your direct reports, helping them overcome challenges, and celebrating their successes. Your days will include one-on-ones, team planning sessions, and working to remove obstacles so your team can excel. You'll be a coach, a mentor, and a champion.

Seeing a junior engineer you mentored grow into a Senior role and lead their own project, or successfully recruiting a top-tier talent to join your team and seeing them flourish.

Shaping Organisational Strategy and Culture

You're driven by the opportunity to influence how a large engineering organisation operates at a fundamental level. You'll be in strategic discussions with VPs, presenting your vision, and seeing your ideas become company-wide initiatives. This isn't just about tools; it's about changing how people think about knowledge.

Successfully championing a new company-wide standard for documentation, or getting the VP of Engineering to explicitly include knowledge sharing as a key performance indicator for all engineering teams.

What frustrates people

The 'Documentation Janitor' perception: Constantly having to prove that KM is a strategic engineering discipline, not just tidying up wikis.
Evangelism Fatigue: The ongoing effort to convince busy engineers to contribute and maintain documentation, often feeling like you're chasing people.
The Ownership Hot Potato: Getting engineering teams to take genuine ownership of their content's lifecycle, rather than just seeing it as 'your team's problem'.
ROI Justification Loop: Constantly having to quantify the value of KM in 'hard' business terms to justify budget and headcount, when the benefits can feel intangible to some.
Legacy System Archaeology: Inheriting a mess of outdated, unstructured knowledge from previous systems and having to figure out how to migrate or archive it.

What this role does not give you

A purely technical IC role: While you'll stay technical, your focus shifts to strategy, leadership, and programme management, not daily coding.
A 'set it and forget it' environment: Knowledge management is an ongoing, evolving challenge, not a one-off project.
Universal agreement and easy buy-in: You'll need to be comfortable with healthy debate and persistent persuasion.

6Who you work with

This role directly drives the efficiency and effectiveness of our entire engineering organisation. By optimising how knowledge is created, stored, and retrieved, you'll reduce time-to-market for products, lower operational costs through faster incident resolution, and significantly improve the onboarding experience for new hires. Frankly, you're building a competitive advantage by making our engineers smarter and faster.

Inside the business

VP of Engineering
Heads of Product
Engineering Directors and Managers across all teams
HR & Talent Acquisition (for onboarding)
Legal & Compliance (for documentation standards)

Outside the business

Knowledge Base Platform Vendors (e.g., Atlassian, Guru)
Industry peers and KM communities
Consultancy partners for specific projects

7What you need before you start

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

Extensive experience (10+ years) in knowledge management, technical writing, or a related field within a large-scale technical organisation.
Proven track record of leading and managing technical teams, including hiring, performance management, and career development.
Demonstrable experience in defining and executing strategic roadmaps for complex technical systems or programmes.
Strong understanding of modern software development practices and the engineering lifecycle.
Significant experience with at least two major knowledge base platforms and enterprise search solutions.

8What to practise next

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

Advanced RAG (Retrieval-Augmented Generation) Architectures

Simple RAG is becoming standard for internal answer bots. The next step is more sophisticated RAG architectures that can combine information from multiple, disparate sources, handle complex queries, and provide more nuanced, contextual answers. You'll need to understand the strategic implications and technical feasibility.

Multi-modal RAG · Agentic AI for Knowledge Discovery · Fine-tuning & Custom LLM Deployment · Vector Databases & Embedding Models

This month: Read technical papers and industry reports on advanced RAG and agentic AI.
Next quarter: Work with your Lead Engineers to prototype a multi-source RAG system.
Month 6: Evaluate vendor solutions for advanced RAG capabilities and integration with our existing stack.
Month 9: Develop a strategic plan for integrating advanced RAG into our core knowledge platforms.

Quick win: Challenge your team to identify one complex, recurring engineering question that a basic RAG bot struggles with, and brainstorm how an advanced RAG architecture could solve it.

Knowledge Mesh & Federated Search

As organisations grow, centralising all knowledge becomes impractical. The 'knowledge mesh' concept, inspired by data mesh, suggests a federated approach where different teams own and serve their knowledge, connected by a common governance layer and federated search. This is key for scaling KM in large enterprises.

Domain-Oriented Knowledge Ownership · Knowledge as a Product · Federated Search Architecture · Global Knowledge Governance

This quarter: Research the 'knowledge mesh' concept and its application in large tech companies.
Next quarter: Identify a pilot engineering team to experiment with a 'knowledge as a product' approach.
Month 6: Develop a proposal for a federated search architecture that integrates 2-3 key knowledge sources.
Month 9: Present a strategic vision for evolving our knowledge ecosystem towards a knowledge mesh model.

Quick win: Start a conversation with a few engineering managers about how they currently manage their team's critical knowledge and what challenges they face with discoverability across the organisation.

9Staying current once you are in

What people here do to keep up

Regularly attending industry conferences (e.g., KMWorld, Enterprise Search & Discovery) to stay abreast of trends and network with peers.
Participating in online courses or workshops on advanced topics like AI in information retrieval, knowledge graph technologies, or organisational change management.
Contributing to open-source projects or publishing articles on knowledge management best practices.
Mentoring junior professionals in the field, which helps solidify your own expertise and leadership skills.

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: AI Ethics & Governance for Knowledge Systems

As we embed more AI into our knowledge platforms (e.g., for content generation, search relevance, answer bots), understanding the ethical implications, biases, and governance frameworks becomes critical. We can't just deploy AI; we need to deploy it responsibly. This is already a hot topic and will only become more important.

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.

AI Ethics & Governance for Knowledge Systems

As we embed more AI into our knowledge platforms (e.g., for content generation, search relevance, answer bots), understanding the ethical implications, biases, and governance frameworks becomes critical. We can't just deploy AI; we need to deploy it responsibly. This is already a hot topic and will only become more important.

Algorithmic Bias in Search & Recommendations
Data Privacy & Security in LLM Integration
Transparency & Explainability of AI Outputs
Responsible AI Deployment Frameworks

What you’ll use

Skills this role draws on

Technical

Enterprise Information Architecture
Taxonomy & Ontology Governance
Knowledge Graph Strategy
Internal Search Platform Optimisation
Content Lifecycle Management Programme Design

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
Lead/Staff Knowledge Management Engineer
3-5 years in a Lead/Staff role
Skills to master
- Architecting complex KM systems, leading cross-functional projects, mentoring senior engineers, influencing technical direction without direct authority, and demonstrating measurable impact on engineering productivity.
You're ready to move on when
- Successfully designed and implemented a major component of an enterprise knowledge system (e.g., a new search service, a company-wide taxonomy).
- Consistently sought out for technical guidance by other senior engineers and managers.
- Demonstrated ability to present technical strategy to senior leadership and secure buy-in.
- Proven track record of mentoring and developing junior team members.
2
Technical Programme Manager (with KM focus)
5-7 years in a TPM role, with significant KM exposure
Skills to master
- Managing large, complex technical programmes, coordinating multiple engineering teams, stakeholder management at a senior level, defining programme KPIs and reporting on progress, and a deep understanding of knowledge management principles.
You're ready to move on when
- Successfully delivered a multi-year technical programme with significant cross-functional dependencies.
- Demonstrated strong leadership in ambiguous situations, driving clarity and alignment.
- Built strong relationships with engineering VPs and Directors, earning their trust and respect.
- Developed a strong technical understanding of knowledge systems and their impact on engineering productivity.
3
Head of Technical Content / Documentation
5-8 years leading a technical content team
Skills to master
- Leading large teams of technical writers, defining content strategy, managing content lifecycle, implementing content management systems, and demonstrating the business value of high-quality documentation. You'd need to layer on more technical systems architecture and engineering leadership experience.
You're ready to move on when
- Successfully scaled a technical documentation function for a large engineering organisation.
- Implemented new content management systems and workflows that improved efficiency and quality.
- Demonstrated ability to recruit, manage, and develop a team of technical content professionals.
- Proven ability to influence product and engineering teams on documentation standards and practices.

11Where this role leads

The long view:This role is a springboard for significant leadership opportunities. We're looking for someone who doesn't just want to manage a team, but who wants to fundamentally change how a large organisation works, making it smarter, faster, and more connected. The impact you'll have here will set you up for a truly impactful career.

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 Director, Knowledge Platforms 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:

Manage knowledge in an organisationLevel 5

Applied to your work in Director, Knowledge Platforms

This unit aims to provide learners with an understanding of knowledge management principles, strategies, and the role of technology within organisations. Upon completion, learners will be able to identify, assess, and effectively manage knowledge assets to support organisational objectives.

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 Director, Knowledge Platforms

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.

Engineering Time-to-Information ReductionThe average time it takes for an engineer to find a specific piece of technical information (e.g., a runbook, API spec, design decision).If engineers currently spend 10 minutes searching for a specific service's incident response guide, your goal is to get that down to 8 minutes or less, on average, for a significant portion of common queries.Reduce average time by 20% year-over-year across key engineering teams.
Reduction in Repetitive Support QueriesThe percentage decrease in common 'how-to' or 'where-is' questions directed to engineering teams or support channels (e.g., Slack, Jira Service Desk).If the 'how do I deploy X service?' question pops up 50 times a month, your team's improved documentation and search should bring that down to 37 or fewer, freeing up senior engineers.Achieve a 25% reduction in identified repetitive queries within 12 months.
Knowledge Platform ROIThe demonstrable return on investment from our knowledge management programmes and platform spend, quantified in saved engineering hours or reduced operational costs.By making runbooks more accessible, you might save 100 engineers 2 hours each per month, which at an average cost of £80/hour, is a saving of £192,000 annually. You'll build on these types of calculations.Deliver a business case showing >£1M annual saving in engineering hours by end of year one.
Knowledge Base Content Health ScoreA composite score reflecting the freshness, accuracy, and completeness of critical technical documentation.This means less than 10% of our core API documentation is more than 6 months old, has broken links, or is flagged as incomplete by automated tools.Maintain an average content health score of 90% across all critical engineering knowledge spaces.

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 Director, Knowledge Platforms to VP, Engineering Enablement, and whatever you decide comes after.

Level 7 · in progressAI Fluency→ VP, Engineering Enablement→ your design

Where this takes you

This role is a springboard for significant leadership opportunities. We're looking for someone who doesn't just want to manage a team, but who wants to fundamentally change how a large organisation works, making it smarter, faster, and more connected. The impact you'll have here will set you up for a truly impactful career.

See Your Progress GrowIllustration

Director, Knowledge Platforms

Enterprise Information Architecture
Taxonomy & Ontology Governance
Knowledge Graph Strategy
Internal Search Platform Optimisation
Content Lifecycle Management Programme Design

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

Director, Knowledge Platforms is a start, not a ceiling. Each step below asks for new skills and hands back more autonomy.

VP, Engineering Enablement
3-5 years as Director, Knowledge Platforms
Level 7 (C-Suite equivalent for a large function)
- Holistic developer experience strategy (covering tools, training, onboarding, and knowledge).
- Organisational design and scaling large, diverse technical teams.
- Strategic vendor management for all engineering enablement tools.
- M&A due diligence and integration for enablement functions.
Director, Product Management (Platform/Developer Tools)
3-5 years as Director, Knowledge Platforms
Level 6/7 (depending on scope)
- Product lifecycle management from conception to end-of-life.
- User research and usability testing for platform products.
- API design and developer experience for platform offerings.
- Competitive analysis and market positioning for developer tools.

Working with AI on the job

Working with AI

Where AI is starting to help

As a Director, your time is precious. AI isn't just for individual contributors; it's a powerful strategic tool that can amplify your team's impact and free you up for high-level thinking. Imagine if your team could deliver more, faster, with less manual effort. That's the promise of AI in knowledge management.

In this role, AI won't replace your strategic brain, but it will certainly extend it. You'll be thinking about how to embed AI into your team's workflows and our knowledge platforms to drive efficiency, improve content quality, and accelerate discovery across the entire engineering organisation. It's about enabling your team to do more with less, and making smarter decisions faster.

AI-Powered Content Governance

Imagine AI scanning all our technical documentation, automatically flagging stale content, suggesting updates based on recent code changes, and identifying compliance risks. You'll define the rules, and AI will do the heavy lifting, ensuring content health at scale without your team drowning in audits. This frees up your team for more complex, impactful work.

Predictive Knowledge Gap Analysis

Instead of reactive content creation, use AI to proactively identify what knowledge engineers will need *before* they even ask. AI can analyse project plans, code repositories, and support tickets to predict future knowledge gaps, allowing your team to create content strategically. This means your team is always a step ahead, not just catching up.

Enterprise-Wide Answer Bots & RAG

You'll oversee the deployment of sophisticated, context-aware AI bots that don't just link to documents, but synthesise direct answers from our entire knowledge base. This significantly reduces the 'noise' of repetitive questions in Slack and Jira, allowing your engineering teams to focus on building, not answering basic queries. It's about making knowledge instantly accessible, wherever engineers work.

Automated Strategic Reporting

Spend less time manually compiling reports for leadership. AI can aggregate data from various knowledge platforms, analyse trends, and even draft initial summaries of KM performance, highlighting key insights and areas for strategic focus. This means you get to the 'so what?' faster, and spend more time on strategy, less on data wrangling.

Common questions

How do you become a Director, Knowledge Platforms?

Common routes in include Lead/Staff Knowledge Management Engineer (3-5 years in a Lead/Staff role), Technical Programme Manager (with KM focus) (5-7 years in a TPM role, with significant KM exposure) and Head of Technical Content / Documentation (5-8 years leading a technical content team). Times vary with prior experience.

Where can a Director, Knowledge Platforms progress to?

This role can lead on to VP, Engineering Enablement (3-5 years as Director, Knowledge Platforms) and Director, Product Management (Platform/Developer Tools) (3-5 years as Director, Knowledge Platforms), depending on the skills you build.

What level is a Director, Knowledge Platforms in the UK?

This role aligns to RQF Level 7 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 Director, Knowledge Platforms?

Increasingly, AI Ethics & Governance for Knowledge Systems. 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 Director, Knowledge Platforms, 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 3 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 Director, Knowledge Platforms: 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 of nine units, ninety credits, each one an Ofqual-regulated unit the learner can tick or untick before starting. — 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 7

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

Other roles in Technical roles

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

If you leave this industry

The skills you'll hone in this role—strategic thinking, technical leadership, organisational change management, and building scalable information systems—are highly transferable. You could move into similar Director or VP roles in other large tech companies, or even transition into consulting, focusing on enterprise knowledge strategy or developer enablement.

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.

Director, Knowledge Platforms

What's rising in its place

AI Ethics & Governance for Knowledge Systems

Skills this role draws on

Technical

How you actually get there, here

Lead/Staff Knowledge Management Engineer

Technical Programme Manager (with KM focus)

Head of Technical Content / Documentation

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

VP, Engineering Enablement

Director, Product Management (Platform/Developer Tools)

Where AI is starting to help

AI-Powered Content Governance

Predictive Knowledge Gap Analysis

Enterprise-Wide Answer Bots & RAG

Automated Strategic Reporting

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.