Private-Cloud Capacity Signal Recovery Leader

The mandate

A placement controller admitted new cargo-processing workloads using stale free-capacity and reservation data, concentrating compute and storage pressure inside one failure domain before a regional shipping peak. Automated rescheduling then moved additional services into the same constrained cells. The infrastructure-capacity head resigned after the incident showed that nominal capacity, allocatable capacity and survivable capacity had no common definition.

The interim must assume the Singapore seat within fifteen days and serve for ten months, with a possible two-month extension only if the final seasonal-peak exercise moves. The permanent capacity leader search opens after a common capacity ledger and admission policy run in both primary regions, expected in month five. The successor will overlap for five weeks and command the last peak simulation.

Handover requires compute, memory, storage, network and control-plane reservations to reconcile to deployed demand; every critical service to retain tested failure headroom; placement to reject stale or incomplete capacity evidence; two regional evacuation and peak exercises to pass; business teams to see constrained supply before release; and the permanent leader to accept forecasts, overrides and expansion triggers.

The interim may stop workload admission, reserve capacity, change placement policy, cap noisy tenants, sequence hardware release, redirect internal teams and approve up to SGD 24 million within the recovery programme. Permanent hiring, new facilities, supplier replacement, customer commitments and decisions above SGD 5 million require council approval. The seat cannot override cargo priority or customs processing rules.

Application feature redesign, public-cloud migration, warehouse equipment and long-range real-estate planning are explicitly outside scope. The assignment covers private-cloud capacity telemetry, reservations, placement and admission, failure headroom, demand planning, operational escalation and the team accountable for translating infrastructure supply into reliable cargo service.

Why this seat is open

The disruption showed that high utilisation had been rewarded without accounting for the capacity needed to survive failure and cargo peaks. Leadership departure left application, platform and finance teams defending incompatible numbers. A temporary executive must create one allocatable-capacity truth, operate it through seasonal stress and hand permanent management evidence it can use before accepting new demand.

What you will own

• Reconcile physical inventory, hypervisor and cluster capacity, reservations, quotas, deployed demand, growth and maintenance across failure domains.
• Define nominal, healthy, allocatable, protected and recoverable capacity for compute, memory, storage, network and control-plane services.
• Establish freshness, completeness and confidence rules for signals used by placement, autoscaling, admission and planning decisions.
• Decide headroom, overcommit, tenant isolation, placement affinity and degradation policies by cargo-service consequence.
• Install demand forecasts joining shipment events, releases, batch windows, resilience exercises, hardware lead time and technical debt.
• Command simulations for regional evacuation, storage degradation, network contention, control-plane loss and simultaneous peak admission.
• Transfer capacity ledgers, forecast assumptions, admission rules, overrides, supplier actions and expansion triggers through successor-led governance.

Candidate qualifications

• Held executive accountability for private-cloud or large platform capacity supporting time-critical transaction operations.
• Recovered a saturation event caused by stale telemetry, unsafe overcommit, placement concentration or missing resilience reserve.
• Defined allocatable and survivable capacity across compute, memory, storage, network and control planes.
• Built admission and placement controls that failed safely when capacity evidence was late, incomplete or contradictory.
• Connected business peaks and release demand to infrastructure forecasts and procurement lead times without double-counting headroom.
• Handed a capacity-recovery function to permanent leadership after live peak and failure exercises.

Non-negotiables

• Can start in Singapore within fifteen days and travel monthly to regional cargo or recovery facilities.
• Will accept exclusive executive duty and continuous escalation availability during peak windows and capacity incidents.
• Brings direct private-cloud admission and placement evidence; financial capacity planning or public-cloud billing alone is insufficient.
• Must disclose relationships with infrastructure, virtualisation, storage, network and capacity-service providers.

1. 49 words maximum. State your earliest Singapore start and the largest private-cloud capacity incident you personally commanded.
2. 49 words maximum. Describe a free-capacity signal that was numerically correct but unsafe for workload admission.
3. 49 words maximum. Which headroom measure would you protect first before a cross-border cargo peak?