Hire Product Designer — from user research to shipped interface

It depends on risk. Redesigning a known flow can start from analytics; building something new without talking to users is how expensive mistakes happen. I will tell you honestly which you need.

As a partner from the flows stage — technical constraints surface early, handoff is spec’d properly, and design QA runs through the build.

Yes — extending systems is standard. Where the system is the problem, I will show you and scope the fix separately.

Specs, assets at correct densities, interaction notes, and a walkthrough — everything engineering needs to build without reverse-engineering intent from pixels.

A focused feature (research to handoff) typically runs four to eight weeks; full product design engagements are scoped by roadmap after discovery.

I price by engagement, not by hour, so incentives stay aligned with shipping. A validated prototype or a single funnel redesign is usually a fixed-scope project; ongoing product design runs as a monthly fractional retainer with a defined number of days. When you hire a product designer who is also a CTO, you are paying one senior rate instead of a designer plus the engineering translation layer. I give you the number before we start, after a short scoping call, so there are no surprises.

Most of the value in product design is front-loaded - discovery, flows, a design system - and then the cadence drops. Hiring a full-timer for that shape means paying for troughs. A fractional arrangement lets you hire a product designer for the intense setup and keep a lighter retainer for iteration and design QA. If your product reaches a point where design is genuinely full-time work, I will tell you, help you write the job spec, and interview candidates with you.

A UX designer typically owns research and interaction; a UI designer owns the visual layer; a product manager owns the roadmap and the business case. When you hire a product designer in the sense I practise, you get the first two in one person, working tightly with whoever owns the third. On a small team I will happily carry some product-management weight - writing the metric, prioritising the backlog - but I am clear about where my remit ends so nothing falls through a gap.

Yes, and this is where hiring a designer with fifteen years of engineering pays off. I can take a design through to production React, Next.js or React Native, wire the components to your API, and set up the Storybook and token pipeline that keeps design and code in sync. For many clients I design and implement the critical path myself, which removes the handoff drift entirely. For larger builds I design, spec and then work alongside your engineers through QA.

Before I design anything we agree the metric it should move and I build the analytics events into the design, usually through Amplitude, PostHog or Mixpanel. After launch we read the funnel and session replays against the baseline we recorded first. I would rather ship behind a feature flag and compare cohorts than argue about taste. If a change did not move the number, I say so and we iterate, because the point of hiring a product designer is business outcomes, not a nicer-looking screenshot.

Yes. Serving the UAE and wider Gulf markets means designing for Arabic and right-to-left from the start, not bolting it on, so I build mirrored layouts, bidirectional text handling and locale-aware components into the system. I design to WCAG AA as a default - contrast, focus order, keyboard paths, reduced-motion - because accessibility is both a legal and a usability concern. If you are expanding across UAE, UK, US and South Asian markets, I design one system that flexes across all of them.