Hire a UX designer for the decisions and user problems you need help with. A polished portfolio is useful, but it does not show on its own whether someone can investigate a problem, work within constraints and help your team implement a better experience.
Before opening the role, decide whether you need research, product and interaction design, visual design or a combination. One person may cover several areas, but the expectations should match their experience and available time.
Define the problem before the deliverables.
Low conversion, customer complaints or a difficult mobile journey may justify investigation. They do not prove that a visual redesign is the answer. Product fit, traffic quality, pricing, technical performance and missing information can also affect outcomes.
Write down the journey you want to improve, the evidence available and the decisions the designer will own. For example: understand why users abandon onboarding, test a simpler flow and collaborate with engineering on an implementable solution.
Choose the working arrangement around the work. A focused audit or prototype may suit a project. Ongoing research and product decisions may justify a longer engagement or direct hire.
Ask how the design was reached.
Review a small number of relevant projects in depth. Ask the candidate to explain the initial problem, their personal contribution, the constraints and how the design changed as they learned.
- What evidence supported the problem definition?
- Which alternatives were considered, and why was one chosen?
- How did research participants relate to the intended users?
- What did engineering or commercial constraints change?
- What was implemented, and what outcome was actually measured?
Distinguish a concept, a shipped experience and a measured result. A percentage improvement needs a baseline, measurement period and explanation of other changes. A candidate should be able to describe uncertainty without inventing certainty.
Explore collaboration and practical judgment.
Ask how the person handles disagreement with engineering, incomplete analytics or a stakeholder requesting a solution before the problem is understood. Look for clear reasoning and an ability to work toward a decision.
Include accessibility and responsive behavior in the discussion. The W3C WCAG reference provides requirements relevant to contrast, keyboard access, focus, forms and other interaction details. Ask how the designer considers those needs and works with developers to verify implementation.
Do not assume that attractive desktop screens demonstrate a usable mobile flow. Ask to see loading, error, empty and success states, along with how content changes at smaller sizes.
Use a bounded, job-relevant exercise.
If an exercise is needed, explain the purpose, time expectation and criteria. Use a hypothetical or appropriately sanitized problem, and agree on compensation where appropriate. Avoid asking for a usable redesign of your production product as unpaid hiring work.
Assess the questions the candidate asks, the assumptions they identify and how they explain a next step. A short exercise cannot validate an entire research process or predict commercial results.
Give the designer access to the problem.
Prepare product context, relevant analytics, customer feedback, existing design files and the engineering constraints. Name the decision owner and agree on research access, review cadence, deliverables and implementation responsibilities.
Evaluate the work through better-supported decisions, usable designs and implementation quality. Treat conversion or retention gains as outcomes to measure, not guarantees attached to a job title.
Explore UX/UI design talent or tell Odesa about the user journey and design capability your team needs.
