Just Write Click

Technical writing with Continuous Integration and docs-as-code

  • JustWriteClick
  • Contact
  • Books by Anne Gentle
  • Introducing Docs Like Code
You are here: Home / work / Technical Writers in Demand, Mix Experience and Education Before Applying

December 9, 2008 by annegentle

Technical Writers in Demand, Mix Experience and Education Before Applying

This post was contributed by Kelly Kilpatrick, who writes on the subject of online colleges and universities. She invites your feedback at kellykilpatrick24 at gmail dot com.

According to the Bureau of Labor Statistics, there were 49,000 technical writers in the United States last year. They also say job prospects are best for technical writers over all other types of writers. So, why are so many people just coming out of college with technical communications degrees having a tough time landing that first job? It can be completely frustrating for both new graduates and prospective employers who have vacancies and feel the talent just isn’t there.

Let’s look at some of the skills and education required for technical writers and then examine why entry-level technical writing jobs are few and far between.

Some of these include:

A degree or certification in technical communications.

Often a background in another technical field such as engineering or science and may specialize in a technical area where they have expertise.

An ability to create, assimilate and convey technical material in a concise and effective manner.

In technical writing, even more than in other fields and industries, you need experience to get the job. A technical communications degree is a very good start but many companies (often led by engineers) doing this sort of hiring see writers as ill-equipped for the job and seek a more technical background to “prove” they can handle the job. Writing skills aren’t enough and even knowing the lingo and the software used are often not enough. So, what’s a new technical writer to do?

Here are some ideas:

If you can, take some engineering or computer science classes. If you’ve already graduated, take some continuing education classes to bolster your knowledge.

Offer to do a small project on spec (unpaid) for a company, or seek out volunteer work, such as documentation for an open source software project. You get a portfolio piece if nothing else and the company or organization for whom you did it may be willing to keep you around if they like what you’ve done.

If you’re a more creative type, learn how engineers work and think. They are very linear, literal and see few gray areas in anything. If you can learn how to talk to them in their language, you’ll be more successful.

Like anyone starting a new profession, you’ll need to take smaller or lower-paying jobs in the beginning as you build your portfolio and gain experience. This takes time, but if you decide you can stick it out, you’ll find a wealth of opportunities in a field that’s got nowhere to go but up.

Related

Filed Under: work Tagged With: education, jobs, online education, portfolio, technical writer jobs, technical writing, technical writing career, techpubs

More reading

Bubble graph showing sources of developer support data

I’ve been thinking a lot about developer support at Cisco recently, especially for the way the world works today with multiple cloud providers. This post is a re-publish of my talk from over five years ago, but the techniques and tools for listening and helping others are still true today. At Rackspace, we watched several […]

Cisco DevNet is our developer program for outreach, education, and tools for developers at Cisco. From the beginning, the team has had a vision for how to run a developer program. Customers are first, and the team implements what Cisco customers need for automation, configuration, and deployment of our various offerings. Plus, the DevNet team […]

I had a great talk with Ellis Pratt of Cherryleaf Technical Writing consulting last week. Here are the show notes, full of links to all the topics we covered. Podcasts are great fun to listen to and participate in, if a bit nerve-wracking to think on your feet and make sure you answer questions succinctly […]

At the beginning of this year, I worked hard to summarize my thoughts on API documentation, continuous publishing, and technical accuracy for developer documentation. The result is an article on InfoQ.com, edited by Deepak Nadig, who also was forward-thinking in having me speak to a few teams at Intuit about API documentation coupled with code. Always […]

Recently on Just Write Click

  • A Flight of Static Site Generators: Sampling the Best for Documentation
  • Try a GPT about “Docs Like Code” to ask questions
  • Discipline and Diplomacy: Docs in the Open
  • Let’s Find Out: When Do Static Site Generators Do Rendering?
  • GitHub for Managing Tech Docs

Just Write Click in your Inbox

Enter your email address to subscribe to Just Write Click and receive notifications of new posts by email.

Read More

  • Privacy Policy
  • About Anne Gentle, developer experience expert
  • Books by Anne Gentle
    • Conversation and Community
    • Docs Like Code, a Book for Developers and Tech Writers
  • Woman in Tech Speaker Profile
  • Contact

Books

  • JustWriteClick
  • Contact
  • Books by Anne Gentle
  • Introducing Docs Like Code

Copyright © 2025 · WordPress · Log in