A UX/UI Portfolio That Tells the Story of Your Decisions
A recruiter abroad skims dozens of portfolios and looks for a line of reasoning. For each project, set out the starting problem, the people affected, your constraints and the result you observed. The final screens come last, as proof of a process rather than as the starting point.
Three to five well-documented projects are enough. Choose them to show different situations: a complex user journey, a redesign, a mobile product, a component system. An opening sentence in English, or in the language of the job, helps the reader understand the context before diving into the details.
- The user problem stated in one sentence
- Your exact role and the scope of your contribution
- The research methods you used
- Options you rejected and why you chose the final one
- Effects observed after the product went live
Showing User Research Without Breaking Confidentiality
Projects done for an employer or a client are often covered by non-disclosure agreements. You can still present your method by blurring data, renaming the product or rebuilding a case from the original structure. State these adaptations clearly so that you stay honest.
Avoid publishing identifiable quotes or screenshots of internal tools. If a project cannot be shown at all, offer to talk it through in the interview, without slides. Product teams understand this constraint, provided you mention it from the start and keep at least one public project on which they can judge your work.
The Design Challenge and the Team Interview: Getting Ready
Many companies ask for an exercise: analysing an existing app, designing a flow from a brief, or critiquing an interface. Ask the recruiter how much time is expected and what the assessment criteria are. A task that is too long and unpaid deserves a conversation rather than silent acceptance.
During the presentation, the focus is on your reasoning: the assumptions you made, the trade-offs you accepted, how you respond to objections. Practise presenting in ten minutes, then defending a choice in front of a developer or a product manager. Admitting what you would test next shows a maturity that screens alone cannot prove.
Design, Product and Engineering: How the Team Settles Trade-Offs Every Day
The job has a different content depending on whether you join an integrated product team, an agency or an in-house department. Ask who decides the priorities, how deadlines are negotiated with developers and at what point design enters the roadmap. These answers tell you more than the job description does.
Find out about the tools, the review rituals and the role given to research. In some organisations the designer delivers mock-ups on a conveyor belt; in others they help define the product. Choose with your eyes open, because the gap in responsibilities shapes the work as much as the salary does.
Accessibility, Component Systems and Testing: What Shapes Your Days
A shared component system requires discipline: naming, documentation, contributions from other teams. Ask whether the system exists, who maintains it and how it is versioned. In an organisation without one, you will spend more time rebuilding elements that already exist.
Accessibility is a legal or contractual requirement in some countries and for some audiences. Check how the team tests for it, with which tools and with what support. User testing, whether regular or occasional, determines how much research there is in your job, so ask how often sessions are held and who runs them.
- A documented component library, or none
- Accessibility criteria applied before release
- Frequency and format of user testing
- Working relationship with front-end developers
Markets, Languages and Habits: The Cultural Angle of the Job
Designing for a foreign audience forces you to question your reflexes: reading direction, date and address formats, payment methods, attitudes to trust online. If the job targets a market different from yours, ask how the team gathers local knowledge and who reviews your proposals.
The language of research interviews matters too. A designer who cannot follow the participants depends on an intermediary and loses nuance. State your real level in each language and ask whether the job includes live sessions. Your command of French or other languages may turn out to be a specific asset.
A Designer’s Status and Contract: Employee, Freelancer or Contractor
A designer sometimes works as an employee and sometimes as a freelancer billing by the project. The two arrangements do not carry the same rights regarding social protection, paid leave and ownership of deliverables. Ask for the proposed status and the contractual place of work before agreeing.
Check the clause on copyright and usage of your creations, whether you may show the work in your portfolio, and the rules on side activities. If you plan to move, ask the immigration authority of the country: a remote-work advert does not automatically give you the right to live there.
An Action Plan for Looking for a UX/UI Job Outside Your Home Country
First pick two or three countries and a type of employer, for instance software products, online retail or digital services. Adapt your portfolio to each target by moving the project closest to that sector to the top. Follow the careers pages of companies such as Booking, Datadog or Google to understand the level expected.
Then prepare your references, a summary in English and a calendar of your availability. After each interview, note the questions you were asked so you can improve your presentation. Compare offers on the content of the job, the contract and the conditions of stay before you hand in your notice to your current employer.
Frequently asked questions
How many projects should a UX/UI portfolio include?
Three to five detailed projects are better than a long gallery. Choose different cases to show the range of your practice, and document the problem, your role, the method and the result for each. A less flashy project that is well explained convinces more than a visual with no context.
Do I need an English portfolio to apply outside my home country?
In most international companies, yes, at least for the summary and the project titles. For a job in a country where another language is used at work, a version in that language is an advantage. Keep an identical structure in every version to avoid differences in meaning.
Can I show a project I did for a former employer?
Only if your confidentiality obligations allow it. Otherwise anonymise the data, change the brands or rebuild an equivalent case and say so. You can also present the process orally in the interview. If in doubt, reread your contract or ask the former employer for written consent.
Is an unpaid design exercise normal?
A short, well-defined exercise is part of many hiring processes. A long task that looks like real client work is a concern. Ask about the expected duration, the assessment criteria and how your output will be used. You can offer a shorter version or decline if the terms seem unbalanced.