Lead Product Manager

Most platform jobs are maintenance work on foundations somebody else poured. This one is not.

DigitalZone runs a digital goods and top-up business, a ticketing platform and a regulated trading venue across Iraq and the region. Today they share rails that were built to serve one product and now serve four. Your job is to turn that into a real platform: payments that move customer money reliably, an identity that belongs to us rather than being borrowed from a partner, and marketing technology that can reach and personalise for every customer we have.

Get it right and four product squads move faster than they could alone. Get it wrong and nobody ships, and everyone blames the roadmap.

The hard part

Payments here are not a Stripe integration. It is a cash-heavy market, local rails, telecom billing, agent networks, and fraud that adapts faster than the release cycle. Every control you add prevents loss and costs conversion, and you will be the one who has to say which number wins.

Identity is harder still. A large share of our customers reach us through a partner's login today. Migrating them to an identity we own, without losing them on the way across, is the single most consequential product problem in the company. It has no clean playbook and no second attempt.

What you'll do

Own the roadmap across payments (orchestration, rail integrations, authorisation rates, retries and routing, refunds, disputes, reconciliation), identity (company-owned identity, one unified profile, verified contact and consent) and marketing technology (event and campaign infrastructure, direct reach, attribution, personalisation delivery).

Run the payment funnel as numbers: authorisation rate by rail, failure taxonomy, cost per transaction, fraud loss and chargebacks against the friction each control adds.

Take company-owned identity from near zero to the majority of monthly actives, including the migration path and the day the partner login stops being the front door.

Treat the vertical squads as your customers: contracts, docs, self-serve, measured adoption, and no tolerance for four half-maintained copies of the same capability.