CTO – Product and Engineering — Transit-Technology Business

The mandate

The business supplies fare, passenger-information and fleet-control products to transport authorities. During rapid regional growth, project teams promised customer-specific features and engineering absorbed them into separate branches, interfaces and support arrangements. Several contracts remain commercially attractive on paper, yet the cost of testing, release, cyber remediation and long-term service is dispersed across central budgets. The CTO must re-establish what is a product, what is paid custom engineering and what the company should no longer promise.

Approximately 500 employees and material partners sit across product management, engineering, architecture, quality, cyber engineering and reliability. Programme directors own customer milestones; this executive owns technical commitment, reusable road maps and product-service economics. They will have authority to reject unsupported bid features and require change control where a customer request materially alters lifecycle cost or safety assurance.

Transit systems operate for decades, so rationalisation cannot abandon installed customers. The CTO needs a version and support strategy that protects contractual service while reducing future divergence. Arabic language, local payment, data-residency and authority integration may be legitimate regional needs; presentation or workflow preferences are not automatically platform requirements. Every exception must identify its owner, funding, test and retirement path.

Unit economics require engineering evidence. Product margin should include deployment effort, defect demand, cloud or licence use, security maintenance and support over the contract term. The appointee will work with finance to create this view and use it in bids, road-map allocation and customer negotiations.

Safety and technical certification cannot be amortised casually across variants. A change to fare-gate control, passenger messaging or operational integration may trigger authority testing or independent assessment even when code reuse is high. The CTO will maintain an assurance map by product and version, ensure estimators include re-certification effort and refuse shortcuts that convert margin pressure into latent public-system risk.

Why this seat is open

A bid review revealed technical commitments that had not passed engineering approval, and the former distributed leadership model could not resolve them. The board created this urgent, unplanned CTO role above product and engineering; no incumbent is being displaced. Interim controls protect current bids, but a permanent leader is required before the next product release and contract cycle.

What you will own

• Define core products, configurable regional layers and controlled custom engineering with explicit lifecycle economics.
• Create engineering authority in bid and change governance, including enforceable refusal and escalation rights.
• Rationalise branches, interfaces and releases without breaching installed-system or safety obligations.
• Establish product-line contribution including deployment, cloud, defects, cyber, support and obsolescence.
• Set quality and reliability objectives for fare, passenger and control journeys and lead material incident review.
• Govern secure development, supplier components, vulnerability remediation and software provenance.
• Align programme and product leaders on acceptance evidence, release timing and customer communication.
• Build a product-and-engineering leadership bench capable of challenging both sales and technical orthodoxy.

The first 12 months

Within 90 days, catalogue commitments across the ten most material contracts, reconstruct effort and lifecycle cost, and identify unsupported features in live bids. Review installed versions and critical vulnerabilities. Present the executive committee with product boundaries, interim technical approval and a financed plan for obligations that cannot be standardised.

By month six, operate a joint bid and road-map forum, converge the first product branches and re-contract or formally fund priority customer variants. Introduce product-line economics and end-to-end reliability measures. Engineering leaders should own service outcomes after release rather than transfer defects to programme support.

At twelve months, raise reusable engineering allocation above 75%, reduce variant-related test and release effort by 25%, and improve gross contribution on new signed work by at least ten points against the prior cohort. Critical product availability should meet 99.95%, high-risk vulnerabilities should close within agreed service levels, and no bid should contain an unapproved technical obligation.

What the board will measure

• Product-line cash and contribution reconciled to complete lifecycle effort.
• Reduction of variation while honouring contracted, regulatory and safety needs.
• Technical authority exercised before commercial commitment.
• Reliability, cyber and release quality across installed systems.
• Road-map concentration on repeatable customer value.
• Retention and succession in product, engineering and architecture leadership.

The person

You have 18–22 years in product and engineering leadership for transit, payments, industrial software, smart infrastructure or another long-life technology platform. You have inherited contractual customisation and converted it into governed product or explicitly priced service. You understand that legacy support is an obligation, not a reason to accept indefinite divergence.

Your experience should include at least 350 engineers and partners and technology supporting contracts above AED 2 billion. You can identify the feature you refused, the version you retired and how finance validated engineering economics. The board will examine customer judgement, incident ownership and whether your architecture choices reduced cost after transition.

This hybrid Dubai role includes regional customer travel and reports to the Group Chief Executive or designated executive sponsor.

Compensation and terms

Fixed compensation is AED 1.9–2.7 million plus annual incentive and long-term incentive measured through product economics, reliability, reuse, cyber and leadership. This permanent hybrid Dubai role reports to the Group Chief Executive or designated sponsor. Notice up to six months may be considered alongside urgent bid controls.

Confidentiality

The company, authorities, contracts, products and vulnerabilities are confidential. Detailed technical material follows reciprocal fit, conflicts and a signed undertaking. Figures and circumstances are deliberately combined; applicants must not contact suspected customers, engineers or suppliers to identify the business.