I would run Careem's AI-native transformation the way Careem builds product: inside the workflow, shipping.
I am a transformation operator who does not just scope AI programs, I build and ship them myself. Ten-plus years of operating-model and venture change, and AI products I have taken end to end. I am moving to Dubai to do exactly this work.
Straight up: the Applied AI Manager req has closed. I built this anyway, because it is the actual week-two work, and because WorkOS says Careem is not slowing this down. Treat it as me raising my hand for where this goes next.
The Redesign Desk
The job names one judgment above all others: for a given workflow, do you augment it (AI-enabled, keep the process, add a copilot) or rewrite it (AI-native, zero-base it around agents)? Pick a real Careem workflow, make the call, and watch the system, the stack, the ROI, the rollout and the guardrails change with it. This is the meeting we would have in week two.
Captain support at 50k tickets a day
Every claim on that desk has a receipt.
The desk works because I have done the parts it is made of: reading a business for where the value is, building the thing, and getting people to actually use it. Left is the claim, right is the engagement that backs it.
Three things you would rightly want to pin down.
I would rather name the gaps than have you find them. Here they are, with the counterweight.
This is a work sample, not a brochure.
I designed and built this whole page, and the logic inside the Redesign Desk, with the same AI toolchain I would bring to Careem: Claude Code plus my own prompt and automation stack. The desk is not a slide of a demo. It runs real logic, recomputes real trade-offs, and cites its sources.
If you want to know how I would work on your Care queue or your Pay disputes, you are already looking at it. This took an afternoon. Imagine it pointed at your real data.
Careem is putting agents into Care, Pay, Food and People. I want to be the operator who ships them.
The role I clicked has closed, so this is me reaching out directly. If WorkOS or the AI-native transformation work has room for someone who makes the augment-versus-rewrite call and then builds it, let's talk. Fifteen minutes is plenty to start.
scan for LinkedIn