01
About the role
AI products break the usual product playbook: the system is probabilistic, the quality bar is a distribution rather than a pass, and users trust it too much on Monday and not at all on Tuesday. You'd own products in that world.
You'd work with the client's stakeholders and our engineers to decide scope, success measures and guardrails, then live with the result: reading transcripts, watching evaluations, and deciding what ships next.
You'd use these tools daily yourself. It's the only way to have useful instincts about what they can and can't do.
02
What you'll do
- Decide what it's for. The job the product does, the cases it refuses, and the ones we route to a person.
- Set the quality bar. With the evaluation engineer: what good means, measured, before launch instead of after complaints.
- Sequence the work. What ships first, what waits, and which impressive feature isn't worth its failure modes.
- Own the feedback loop. Transcripts, evaluations, support tickets and usage, turned into the next two weeks of work.
- Keep stakeholders grounded. Including the executive who saw a demo and now wants it for everything by Friday.
03
What we look for
- Four Years in Product Management: with at least one AI or data-heavy product shipped to real users.
- Writes the Eval Before the Feature: what good looks like, defined and measurable, before anyone builds it.
- Model Economics: tokens, latency and unit cost carried into the roadmap, not discovered in the invoice.
- Data and Consent Strategy: what may be trained on, what may be logged, and who has to agree to it.
- Scope and Refusal Design: what the product deliberately won't do, written down and defended in the room.
- Analytics Fluency: instrumentation, funnels, and the query you run yourself at 9pm instead of requesting it.
- Discovery With Users: interviews and usability sessions you ran, not ones you read about in a deck.
- Roadmaps Under Uncertainty: sequencing work when the underlying capability may change under you next quarter.
- Technically Credible: you can discuss retrieval, evaluation and latency without needing a translator.
- Measurement First: you define success in numbers before the build starts.
- Risk Literate: hallucination, bias, privacy and the reputational cost of a bad answer.
- Client-Facing Confidence: you can say no to a senior stakeholder and keep them on side.
- 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 in the Loop: you use these tools daily and have opinions formed by use rather than by conference talks.
04
Personal traits
- Decisive: you make the call with the evidence available and revisit it when more arrives.
- Curious about users: you read the transcripts yourself instead of the summary of the summary.
- Straight talking: you'd rather disappoint early than surprise late.
05
Nice to have
- Support, operations or fintech domain experience.
- You have retired an AI feature that wasn't working, and handled the politics.
- Arabic-speaking markets and the product questions they raise.
06
Why you'd like it here
- 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.