Getting Started in Technical Writing¶

Breaking into technical writing requires demonstrating that you can explain complex topics clearly. Whether transitioning from another field or starting fresh, here's how to begin.

Do You Have What It Takes?¶

Self-Assessment¶

Answer honestly:

Common Backgrounds¶

Technical writers come from many fields:

Technical Backgrounds: - Software development - Quality assurance - Support/customer service - System administration

Writing Backgrounds: - Journalism - English/communications - Marketing - Education

Other Backgrounds: - Subject matter expertise - Library science - Translation - Project management

Building Foundation Skills¶

Writing Skills¶

Develop clear writing:

1. Study good documentation
2. Read docs you admire
3. Analyze what makes them effective

4. Note structure and style

5. Practice regularly

6. Write explanations of processes
7. Document things you learn

8. Seek feedback on your writing

9. Learn technical writing principles

10. Audience analysis
11. Task-based writing
12. Plain language
13. Information design

Technical Skills¶

Build technical competence:

## Technical Foundations

### Essential
- Basic command line usage
- Version control (Git)
- Markdown formatting
- One programming language (basics)

### Valuable
- API concepts (REST, endpoints)
- Static site generators
- HTML/CSS basics
- Database concepts

### Advanced
- Docs as code workflows
- CI/CD basics
- Scripting for automation
- Specific domain knowledge

Tool Proficiency¶

Learn common tools:

Creating Your First Samples¶

Write About What You Know¶

Choose accessible topics:

• Software you use daily
• Processes you've learned
• Technical hobbies
• Professional knowledge

Sample Ideas¶

Tutorial: Write a step-by-step guide for installing or using software.

How-to Guide: Document a process you do regularly.

Explanation: Explain a technical concept to a beginner.

API Documentation: Document a public API (even unofficially).

Improvement: Rewrite poor documentation you've encountered.

Sample Structure¶

## Sample Project: Installation Guide

### Target
Installation guide for [open-source tool]

### Components
1. Overview and prerequisites
2. Installation steps (multiple platforms)
3. Verification procedure
4. Troubleshooting common issues

### Process
1. Install the tool yourself
2. Note every step and decision
3. Write clear instructions
4. Test with someone else
5. Refine based on feedback

Getting Experience¶

Volunteer Opportunities¶

Open Source Projects: - Many need documentation help - Real experience with real users - Portfolio-worthy contributions - Community connections

Finding projects: - Good First Issues on GitHub - Write the Docs community - Project documentation requests

Nonprofits: - Local organizations need help - Variety of documentation types - Meaningful contribution - References and experience

Internships and Entry Positions¶

Internships: - Structured learning - Mentorship - Real experience - Path to full-time

Entry-Level Roles: - Junior Technical Writer - Documentation Specialist - Technical Writing Associate - Content Developer

Adjacent Roles: - Technical Support (writing knowledge base) - QA (writing test documentation) - Customer Success (user guides)

Creating Opportunities¶

Internal Transfer: If employed, document things at work: - Processes your team uses - Knowledge your team needs - Tools your team relies on

Show value, then propose role change.

Freelance Start: - Small projects build experience - Upwork, Fiverr, LinkedIn - Network referrals - Start small, grow portfolio

Education Options¶

Formal Education¶

Degrees: - Technical Communication degree - English with technical focus - Computer Science - Any field + portfolio

Certificates: - University certificates - Online certifications - Professional certifications (STC)

Self-Study¶

Online Courses: - Google Technical Writing courses (free) - Coursera/LinkedIn Learning - Technical writing bootcamps - Platform-specific tutorials

Books: - The Product is Docs by Splunk team - Docs for Developers by Bhatti et al. - Every Page is Page One by Baker - Style guides (Google, Microsoft)

Practice: - Write regularly - Get feedback - Iterate and improve - Build portfolio

Breaking In: Step by Step¶

Your First Six Months¶

## Month 1-2: Foundation
- [ ] Complete Google Technical Writing courses
- [ ] Learn Markdown thoroughly
- [ ] Set up Git and GitHub account
- [ ] Read 3 documentation style guides
- [ ] Analyze 5 excellent documentation sites

## Month 3-4: Building
- [ ] Create first writing sample
- [ ] Contribute to open source docs
- [ ] Learn a static site generator
- [ ] Start building portfolio site
- [ ] Join Write the Docs community

## Month 5-6: Positioning
- [ ] Create 3-5 portfolio pieces
- [ ] Optimize LinkedIn profile
- [ ] Start applying to positions
- [ ] Network with technical writers
- [ ] Continue learning and writing

Common Challenges¶

"I don't have experience." Create experience through samples and volunteering.

"I'm not technical enough." Start with what you know. Technical skills can be learned.

"I need a degree." Many successful technical writers don't have specialized degrees.

"There are no entry-level jobs." Look for adjacent roles, internships, and contract work.

Resources for Getting Started¶

Free Resources¶

• Google Technical Writing Courses
• Write the Docs community
• Technical writing subreddits
• Company documentation as examples

Communities¶

• Write the Docs Slack
• Technical Writer HQ
• LinkedIn technical writing groups
• Local meetups

Job Boards¶

• Write the Docs job board
• LinkedIn
• Indeed (filter for technical writer)
• Company career pages

Summary¶

Getting started in technical writing:

1. Assess fit - Confirm interest and aptitude
2. Build skills - Writing, technical, tools
3. Create samples - Demonstrate ability
4. Gain experience - Volunteer, intern, contribute
5. Position yourself - Portfolio, network, apply

The path requires effort, but technical writing is accessible to anyone willing to learn and practice.