Interim Director, Semiconductor Software GCC — Ownership Transfer

The mandate

A product-line acquisition closed with firmware and driver experts scheduled to leave before knowledge transfer to India was complete. The selected GCC director declined after close, leaving customer release obligations exposed across the seller, global silicon team and a partially hired Bengaluru group.

The interim must start within three weeks for fourteen months, covering knowledge capture, two silicon-release cycles and local leadership build. A permanent director search begins after the first India-owned release, with extension possible for six weeks if the second customer qualification moves.

Handover is complete when India owns build, validation and field support for the specified firmware stack, two releases meet quality and schedule gates, key-person dependencies have tested backups, and the successor approves one customer patch and one forward roadmap.

The interim may prioritise hiring, set transfer acceptance, stop releases and deploy ₹14 crore of mobilisation spend. Changes to silicon roadmap, permanent director hires, product end-of-life, customer concessions above ₹4 crore and supplier commitments over ₹10 crore require global engineering or executive approval.

Chip architecture, fabrication sourcing and ownership transfer for unrelated product lines are excluded. The centre takes accountable software responsibility for the acquired stack without assuming global silicon investment decisions.

Why this seat is open

The post-close withdrawal removed the intended bridge between acquired experts and the India team. Functional managers can capture documents but cannot adjudicate whether knowledge is operationally sufficient. A temporary director can prove ownership through releases before permanent succession.

What you will own

• Define transfer acceptance for source, toolchains, build, test, defects, release, field support and customer obligations.
• Decide critical-expert retention and knowledge sequencing using release dependency and replacement readiness.
• Recruit firmware, driver, validation and customer-engineering leaders against a product-specific capability map.
• Approve India ownership only after teams reproduce builds, debug failures and resolve representative customer defects.
• Govern two release cycles through silicon dependency, regression, performance, security and qualification gates.
• Establish on-call and field escalation with tested backups for every critical component.
• Transfer product charters, key-person risks, customer commitments, release evidence and talent decisions to the permanent director.

Candidate qualifications

• Led semiconductor firmware, driver or embedded-software engineering at director level.
• Transferred product ownership after an acquisition or site consolidation with departing experts.
• Shipped software across at least two silicon releases and customer qualification cycles.
• Built India engineering teams spanning firmware, validation, tools and field support.
• Managed hardware-software dependencies, regression evidence and critical customer escalations.
• Can distinguish documented knowledge from demonstrated build, debug and release capability.

Non-negotiables

• Available in Bengaluru within three weeks.
• No current relationship with the seller, acquired leadership or staffing suppliers.
• Will not declare knowledge transfer complete from document delivery alone.
• Must have owned customer-facing semiconductor software releases.

1. 49 words maximum. Confirm availability and disclose any seller or semiconductor competitor conflict.
2. 49 words maximum. Describe a firmware ownership transfer you accepted and the practical test used.
3. 49 words maximum. Which key-person dependency would you test first before an acquired expert exits?