01
About the role
An AI product is mostly writing. What it says first, how it asks for a missing detail, how it declines, and how it hands over to a person without making the customer repeat themselves. Get that wrong and no model saves you.
You'd design conversational products with the AI engineers: flows, prompts, tone, error and refusal behavior, and the interface around the conversation. Then you'd sit with transcripts and fix what real users hit.
You'd use models constantly to draft variations, then apply the judgment that decides which one a bank or an airline can say.
02
What you'll do
- Define the persona and the limits. What it does, what it refuses, and how it sounds while doing either.
- Write the conversation. Openings, clarifying questions, confirmations, apologies, and the handover to a human.
- Design for being wrong. Uncertainty, citations, and a way for the user to check or escalate.
- Work the transcripts. Read real conversations weekly and turn failures into prompt or flow changes.
- Shape the surrounding interface. With the product designer, because a chat box alone is rarely the answer.
03
What we look for
- Three Years in Content Design, UX Writing or Conversation Design: with shipped products behind you.
- System Prompt Architecture: persona, scope, refusals and tone, written as something engineers can version.
- Flow Design: happy paths, repair, escalation, and a handover to a human that doesn't lose the context.
- Refusal and Error Copy: what it says when it can't help, without sounding either robotic or groveling.
- Voice and Tone Systems: a spoken style guide per client, applied consistently across hundreds of responses.
- Reads Transcripts Weekly: changes traced back to what people typed, not to what we assumed they would.
- Works in the Repo: prompts and copy in source control, reviewed like code rather than pasted from a document.
- Multilingual Awareness: what changes when the same assistant answers in Arabic, and what you can't assume carries over.
- Prompt Craft: you write prompts as a design material and can explain why one version behaves better.
- Editorial Judgment: tone, brevity, and the discipline to cut a sentence the model was proud of.
- Works From Evidence: transcripts and evaluations guide your changes, not taste alone.
- Comfortable With Engineers: you can read a prompt template in a repository and suggest the change yourself.
- 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 generate options at volume and edit hard, which is the job now.
04
Personal traits
- Precise: you care about the difference between sorry and unfortunately.
- Empathetic: you design for the person who's already annoyed before they typed anything.
- Collaborative: you work inside the engineering loop instead of handing over a document.
05
Nice to have
- Arabic and English conversation design, including dialect considerations.
- Voice products as well as chat.
- Regulated industries, where refusals matter as much as answers.
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.