Over 100,000 merchants run their businesses on Salla. The largest and most complex of them , holding companies, multi-brand groups, franchises, and cross-border operators , have grown into a level of operational complexity that calls for a dedicated enterprise layer: purpose-built capability on top of a platform that already runs their commerce.

This role owns that segment end-to-end. You will define what "enterprise" means at Salla in terms of needs, not labels: multi-storefront, multi-entity permissioning, headless and API-driven operations, reliability backed by service-level commitments, and merchants running several markets from one account. You lead a dedicated enterprise engineering pod as its one accountable product owner, and you feed into the commercial line: which capabilities justify the enterprise tier, and where the line sits. Few product roles let you define a segment, build it, and shape how it is priced at the same time. This one does.

You will need to hold one tension permanently: meet enterprise complexity through extensible platform capability, never through bespoke one-offs that fork the codebase.

You will drive impact across four major domains:

• Enterprise Strategy and Packaging (segment definition, roadmap, tier gating, rate limits)
• Delivery Through a Dedicated Pod (one accountable product owner from discovery to release)
• Multi-Market Capability (multi-currency, multi-tax including ZATCA and Gulf equivalents, per-market payment rails, cross-border)
• Agent and API Readiness (making enterprise merchants the proving ground for emerging agentic commerce protocols)

Responsibilities:

• Own the strategy and roadmap for the enterprise segment, prioritized by retention and expansion impact, not feature count.
• Run deep discovery with enterprise merchants and convert organizational, business-model, and market complexity into an evidenced, defensible requirement set.
• Lead the dedicated enterprise engineering pod as its one accountable product owner: discovery, specification, prioritization, execution, release.
• Ship enterprise-grade capability: multi-storefront, headless and API-first operation, role-based access and approvals, reliability and performance at scale.
• Own the capabilities that let one merchant run multiple markets from one account: multi-currency, multi-tax compliance, per-market payment rails, cross-border operation.
• Feed capability and feature-gating decisions into enterprise packaging, including where rate limits sit.
• Guard against platform forking: meet enterprise needs through reusable capability, with domain teams retaining architectural review rights.
• Own enterprise success metrics with the data team: capability adoption, net revenue retention contribution, enterprise win rate, time-to-value for complex onboarding.

Requirements

• Proven ownership of an enterprise or top tier on a multi-tenant software or commerce platform, with the retention or expansion metrics you delivered.

• Deep hands-on fluency in at least two of: multi-storefront architecture, headless and API-first commerce, role-based access and approval systems, multi-currency and multi-tax operation.

• Track record converting messy enterprise discovery into prioritized requirements that engineering respected.

• Commercial packaging judgment: you have decided which capabilities gate a tier and where rate limits sit, and defended the line.

• Experience operating as the single product owner for a dedicated engineering pod across two-to-four-quarter horizons.

• A demonstrated bias for platform capability over bespoke delivery, with a real example of saying no to a large account.

• Strong analytical mindset, comfortable instrumenting segment economics per account.
• Six or more years in product management; exposure to agentic commerce protocols or building for AI agents is a plus.
• Full professional fluency in Arabic and English is required; Gulf market experience is preferred over theoretical knowledge. Willing to relocate to Saudi Arabia.