How to Become a Technical Writer: Degree, Steps & Salary (2026)

Updated August 12, 2026 BLS data College Scorecard On this page

Key takeaway: Technical writing is an unlicensed profession with no required exam or certification -- a bachelor's degree is the common hiring expectation, but what decides the hire is a portfolio of documentation samples plus demonstrated fluency in a subject domain and its toolchain. Technical writers had a median annual wage of $90,390 (Bureau of Labor Statistics, May 2025 OEWS national median).

Technical writing sits at an unusual intersection: it pays like a technical role, it is hired like a creative one, and it is regulated like neither. There is no license, no board, and no required credential. The gate is a portfolio, and the reason the pay sits where it does is that the job requires two competencies at once – writing precisely, and understanding a technical subject well enough to be trusted to explain it.

That combination is also what makes the entry path flexible. People arrive at this work from English and communications degrees, from engineering and computer science, from science labs, and from support and quality-assurance roles inside the companies they end up documenting for. This guide covers the path in order, and is explicit about which steps are genuine requirements and which are conventions.

For the wider view of the field, start with the Online Technical Communication Degrees guide.

Step-by-step: how to become a technical writer

Step 1: Earn a bachelor’s degree

A bachelor’s degree is the standard hiring expectation, but the field of study is genuinely open. Three routes are all common:

  • A bachelor’s in technical communication or professional writing. The most direct route, and the only one that teaches documentation structure, information architecture, audience analysis, usability testing, and the publishing toolchain as an explicit curriculum.
  • A writing-centered degree in English, communications, or rhetoric, paired with technical coursework or self-taught domain knowledge.
  • A technical degree in engineering, computer science, or a physical or life science, paired with demonstrated writing ability. Employers documenting complex products often prefer this direction, because subject knowledge is generally harder to teach on the job than writing conventions are.

If you take one of the latter two routes, close the gap deliberately. A technical writer who cannot read the source material is limited to editing what an engineer already drafted, and that is a lower-paid version of the job.

Step 2: Choose a domain and learn it seriously

Technical writing is not one market. Software documentation, hardware and manufacturing, medical devices and pharmaceuticals, aerospace and defense, and finance each have distinct conventions, regulatory constraints, and pay bands. Pick a direction early, because domain depth is what separates a generalist from a specialist.

Some domains carry real external constraints worth knowing before you enter them. Medical device and pharmaceutical documentation is written under FDA requirements. Aerospace and defense documentation often follows specifications such as S1000D and may require security clearance eligibility for a given role. These are employer and regulatory conditions rather than personal credentials, but they shape who gets hired.

Step 3: Learn the toolchain

Nobody certifies you on these, and every job posting lists them. The specific stack varies by domain:

  • Structured authoring and help systems. MadCap Flare, Adobe FrameMaker, Paligo, or Author-it, and the DITA XML standard in structured environments.
  • Docs-as-code. Markdown, Git and GitHub, static site generators, and continuous-integration publishing pipelines. This is now the default in most software documentation teams.
  • API documentation. OpenAPI and Swagger specifications, plus enough familiarity with a programming language to read code and test the examples you publish.
  • Graphics and content management. Snagit or Camtasia for screenshots and screencasts, diagramming tools, and a component content management system in larger organizations.

You can learn most of this outside a classroom. Building a small documentation site in Git and publishing it is both practice and a portfolio piece.

Step 4: Build a portfolio

The portfolio is the closest thing this field has to a credential, and it is what hiring managers open first. Three to five substantial samples is a workable target, each showing a different documentation type: a procedural how-to, a conceptual overview, API reference material, a troubleshooting guide, or a release note set.

If you have no professional samples yet, produce them:

  • Document an open-source project. Open-source maintainers routinely accept documentation contributions, and the result is public, real, and reviewed by someone else.
  • Rewrite bad documentation. Take a genuinely confusing manual or help page, rewrite it, and include a short note on what was wrong and what you changed. That commentary shows judgment, which matters as much as the prose.
  • Internships and course projects. Technical communication programs often build client projects into the curriculum, which produces reviewed samples with a real audience.

Confidentiality is a practical constraint later in your career: much professional documentation is proprietary and cannot be shared. Keep sanitized or publicly releasable samples as you go rather than reconstructing a portfolio under deadline.

Step 5: Consider certification, but know it is optional

There is no required certification. The most recognized voluntary credential is the Certified Professional Technical Communicator (CPTC), offered by the Society for Technical Communication at Foundation and Practitioner levels, which involves an exam based on a defined body of knowledge and, at the higher level, documented professional experience.

Treat it as a supplement rather than an entry ticket. It can add credibility for career changers without a related degree or a deep portfolio, and some government and contracting environments value it. It does not substitute for writing samples, and no employer that would reject your portfolio will hire you for holding it. Domain-specific technical certifications – a cloud platform credential for someone documenting infrastructure, for example – often carry more hiring weight than writing certifications do.

Step 6: Take an entry role

Entry titles include technical writer, associate or junior technical writer, documentation specialist, and content developer. Two lateral routes into the job are extremely common and worth naming, because they are often faster than applying cold: moving from a technical support role into documenting the product you already support, or moving from quality assurance into documentation, since both jobs already require reading specifications and describing behavior precisely.

Contract and staffing-agency roles are a normal part of this field, particularly in aerospace, defense, and pharmaceuticals, and are a legitimate way to accumulate domain experience. From there the ladder runs toward senior technical writer, lead or documentation manager, information architect, and adjacent specializations such as content strategy, user experience writing, or developer relations. See what you can do with a technical communication degree for the broader map.

What degree do you need to be a technical writer?

A bachelor’s degree is the common expectation, and the subject is negotiable. A bachelor’s in technical communication is the most direct route because it teaches the discipline explicitly rather than leaving you to reverse-engineer it. A writing degree plus technical fluency, or a technical degree plus demonstrated writing skill, both work and both are well represented in the field.

A master’s in technical communication is most useful in two situations: as a career-change route for someone with a bachelor’s in an unrelated field who wants structured training and a portfolio, and as a move toward information architecture, content strategy, documentation management, or teaching. It is not expected for standard technical writing roles.

Graduate and undergraduate certificates in technical communication are a lighter-weight option for people who already hold a degree and need the discipline-specific coursework plus portfolio pieces rather than a second full credential.

How much do technical writers make?

Technical writers had a median annual wage of $90,390 (Bureau of Labor Statistics, May 2025 OEWS national median). That figure is the midpoint of the national distribution and is notably high among writing occupations – for comparison within the same source, editors had a median annual wage of $77,920 and news analysts, reporters, and journalists had a median annual wage of $62,200 (Bureau of Labor Statistics, May 2025 OEWS national medians).

The premium reflects the dual requirement. You are paid for the technical understanding as much as for the writing, which is why domain choice affects earnings so directly: documentation for regulated medical devices, aerospace systems, or developer platforms typically pays differently than general consumer documentation. Employer type, industry, and geography drive the spread more than the job title does. To weigh the cost of the credential against these figures, see is a technical communication degree worth it.

How long does it take to become a technical writer?

There is no licensure or supervised-hours requirement, so the timeline is set by the degree and the portfolio.

  • Standard route: about four years – a bachelor’s degree, with the portfolio built through course projects, internships, and open-source contributions along the way. Hiring directly out of the degree is common when the portfolio is ready at graduation.
  • Career changer with a bachelor’s in another field: roughly six months to two years. A certificate program plus a deliberate portfolio push can be done in six months to a year; a master’s typically runs one and a half to two years. If you are already inside a technical organization in support, QA, or engineering, the internal move can happen faster than either.
  • Adding the optional CPTC: weeks to months of preparation, layered on top of any of the above rather than extending the path.

These are ranges. The variable that moves the date most is not coursework but how quickly you assemble three to five samples someone else has reviewed.

Frequently asked questions

What degree do you need to be a technical writer?

A bachelor’s degree is the common hiring expectation, but the field is open. A bachelor’s in technical communication or professional writing is the most direct route. A writing degree such as English or communications paired with technical knowledge works, and so does a technical degree in engineering, computer science, or a science paired with demonstrated writing ability.

How long does it take to become a technical writer?

About four years on the standard route through a bachelor’s degree, with the portfolio built during it. Career changers who already hold a bachelor’s typically need six months to two years, depending on whether they use a certificate, a master’s, or an internal move from a support, QA, or engineering role.

How much do technical writers make?

Technical writers had a median annual wage of $90,390 (Bureau of Labor Statistics, May 2025 OEWS national median). That is above other writing occupations in the same data – editors had a median of $77,920 and news analysts, reporters, and journalists $62,200 – reflecting the technical subject knowledge the role requires alongside the writing.

Do you need a degree to be a technical writer?

Not legally, and not always in practice. Technical writing is unlicensed, and people move into it from support, quality assurance, and engineering roles without a writing degree, on the strength of domain knowledge and work samples. Most posted positions do list a bachelor’s degree as a requirement, so entering without one usually means moving internally at a company that already knows your work.

Do technical writers need certification?

No. There is no required certification. The Society for Technical Communication offers the voluntary Certified Professional Technical Communicator (CPTC) credential at Foundation and Practitioner levels, which can add credibility for career changers or in some government and contracting environments. It does not replace a portfolio, and domain-specific technical certifications often carry more hiring weight.

What should be in a technical writing portfolio?

Three to five substantial samples covering different documentation types – a procedural how-to, a conceptual overview, API reference material, a troubleshooting guide, or release notes. If you have no professional work yet, contribute documentation to an open-source project or rewrite a genuinely confusing manual and include a short note explaining what was wrong and what you changed.

Wage figures on this page are national medians from the U.S. Bureau of Labor Statistics Occupational Employment and Wage Statistics program, May 2025. Individual outcomes vary by industry, domain, employer, and experience.

Data verified: August 12, 2026. Salary, employment, and tuition figures on this page are sourced from the U.S. Bureau of Labor Statistics (OEWS May 2025; Employment Projections 2024–2034) and the U.S. Department of Education College Scorecard (2023 cohort). The source agency and data year are cited inline with every statistic.

Back to Online Technical Communication Degrees: Programs & Careers (2026)