CTO – Product and Engineering — Cybersecurity Hub

The mandate

The board has concluded that incremental adjustment will not resolve product engineering requiring a step-change in pace without compromising reliability within a listed multinational global-capability-centre network. The immediate arena is the cybersecurity hub during a move from delivery to product ownership. For mandate 241, the successful executive inherits decisions that have been deferred, competing stakeholder expectations and a need to establish facts before committing further capital.

The CTO – Product and Engineering operating perimeter covers approximately PHP 4,000 million in annual global services budget, with activity spanning several cybersecurity hub customer, product and delivery clusters rather than a single asset. The CTO – Product and Engineering Global Capability Centres remit carries direct influence over roughly 1,100 colleagues and third-party capacity.

The chair, executive committee and principal capital sponsors want a CTO – Product and Engineering who can convert ambiguity into a short list of explicit choices for the cybersecurity hub. The CTO – Product and Engineering Global Capability Centres seat must resolve a move from delivery to product ownership, while preserving the underlying strengths of the cybersecurity hub. For mandate 241, value will come through sharper allocation, stronger leaders and an operating cadence that exposes variance early.

The CTO – Product and Engineering’s first year on the cybersecurity hub is expected to end with release confidence, architecture health and engineering productivity. In mandate 241, authority covers resources and leadership appointments; material trade-offs go directly to the board sponsor.

Why this seat is open

This is a planned replacement for the CTO – Product and Engineering — Cybersecurity Hub seat. The incumbent continues to lead the cybersecurity hub through an agreed succession period and will support a structured handover. The board has allowed 4–6 months to assess candidates, complete diligence and protect continuity while a move from delivery to product ownership is addressed. The search is confidential so the transition can be communicated to employees, customers and partners in a controlled sequence.

What you will own

• Set the CTO – Product and Engineering value-creation thesis for the cybersecurity hub, translate it into no more than five enterprise priorities and stop work that does not support them.
• Carry stewardship of approximately PHP 4,000 million in annual global services budget, including allocation, risk acceptance and board forecasts.
• Lead the CTO – Product and Engineering Global Capability Centres organisation of about 1,100 employees and partners, appointing a team with clear decision rights and credible succession for every critical seat.
• Resolve the cybersecurity hub economics and execution constraints created by a move from delivery to product ownership, with CTO – Product and Engineering-approved owners, dated milestones and transparent escalation thresholds.
• Establish one CTO – Product and Engineering operating review across commercial, customer, financial, people, technology and risk outcomes for the cybersecurity hub; remove reconciliations that obscure accountability.
• Have made consequential architecture and engineering trade-offs while scaling release throughput and reliability in mandate 241.
• Build the CTO – Product and Engineering’s three-year succession and capability plan for the cybersecurity hub, reducing dependence on individual executives and improving mobility across the wider Global Capability Centres organisation.

The first 12 months

• Days 1–90: Validate the cybersecurity hub baseline, meet the 30 stakeholders most consequential to product engineering requiring a step-change in pace without compromising reliability, assess the leadership team, stabilise immediate delivery risks and agree a board-owned scorecard with explicit decision gates.
• Months 4–9: Make the principal CTO – Product and Engineering portfolio and organisation choices for the cybersecurity hub, install the new operating cadence, fill critical leadership gaps and deliver the first measurable release of cash, capacity or customer value.
• Months 10–12: Demonstrate a repeatable cybersecurity hub trend against release confidence, architecture health and engineering productivity, lock the following year’s capital and talent plan, evidence control sustainability and present a credible three-year value case with downside actions.

What the board will measure

• Delivery of the CTO – Product and Engineering’s agreed first-year cybersecurity hub value case within a 10% tolerance, with variance explained before rather than after the relevant quarter closes.
• A CTO – Product and Engineering forecast that remains decision-useful across three consecutive quarters and reconciles the cybersecurity hub’s operating, cash, customer and people assumptions.
• Closure of the CTO – Product and Engineering mandate’s highest-priority cybersecurity hub risk and execution issues by their board-approved dates, with independent evidence that fixes are sustained.
• Retention of at least 90% of critical cybersecurity hub talent and ready-now successors for at least 70% of the CTO – Product and Engineering’s direct reports.
• A quantified CTO – Product and Engineering-owned improvement in the cybersecurity hub operating constraint behind a move from delivery to product ownership, supported by a clean baseline and named data owner.
• Clear stakeholder confidence in mandate 241: no unresolved high-severity escalation older than 30 days and no material surprise withheld from its agreed governance forum.

The person

You are currently a CTO, SVP Engineering or Product Technology Head in a listed Global Capability Centres or adjacent enterprise. In relation to the cybersecurity hub, your CTO – Product and Engineering track record includes a transition where the original plan was no longer sufficient; you can explain your choices, evidence and numerical impact. Candidates from GCCs, shared services, enterprise technology, business services or multinational operations will be considered where the operating model, customer stakes and governance intensity match this CTO – Product and Engineering brief.

As a CTO – Product and Engineering candidate, you bring 18–22 years of progressive Global Capability Centres or adjacent-sector experience, consistent with the 18-22 experience band. At minimum, you have carried a P&L, book, budget or accountable portfolio of PHP 2,300 million and led an organisation of at least 775 people.

For mandate 241, the board wants two transitions: a difficult cybersecurity hub portfolio choice and a leadership-system change during a move from delivery to product ownership. As the prospective CTO – Product and Engineering for this cybersecurity hub, you must challenge optimistic cases and still create followership. References for mandate 241 must distinguish your contribution from the institution around you.

The CTO – Product and Engineering must be based in Manila; international relocation is supported, but this Global Capability Centres role is not designed as a remote appointment.

Non-negotiables

• Current or recent accountability at the level of CTO, SVP Engineering or Product Technology Head, with direct exposure to a board, investment committee or equivalent Global Capability Centres governance forum.
• Proven CTO – Product and Engineering ownership of at least PHP 2,300 million and leadership of no fewer than 775 employees in a comparable cybersecurity hub context.
• One completed Global Capability Centres or adjacent-sector example of product engineering requiring a step-change in pace without compromising reliability with outcomes sustained for at least two reporting periods after the initial intervention.
• Sector credibility from GCCs, shared services, enterprise technology, business services or multinational operations; experience that is purely functional and lacks CTO – Product and Engineering-level cybersecurity hub consequences will not meet the bar.
• Willingness to meet the Manila location expectation, complete conflicts and background diligence, and protect the confidentiality of mandate 241.

Compensation and terms

The anticipated CTO – Product and Engineering package is PHP 20–28 million base + annual incentive and LTI, calibrated to the final cybersecurity hub scope and the candidate’s current mix. Any long-term participation for mandate 241 follows standard vesting and performance conditions. The CTO – Product and Engineering appointment in Manila, centred on the cybersecurity hub, offers regular exposure to the chair, executive committee and principal capital sponsors. A notice period of up to 6 months can be accommodated for the selected executive in mandate 241.

Confidentiality

The organisation will be identified only after reciprocal interest and a confidentiality undertaking for mandate 241. The market, scale and situation in this brief are intentionally composite and are not a coded description of a named enterprise for mandate 241.