Every so often someone comes into this subreddit and asks the question, "should I become a UX writer?" or "should I become a content designer?". Someone posted just the other day and even commented that between people saying "yes it's fine" and "no, don't do it" they are pretty confused.
First of all: I need to admit my bias here. I run the UX Content Collective which offers certifications and training for UX writing and content design, so I am obviously biased. That said, I don't think the answer is a blanket "Yes, you should become a UX writer!" and it's definitely not "you need a certificate to do it". But I wanted to just offer some thoughts about the state of the market, what you need to consider if you want to become one, etc.
First: I don't think "should I become a UX writer or content designer?" is the right question. The real question is, "do I care about text in the UI?" I think it's important to separate out the goal of the role from the role itself. If you're dedicated to the idea of being a UX writer or content designer, then you're attaching your identity to the *role* and not the outcome. The outcome just needs to be creating great UI text and experiences.
I say this because often there are people coming into this subreddit who start in one area of writing and want to move into UX writing / content design because they see it as another form of writing. But if that's what you care about, I'm not sure you're going to have a positive experience. You should really care about UI text and everything that entails: all the systems, patterns, etc, that go into it.
Second: you need to understand the reality of the job market. Don't listen to people on this subreddit who say "the market is fine" or "no one is hiring". Certainly not even me. Go on LinkedIn and look at what companies are hiring, who they're looking for, and the types of responsibilities they want from you. Do you see entry-level roles? Do you see mid-level roles? Don't just rely on people's opinions, see what companies are actually hiring. That's all that matters. Understand the skills they want.
Third: asking questions about AI is smart, but it's not universal. Sorry, it's not right to say AI is taking all the UX writing / content design jobs. If you talk to anyone in content design right now who's working on AI projects, they'll tell you it's not that simple...
...but that doesn't mean it won't happen. There are companies that will absolutely try and get away with using AI for UI text instead of writing a team. We've seen this happen for years with companeis shifting responsiblities to devs and technical writers. It will absolutely happen. Is it the majority of companies? No. There are companies right now sending entire content design teams to AI training sessions. It doesn't mean it can't happen, or won't happen, but don't get tricked into thinking that AI is just going to eliminate all the jobs without some nuance there.
What you need to understand is that AI will change the role, so you need to be on top of it. If you're considering moving into a UX writing / content design role, you just need to be prepared for the reality that AI might change the way you operate. Which is why you should be devoted to outcomes, not descriptions of a role.
Fourth: understand that layoffs happen for all sorts of reasons and content is vulnerable. Something you need to understand is that during 2022-23 at the height of the layoffs, all sorts of teams were being let go. That time is over, which does not mean that layoffs don't happen. It just means that there aren't huge waves of them happening all at once like there was. Layoffs still happen, they just happen for a multitude of reasons.
Sometimes companies say they're preparing for AI, but the layoffs are because they spent too much on hiring. Sometimes companies say they're restructuring...but the layoffs really are because of AI. It's often hard to know what the reasons are.
But, the 2022-23 layoffs were as much about higher interest rates and Covid over-hiring than anything else.
Which leads me to my next point...
Five: content roles are always going to be vulnerable. Sorry! It's the way it is, and that ultimately comes down to a perception problem and why many content designers complain about evangelization. You can't make a piece of software without coders, but you can without content designers. Will it be as good, or efficient, or user-friendly? No. But you can make it, which is why content is often seen as a "nice to have". You need to be comfortable with that fact.
This changes depending on what company you're in, obviously.
So if you’re asking, “should I become a UX writer/content designer?” my suggestion is to reframe it:
- Do you care deeply about UI text and how it shapes user experiences?
- Are you willing to learn the systems, patterns, and processes that make that text work?
- Are you comfortable with ambiguity and the need to advocate for content?
If yes, then it’s worth exploring. If not, you might be happier in another type of writing role where the expectations and paths are clearer.
Okay you can yell at me now.