Chief People Officer — Electronics Portfolio

The mandate

A Bengaluru automotive-electronics portfolio is reorganising around domain controllers, embedded software and continuous vehicle features. Its people system was built for hardware programmes and functional engineering. Software specialists encounter slow grading, safety engineers fear agile language will weaken independent review and product leaders borrow talent without accepting development or succession responsibility. A planned Chief People Officer succession coincides with the most consequential organisation choices.

The CPO will lead people strategy across approximately 875 employees and material partners within an electronics perimeter near ₹3,650 crore. Scope covers organisation design, workforce planning, job architecture, reward, talent acquisition, technical careers, leadership, employee relations and succession. Engineering owns technical standards and product executives own roadmaps. The CPO ensures that roles, incentives and workforce decisions support safe software-defined delivery.

The portfolio must integrate disciplines without pretending they are interchangeable. Embedded, cloud, cybersecurity, functional safety, hardware and validation have different evidence and career requirements. Product groups need persistent teams, yet independent safety and assurance authority must remain protected. The appointee must translate those realities into clear accountability and credible mobility.

Competition for software talent cannot be answered by broad salary inflation. The CPO should identify pivotal capabilities, compare total proposition and role quality, correct unjustified internal anomalies and build learning paths from adjacent automotive disciplines. Contingent talent and partners require deliberate knowledge transfer and access governance.

Employee relations will extend beyond the Bengaluru engineering population. Electronics programmes depend on manufacturing, prototype and validation teams whose roles may change as hardware content consolidates and software support continues after launch. The CPO will coordinate consultation and mobility across locations, distinguish permanent role change from temporary programme fluctuation and ensure selection evidence is explainable. Where working patterns include late global collaboration or incident response, workload, transport, fatigue and on-call compensation must be designed rather than accepted as the price of a software culture.

Executive behaviour will be assessed as part of the design. Leaders who celebrate rapid release while bypassing review, or protect functional talent from product accountability, can undermine any formal structure. The CPO will link appointment and reward evidence to both delivery and controlled decision quality.

Why this seat is open

The incumbent will move into a planned group role and supports a four-to-six-month transition. This is a planned replacement, not a reaction to attrition, employee relations or programme failure. The board wants the successor appointed before new job architecture and leadership selections become final.

What you will own

• Design product, platform, engineering, safety, validation and technical-leadership accountabilities.
• Create comparable career systems for software, hardware, safety specialists and people managers.
• Protect independent assurance roles while embedding them effectively in product flow.
• Build workforce scenarios around programme demand, proficiency and time to competence.
• Establish targeted market, reward and retention strategies for pivotal capabilities.
• Redesign talent acquisition and assessment around demonstrated technical and product evidence.
• Govern contingent workforce, knowledge transfer and pathways into critical permanent capability.
• Lead executive assessment and succession across the electronics portfolio.

The first 12 months

Within 60 days, the CPO will map roles, skills, pay, vacancies, programme demand and safety-critical dependencies. By day 90, the executive committee will approve organisation principles, protected assurance roles and two capability populations for immediate intervention. No leadership selection will precede transparent criteria.

By month eight, pilot product groups should operate under the new accountabilities, technical-career standards should govern real promotion decisions and targeted learning should move adjacent engineers into productive software or validation roles. Priority pay anomalies and contingent dependencies will have documented actions.

At year-end, 90% of employees should map to approved roles and proficiency, pivotal attrition should fall by six percentage points and internal moves should fill 30% of priority openings. Product decision cycle time should improve without a material safety, audit or employee-relations failure attributable to organisation change.

What the board will measure

• Product accountability and independent safety challenge working together in practice.
• Pivotal capability, proficiency and retention rather than gross hiring volume.
• Credible technical careers across hardware and software disciplines.
• Fair, explainable leadership and reward decisions.
• Successor depth across people, product and specialist roles.

The person

You are a Chief People Officer, automotive engineering HR leader or technology-workforce executive who has redesigned organisations around software products and controlled engineering. You understand that agile delivery does not remove formal safety authority and can distinguish a scarce-skill problem from poor role design.

You bring 22–28 years of experience and have led people strategy for at least 600 employees within a perimeter of ₹2,100 crore or more. The board will test a protected role you kept independent, a technical-career system you implemented and a capability gap you closed without relying solely on external hiring.

The role is onsite in Bengaluru with regular work at engineering and validation locations.

Compensation and terms

This CPO appointment offers ₹2.2–3.0 crore fixed with a performance variable. Objectives include capability, pivotal retention, product accountability, safety independence and succession. Hiring volume alone creates no reward. Final terms reflect current mix and portfolio scope, with the planned transition able to accommodate notice.

Confidentiality

The electronics products, programmes, incumbent and capability data are confidential. Detailed information follows qualification and an undertaking. Bengaluru and the rounded workforce must not be used to infer the company.