A UX researcher finds and checks why people get stuck. A UX designer turns those findings into a task flow people can use and test. A research portfolio should show how an observation changed what the team understood. A design portfolio should show what you changed in the interface and how you tested it.
- UX research typically involves research plans, interview notes, and findings backed by evidence. Practice asking questions, choosing participants, and separating observation from interpretation. For a first exercise, watch two volunteers complete one task and note where they get stuck and what you still need to verify.
- UX design typically involves task flows, clickable prototypes, and notes on revisions. Practice organizing information, designing interface states, and making trade-offs. Map the shortest path through one task, then add a recovery path if something goes wrong.
Before you choose a role: check what users or decisions you serve, what you would do each week, what you would hand over, who reviews it, and what counts as done. Ask for an example from the last project if the listing blends both jobs.
How do findings turn into a design for rescheduling a reservation?
Imagine a library that lets readers reschedule a study-room reservation online. Readers worry that opening the rescheduling page will cancel their original slot. The team can change the wording and interaction this week. The rule stays the same: the old reservation is replaced only after rescheduling succeeds. Research and design agree on one test question. Can a first-time visitor tell whether the old reservation is held while they choose a new slot?
The researcher asks librarians where readers tend to seek help and what they see on screen. Participants describe how they last changed a reservation and then try the task with sample data. A neutral prompt is, “You can't make your original time. Try changing your reservation to a time you can attend.” Telling participants that the old booking is still held would give away the answer. In the notes, separate what people did, what they said, and your interpretation. The UK Government Digital Service describes how to group observations, develop findings, and decide what to do next. GOV.UK guide to analyzing research sessions
Suppose one participant sees a red reschedule button, assumes it cancels the booking, and goes back. Another picks a new slot and looks for the original reservation to check whether they now hold two places. Here is a sample handoff.
| Handoff item | What to record |
|---|---|
| Observation | The message each participant saw and what they did next |
| Explanation to test | Some readers may not know when the old reservation is replaced. Two observations do not establish how common this is |
| Design task | While users choose a new slot, explain when the original booking stays in place and make it clear whether the change succeeded |
The designer shows the existing and proposed times together on the confirmation page and explains what the next action will do. The prototype also covers failure. If someone takes the new slot before submission and the server confirms that the original reservation is still active, the error state says so and shows how to return to it. The handoff to engineering names the event that triggers each state and the server result used to display it. Paper sketches and clickable prototypes suit different stages of testing. GOV.UK guide to prototyping
In the next test, the designer can suggest revisions while the researcher explains what the evidence supports. If people still fear losing their slot, check whether the task gave any hints, then find out whether users missed the message or saw it and did not trust it. Each finding leads to a different change. Showing the two versions in a portfolio makes your reasoning visible.
How can you identify the main responsibility in a job listing?
Two mainland China examples show how titles can vary. Hebei University of Technology's career site carried a dedicated user research vacancy from Beijing Siming Qichuang that listed in-depth interviews and testing, data analysis, and experience monitoring. A Baidu graduate vacancy in Beijing for a product experience designer listed information architecture, interaction flows, and prototypes alongside user research and usability testing skills. Check what the team expects when you apply. University job listing · Baidu job listing
For an English-language role reference, the UK Government Digital Service separates user research from design on its service teams. User researchers plan and carry out research to inform decisions. Designers design services or interactions and work with researchers and developers. Apply that distinction to a vacancy by circling who owns study design, who turns findings into an interface, and who would review each artifact. A UK consulting vacancy from Triad adds an employer example: it asks a user researcher to choose methods and run interviews and usability testing. The government model and employer listing describe their own setting. Triad user researcher role · GOV.UK service team roles
- Ask who reviews a new hire's first deliverable. Research findings may go to product, design, and business teams. Prototypes and state documentation may also go to engineering and QA.
- Ask what someone in the role shipped recently. When a listing mixes research, insights, and design, real deliverables show which work the role owns.
- Ask how the team decides the work is done. Researchers explain whom they observed, what they recorded, and the limits of their findings. Designers show whether the task works and users can recover from errors.
Use international role guides to compare methods and check job titles against the local market and employer. Both listings are from Beijing, but their duties, recruiting stages, and salary disclosure differ. Compare pay with separate samples for the same city and level that disclose it on the same basis. Web and digital interface designer profile
Make two portfolio pieces from one task
Research sample. Ask two volunteers to try a public reservation page with fictional information and stop before submitting. Record exactly where they pause or go back. Write one page with participant scope, two observations, one possible explanation, and what to test next.
Design sample. Pick one sticking point and make a first and revised design. Include at least one empty or error state. Ask another person to try it and check whether they understand the result. Document their feedback, the reason for your revision, and what remains untested.
Use this caption in either portfolio: Observation → decision → check. For research, pair an anonymized observation with the question you tested next. For design, put it beside the revised state and record what the next tester understood. A before-and-after screenshot alone leaves out why the change was made.
If both jobs appeal to you, ask about the time split and portfolio review in a combined role. Try both exercises before investing in a course. Comparing adjacent design roles can help you connect a finished piece with the role that owns it. Industrial design vs. graphic design · How to evaluate a career-change course · 94-question career assessment
Frequently asked questions
Can one portfolio support both applications? Yes. Lead with the research record for a researcher application and the annotated prototype for a designer application. In both versions, credit everyone who did the work.
How do you build your first case study if you come from operations or customer support?
Start with a task you know well, such as signing up for an event, requesting a refund after a purchase, or giving a new hire access. Pick a clearly bounded step you can recreate with sample materials. Write one sentence of business context, then explain what the user needs to do and what they will see if it succeeds or fails. Redraw the screens yourself and use fictional records to show how you made your decisions.
To try research first, treat past customer feedback as clues. If three people said, “I thought I'd submitted it,” record where each person drew that conclusion. Give a volunteer a neutrally worded task and observe where they stop and where they look for the result. In the case study, identify what you observed directly and which explanation needs another check. In an interview, explain in one sentence how the finding would change the next design discussion.
To try design first, take the same point of confusion and sketch screens for a pending request and a completed request. In one flowchart, show what appears immediately after submission, which status updates later, and how the user can get back to the page. Ask someone to try the flow from the start and revise one thing based on how they understood it. If they realize they submitted the request but have no idea where to check the result, add a way to find the result and keep both versions.
Once you've picked a case study to submit, rehearse your explanation using questions someone in the target role might ask. For research, try “Which observation changed your mind?” For design, try “Why did you put the result message there?” If it was a team effort, add one sentence describing your responsibility and who chose the final approach. Interviewers get something concrete to ask about, and you get a clearer sense of which part you want to explore further.


