The End of the Technical Writer? 2.0

Person typing on laptop with plant.

For roughly six years, I have been keeping track of the number of technical writer job postings on—the largest job aggregator website in the United States. With the exception of a brief surge in technical writing job postings in late 2015/early 2016, there has been a steady decline in technical writer job postings. Despite the strong economy, an overall declining unemployment rate, and the fact that remains a top job aggregator website, this trend continues to this day.


Tech writer job listings on Indeed graph.


DITA Experience and Technical Writing 

The primary reason for checking the number of job postings on is to get a better sense as to the types of job skills that technical writer postings are looking for—particularly those that require knowledge or experience with DITA. If I do a search on “DITA” alone, I come up with many more job listings that are related to but are not exactly the traditional technical writer-type of job. The sense I have is that, at least when it comes to DITA, “technical writer” may not be the most popular job title associated with this skillset.

While I have been claiming at a few conferences that DITA is associated with other job titles in addition to “technical writer”—justified by the many more job postings available on when I remove “technical writer” out of my search—I thought I would do a more thorough investigation to see whether my hunch was correct.

Another project I have undertaken for the past several years is keeping track of the LinkedIn posts of those who self-report they use DITA as part of their job. I monitor about 1,500 people to get a better sense of trends in the market, who is using what tools and CCMSs, along with how and why their firm is using DITA.

But in this case, I did a sort on all jobs that had “technical writer” or at least “writer” as part of their job title. This list includes people with the following job titles in addition to “technical writer:”

  • Advisory Technical Writer
  • Associate Technical Writer
  • Content Writer
  • Contract Technical Writer
  • Engineering Writer
  • Lead Technical Writer
  • Manager, Technical Writer
  • Principal Technical Writer
  • Project Engineer, Technical writer
  • Senior Programmer Writer
  • Senior Technical Writer
  • Staff Technical Writer
  • Technical Writer II
  • Technical Writer III
  • Technical Writer IV
  • Technical Writing Consultant
  • Technical Writing Intern
  • Technical Writing Manager

I discovered that there were 589 people who were using DITA that had some variant of either “technical writer” or “writer” as part of their job title. As you can see from the list, the generic term “writer” seems to be used primarily to denote different levels of seniority, ranging from interns to senior and staff technical writers, along with consultants and those who are either working within an engineering group or are engineers themselves.


Non-Technical Writers Using DITA 

The remaining group on the list was comprised of those whose job titles implied that there are many associated jobs relating to working with structured content and DITA. In all, there were 891 people who had jobs that included working with DITA that were distinctly different than technical writers.

That means that roughly 66% of the roughly 1,500 people who claim to be using DITA are not employed as traditional technical writers.

Here is a representative sample of job titles from the second, non-technical writer list:

  • Analyst II Technical Documentation
  • Ant Build Specialist
  • Applications Engineer
  • Associate Technical Content Developer
  • Business Analyst and Technical Author
  • Chief Information Architect, UX Analyst
  • Consulting Content Strategist
  • Content Architect
  • Content Developer
  • Content Management Specialist
  • Content Strategist
  • Customer Documentation Specialist
  • Director of Documentation
  • Director of Information Experience
  • Director of Knowledge & Training
  • Director, Documentation & User Assistance
  • Director, Product Documentation
  • Director, Technical Publications and Training
  • DITA Architect
  • DITA Content Strategist
  • DITA Information Architect
  • DITA Migration Specialist
  • DITA Toolsmith
  • Documentation Architect
  • Documentation Manager
  • Engineer III – Information Development Technologist
  • Head of the Search and Technologies Documentation Team
  • Information Architect
  • Information Developer
  • Information Experience Manager
  • Knowledge Architect
  • Lead Information Developer
  • Localization Program Manager
  • Manager Technical Communications
  • Manager, Technical Communication
  • Manager, XML CMS and L10n Systems
  • Principal Content Experience Developer
  • Principal Information Developer
  • Product Architect
  • Project Manager and Documentation Engineer
  • Senior Content Developer
  • Senior Content Strategist
  • Senior Documentation Tools Developer
  • Senior Information Developer
  • Senior Software Engineer
  • Staff Information Architect
  • Team Leader Technical Documentation
  • Technical Communications Specialist
  • Technical Leader, Technical Communications
  • Technical Publications Manager
  • Tools Developer
  • User Assistance Development Architect
  • UX Designer
  • XML/DITA Coordinator

What is evident to me is that there are three main positions associated with DITA job titles which are not technical writers: managers, those who assist with the publication process, and those who are structuring content or providing some additional value to the output process.

There are many managerial positions that appear in this list, (e.g. director of documentation, documentation manager, manager technical communications, team leader technical documentation, etc.), though it is worth pointing out that there is some overlap with the technical writer list (e.g. manager, technical writer; project engineer, technical writer; technical writing manager). I find it intriguing that so many senior people are working with DITA, though evidence shows that they are primarily (though not exclusively) overseeing the process of using DITA within their publication process rather than working with writing DITA content themselves.

There are still more positions that imply different skills are being used alongside experience with DITA. The majority of people who are working with DITA are not just writing content (if they are writing content at all) but are also providing support for the publication process (e.g. Ant build specialist, applications engineer, DITA toolsmith, senior documentation tools developer). To me, this implies that larger companies that are using DITA. For larger firms, having people work full-time in these roles is cost-effective.

An interesting trend that appeared was the significant number of job titles that were closely allied to technical writer, like “information developer,” “documentation specialist,” and “content developer.” These might point the way towards new, alternate titles for jobs which may be functionally similar to technical writer. You have to admit that these positions have more pizzazz than the relatively-dowdy technical writer, and may better position their holders for career advancement in other areas.

Within the non-technical writer category, job titles like “content strategist,” “information designer,” and “information architect” come up a lot. This suggests the ability to effectively structure content is a specialist role. This makes sense, since to be able to make DITA cost-effective for a company, the ability to effectively reuse content and to devise a plan to ensure that happens consistently among writing teams is worthy of a dedicated person to handle that role.

Search engines have played a fundamental role in the shift of the customer journey. They often lead users to technical content because it closely matches what they are looking for.

Technical documentation can do a lot to enhance the perception of the company and the quality of its products/branding.  Most importantly, it amplifies the influence it has on the initial decision to purchase a product. It should therefore be considered important from an SEO perspective, and work hand in hand with marketing, to satisfy customers and enhance CX (customer experience).

Despite the scarcity of its SEO, technical documentation, and more specifically, DITA topic-based information, already appears to be in line with what SEO experts advocate marketers do.

Benefits resulting from crafting an SEO strategy for technical documentation include writing better, more find-able documentation with a focus on information users are looking for. It also improves and enhances the overall customer experience with an efficient and lasting impact on the company’s bottom-line.

What can be concluded?

The sample size may not be big enough to speak to the results of the technical writing community as a whole. Within the niche that is DITA-based technical publications, however, it is safe to say that more people are working outside of the traditional technical writer role. This in part explains why we are experiencing a drop in the total number of technical writer jobs within the U.S., as there are an increasing amount of jobs in related fields.

I don’t think we are seeing the end of the technical writer, but more the diversification of that role as people are finding positions that compliment and provide additional value to the process of efficiently producing structured content.


Keith Schengili-Roberts
Senior DITA Content Strategist at IXIASOFT

Keith is IXISOFT’s Senior DITA Content Strategist. He is also an award-winning lecturer on Information Architecture at the University of Toronto’s School for Continuing Education. He is the Chair of the OASIS DITA Adoption Committee, regularly presents at conferences, and works with customers. Keith continuously researches how DITA is being used and then shares those results with the community. Keith’s popular industry blog has become a focal point on DITA resources.

Sign up to our newsletter now to keep up with the techcomm industry and IXIASOFT’s latest updates!