Thinking About Becoming a UX Designer? Ask Yourself These Questions First

What the Job Actually Involves Day to Day

The two tasks ONET lists for this occupation describe most of the job: "Conduct user research to determine design requirements and analyze user feedback to improve design quality," and "Develop new visual design concepts and modify concepts based on stakeholder feedback" (ONET OnLine, U.S. Department of Labor). In practice that breaks into a repeating set of jobs:

• Running user interviews and usability sessions, usually over Zoom or Teams, with a written script and a recording you then watch back. Sessions typically run 30 to 60 minutes each, and a round of five to eight of them eats most of a week.
• Synthesising those recordings into themes — sticky notes in FigJam or Miro, quotes in a spreadsheet, and a short findings document that names the top problems in order.
• Drawing and redrawing screens in Figma, which O*NET lists as a Hot Technology for this occupation. You will maintain components, keep a shared library tidy, and version files so a developer can tell which frame is current.
• Walking stakeholders through work and changing it afterwards — design critiques, sprint reviews, and comment threads left on your Figma file by product managers, engineers and legal.
• Writing tickets and acceptance notes, commonly in Jira or Linear, so an engineer knows what the hover state does and what happens when the form fails.
• Answering questions in Slack about spacing, copy and edge cases while someone builds the thing you drew last month.

The meeting load depends heavily on employer type. In-house product roles at larger organisations tend to be calendar-heavy — standups, refinement, critique, one-to-ones — and design work gets squeezed into whatever blocks survive. Agency and contract work usually flips that: fewer internal rituals, more concentrated solo production, and client presentations clustered at the end of a phase. Ask about this directly in interviews; the answer differs between two companies in the same city, let alone between a startup and a bank.

Signs This Career Fits You

• You have already redesigned something at work nobody asked you to redesign — an intake form, a shift rota, a spreadsheet — and you can describe the before and after.
• You have come off a complaint call and written down why the customer got confused, not just how you fixed it for them.
• You have had a piece of your work pulled apart in front of other people and changed it afterwards without relitigating it.
• You can go three days producing only notes and a document, with no finished artefact, and not feel like the week was wasted.
• You are comfortable asking a stranger the same question four different ways for 45 minutes while a recorder runs.
• You have sat between two teams that wanted opposite things and written the summary everyone then worked from.
• You poke at software for fun — you have mapped out a tool's settings menu or explained to a colleague why an app's checkout is confusing.

Signs It Might Not Be a Fit

• You want your output to be final. One of the two core tasks for this occupation is modifying concepts based on stakeholder feedback (O*NET OnLine), which means work you considered finished gets reopened routinely.
• You dislike ending a day with nothing shippable. Research weeks produce documents, not screens.
• Talking to strangers drains you. Moderated interviews and usability tests are a recurring, scheduled part of the job, not an occasional extra.
• You need a predictable, posted pay figure. Compensation is typically a base salary plus any bonus or equity in product roles, or hourly and project rates in contract work, and it moves with state, employer size and seniority — the BLS Occupational Outlook Handbook publishes a 2025 median annual wage for web developers and digital designers, and CareerOneStop publishes a median hourly wage for Web and Digital Interface Designers; look both up for your state before you commit.
• You cannot give up roughly 10 hours a week for about six months of evenings and weekends, which is the recommended pace for the Google UX Design Professional Certificate (shortcoursesportal).
• You would rather not write. Findings documents, ticket descriptions and rationale notes are a large share of the output.

Skills You Already Have vs. Skills You'll Need to Build

How to Test the Waters Before You Commit

1. Read the occupation entry and score the tasks. Open O*NET OnLine's page for 15-1255.00, Web and Digital Interface Designers — the one that lists UX Designer as an alternate title — and mark each listed task as "would do willingly," "tolerable," or "no." 30 minutes, free. Outcome: a one-page list you can show to someone already in the job.
2. Look up the pay yourself, for your state. Check the BLS Occupational Outlook Handbook 2025 median pay for web developers and digital designers and the CareerOneStop median hourly wage for this occupation, filtered to your state. 20 minutes, free. Outcome: two numbers written down, not a vague impression.
3. Build one Figma rebuild project. Pick three screens from an app you use and redraw them, then write 200 words on what you changed and why. Figma has a free tier; budget 8-12 hours across two weekends. Outcome: a shareable file and a short rationale note.
4. Run three informational interviews. Ask each person how many hours a day they spend in meetings and how often finished work gets reopened. 30 minutes each, two to three weeks to schedule, free. Outcome: three sets of notes and a clearer picture of the meeting load at different employer sizes.
5. Use a free trial before paying for a certificate. The Google UX Design Professional Certificate is priced as a flat monthly Coursera subscription after a free trial period (Designlab); finish the first of its 7 courses inside the trial and check the current monthly price before continuing. Outcome: a completed first course and a decision based on the real syllabus.
6. Do one volunteer usability review. Offer a local nonprofit or community group a written review of a single page — donation form, signup, contact page. 6-8 hours total, free. Outcome: a findings document listing five problems ranked by severity, which is also your first portfolio piece.