How to become a technical writer for free

Free Plan to Master the Technical Writer Profession for Beginners

Technical writers create documentation, instructions, and guides for software, hardware, and IT systems. They ensure users and developers understand the products. To break into the profession without any investment, use free resources: YouTube videos, courses, and self-study of tools. The full plan takes 3–4 months of intensive work.

Initial Stage: Understanding the Role

Start by assessing the profession's specifics through introductory materials. Watch videos like "Profession: Technical Writer," "How to Become a Technical Writer?" and "Technical Writer in IT: Expectations vs. Reality." For a text-based option, check out the article "Who is a Technical Writer and How to Become One." These resources provide an overview of tasks, from writing API documentation to user guides.

Tasks for this stage:

• Analyze typical responsibilities: creating man pages, READMEs, specifications.
• Assess required skills: structured writing, IT terminology.
• Determine your motivation: working with code without programming.

Basic Course on Technical Documentation

Move to systematic learning with the course "Technical Documentation in IT Projects" from the documentat.io channel. The material covers:

• Formatting standards: DITA, DocBook.
• Document structure: table of contents, glossary, examples.
• Integration with development: links to Agile processes.

The course explains how documentation fits into CI/CD pipelines and tools like Sphinx or MkDocs.

Mastering Key Technologies

For junior-level roles, study tools used in 90% of technical writer job postings:

• LaTeX: for complex documents with formulas and diagrams. Start with basic tutorials on article/book classes, tikz and listings packages.
• Markdown: standard for READMEs and GitHub repositories. Master extensions: tables, code blocks, admonitions.
• HTML: foundation of web documentation. Learn semantics (header, section, aside), CSS for styling.
• Jira and Confluence: for task management and wikis. Practice creating pages, macros, and Git integration.

Find tutorials on your own and practice on pet projects: document a simple Python script.

Continuous Development: Reading and Community

Expand your knowledge via the "Mishka in the Know: Technical Writer" channel. Read posts on real-world cases: migrating legacy documentation, automation with AsciiDoc.

For questions, join the "Technical Writers" chat. Discuss:

• Best practices for documentation reviews.
• Tools like MadCap Flare or Paligo.
• Interview preparation: portfolios with 3–5 samples.

What’s Important

• The full plan requires 3–4 months: 10–15 hours per week.
• After completion, seek junior positions or internships at IT companies.
• Portfolio: document open-source projects on GitHub.
• Prepare for interviews: questions on Markdown, Jira, review examples.
• The profession is in demand in DevOps, SaaS, and enterprise products.

Once mastered, proceed to interviews. Build a resume with links to GitHub documentation repositories.

— Editorial Team