UX postings almost always ask for a portfolio link, so your resume is read beside work the reader can already see. Describing the screens again spends the page on the one thing the portfolio covers, while the research behind a redesign, the constraint you worked inside, and what changed after launch often appear nowhere. These prompts get an AI to pull process out of your case studies and compress it into lines a hiring manager can read before opening a single link.
Want a finished document to work backwards from? There is a full ux designer resume example in Markdown you can copy into the editor.
Before you paste any of these
Hand it a case study and ask for the parts the portfolio hides — Point the AI at the method and sample size (moderated usability sessions, a diary study, a sweep of support tickets), the constraint you designed around (a legacy design system, a 2-week release train, a locked backend), and how the work reached engineering.
Ask for one compressed line per project, not a narrative — Case study prose does not shrink on its own. Specify the shape you want: the problem, what the research told you, what you changed, what moved afterward — with a bracket wherever a task-completion or support-volume figure belongs.
State your role in the research honestly — Running the sessions yourself and reading someone else's findings are different jobs, and only one of them is yours to claim. Have the AI phrase both accurately — "ran [N] moderated sessions" against "built on research the insights team ran" — so the resume matches the story you tell out loud.
Reject any bullet that could describe any screen — Left to itself, a model writes about clean, modern, intuitive interfaces. Put that class of adjective on a banned list and require the prompt to ask you which task got faster, which step disappeared, or which error stopped happening instead.
3 prompts to copy
Every prompt ends with the same rules: use only what you give it, and mark a missing number with a placeholder instead of guessing one.
Your resume repeats what the portfolio already shows — redesigned the onboarding flow, built a design system — so it adds nothing a hiring manager cannot see in the screenshots
What to have ready
•One portfolio case study, pasted as text — the write-up, not the images
•The 2 or 3 resume bullets you currently use for that project
You are converting a UX designer's portfolio case study into resume lines. The resume gets read beside the portfolio, so any line describing the visuals is wasted space. Resume lines have to carry what screenshots cannot: the research that set direction, the constraint you designed against, the tradeoff you argued for, and what shipped.
My case study:
[PASTE THE CASE STUDY TEXT]
My current bullets for this project:
[PASTE 2 OR 3 BULLETS]
Do this:
1. Extract, quoting my case study for each item:
- The question the project started from, and who asked it.
- The research: method, how many participants or sessions my write-up states, and what it changed about the direction. Name the method exactly as I named it — moderated usability sessions, diary study, intercept survey, support-ticket review, session replay.
- The constraint: platform, accessibility requirement, engineering budget, a legacy component, regulated copy, a launch date.
- The tradeoff I argued for, and what I gave up to get it.
- What shipped, to whom, and how anyone knew whether it worked.
Write "not in the case study" for anything absent, including a participant count I did not state.
2. Compare. For each current bullet, say whether it describes something already visible in the portfolio. If it does, mark it "the portfolio already says this" and replace it.
3. Write 4 replacement bullets, ranked strongest first. Each under 28 words, each traceable to a line you quoted in step 1. Use [add detail] where a fact is missing.
4. Close with the 3 questions you would need answered to make these stronger, and say which one matters most.
Rules:
- Do not treat layout, color, typography or component work as an achievement on its own — the portfolio shows those better than a sentence can.
- If the case study contains no research and no outcome, say so plainly. That is a portfolio problem, and a rewritten bullet cannot hide it.
- Keep me as the subject of every sentence, and be exact about what I decided versus what I contributed to.
Rules — these override everything above:
- Use only the experience I give you. Do not invent employers, job titles, dates, degrees, certifications, skills, or metrics.
- If a number would strengthen a line and I have not given you one, write a placeholder like [X%] or [$X] for me to fill in. Do not estimate it.
- Do not add a tool, skill, or credential I did not list, however standard it is in my field.
- Rewrite, reorder, tighten and re-emphasize what is already there. Where I have given you too little to work with, ask me for it or leave [add detail].
Send this next
Run this once per case study, then read the sets side by side. The method that keeps reappearing is your specialty, and it belongs in your summary.
Microsoft Copilot: Run this in Copilot Chat rather than as an inline completion in a file — the 4 numbered steps need room, and an editor completion is the wrong place for them.
Open inCopies the prompt, then opens the assistant
A hiring manager opens your portfolio first and your resume second. By the time they reach the summary it has to say something the screenshots did not — and "passionate about user-centered design" does not
What to have ready
•Your current resume
•The opening paragraph of your 2 or 3 strongest case studies
•The job posting, or 3 sentences describing the role you want next
You are writing the summary block at the top of a UX designer's resume. It gets read after the portfolio, so it must not describe visual work. It has to answer 3 things: what kind of design problem this person handles, at what scope, and on what evidence.
My resume:
[PASTE YOUR RESUME]
Opening paragraphs from my strongest case studies:
[PASTE 2 OR 3]
The role I want next:
[PASTE THE POSTING OR DESCRIBE IT IN 3 SENTENCES]
Step 1 — evidence pass. From my text only, list:
- The surfaces I have designed: consumer app, internal tool, enterprise admin, hardware companion, marketplace, developer product.
- Research methods that appear more than once.
- Scope signals: team size, engineers I worked beside, design system ownership, whether I set direction or executed it, whether I ran discovery.
- Any accessibility, localization or platform depth stated in my material.
Quote the source of each item. Mark anything I would clearly like to claim but have not evidenced as "not supported".
Step 2 — write 3 summary variants, each 2 sentences and under 45 words:
A. Research-led — the designer who starts from evidence.
B. Systems-led — the designer who makes many teams consistent.
C. Product-led — the designer who owns an outcome end to end.
Step 3 — for each variant, list its load-bearing phrases and trace each one to a quoted line from step 1. Then name the variant this posting rewards, and quote the line in the posting that decided it.
Rules:
- No adjective survives unless my material supports it. "Senior" needs scope, "research-driven" needs a named method, "systems thinker" needs a system.
- Do not add a seniority level, a team size or a specialty I did not state.
- Do not write "passionate", "user-centered", "pixel-perfect" or "storyteller".
- If none of the 3 variants is supported, say which is closest and what evidence would earn it.
Rules — these override everything above:
- Use only the experience I give you. Do not invent employers, job titles, dates, degrees, certifications, skills, or metrics.
- If a number would strengthen a line and I have not given you one, write a placeholder like [X%] or [$X] for me to fill in. Do not estimate it.
- Do not add a tool, skill, or credential I did not list, however standard it is in my field.
- Rewrite, reorder, tighten and re-emphasize what is already there. Where I have given you too little to work with, ask me for it or leave [add detail].
Send this next
Pick one variant and delete the other 2 from your file. 3 summaries kept for later become 3 slightly different claims about the same person.
Open inCopies the prompt, then opens the assistant
Plenty of designers have a clean portfolio. The resume's real job is to carry what a portfolio structurally cannot: how you work with engineers, what you did when research contradicted the plan, and what happened after launch
What to have ready
•Your resume
•Your case study titles, with one line on what each one shows
•Optional: a short note on a project that went badly and what you did about it
You are auditing a UX designer's resume for the things a portfolio cannot demonstrate. A portfolio shows artifacts well and behavior poorly, so the resume is where behavior has to live. Find what is missing and tell me where the evidence would come from.
My resume:
[PASTE YOUR RESUME]
My case studies, one line each:
[PASTE TITLES AND WHAT EACH SHOWS]
A project that went badly (optional):
[PASTE IT OR WRITE "skip"]
Audit against these 6, one section each:
1. Collaboration under constraint — evidence of designing with engineers rather than handing off to them: a scoping session, a component cut for effort, a spec I wrote, a build I paired on.
2. Research that changed the plan — a moment evidence overturned the intended direction. It is the hardest thing on a designer's resume to imitate, so quote it exactly where it is there.
3. Decision ownership — what I decided versus what I proposed. Watch the verbs: "explored" and "supported" read very differently from "set" and "cut".
4. Life after launch — anything showing I stayed attached once it shipped: an iteration, a metric someone watched, a rollback, a follow-up study.
5. Scope honesty — anywhere my resume claims more of a project than my case study line supports, or less.
6. The recoverable failure — what the optional note gives you, if I supplied one.
For each section, quote the strongest evidence already in my material, or write "absent". Where it is absent, name the specific artifact I should go find in my own history — a ticket, a research readout, a launch retro, a decision thread — and the one question I should answer before writing anything.
Finish by quoting the 2 strongest lines already in my resume, with one sentence each on why they survive a portfolio-first read.
Rules:
- Do not draft replacement bullets in this pass. This is an evidence audit.
- Do not infer that something happened because it usually happens on projects like these.
- Where evidence is absent, describe the artifact to go looking for rather than what it probably said.
Rules — these override everything above:
- Use only the experience I give you. Do not invent employers, job titles, dates, degrees, certifications, skills, or metrics.
- If a number would strengthen a line and I have not given you one, write a placeholder like [X%] or [$X] for me to fill in. Do not estimate it.
- Do not add a tool, skill, or credential I did not list, however standard it is in my field.
- Rewrite, reorder, tighten and re-emphasize what is already there. Where I have given you too little to work with, ask me for it or leave [add detail].
Send this next
Put the absent items in your notes, not straight onto the page. Only the ones you can actually source belong in the resume.
Open inCopies the prompt, then opens the assistant
General prompts that also work for a ux designer resume
A chat window returns text. Paste it here and it opens in the editor, where 32 templates turn it into an interview-ready PDF. Free, no signup, and your draft stays in your browser.
