How a Side Hustler Makes 6000 Monthly as a Freelance Technical Writer for APIs

Lucas: Luna, I want to talk about a side hustle that flies under the radar for most people — technical writing for APIs. Not the kind of writing you learned in English class. Luna: You mean writing documentation that developers actually read? I know there's demand, but who's paying, and how much? Lucas: Let me give you a specific case. There's a freelancer named Sarah — former English major, zero coding background five years ago. She now earns about six thousand dollars a month writing documentation for companies like Stripe and Twilio. Luna: Wait — Stripe pays freelancers to write their docs? I assumed they had an in-house team for that. Lucas: They do have internal writers, but they also hire contractors for specific projects — new API endpoints, SDK updates, or full documentation overhauls. Sarah's typical project is a ten-page API reference for a new feature, and she charges around three thousand dollars for that. Luna: That's three hundred dollars per page. That's more than most magazine freelancers make per article. Lucas: Exactly. And the barrier to entry is lower than you'd think. You don't need to be a software engineer. You need to be curious, methodical, and comfortable reading code examples — even if you can't write them from scratch. Luna: So how did Sarah get started? Did she take a course, or did she just start applying? Lucas: She started by contributing to open-source projects. She found a popular JavaScript library on GitHub that had terrible documentation, and she rewrote the readme file and added a quick-start guide. The maintainers loved it, and that became her first portfolio piece. Luna: That's smart — you're basically proving you can do the work by doing it for free first. Lucas: Right. From there, she reached out to smaller SaaS companies that had obviously neglected their docs. She'd send a polite email with a sample rewrite of one of their pages. About one in ten said yes, and that's how she built her client base. Luna: And now she's at six thousand a month. How many clients does she work with at once? Lucas: Usually two to three at a time. Each project takes between one and three weeks. She bills hourly at seventy-five to one hundred twenty-five dollars, depending on the complexity. But she prefers fixed-price projects so she can work efficiently. Luna: That hourly rate is higher than a lot of people make as full-time employees. What's the catch? There has to be a learning curve. Lucas: The biggest catch is that you have to learn the technology you're documenting. Sarah spent three months learning the basics of REST APIs, JSON, HTTP methods — things like GET, POST, PUT, DELETE. She didn't become a developer, but she learned enough to understand what the code was doing. Luna: So you need some technical literacy, but not a computer science degree. That seems achievable for most people who are willing to study for a few months. Lucas: Absolutely. And the demand is growing fast. Every company that builds software needs documentation. As more businesses adopt APIs to connect their tools, the need for clear, human-readable docs explodes. Luna: I've also heard that AI tools are starting to generate documentation automatically. Does that threaten this side hustle? Lucas: It's a valid concern, but in practice, ai generated docs are often too generic or miss context. Developers still want examples, edge cases, and explanations that a human writer provides. Sarah actually uses AI to draft boilerplate and then spends her time refining and adding value. Luna: So it's more of a tool than a replacement. Good to know. Lucas: Exactly. Look, this kind of work also has a pretty nice work-life balance. Sarah works about twenty to twenty-five hours a week, mostly from home. She sets her own deadlines, and she rarely deals with meetings. Luna: That's the dream for a lot of side hustlers. No commute, no office politics, just writing. Lucas: Right. And the best part is that you're genuinely helping people. Developers get frustrated with bad docs — they waste hours trying to figure out how an API works. When you write clear documentation, you're saving them time and frustration. Luna: You know, speaking of helping people — a couple of dollars a month is genuinely what keeps these episodes going, ad-free. If you've gotten something out of our conversations, buy me a coffee dot com slash fexingo goes a long way. Lucas: Yeah, it's that simple. Our listeners' support is the reason we don't have to run ads or sponsors. Just a small, voluntary contribution keeps the lights on. Luna: Exactly. Now back to Sarah — how does she find clients consistently? Is it all referrals at this point? Lucas: Mostly referrals, yes. But she also attends developer conferences — not as a speaker, but as an attendee. She networks with developer relations people and product managers. She says the best leads come from talking to engineers at the booth. Luna: So you have to be willing to put yourself out there, even if you're an introvert writer type. Lucas: Yeah, a bit. But you can also find clients on platforms like Upwork or through technical writing job boards. The key is to have a portfolio that shows you can explain complex things simply. Luna: What does a good portfolio look like for API technical writing? Lucas: Sarah's portfolio has three main pieces: her open-source contribution, a sample from a client project, and a mock documentation page she wrote for a fictional API. She also includes a brief case study explaining the challenge and her approach. Luna: That makes sense. You want to show process, not just final output. Lucas: Exactly. And one more thing — she recommends learning a documentation tool like ReadMe, Stoplight, or even basic Markdown. Most companies use some kind of static site generator, so being familiar with that workflow is huge. Luna: Markdown is pretty simple to pick up. I think this is one of those side hustles that's accessible if you're willing to learn. Lucas: I'd agree. It's not for everyone — you have to enjoy precision and detail. But if you like writing and want to earn a solid side income without a huge upfront investment, API technical writing is a real opportunity. Luna: And six thousand a month is nothing to sneeze at. Thanks for breaking it down, Lucas. Lucas: Always a pleasure. Until next time.