Latest / The Career Change Podcast with Fexingo: Switching Fields, Bootcamps, and Reskilling / How Bootcamp Grads Break Into Technical Writing
Transcript
- Lucas: We spend a lot of time talking about how to get hired as a coder, but let's be honest with our listeners: not everyone wants to write code all day. There is a huge gap in the market for people who understand what code does but prefer to explain it rather than build it. Luna: Exactly. I see so many bootcamp grads burning out because they think their only option is full-stack development. The reality is that every API needs documentation, and most engineers hate writing it. Lucas: Right. And this isn't just about making things pretty. Good technical writing directly impacts adoption rates. If a developer can't figure out how to use your API in five minutes, they go to a competitor. Today we are looking at the rise of the technical writer as a primary hire, not an afterthought. Luna: Let's start with a concrete example. Have you seen the recent hiring trends at those mid-size cloud infrastructure companies? Lucas: I have. Take a company like DigitalOcean or even the documentation teams at larger players like Twilio. They aren't just hiring senior editors anymore. They are actively recruiting people with six-month bootcamp backgrounds who can parse JSON and understand REST endpoints. Luna: That is fascinating because it lowers the barrier to entry significantly compared to traditional software engineering roles. Lucas: It does. The skill set is hybrid. You need enough technical literacy to not be scared of a terminal window, but you need strong editorial instincts to make that terminal window feel approachable. It is basically translation work between machine logic and human intent. Luna: So if someone comes to us with a background in something totally unrelated, like retail management, how do they prove they can handle the technical side? Lucas: They don't need a degree. They need a portfolio. And by portfolio, I don't mean a blog post about why Python is cool. I mean actual documentation samples. If you take an open-source library on GitHub and rewrite its README to be clearer, that is a valid work sample. Luna: I love that idea. It shows initiative and practical application. But isn't there a fear among hiring managers that these candidates won't understand complex architecture? Lucas: There is, which is why the interview process is different. They aren't asking you to whiteboard a sorting algorithm. They are asking you to explain a concept you learned recently to someone who knows nothing about it. It tests clarity, not coding speed. Luna: Clarity over complexity. That makes sense for a writer, but it feels counter-intuitive for someone coming from a coding bootcamp where you're taught to optimize everything. Lucas: Optimization is for machines. Clarity is for humans. The best technical writers know when to simplify without dumbing down. They use analogies effectively. They structure information hierarchically. It is a distinct craft. Luna: What about the tools? Do they need to know Markdown and Git? Lucas: Absolutely. Markdown is non-negotiable. Git is highly preferred because you are often working alongside developers who commit code changes. If you can submit a pull request that updates the docs alongside a bug fix, you are instantly more valuable than a writer who works in a silo. Luna: So learning basic version control is actually part of the reskilling package now? Lucas: Yes. And it is easy. Most bootcamps cover it briefly. You just need to know how to clone a repo, create a branch, make your changes, and push them. You don't need to be a DevOps expert, but you need to speak the language. Luna: This really democratizes the field. You don't need four years of computer science to contribute meaningfully to software products. Lucas: Precisely. And the pay is surprisingly competitive. Entry-level technical writers at well-funded startups can make seventy thousand to ninety thousand dollars. Senior roles easily clear one hundred and twenty thousand, especially in fintech or enterprise SaaS. Luna: That is a very respectable salary for someone who doesn't want to be on-call for server crashes at three in the morning. Lucas: Exactly. It is a better work-life balance for many people. The pressure is on accuracy and usability, not uptime. Although, obviously, if the docs are wrong and people lose data, that is bad. But the stress profile is different. Luna: Let's talk about the specific types of documentation. Is it mostly user guides? Lucas: User guides are one piece. But the highest demand right now is for API references and developer tutorials. This is content for other builders. It requires a bit more technical depth because your audience is another developer. Luna: So you are writing for peers, essentially. That changes the tone completely. Lucas: It does. You can be concise. You can assume some baseline knowledge. You don't need to explain what an integer is. You need to explain how to authenticate an OAuth token correctly. That specificity is where the value lies. Luna: How do you recommend someone find these entry-level roles? They don't always show up on generic job boards. Lucas: Look for companies that mention Developer Experience or DevRel in their mission statements. Also, check the careers pages of companies whose documentation you already use and enjoy. If their docs are great, they probably have a growing team. Apply directly to the documentation lead if you can find them on LinkedIn. Luna: Direct outreach is key. Networking into a niche field is often easier than applying through a portal. Lucas: Yes. And once you are in, keep contributing to open source. It keeps your skills sharp and builds your public reputation. Many hires happen because a manager saw your contributions to a popular library. Luna: It creates a virtuous cycle. You write docs to learn the product, then you get hired to write docs for the product. Lucas: Spot on. It is one of the few paths where your output during the interview process becomes your first week on the job. It removes the guesswork for both sides. Luna: Before we wrap up, what is the biggest mistake these candidates make when applying? Lucas: They send a generic resume. They need to tailor their portfolio to the specific technology stack of the company. If the company uses React and TypeScript, your writing samples should reflect familiarity with those ecosystems, even if you aren't building apps. Luna: Relevance wins every time. Okay, we have covered a lot of ground here on a very specific career path. Lucas: If today was actually useful to you, the way these stay ad-free is listener support — buy me a coffee dot com slash fexingo. Luna: Yeah, if you found this breakdown helpful, consider grabbing us a coffee. It helps us keep digging into these niche career opportunities for you. Lucas: Thank you. Now, back to the question of whether technical writing is sustainable long-term. Luna: Is there a risk that AI will replace technical writers soon? Lucas: It is a valid concern. AI can generate draft documentation quickly. But it struggles with context, nuance, and knowing what the user is actually confused about. The human element of anticipating confusion is hard to automate. Luna: So the role shifts from writing from scratch to curating and refining AI output? Lucas: Exactly. The smart technical writers will learn to use AI as a force multiplier. Draft the boring parts with AI, then add the human insight, the troubleshooting tips, and the real-world examples. That hybrid workflow will define the next decade of the profession. Luna: Adapting to the tool rather than fighting it seems like the winning strategy. Lucas: Always. Whether you are coding or writing, the ability to leverage new tools is what keeps you employable. Luna: So, for anyone listening who has been thinking about switching fields but fears the technical jump, what is your final thought? Lucas: Start small. Pick one tool you use daily and try to document how it works. You might find that you enjoy the explanation more than the execution.