Chief Technology Officer — Beauty And Personal-Care Business

The mandate

The business is changing how consumers discover, evaluate and replenish beauty products. Wholesale and specialist retail remain essential, while brand websites, marketplaces, social commerce and digitally assisted consultations are taking a larger role. Technology has been added channel by channel: separate recommendation tools, campaign experiences, consultation applications and commerce services now compete for customer identity, product information and engineering attention. The business cannot create a connected relationship if every touchpoint treats the same consumer and product differently.

The Chief Technology Officer will establish the technical product and engineering system for that transition. The remit covers consumer-facing architecture, software engineering, platform reliability, developer experience, integration patterns, identity technology, experimentation services and applied capabilities such as recommendation and computer vision. Enterprise applications and workplace technology remain under the CIO; brand and commercial executives own propositions and channel results. The CTO is accountable for turning those propositions into secure, reusable and observable products that work at international scale.

The appointment is not a brief to force all channels onto one interface. A beauty adviser in a store, a marketplace shopper and a replenishing subscriber have different needs and data permissions. The common foundation should enable continuity where it benefits the consumer while allowing experiences to remain appropriate to their context. Technology must also respect the role of retail partners; owning a platform does not confer rights over customer data supplied under another party's terms.

Scope and operating context

Based onsite in Singapore, the CTO will shape an ecosystem of approximately 1,625 employees and material partners across the city-state and the wider international region. Direct leaders will span architecture, engineering, site reliability, quality engineering, product technology, data engineering interfaces and technical programme delivery. Much capacity currently sits with agencies and systems integrators. The CTO will decide which capabilities are strategic enough to own and where external scale remains advantageous.

The consumer estate must support major launch peaks, live campaign traffic, multiple languages, local payment methods, consent variation and integration with retail or marketplace environments the group does not control. Physical consultation introduces additional constraints: variable connectivity, shared devices, camera calibration, accessibility and the need for advisers to explain rather than blindly repeat an algorithmic recommendation.

Product and shade data are foundational. Recommendation accuracy depends on consistent attributes, claims, imagery, availability and regional assortment, yet those records currently originate in several systems. The CTO will partner with product, regulatory and data owners to make provenance and permitted use visible to consuming services. Technology cannot compensate indefinitely for unclear business ownership of source information.

First-year agenda

The first hundred days will produce a clear technical and product baseline. The CTO will trace priority journeys across channel boundaries, examine architecture and service health, assess engineering capability, quantify vendor dependence and review the validity of current experimentation claims. They will identify where duplicated components create inconsistency, where a shared service would introduce unacceptable coupling, and which fragile interfaces pose immediate launch or customer risk.

An engineering strategy will follow. It should define bounded platform capabilities for identity, consent signals, product content, recommendation inputs, experimentation, order and availability interfaces, observability and secure integration. Each capability will have a product owner, service expectations, adoption path and retirement plan for what it replaces. Standards will be enforced through working paved roads and automated controls, not lengthy architecture approval meetings.

The CTO will select a small number of journeys to prove the model. One may connect a consented consultation record to later owned-channel discovery; another may provide consistent recommendation logic to advisers and a brand site while preserving channel-specific explanation. A third might improve marketplace product and availability feeds. Choices will be based on consumer value, technical learning and commercial commitment after appointment, not on a predetermined demonstration project.

Reliability and delivery practice require simultaneous attention. Teams will adopt service ownership, measurable error budgets, safe deployment, incident learning and product-level cost visibility. The CTO will reduce large release dependencies so that channel teams can improve at different speeds without destabilising shared services. Peak-readiness exercises will test the entire consumer journey, including external partners and manual fallback.

Applied artificial intelligence will be governed as a product capability rather than a publicity theme. Recommendation or image-based tools must be assessed for performance across relevant skin tones, devices, lighting and markets; limitations need to be communicated to users. Models that cannot be monitored or supported should not move into consequential consumer journeys. By year-end, the board should see fewer disconnected builds, more predictable launches and evidence that reusable foundations improve time, quality or customer continuity.

Leadership responsibilities

The CTO will lead the engineering community and create an environment in which technical dissent can surface early. They will define senior technical roles, improve succession and distinguish accountable internal ownership from purchased delivery. Engineers should understand brand and adviser context, while commercial teams should understand capacity, reliability and data constraints.

Investment decisions will be shared with product and channel owners. The CTO will state total costs, architectural consequences, security exposure and expected reuse, then hold teams to observable outcomes after launch. They must resist both local customisation presented as urgency and central platforms built without committed users.

The role will partner closely with the CIO, information-security, privacy, regulatory, product and marketing leaders. Boundaries between enterprise records, consumer products and analytical services will be explicit, but incidents and dependencies must not fall between functions. For material failures, the CTO will ensure customer impact is contained, facts are communicated and engineering learning changes the system.

Measures of success

The executive committee will review journey availability, latency, change failure, recovery, critical defects, peak performance and engineering throughput. Product measures will include adoption by advisers or channels, experiment validity, recommendation performance, customer effort and continuity across touchpoints where consent permits. Technical activity without a user or commercial outcome will not be treated as value.

Platform progress will be shown through reduced duplicate components, declining integration lead time, use of supported services, vendor knowledge transfer and retirement of replaced technology. Cost will be tracked by journey and capability rather than only by contract. Talent measures include retention of pivotal engineers, internal technical leadership and credible successors across major domains.

Candidate profile

Candidates should bring 22–28 years across product engineering and technology leadership in beauty, consumer platforms, retail, commerce, marketplaces, media or another high-scale digital environment. They must have owned customer-facing services across countries and peak events, with direct accountability for reliability and engineering economics. Experience linking digital journeys to physical retail or adviser workflows is particularly valuable.

The board wants evidence of creating reusable platforms without suppressing legitimate product variation. Candidates should explain a component they centralised, one they deliberately left local and the operating evidence behind each choice. They must have managed substantial external engineering capacity while building authoritative internal architecture and product ownership.

Strong candidates will also understand responsible personalisation, consent boundaries and model performance. They do not need to be a beauty scientist, but they must know when consumer recommendation claims require product, regulatory or domain review. Clear communication with brand leaders, boards and deeply technical teams is essential.

Compensation and appointment terms

The anticipated base salary is SGD 420,000–570,000, augmented by annual incentive and long-term participation linked to product, reliability and enterprise outcomes. Final placement will reflect relevant scale, technical depth and current arrangements. Relocation or responsible treatment of forfeited awards will be assessed individually during appointment negotiations.

Confidentiality

The client is unnamed because the role touches unreleased channel plans, consumer-data architecture and proprietary recommendation capability. Candidates advancing in the process will receive controlled technical and organisational disclosure after conflict and confidentiality checks. Applications must exclude customer records, security vulnerabilities, source code or protected model details from other businesses.