Understand UX, UI and product design
UX work can include research, information organisation, task flows and usability testing. UI design concentrates on interface details such as typography, spacing and states. Product-design roles often combine these responsibilities. O*NET's digital-interface profile covers designing and testing layouts, navigation and usability across devices.
Titles are inconsistent between employers. Read whether the vacancy expects research, visual design, prototyping, frontend knowledge or all of these. A portfolio should demonstrate the relevant work rather than relying on a job title alone.
Learn observation before decoration
Practise writing a research question and observing how someone attempts a task. Separate what you saw from what you assume. Turn the findings into a flow, sketch alternatives and test a rough prototype before spending time on polished screens.
Learn interface fundamentals, responsive behaviour and accessibility. Include keyboard use, readable contrast, clear labels and helpful error messages in your reviews. Become competent with a design tool, but remember that a tool certificate says little about the quality of your decisions.
Choose a learning route with feedback
Design, computing, psychology and business backgrounds can contribute different strengths. There is no single universal degree requirement across UX vacancies. A structured course can help if it includes research practice, critique and repeated revision.
Ask whether students work on original problems, speak to appropriate participants with consent and explain their decisions. Compare the mentor-feedback process and the portfolio expectations. A course that only teaches a tool may leave important gaps in research, interaction design and working with developers.
Build one honest case study
Choose a manageable task, such as finding a course timetable or rescheduling a fictional appointment. Describe the context and constraints. Interview a small suitable group with consent, test an existing flow where appropriate and identify a specific friction point.
Create two possible approaches, explain the trade-off and test the preferred prototype. Include loading, empty, error and success states. Report what changed after feedback and what you could not validate. Do not invent interview participants, usability results or business impact. A clear account of limited evidence is more credible than exaggerated certainty.
Find an entry role and assess the offer
Look for UX intern, junior product designer, UI designer and research-assistant roles aligned with your strengths. Practise presenting a case study in ten minutes and answering why you rejected an alternative. Show collaboration and willingness to revise, not only finished screens.
When comparing compensation, check the city, employment type, role scope and experience expectation. Clarify whether the position includes design review and mentorship. A broad sole-designer role can be demanding for a beginner even if its title sounds attractive. No portfolio course can promise a particular salary or hiring outcome.
Common questions
Do UX designers need to code?
Not every role requires coding, but understanding how interfaces are built can improve collaboration and feasibility decisions. Check the requirements of the roles you want.
How many portfolio projects should I create?
Start with one complete, honest case study that shows your process and revisions. Add a second project when it demonstrates a different problem or skill rather than repeating the same template.
Sources & further reading
Official sources inform factual references. Practical exercises and comparison checklists are Degree360’s editorial guidance. Confirm changing programme details on the source website before applying.
Read our editorial policyKeep your next step practical.
Explore the relevant courses and tools, or save your questions in a guidance enquiry.