I have read a lot of writing resumes while hiring, and UX writing resumes fail in a predictable way. They describe responsibilities that any writer in the role would have, and they leave out the two things a hiring manager is looking for: proof that you have shaped real product content, and a portfolio link that opens on the first click.
Your resume is not competing with your portfolio. It is the document that decides whether anyone opens the portfolio at all. Major employers make this explicit. Google's current content design listings ask applicants to include a portfolio, website, or other viewable link to their work along with access instructions, which means the resume is judged partly on how cleanly it hands over that link.
Below are three worked examples for different career stages, written out in full rather than described, plus the specific edits I would make to the sections that usually sink an application. Treat the sample text as structural models to adapt, not lines to copy, since the details in them are illustrative rather than descriptions of real people.
What a UX Writer Resume Has to Do
A UX writing resume has one page to answer three questions. What interfaces have you written for, what changed because of your writing, and can you work inside a product team. Everything that does not serve one of those questions is taking up space that a result could occupy.
The section order I would use is contact details with the portfolio link, a short professional summary, experience, skills, then education and any certification. Put the portfolio in the contact block, not at the bottom, because it is the most valuable line on the page. Give it a clean, readable URL rather than a shortened tracking link, make sure it is publicly viewable, and if a case study is password protected, write the password directly on the resume.
Keep it to one page for anything under about a decade of experience. Use a single column, standard headings, and no graphics, since applicant tracking systems parse plain structure reliably and creative layouts unpredictably. Save it as a PDF with your name in the filename. Keep capitalization and terminology consistent down the page, and use a published standard such as the Google developer documentation style guide as your tiebreaker when you are unsure. Ironically, a resume for a job about clear interface language is a fine place to prove you can respect a constrained format.
Example One: The Career Changer From Copywriting
This is the hardest version to write, because the applicant has real writing skill and little product experience. The fix is to lead with interface work of any kind, including volunteer work and the assessed projects inside a UX writing certification course, and to translate marketing results into user outcomes. Here is how the top of that resume can read.
Summary: Copywriter with six years in B2B software marketing, now writing product content. Redesigned onboarding and error content for two small SaaS teams, cutting repeat support questions about account setup. Comfortable in Figma, working from design files and shipping strings with engineers.
Relevant experience: Content designer, volunteer engagement, community health nonprofit. Rewrote the donation flow across five screens, including confirmation and failure states. Replaced the generic payment error with specific recovery instructions, and abandoned donations at the payment step fell after launch.
Professional experience: Copywriter, software marketing agency. Wrote landing pages, email sequences, and in-app announcement copy for eight client products. Ran headline and call to action tests, then documented the winning patterns in a shared voice guide used by three writers.
Training: Completed a graded UX writing course with an assessed interface project, plus a design fundamentals certificate covering research, wireframing, and prototyping in Figma.
Notice what that version avoids. It never claims a UX writer title the applicant has not held, and it never hides the marketing background. It reframes the background as evidence of testing discipline, which is a genuine strength that transfers. If you are making this move, the difference between UX writing and copywriting is worth being able to articulate in one sentence, because you will be asked about it. If the training line is thin, a program from my roundup of certifications built for content designers can give you an assessed project to cite here.
Example Two: The Mid-Level UX Writer
Once you have held the title, the resume's job changes. Nobody doubts you can write a button label, so the page needs to show scope, collaboration, and impact. This version leans on measurable outcomes and named surfaces.
Summary: UX writer with four years designing content for mobile and web banking products. Owns onboarding, identity verification, and error handling content for an app used by roughly two million customers. Built the terminology set the design system now ships with.
Experience bullet: Rewrote identity verification across eleven screens with research and engineering, cutting support contacts about rejected documents in the quarter after launch.
Experience bullet: Created the product's voice and tone guidance and a reusable pattern library for confirmations, warnings, and empty states, then trained designers and product managers to apply it without writer review.
Experience bullet: Partnered with localization to restructure strings that broke in German and Japanese layouts, reducing translation queries per release.
Experience bullet: Ran comprehension testing with the research team on two fee disclosure screens, then rewrote the copy that most participants misread on the first attempt.
Every one of those lines names a surface, a partner, and a consequence. That is the pattern to imitate. If you do not have clean metrics, use honest proxies such as support contact volume, task completion, translation queries, or the number of teams that adopted your pattern. Never invent a percentage, because interviewers ask how you measured it and the answer is where a fabricated number falls apart.
Example Three: The Senior Writer Moving Into Content Design Leadership
At this level the resume has to show influence beyond your own screens. Hiring teams want evidence that you set standards, made decisions under conflicting priorities, and made other people better at content. It is also the level where the gap between titles is largest, so it is worth checking what UX writers earn at each level before you decide which seniority to apply for.
Summary: Content design lead with nine years in product content, four of them leading a team of five writers across payments and identity. Sets content standards, runs critique, and represents content in roadmap and prioritization decisions.
Leadership bullet: Established a content design practice from scratch, including hiring criteria, a portfolio review rubric, and an onboarding path that brought new writers to independent shipping in their first quarter.
Leadership bullet: Introduced content quality checks into the design review process, so errors, empty states, and permission dialogs were written before engineering handoff rather than after.
Leadership bullet: Negotiated a plain language rewrite of legally reviewed disclosure copy with legal and privacy partners, keeping the required meaning while shortening the screen substantially.
Leadership bullet: Defined content standards and evaluation guidelines for AI generated product copy, including review criteria used before any generated string shipped to customers.
That last line matters more each year. Large employers are now hiring content people to shape how models write, not only to write themselves, and current listings for these roles name practices such as writing system instructions and defining evaluation rubrics. If you have done any version of that work, it belongs on the page, and what Google expects from a UX writer is a useful benchmark for how to phrase it.
Turning Duties Into Evidence
Most weak resumes are made of duties. Responsible for writing microcopy for the mobile app tells a reader nothing, because it is true of everyone who has ever held the job. The rewrite adds the surface, the reason, and the result: rewrote the mobile signup flow, replacing three confirmation screens with one, and reduced drop off between account creation and first session.
Apply the same test to collaboration claims. Worked closely with designers is a filler. Sat in design critique twice a week and rewrote component labels with the design systems team is a description of how you actually operate. Specificity is what makes a resume sound like a practitioner instead of a job description, and it maps directly onto the skills UX writing roles are screened for.
For the skills section, keep it short and truthful. Name the design and collaboration tools you genuinely use, such as Figma and whatever ticket system you live in, plus real capabilities such as content design systems, error and empty state content, comprehension testing, accessibility, localization-ready writing, and style guide ownership. Drop the padding. Nobody is impressed by a listed proficiency in word processing.
The Mistakes I Would Cut Before Sending
The first is a portfolio link that fails. A broken link, a request access screen, or a missing password ends the application silently, because no recruiter will chase you for it. Test it in a private browser window before every submission.
The second is inflated numbers. If you cannot explain how a result was measured and what else changed at the same time, leave it off. The third is decorative design. Two columns, sidebars, icons, and skill rating bars confuse parsers and add nothing a hiring manager needs. The fourth is a generic summary reused across every application, when the same paragraph rewritten around the specific product would take five minutes.
The last one is subtler. Many candidates describe writing and never describe deciding. Content design is a judgment role, so include at least one line that shows a tradeoff you made, a constraint you worked within, or something you argued to remove. That single line is usually what prompts the first interview question, and preparing for the questions UX writing interviews ask is much easier when you choose the story yourself.
If you are early in this career and short of material, the fastest fix is not a better template. It is one real project. Rewrite a flow for a small organization that will let you ship it, measure whatever you can, and write it up honestly. A resume built on two of those beats a beautifully formatted page built on adjectives, and it gives you something worth talking about when someone finally calls.
Conclusion
A compelling UX writer resume achieves two goals: opening the door to your portfolio and proving you can communicate impact clearly. By tailoring your resume to highlight measurable outcomes, collaboration with product teams, and interface work, you signal to hiring managers that you understand the demands of content design. Include a clear portfolio link that works flawlessly, and use honest metrics or proxies to describe the changes your writing brought to products or processes.
The examples shared here illustrate how to craft resumes for different career stages, from transitioning writers to those in leadership roles. Whether you're reframing past marketing experience or showcasing leadership in a content design team, focus on how your writing shaped meaningful results. Avoid overcrowding your page with generic summaries or unverifiable claims, and let concise, evidence-driven writing prove that you're the right candidate. With a well-crafted resume and portfolio, you'll stand out as a UX writer who delivers value one clear sentence at a time.
Related Resources
Frequently Asked Questions
Here are the most frequently asked questions about UX writer resumes.
How long should a UX writer resume be?
One page for most applicants, and no more than two if you have a decade of experience or a leadership record that genuinely needs the space. Recruiters skim, and a tight page signals the editing judgment the job requires.
Do I need a portfolio as well as a resume?
Yes. Major employers ask for a viewable link to your work in the application itself, and content design is evaluated on reasoning that a resume cannot show. The resume gets the portfolio opened, and the portfolio gets you the interview.
What if I have never held a UX writer title?
Lead with interface work regardless of where it happened, including volunteer projects, internal tools, support content, and assessed course projects. Describe the flow, the constraint, and the outcome. Keep your previous title accurate and let the work argue for the switch.
Should I include metrics I cannot verify?
No. Use only results you can explain, and choose honest proxies when precise numbers are unavailable, such as support contact volume, adoption of a pattern by other teams, or reduced translation queries. Interviewers probe numbers, and unverifiable claims collapse quickly.
How do I format a resume for applicant tracking systems?
Use a single column, conventional section headings, standard fonts, and no images, tables, or text boxes. Submit a PDF unless the employer asks for another format, name the file with your own name, and keep dates and job titles in a consistent structure.
Does a certification belong on a UX writing resume?
It belongs near the bottom, alongside education, and it helps most when the program includes an assessed project work you can also show in your portfolio. On its own, a certificate line rarely moves a hiring decision the way a documented interface project does.