Keep the Title. Improve the Job Description.
Every few years, our profession seems to get a new name.
Technical Writer. Technical Author. Information Developer. Documentation Engineer. Content Designer. And now, more recently, Context Engineer.
It got me thinking…
Are we really solving a problem by changing the job title? Or are we just making it harder for employers and candidates to understand what the role actually is?
We’ve all seen organisations replace well-understood job titles with trendier alternatives. Sometimes it’s because the role has evolved. Sometimes it’s an attempt to sound more modern or attract talent. Whatever the reason, the result is often the same: people spend more time trying to understand the title than the job itself.
Technical Author shouldn’t fall into the same trap.
A profession can evolve without changing its name
Our profession has never stood still.
We’ve gone from printed manuals to online help systems. From static PDFs to interactive knowledge bases. From documenting software features to designing information that improves the customer experience.
Now AI is changing the way we work again.
We’re hearing more about Context Engineering—creating information that’s structured, trustworthy and easy for both people and AI to understand, retrieve and use.
Those are valuable skills.
But are they really a new profession?
I don’t think so.
The job title tells me what you are. The job description tells me what you do.
If I’m hiring a Technical Author, I already understand the profession.
What I need to know is what your organisation expects from that person.
Do you need someone to:
- Create API documentation?
- Design an information architecture?
- Build and maintain a knowledge base?
- Develop metadata and taxonomies?
- Structure content for AI-assisted retrieval?
- Manage a MadCap Flare project?
- Work closely with developers and SMEs?
- Produce video tutorials?
- Define documentation standards and strategy?
Those expectations belong in the job description—not the job title.
We’ve always had different types of Technical Authors
One of the biggest misconceptions about our profession is that there’s only one type of Technical Author.
There isn’t.
Some specialise in software documentation.
Others work in healthcare, aerospace, manufacturing, finance or defence.
Some focus on APIs.
Others specialise in UX writing, knowledge management, information architecture or regulatory documentation.
AI is simply introducing another area of expertise.
It doesn’t suddenly make Technical Author an outdated profession.
Better job descriptions create better hiring
One of the biggest challenges in our industry is that employers often struggle to find the right person.
I sometimes wonder if we’re making that harder ourselves.
Every new job title creates another search term.
Another interpretation.
Another opportunity for misunderstanding.
Candidates aren’t sure whether they’re qualified because they’ve never seen the title before.
Recruiters struggle to compare similar roles across organisations.
Hiring managers receive applications from people whose expectations don’t match the job.
Changing the title doesn’t solve that problem.
Writing a clearer job description does.
For example, instead of advertising for a Context Engineer, why not advertise for:
Technical Author (AI Documentation & Knowledge Management)
Then explain exactly what you’re looking for.
- Experience creating AI-friendly documentation.
- Strong information architecture skills.
- Knowledge of metadata and taxonomy.
- Experience with retrieval-augmented generation (RAG) concepts.
- Single-source documentation experience.
- Confidence working with AI-assisted authoring tools.
Now everyone understands both the profession and the specialism.
Clarity over buzzwords
I’m not arguing that our profession shouldn’t evolve.
It absolutely should.
AI is changing how we create, manage and deliver information, and Technical Authors should embrace the opportunities that come with it.
What I’m questioning is whether changing the job title actually helps anyone.
Technical Author is already a recognised profession. It has decades of history behind it and a shared understanding across industries.
Let’s build on that foundation.
Keep the title.
Improve the job description.
Because employers don’t hire job titles.
They hire skills.
And clarity will always be more valuable than buzzwords.