UX Researcher

Our clients' users are dispatchers, traders, support agents and travelers: people with a job to finish and no patience for software that gets in the way. You'd spend time with them, then turn what you learn into something the team can act on this week.

This is applied research on a delivery schedule. Studies run in days instead of months, findings land before the decision is made, and you follow up to see whether the change worked.

You'd work across engagements with designers and delivery leads, and sit in the client conversations where assumptions get made out loud.

Models do the mechanical half of research here: transcripts, first-pass coding of themes, summaries. You check them against the recordings instead of trusting them on sight.

• Choose the right method. Interviews, usability sessions, diary studies, or an afternoon watching someone work.
• Recruit the hard-to-reach. Including the shift worker inside a client's operation who has never been asked before.
• Turn sessions into decisions. Findings with evidence attached and the uncertainty stated plainly.
• Test early, while it's cheap. Usability work on things still in progress, not on the week of launch.
• Check afterwards. Did the change do what we expected? Say so either way.

• Two Years of Product Research: studies you ran end to end, not just notes you took for someone else.
• Recruitment Reality: you find eight relevant participants in a niche B2B market, not eighty students.
• Analysis You Can Show: transcripts coded, themes traceable to quotes, conclusions someone else could audit.
• Usability Testing Craft: moderated and unmoderated, with tasks that reveal behavior rather than flatter the design.
• Surveys Without Leading: sampling, question order, and the discipline to avoid asking what you hope to hear.
• Research Ops Basics: a repository, consent records, incentives, and a retention policy that exists.
• Quant Comfort: funnels, analytics, and enough statistics to know when a difference is just noise.
• Method Range: and the judgment to pick the cheapest one that answers the question.
• Room Reader: you get value from a session with a senior stakeholder and from one with a night-shift dispatcher.
• Findings People Read: short, specific, and hard to ignore.
• Delivers Unwelcome News: with the evidence in hand and the relationship intact.
• Fluent English, Written and Spoken: most of our work happens in a written thread or on a call, and both have to be clear. Arabic is a genuine advantage across the region.
• AI-Assisted Analysis: you speed up synthesis with models and stay the person accountable for what the findings claim.

• Curious: you like people's work stories more than your own hypotheses.
• Rigorous: you separate what you saw from what you concluded.
• Fast: a useful answer this week beats a perfect one next month.

• Quantitative work: surveys, analytics, simple experiments.
• Research inside enterprise or operational settings instead of consumer apps.
• Accessibility research with assistive technology users.

• Remote across MENA. Work from wherever you are in the region, with hours built around your team's overlap rather than someone's attendance spreadsheet.
• Work that ships. Products go live in weeks, not quarters. When someone asks what you have been building, you can open it on your phone and show them.
• Small teams, no ticket queue. Four to eight people carry a product from the first client call to handover. Nobody hands you a spec and disappears.
• Kit and tools you choose. A budget for your setup, and for the editor, licenses and services that make you fast. No three-week procurement saga.
• A learning budget with time attached. Money for the course or the conference, plus room in the week to use it. The second half is the part most places skip.
• Client contact from day one. You sit in the room where the decisions get made. Plenty of engineers wait a decade for that seat.
• Time off people take, and no timesheets. We measure engagements, not humans in fifteen-minute increments. Book the holiday, go, come back.