About UsWe are a product software company building two enterprise SaaS platforms used by manufacturers, regulators, and supply chain partners across the region:Track & Trace (L3/L4) — a serialization and traceability platform for regulated markets, connecting manufacturers to national reporting hubs and ensuring end-to-end product authenticity and compliance.Supply Chain Visibility & Loyalty — an engagement and incentive platform for unregulated industries, helping manufacturers build connected networks from distribution through to the end customer.Both platforms are built on the Microsoft technology stack and are expanding commercially across the MENA region. We're now investing in the leadership layer that will scale our engineering organization to match.The RoleWe are hiring an Engineering & Architecture Director to lead our engineering chapters and build our architecture practice. This is a leader-of-leaders role: you will manage the chapter heads for Frontend, Backend, Mobile, and QC, stand up and grow the Architecture chapter, and own how engineering delivers — predictably, at quality, and in step with our product and delivery organizations.You will sit on the technology leadership team alongside the Product head, the Delivery & Support head, and the Platform/DevOps head, all reporting to the CTO. Platform and infrastructure are owned by a peer — your focus is people, architecture governance, and delivery execution.What You'll OwnPeople & OrganizationLead, coach, and develop the engineering chapter heads (Frontend, Backend, Mobile, QC); own performance, growth paths, and succession across the chapters.Build the Architecture chapter from the ground up: hire its lead, define its charter and decision rights, and ensure architects stay embedded with delivery squads rather than isolated from them.Own hiring standards, engineering career frameworks, and the health of the engineering organization as it scales.Architecture Governance & SupportEstablish lightweight, effective architecture governance: decision records, review cadences, reference patterns, and a clear exception process — rigor without bureaucracy.Steward our core architectural direction (Clean Architecture, domain-driven design, event-driven integration, provider-agnostic abstractions) across both platforms.Differentiate governance appropriately between the regulated Track & Trace platform (auditability, validation, change control) and the commercial loyalty platform (speed, iteration).Act as the technical design authority supporting chapter heads and squads on high-stakes decisions.Delivery ManagementDrive predictable product delivery through agile ways of working, in partnership with the Product and Delivery & Support heads.Own engineering delivery metrics — predictability, quality, cycle time — and the systems (estimation, commitment, escalation) behind them.Balance roadmap velocity against technical debt and platform sustainability, and make that trade-off explicit and visible to the CTO.What We're Looking For12+ years in software engineering, including several years leading leaders — managing team leads or chapter/function heads, not only individual contributors.Proven architecture governance experience: you have designed or run real governance mechanisms (review boards, ADR practices, reference architectures) and can speak to their cost and evolution, not just their frameworks.Strong delivery track record: measurable improvements in predictability or quality at organizational scale, with the systems thinking to make them durable.Deep familiarity with the Microsoft/.NET ecosystem and modern distributed-systems patterns (messaging, event-driven integration, resilience patterns, multi-tenant SaaS). You won't write production code, but you must hold credibility with those who do.Experience with enterprise or regulated environments (government, pharma, fintech, or similar) is a strong plus — you understand what compliance does to engineering standards, not just to process.Peer-level collaboration skills: you anticipate the natural seams between engineering, product, delivery, and platform organizations and build explicit working agreements across them.Fluent Arabic and English.What Success Looks Like in Year OneThe Architecture chapter exists, is led well, and squads seek its input early rather than route around it.Chapter heads are visibly growing — with clear goals, honest feedback, and at least one internal promotion or succession step.Delivery predictability is measured, published, and improving quarter over quarter.The CTO and peer heads trust engineering's commitments — and engineering's "no."Why JoinDirectly shape the engineering organization of two products entering regional expansion — the structures you build here become the company's operating system.Work on genuinely interesting problems: national-scale serialization and regulatory reporting, high-volume event-driven systems, multi-tenant SaaS on a modern .NET stack.A leadership team that treats engineering as a partner in strategy, not a service function.