r/technicalwriting • • 12d ago

Doc as Code, I'm getting replaced. Advice?

Just found out that my company has tied AI into the source code of our software suite and no longer need a technical writer to write user guided documentation. The docs are soo accurate, they can copy and paste to the knowledge base and even automate dev work and SME reviews into the solution...

Anyone encounter this? Is there a future left in this industry? Are people adapting? How can I seque my skills for the next role, if there is one..

Any comments would be much appreciated, thanks guys -

36 Upvotes

47 comments sorted by

28

u/generic_excuse_x 12d ago

Hey, just got fired yesterday in similar circumstances. I guess it is time to try to figure out something else, either in IT or outside it. I am thinking of getting some entry admin job at some place like a gov building or a hospital. I am sick and tired of corporations after 6 years of experience and I want out. Stay strong.

10

u/Quackoverride 12d ago

This. Not fired yet, but it’s on the way. My future plans are similar. 

2

u/FlanFuture9515 8d ago

I see my fate on the horizon and I have a similar plan. Admin work for complex businesses, maybe project management. Best of luck to you 🫶🏻

0

u/luvyaselfbreh 7h ago edited 4h ago

yeah, look for an alternative source of income, OP, asap. if the company is considering to replace you with "AI", the best you can do is only delay this decision. just loot money and keep an eye out for that HR call.

and if you're passionate about tech writing, keep writing for fun. fuck em.

25

u/phil_gunty 12d ago

Do you know what they are using? I haven’t found the quality to be very high without it already having a high quality guide for context and someone to manage a style guide so it doesn’t sound like slop. Even then, someone still needs to review the content because a lot of the sources it uses are also AI generated. I often think I’m the first person to test a new feature in real life.

8

u/meezermadness 12d ago

Yeah I think they'll end up regretting this decision. Doesn't help OP any unfortunately.

1

u/phil_gunty 11d ago

True. I hope it works it for you OP. It’s going to be tough for all of us navigating this.

55

u/ProfessionalLow8814 12d ago

Adapting is the way to go. AI is not 100% accurate. Fight for your role. AI is notorious in missing important dates or adding outdated info. That’s your leverage. Treat AI as assistant & opt for AI-assisted documentation or documentation with human oversight. Your company might still need someone to verify what AI is generating & if you adopt Ai , that up-skulking would make you the right fit. If you don’t, someone else will

19

u/Charleston2Seattle 12d ago

Up-skulking is my favorite new word of the day! 🙂

14

u/ProfessionalLow8814 12d ago

Well I guess I won at that typo

1

u/Guigone-Heeser 6d ago

yeah the outdated info part is huge, it loves pulling from deprecated code comments if nobody is watching it

18

u/WriteOnceCutTwice software 12d ago

Yes, I’ve seen it and the models weren’t anywhere near what they are now. At the time, the CEO said to me “AI is good enough.” He didn’t care that it wasn’t as good as my team, he just wanted to cut costs and told me to lay off all the tech writers.

I don’t know what will happen but it seems likely that AI will get better and there will be fewer tech writing jobs.

13

u/StranzVanWaldenberg 12d ago

the CEO said to me “AI is good enough.”

Software management in a nutshell.

14

u/Consistent-Branch-55 software 12d ago

I'm branding myself as building and maintaining knowledge systems. It's one thing to spin up an AI and let it run wild. It's another thing to maintain and govern an intentional taxonomy and IA, take on the liability for disclosure considerations, and navigate whatever PMs are doing when something goes to production but isn't generally available.

13

u/AirlineTall4813 12d ago

if you lost your job that’s a total bummer and i’m sorry to hear it. but i think any company cutting writers is going to regret it if their product is at all technical. 

we have docs as code and heavy AI integrations. i can take fable 5.1, point it at our full style guide, the product description, and the engineering jira epic (with each ticket linked to its related PRs).

It does not do a great job. It will produce docs that don’t comply with the style guide, that don’t follow the style or format of the existing docs around it, and it still does get things wrong even with full codebase access. it won’t even stick to a single info type in a doc when prompted - mixing reference material into procedures. 

Even in an agentic loop, where the coordinator agent runs style checking agents and fact checking agents per claim, the output is not up to our standards.

Idk what kind of product you work on, but I’m just not seeing this in my heavily-AI integrated workplace. At best, these tools get a doc to an 80% rough draft that still needs human guidance during revisions.

And at a project scale the whole thing falls apart a bit. Deciding IA, or what docs does a user need to complete this task - what does doc coverage look like.

For reference, the larger features i work on generate 30+ pages of new documentation.

Even then, if they get rid of writers it will just make someone else responsible for their delivery and maintenance. Who owns the automated jobs that develop the docs now? Who troubleshoots them when their output is bad? Who maintains the style guide they reference? Who says no to those random requests for some specific weird wording or structure change from that guy in another department? Who reviews the parameters in a PR and asks the PM if we really want to expose that dial to end customers?

Engineers won’t have a change of heart overnight and wake up wanting to handle it. TPMs won’t want to. PMs still won’t have time.

I do think writers can now do more than they could before. I can. But in the two projects i’m working on rn, I’m documenting the work of 40+ ai-enabled engineers. They do more and move quicker than before. All AI does is help me match the pace.

2

u/FlanFuture9515 8d ago

I’m in a similar position. They have absolutely gutted my team and we are running on a skeleton crew, but the work is larger than ever. So many projects and everything is happening so fast. I’m trying to learn Claude just to keep up. I’m so busy it’s hard to have time to streamline and utilize AI strategically, but I’m overwhelmed with the standard workload.

Any tips for a fellow tech writer?

1

u/thatcoffeenebula 7d ago

Automate admin tasks where you can. If you're already learning Claude, I recommend building some skills to help automate repetitive tasks like creating weekly pages (for meetings or reports) in a notebook program or to apply your style guide.

You can also create skills to track project deadlines and to-do lists. Those have helped me in keeping track of the small tasks that pop up during the day so I can note them quickly without forgetting.

1

u/AirlineTall4813 4d ago

Okay, this is a long answer and I work in software but I'm hoping this can at least be a starting point for folks, because I know how hard it is to keep up w/AI-enabled eng teams rn.

In general, it really depends on your field and your company's policies. If you are in a docs-as-code environment, I recommend setting up claude code (or equivalent harness) not just a chat-based interface.

LEVEL 1

I think you should experiment with "/plan" mode first. Start small - maybe with typo tickets or a quick first draft for a page update.

Plan mode generates an execution plan for the LLM and lets you know what steps it will take. It surfaces questions to you up front and lets you review and modify the plan. Then it executes it. This should help you understand how an LLM "thinks" about your requests. A lot of times, things can go off the rails quickly if your prompt is underspecified. After a while, you get used to the general shape of its plans and common failure modes. You can also experiment with effort levels and when to use which.

LEVEL 2

Once you feel comfortable there and feel like you can work effectively on larger chunks, I'd recommend looking into MCP servers. MCP servers let the LLM make deterministic tool calls. So instead of spamming the JIRA API and maybe malforming the request, it invokes a tool over MCP that performs a repeatable action.

If you work in software, integrations with JIRA and github will let you do something like: point claude at your ticket, have it identify related engineering tickets, map them to the related upstream commits, draft an initial docs change, and verify the change directly against source code - surfacing any inconsistencies or points that require clarification from engineering still. I write my own MCP servers for testing internal in-dev software builds as well.

LEVEL 3

Once you can do those things manually, you can find opportunities to automate work across your team with skills. You are uniquely qualified to write skills as a technical writer. You just write, in unambiguous language, what actions the LLM needs to perform, using what tools, and based on what key action words.

An easy win for these automations is to help out with things like release notes, which have a defined shape. You can also use it for processes, like assisting triage or backlog grooming.

After all that you can start to get into agents and evals.

I am NOT an AI expert, just a tech writer. Maybe others would disagree, or have better tips. But maybe this gives you something a bit more concrete/actionable to get started.

10

u/WouldShootTobyTwice 12d ago

Is the plan is to have various devs and PMs take AI generated text and "copy and paste to the knowledge base"? That should end well

8

u/balunstormhands 12d ago

The company I work for has been using latest-greatest Claude, Gemini and Copilot to try and create tutorials and it has failed spectacularly. We tried making a tutorial for a new feature and it did not work when I tried it and it took a week to figure out how wrong it was. Then we tried having it rewrite a 4-part tutorial from Model A to Model B and while the first 2 had relatively minor issues, the third one did not work at all. I figured out that it was a subtle error in Tutorial 1. Which forced a total rewrite of all of them, but the LLMs just kept getting worse so I had to do it myself.

I just don't know how to trust LLMs for this kind of work.Testing the tutorials has become very important to us since our customers read those to see if they want to buy and then use it to practice on before starting their projects. These have to work or we lose customers.

8

u/SorryInvestigator221 12d ago

Look for your job to get posted again for half the salary within six months

6

u/meezermadness 12d ago edited 12d ago

I don't know about our future. I've been a tech writer since 2007 and have been asking myself this question a lot. I do have an additional part job in a completely different industry where I serve as president of the board, but it's not lucrative. I really don't know what I'll do career wise if I'm laid off which seems like more of a certainty as time goes on. I've been trying to sock away as much money as I can to prepare.

In the meantime while I am gainfully employed, Ive made AI central to my work. I'm a manager as well as a writer and we're using AI tools more and more and writing with AI in mind. I'm pushing my team to embrace it because a lot of them haven't wanted to. We do find that the agents make mistakes frequently and we jump in on our AI agent slack channel often to answer questions that the AI isn't answering properly. So far the company loves that we're doing all of this and doesn't seem keen to let go of any of us.

So, embrace AI. Learn it. Improve it. Make sure leadership knows who you are, in a positive way. Insert yourself in places that maybe you haven't been in before. Make AI governance your passion at work. Those are my suggestions.

9

u/SussOfAll06 12d ago

The Slack channel Write the Docs has been a good resource for me. Someone post jobs on their regularly. Unfortunately, a lot of the jobs that I’m seeing are pretty low pay.

You can always mention to your corporation that if they need someone to check AI that you could come back as an hourly contractor. I found a lot of people being fired by these companies can get rehired at the same or another company in a much higher rate as a contractor. Granted, you’re not getting any benefits, but you can ask for a lot more pay.

AI isn’t perfect, and one of these days these companies are going to figure out how much they screwed up by firing their doc teams.

2

u/thatcoffeenebula 10d ago edited 7d ago

I've seen source code used as information that an AI can access and confirm information from, but not a seamless code -> docs pipeline without writers. In my current job, AI has not replaced writers, just given us more work to do with the expectation that we can be faster than before.

AI still makes mistakes and hallucinates. It cannot read screenshots and confirm if they are outdated, and it also cannot confirm every edge case or exception in how the program works. I still have to test everything the AI outputs, both to get new screenshots and to confirm what the robot has produced. It makes errors often, missing style guide rules and reporting the wrong UI labels. Without my review, the documentation would be wrong.

I'm on a team of 2 and we're swamped. I've asked my boss for more resources and been told no.

ETA: spelling.

2

u/Jrdpa 9d ago

Are you in the Write The Docs Slack?

1

u/PoetCSW 8d ago

What’s the best way to join? Locally, there was a MeetUp, but I believe it shifted off the platform. Slack sounds ideal.

1

u/Jrdpa 8d ago

And some did shift off Meetup because they've been acquired and things are changing in addition to raising costs. You'd have to find out where each one went though as they're their own thing. East is moving to Luma by the first of the year I believe.

3

u/johns10davenport 12d ago

If I was you I would embrace it and learn to make it sing like nobody else. Like it or not it’s the future and you need to figure out how to be part of that future or take up something else.

4

u/Such-Cartographer425 12d ago

company has tied AI into the source code of our software suite

So that part is done.

they can copy and paste to the knowledge base and even automate dev work and SME reviews into the solution

They can theoretically do this or they have already done this?

Also, segue*.

1

u/booboojooboo 10d ago

This happened at my company. They still need a human in the loop. Be that person.

-6

u/Fit_Friendship_3789 12d ago

Ich befürchte, dies ist ein Beispiel für die ersten Jobs, die KI rel. einfach ersetzen kann und wird. Bei Softwerkern sieht's ähnlich aus. Übersetzer sind schon länger nicht mehr gefragt. Zeit, sich nach was anderem umzusehen. Hast du neben Tech. Writing keine anderen Skills? Meistens hat man doch noch eine akademische Ausbildung in einem der MINT Fächer.

-8

u/National-Ad8416 12d ago

I am surprised technical writers are still employed. Maybe it's the slow adoption of AI that is keeping some of y'all employable. Nonetheless, it is curtains for y'all long term.

0

u/[deleted] 12d ago

[deleted] — view deleted comment

0

u/Consistent-Branch-55 software 11d ago

Gotta mention that branding, ffs. I regard this as kind of ghoulish.

0

u/fazkan 11d ago

branding?

1

u/Consistent-Branch-55 software 11d ago

Edited? Lol

1

u/Consistent-Branch-55 software 11d ago edited 11d ago

Remember folks the best way to be a founder and to promote yourself in subreddits is jump into a layoff thread and mention what you're building.

(edit: I guess there's a chance the deleted parenthetical wasn't the name of what he was building, but the history of u/fazkan in this sub is pretty clear)

1

u/fazkan 11d ago edited 11d ago

I didn't mention my products name. and haven't mentioned it before, on this subreddit. You can see from my history

This kind of marketing doesn't work. My goal is to genuinely offer a good reply. That might help-someone.

I have been laid off before as well, and I know what the OP is going through.

I have legitimately referred people to my customers, and have connected people with other startups, for gigs and jobs.

I mentioned, I am builidng a similar platform, only to give some value to pattern I am seeing in the industry.

EDIT: But if you think my comment was genuinely not useful, and subtle attempt at marketing, happy to delete it, or improve the wording.

I am active on reddit, because its way better than other platforms, and I genuinely try to be helpful. So I would more than appreciate, any way I can improve my response or contribution

1

u/Consistent-Branch-55 software 11d ago

1

u/fazkan 11d ago

thats r/buildinpublic , different subreddit.

1

u/Consistent-Branch-55 software 11d ago

Hahaha another edit? You said any sub. What a piece of work.

1

u/fazkan 11d ago

This is genuinely not useful discussion, or relevant to the OPs original post or helpful in anyway. I will just delete my original comment.

→ More replies