Start with the problem, not the portfolio
Hiring a Product Designer in Dubai isn't simply about finding someone with beautiful screens.
The right designer should understand users, define problems, work within technical constraints, collaborate across teams, and connect design decisions to business outcomes.
So before reviewing portfolios, ask:
What problem do we actually need this person to solve?
What should you look for?
A strong Product Designer typically combines five capabilities:
Problem-solving
Product and business thinking
UX and UI craft
Communication and collaboration
Evidence of impact
A polished portfolio is useful.
It just isn't enough.
Define what you need first
Different product problems require different skills.
You might need someone to:
design a new product
redesign an existing app
improve conversion
simplify a complex workflow
build a design system
conduct research
improve onboarding
validate a product idea
These aren't interchangeable responsibilities.
A designer who excels at visual execution may not be the right person for an ambiguous product problem.
Define the responsibility before defining the candidate.
Product Designer vs UX Designer vs UI Designer
Titles vary significantly between companies.
Product Designer
Usually works across:
Discovery + UX + UI + Research + Product Decisions + Business Goals + Technical Constraints
UX Designer
Usually focuses more heavily on:
Research + Usability + Information Architecture + User Flows + Interaction Design
UI Designer
Usually focuses more heavily on:
Visual Design + Typography + Layout + Components + Visual Systems
There are no universal boundaries.
Evaluate the responsibilities, not the title.
Don't judge a portfolio by its cover
Beautiful screens show craft.
They don't necessarily show product thinking.
When reviewing a case study, look for:
the original problem
user needs
business context
research
constraints
alternatives
design decisions
iterations
measurable outcomes
The most useful question is:
"Why did you make this decision?"
Then ask:
What alternatives did you consider?
What did you learn from users?
What constraint influenced the decision?
What happened after launch?
You're evaluating reasoning, not just aesthetics.
Look for outcomes, not deliverables
Compare:
"I redesigned the onboarding experience."
with:
"We identified where users were dropping off, simplified the flow, tested the change, and improved completion."
The second connects:
Problem → Decision → Design → Outcome
That's a much stronger signal of Product Design maturity.
Test their product thinking
Don't ask only:
"How would you redesign this screen?"
Ask:
"If you joined our team tomorrow, where would you start?"
A strong designer may want to understand:
users
business objectives
analytics
customer friction
technical constraints
before proposing a redesign.
That's Product Thinking.
The designer isn't rushing to decorate the problem.
They're trying to understand it.
Look for judgment, not perfection
Real products have constraints.
There isn't unlimited:
time
engineering capacity
research
budget
Ask:
"Tell me about a time you had to compromise on your original design."
Then:
"What did you prioritize, and why?"
You're looking for judgment.
A designer who claims every project went perfectly has either achieved enlightenment or edited the case study very aggressively.
Evaluate collaboration
Product Designers work with Product, Engineering, Research, Marketing, Data, leadership, and sometimes customers.
Ask:
"Tell me about a time an engineer disagreed with your design."
Or:
"What do you do when a stakeholder requests something you believe is bad for the user?"
Look for someone who can defend their reasoning without becoming impossible to work with.
Check how they work with engineers
A design that only works inside Figma isn't a finished product experience.
Ask about:
developer handoff
technical constraints
design QA
reusable components
edge cases
responsive behavior
accessibility
Strong Product Designers understand that good design has to survive implementation.
Consider the Dubai context
Dubai's digital product landscape spans:
fintech
retail
e-commerce
mobility
real estate
hospitality
government services
logistics
SaaS
Industry experience can help, but the ability to learn a new domain quickly can matter more.
For products serving Arabic and English-speaking users, also consider experience with:
Arabic UX + RTL + bilingual interfaces + localization
RTL isn't simply flipping the interface horizontally. It can affect hierarchy, typography, navigation, alignment, and interaction patterns.
Match seniority to the problem
Don't automatically hire the most senior designer you can afford.
Match seniority to responsibility.
Junior → execution support and structured environments
Mid-level → feature ownership and independent UX/UI work
Senior → ambiguous problems, discovery, strategy, and stakeholder alignment
Lead / Staff → broader design direction, systems, and organizational problems
The better question isn't:
"How many years of experience do they have?"
It's:
"What decisions do we expect this person to make independently?"
Watch for portfolio red flags
Be cautious when a portfolio has:
only final screens
no explanation of decisions
no visible constraints
no collaboration
no outcomes
excessive visual polish with little reasoning
projects where everything magically succeeded
A strong case study doesn't need to pretend the designer is a flawless superhero.
Good designers can explain what went wrong, what changed, and what they learned.
Five questions worth asking
Instead of asking about someone's favorite design tool, ask:
Tell me about a product problem you initially misunderstood.
What changed in your design because of user research?
What design decision was hardest to make?
What did you intentionally leave out?
How did you measure whether your design worked?
These questions reveal much more than asking someone to explain their Figma workflow.
A simple evaluation framework
Score candidates across six areas:
Area | What to evaluate |
|---|---|
Product Thinking | Problems, goals, trade-offs |
UX | Clear, usable experiences |
UI | Visual and interaction craft |
Research | Evidence-based decisions |
Collaboration | Cross-functional communication |
Impact | Measurable outcomes |
Don't let exceptional UI hide weak product thinking, or exceptional strategy hide weak execution.
The right Product Designer depends on your stage
Early-stage startup
Look for versatility:
Research → Define → Design → Prototype → Validate → Ship
Growing product team
Look for designers who can own product areas while working within established systems.
Large organization
You may need greater specialization across:
Product Design
UX Research
Design Systems
Content Design
Design Operations
Design Leadership
The best Product Designer is therefore contextual.
How to make the final decision
Don't ask:
"Who did we like the most?"
Ask:
"Who is most capable of solving the problems we need solved?"
Then compare candidates against:
Role requirements + Seniority + Portfolio evidence + Product Thinking + Collaboration + Technical understanding + Expected outcomes
That makes the hiring decision much more objective.
Takeaway
Choosing a Product Designer in Dubai isn't about finding the person with the most impressive Figma file.
It's about finding someone who can understand your problem and help your team make better product decisions.
Look for:
Problem-solving + UX + UI + Product Thinking + Collaboration + Impact
Review the reasoning behind the work, not just the final screens.
And most importantly:
Hire for the problems you need solved, not the title you think you need.
A great Product Designer doesn't simply make your product look better.
They help make the product better.
