Product Designer

The work is functional and detailed: trading interfaces, freight dashboards, support consoles, onboarding flows with more edge cases than happy paths. The craft is making density feel calm and the right action obvious to someone tired, busy and mid-shift.

You'd work across two client products at a time, with the engineers who build your designs, not at a polite distance from them. Figma, prototypes in code when they help, and a component library handed over instead of a specification nobody reads.

Clients often arrive with an existing product and firm opinions. Part of the job is turning those into decisions they can live with.

Design gets agents too: the twentieth variation, the copy drafts, a sketch turned into a clickable prototype before lunch. Taste and judgment stay yours.

• Run discovery. Workshops that produce flows, wireframes and a plan people agree on.
• Design the whole surface. High fidelity interfaces plus the states nobody thinks to ask for: empty, error, partial, enormous.
• Sit with the build. Stay close to the engineers and adjust when the constraints turn out different from the assumption.
• Test with real users. Bring back what you learned and change your mind in public when you were wrong.
• Keep it usable by everyone. Contrast, focus order, and words that make sense to someone on their first day.
• Present to clients. Including the ones who wanted it blue, and the ones who mean something specific by clean.

• Three Years of Shipped Product Design: ideally B2B or data-heavy, ideally still in use.
• Design Systems in Practice: tokens, components and documentation that survive contact with the engineers using them.
• Prototyping Range: from a gray-box flow in an hour to something clickable a client can test on Friday.
• Dense Data Layouts: tables, filters, dashboards and forms with forty fields, made to feel calm.
• Accessibility in the File: contrast, focus order, target sizes and states specified before anyone has to ask.
• Handoff That Works: specs, states and edge cases documented so an engineer never has to guess.
• Motion With A Purpose: transitions that explain what just happened rather than decorate it.
• Typographic Backbone: layout and type fundamentals you can defend out loud, not just feel.
• Figma to a Professional Standard: components, variables and files other people can pick up without a tour.
• Comfortable With Pushback: from engineers, from clients, from the data.
• Tests Designs: you have watched users struggle with your work and changed it accordingly.
• Writes Well: half of design is naming things, and names are writing.
• 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 as a Sketchpad: you generate options fast, then edit without mercy. Volume is cheap now, judgment isn't.

• Curious about the domain: you want to understand freight or trading, not just style it.
• Collaborative: you'd rather design with an engineer than hand over to one.
• Detail-driven: the 4px bothers you, and you fix it without being asked.

• Enough CSS or React to prototype your own ideas.
• Motion design used with restraint.
• Fintech, logistics or another dense domain.

• 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.