Technical Writing as a Career for Kenyans Who Love Words

Technical writers create the words that help people use technology. The output takes many forms.

API documentation. When a company like Africa's Talking or Flutterwave builds an API, someone needs to write the guides that teach developers how to use it. What endpoints exist, what parameters they accept, what errors they return, and how to authenticate. Bad API docs mean developers give up and use a competitor. Good API docs mean developers integrate in hours instead of days.

User guides and help articles. The documentation that explains how to use a product. Setting up your account, configuring features, troubleshooting common problems. When you open a help centre and find a clear, well-structured article that solves your problem in two minutes, a technical writer made that happen.

Tutorials and how-to guides. Step-by-step instructions that walk users through specific tasks. "How to integrate M-Pesa into your React app using the Daraja API." "How to deploy your first Docker container to AWS." These bridge the gap between reference documentation and practical application.

Internal documentation. Companies also need internal docs: onboarding guides for new engineers, architecture decision records, runbooks for incident response, and process documentation. This work is less visible but equally valued.

Blog posts and content. Some technical writing roles include creating blog content, case studies, and thought leadership pieces for the company's website. This overlaps with content marketing but requires technical accuracy that a generic copywriter cannot provide.

Clear writing. This sounds obvious but it is the hardest skill to develop. Technical writing is not creative writing. You are not trying to entertain or impress. You are trying to transfer information from your head to the reader's head with minimum friction. Short sentences. Active voice. One idea per paragraph. No jargon without explanation.

Technical understanding. You need to understand the technology well enough to explain it accurately. For developer documentation, this means understanding APIs, HTTP methods, authentication, databases, and common programming concepts. You do not need to write production code, but you should be able to read code snippets and understand what they do.

Empathy for the reader. Who is reading this document? What do they already know? What are they trying to accomplish? A tutorial for a beginner looks completely different from an API reference for an experienced developer. Technical writers constantly adjust their language, depth, and structure based on the audience.

Markdown. The formatting language used in virtually all modern documentation. It is simple: headings, bold, lists, code blocks, and links. Learn it in an afternoon, use it for years. GitHub READMEs, documentation sites, and most content management systems support Markdown.

Git basics. Documentation often lives in Git repositories alongside code. You need to understand how to clone a repo, create a branch, commit changes, and create pull requests. This puts you in the same workflow as developers, which builds trust and makes collaboration smoother.

Information architecture. Organising large amounts of content so users can find what they need. How do you structure a documentation site with 200 articles? What goes in the getting started guide versus the reference section? Good information architecture is invisible when done well and infuriating when done poorly.

Week 1-2: Learn the basics. Read Google's free Technical Writing courses (developers.google.com/tech-writing). They cover the fundamentals in a few hours: active voice, word choice, lists, paragraphs, and document structure. Then read documentation you admire. Stripe, Twilio, and Africa's Talking have excellent docs. Study how they structure content, explain concepts, and use code examples.

Week 3-4: Learn the tools. Practice Markdown by writing sample docs in a text editor. Create a GitHub account and learn basic Git commands. Explore documentation platforms like Docusaurus, GitBook, or ReadTheDocs. You do not need to master them, but understanding how documentation sites are built helps.

Week 5-8: Build your portfolio. Create three to five sample documentation pieces. Options include: rewrite the README for a popular open-source project (make it clearer), write a tutorial for a tool you use, create an API documentation sample for an imaginary or real API, or document a process at your current job. Quality matters more than quantity. Three excellent pieces beat ten mediocre ones.

Month 3: Contribute to open source. Many open-source projects desperately need better documentation. Find projects with issues labelled "documentation" or "good first issue" and contribute. This gives you real-world portfolio pieces, open-source contribution experience, and connections in the developer community.

Month 4: Start applying. Search for "Technical Writer," "Documentation Engineer," "Developer Advocate," and "Content Engineer" on LinkedIn and job boards. Simultaneously, create profiles on freelance platforms and start pitching to companies whose documentation you think could improve.

Total investment: your time and a free GitHub account. No paid tools or courses are necessary to get started.

Full-time roles in Nairobi: Junior technical writers earn KES 50,000 to KES 100,000. Mid-level writers earn KES 100,000 to KES 200,000. Senior writers and documentation leads earn KES 200,000 to KES 350,000. These roles exist at companies like Safaricom, Africa's Talking, Twiga Foods, and banks with developer APIs.

Freelance for Kenyan companies: KES 3,000 to KES 10,000 per article or documentation page. Retainer arrangements with local companies might pay KES 30,000 to KES 80,000 monthly for ongoing documentation work.

Freelance for international clients: This is where earnings jump. International companies pay USD 30 to USD 80 per hour for experienced technical writers. A Kenyan writer billing 20 hours per week at USD 40 per hour earns approximately KES 400,000 monthly. The rates depend on your niche, portfolio quality, and client base.

Write-for-pay programmes. Several tech companies pay external writers for tutorials and articles. DigitalOcean, LogRocket, Twilio, Auth0, and others have "community writer" programmes paying USD 200 to USD 500 per article. These are excellent for building both your portfolio and your income while you establish yourself.

The freelance path works particularly well for Kenyan writers because of the currency advantage. Living costs in Nairobi are a fraction of San Francisco or London, but international clients pay near-international rates for quality documentation. Writers who build strong reputations and direct client relationships can earn very comfortable incomes by Kenyan standards.

API documentation. The highest-paying niche. Companies with developer products need writers who understand REST APIs, authentication, error handling, and SDKs. Stripe, Twilio, and similar companies set the standard. If you can write docs at that quality level, you are in demand globally.

Cloud and DevOps documentation. AWS, GCP, and Azure all need documentation writers. Companies migrating to the cloud need migration guides, architecture documentation, and runbooks. This niche requires deeper technical knowledge but pays premium rates.

Fintech and payments documentation. Kenyan writers have a unique advantage here. Understanding M-Pesa, Daraja API, and African payment systems is specialised knowledge that international companies entering the African market will pay for. If you can write clear integration guides for African payment systems, you have a niche that almost nobody else can fill.

AI and developer tools. The explosion of AI products creates demand for documentation that explains AI APIs, model training processes, and integration patterns. This is a newer niche with less competition.

Healthcare and compliance. Regulated industries need documentation that meets specific standards. Medical device companies, pharmaceutical firms, and health tech companies pay premium rates for writers who understand compliance requirements.

Choosing a niche early in your career is a smart move. A "technical writer who specialises in API documentation for fintech" is more hireable than a "technical writer" with no specialisation.

Technical writing leads to several growth paths.

Documentation lead or manager. You manage a team of writers, define documentation standards, and oversee the entire docs site. This role exists at larger companies and pays KES 250,000 to KES 500,000 or more.

Developer advocate / Developer relations. Some technical writers move into DevRel, where they create content, speak at conferences, and build communities around developer products. DevRel roles combine writing, presenting, and community management. Pay is similar to senior engineering roles.

Content strategist. You plan the overall content architecture for a product or company: what documentation exists, what is missing, how users find information, and how content serves business goals. This is a more strategic, less hands-on-writing role.

Independent consultant. Experienced technical writers build consulting practices, helping companies overhaul their documentation, set up docs infrastructure, and train internal teams. Consultants set their own rates and choose their projects.

Regardless of your growth path, keep writing. Publish articles on your blog, contribute to open-source docs, and share knowledge publicly. Your public body of work is your reputation, and in technical writing, reputation is how the best opportunities find you.