EVP – Strategy and Portfolio — Data-Centre Silicon Platform

The mandate

A data-centre silicon platform must reshape its product and market roadmap. Individual teams have proposed regional variants and alternate partners, but the combined cases fragment engineering capacity and may not create defensible customer value. A planned new EVP – Strategy and Portfolio will establish the feasible portfolio before the next architecture commitments.

Approximately 1,625 employees and material partners span architecture, design, software, applications, operations and commercial teams. The EVP owns portfolio thesis, market scenarios, resource allocation, partnerships and investment cases and reports to the Group Chief Executive or designated sponsor. Legal determines permissibility and engineering determines technical feasibility; strategy joins those boundaries to an economic choice.

Market sizing will distinguish serviceable demand from theoretical workload growth. Data-centre buyers evaluate performance per watt, software compatibility, supply assurance, qualification and total deployment cost. A product that meets a numerical control threshold may still lack a viable ecosystem or customer problem. The EVP will require named adoption routes and evidence from technical decision-makers.

Portfolio variants create hidden cost. Different interconnect, memory, security or accelerator configurations can split verification, software and support. The strategist will identify reusable architecture and where a variant demands a genuinely separate product. Compliance cannot become a label attached to an otherwise unsupported roadmap.

Partnerships require rights that survive the plan. Licensed blocks, compilers, firmware, foundry services and reference platforms may carry territory, end-use or change-of-control limits. The EVP will ensure contracts and exit routes match the intended product life and that contingency does not depend on unlicensed substitution.

Customer concentration and policy change require scenarios with triggers. The portfolio should contain staged investment, decision dates and stop conditions rather than one forecast. Engineering talent freed by a cancelled route must be deliberately reassigned; it is not an automatic saving.

Software is part of the product moat and obligation. Compilers, firmware, orchestration and developer support can determine whether silicon is adopted even when hardware benchmarks lead. The EVP will allocate resources across this stack, define which elements can remain common across permitted markets and price the continuing support burden in every portfolio case.

Supply economics also shape serviceability. Advanced packages, memory interfaces and test capacity may be concentrated in routes exposed to the same policy or geographic event. Strategy will include qualified manufacturing paths, ramp time and customer acceptance, not merely a second supplier name. Inventory cannot make an unqualified alternate resilient.

This new role was planned after the board requested a unified response instead of separate compliance and product workstreams. The hybrid Bengaluru appointment participates in architecture and investment forums and can build a small strategy team.

What you will own

• Define the serviceable market and portfolio within approved legal boundaries.
• Compare variants, architecture reuse, ecosystem requirements and support cost.
• Allocate engineering and capital through scenarios and evidence gates.
• Evaluate IP, software, foundry and market partnerships with sustainable rights.
• Build customer and policy triggers for investment, pause or exit.
• Integrate product, commercial, legal and operations decisions.
• Track portfolio value after resource reallocation.
• Develop strategy talent with semiconductor and data-centre depth.

The first 12 months

In the first 60 days, review every roadmap branch, customer assumption and external right with specialists. Identify technically feasible products lacking serviceable demand and attractive markets without a lawful delivery path. Present stop, stage and prioritise recommendations before architecture freeze.

By month six, approve the portfolio thesis, conclude priority partner choices and reassign engineering capacity. Establish customer adoption evidence and policy triggers and remove unsupported variants. Each product should have a permitted tool, IP, foundry and support path.

At twelve months, redirect at least ₹300 crore of programme value toward approved high-confidence routes, reduce unsupported roadmap branches by 30% and secure three customer-backed validation programmes. Portfolio forecasts should remain within 15% of evidence-weighted milestones. No new architecture may rely on an undisclosed restricted right or market assumption.

What the sponsor will measure

• Serviceable demand separated from broad market excitement.
• Legal and technical feasibility translated into investable products.
• Variants justified by customer value after full engineering cost.
• Partnerships carrying usable rights through the product lifecycle.
• Resources moved decisively when routes close.
• Strategy clear enough for architects, sellers and directors to act.

The person

You bring 22–28 years in semiconductor strategy, product, architecture or business leadership, including data-centre silicon. You have changed a roadmap because market access, IP rights or ecosystem readiness failed. Policy expertise without product economics is insufficient.

Your prior perimeter should exceed ₹5,000 crore of product investment or 1,200 employees and partners. Evidence must include a market you exited, a partnership-rights issue and engineering reallocation. You can work with counsel without presenting legal interpretation as your own.

Compensation and terms

Fixed compensation is ₹2.2–3.0 crore plus performance variable linked to portfolio decisions, customer evidence, resource value and leadership. This permanent hybrid Bengaluru role reports to the Group Chief Executive or designated sponsor and requires international travel. Start timing follows the planned roadmap cycle.

Confidentiality

The platform, controls analyses, customers, architectures, rights and partners remain confidential. Detail follows suitability, conflicts and signed confidentiality. Applicants must not contact vendors or customers to identify the enterprise.