lvl100Sign in

Aptiv

Supplier Manager

  • Bangalore, India
  • Full-time
  • Posted

Skills

  • Cybersecurity
  • Procurement

Job description

Your Role

Supplier Manager

ROLES AND RESPONSIBILITIES

We are looking for an experienced Software Supplier Manager – Third-Party Software to own and coordinate the selection, acquisition, governance, and lifecycle management of externally sourced software products used within our automotive software platforms and customer programs.

•The role focuses specifically on commercial third-party software and licensed software components, rather than outsourced software-development services.   Typical third-party software products include:
•AUTOSAR Classic and Adaptive platform software
•Microcontroller Abstraction Layers (MCAL)
•Operating Systems and Real-Time Operating Systems (RTOS)
•Cryptographic and cybersecurity libraries
•Compilers, toolchains, and associated runtime libraries
•Communication and diagnostic stacks
•Bootloaders and flash programming solutions
•Middleware and other commercial embedded-software components
•The Software Supplier Manager acts as the central interface between Software Engineering, Architecture, Cybersecurity, Functional Safety, Procurement, Legal, Program Management, Quality, and external software vendors.   In addition, the Software Supplier Manager is the process owner for Automotive SPICE ACQ.4 – Supplier Monitoring within the assigned organizational scope. The role is responsible for defining, deploying, maintaining, and continuously improving the supplier-monitoring process and ensuring its consistent application across applicable third-party software suppliers and programs.   The objective is to ensure that third-party software is technically suitable, commercially competitive, contractually compliant, properly licensed, integration-ready, maintainable, supported throughout the required product lifecycle, and managed in accordance with Automotive SPICE supplier-monitoring expectations

Your Background

•Third-Party Software Sourcing and Supplier Selection
•Coordinate the identification and evaluation of third-party software solutions together with Software Architecture, Platform Engineering, Procurement, Cybersecurity, Functional Safety, Quality, and Program teams.
•Translate technical and program requirements into clear RFQ and supplier-selection criteria.
•Coordinate technical and commercial RFQs for software products such as AUTOSAR stacks, MCAL, operating systems, cryptographic libraries, compilers, middleware, and communication stacks.
•Establish structured supplier comparisons covering functionality, architecture compatibility, performance, maturity, automotive qualification, integration effort, licensing, support model, lifecycle, and total cost of ownership.
•Assess supplier capability, product roadmap, automotive references, support organization, release strategy, quality-management approach, and long-term viability.
•Ensure technical selection and commercial sourcing decisions remain aligned.
•Automotive SPICE ACQ.4 Process Ownership
•Own Automotive SPICE ACQ.4 – Supplier Monitoring for the assigned organizational scope.
•Define, document, maintain, and continuously improve the ACQ.4 supplier-monitoring process, including methods, templates, roles, responsibilities, interfaces, and expected work products.
•Ensure that supplier monitoring is established and executed consistently across applicable third-party software suppliers.
•Define the supplier-monitoring strategy based on product criticality, technical complexity, supplier risk, cybersecurity and functional-safety relevance, and program impact.
•Establish and maintain supplier-monitoring plans defining milestones, deliverables, responsibilities, review mechanisms, acceptance criteria, reporting, and escalation paths.
•Ensure supplier progress is regularly reviewed against agreed technical, quality, schedule, commercial, and process commitments.
•Define objective supplier-monitoring KPIs and ensure that deviations are identified early and supported by appropriate corrective actions.
•Ensure agreed supplier deliverables are reviewed and accepted against defined technical and quality criteria.
•Establish mechanisms for identifying, evaluating, tracking, escalating, and closing supplier-related issues and deviations.
•Ensure supplier changes with potential impact on software functionality, interfaces, quality, safety, cybersecurity, schedule, or integration are identified and managed.
•Define and maintain the required ACQ.4 process evidence and work products to support internal assessments, customer assessments, and Automotive SPICE assessments.
•Coordinate ACQ.4 readiness and assessment activities with Quality, Process, Engineering, Program Management, Procurement, and applicable supplier stakeholders.
•Act as the organizational subject-matter expert for ACQ.4 , providing guidance and coaching to Software Supplier Managers, Engineering teams, and projects.
•Identify systematic weaknesses and lessons learned across supplier engagements and translate them into improvements of the ACQ.4 process, templates, governance, and supplier-management practices.
•Track process effectiveness and drive corrective and preventive actions where ACQ.4 implementation does not achieve the expected supplier-control outcomes.
•Represent the ACQ.4 process area during process reviews and assessments and coordinate resolution of findings affecting the process.
•Maintain alignment between ACQ.4 requirements and related internal sourcing, procurement, quality, cybersecurity, functional-safety, software-engineering, and program-management processes.
•Licensing and Commercial Management
•Manage the commercial framework for third-party software together with Procurement and Legal.
•Understand and manage software licensing models including development, runtime, per-project, per-ECU, site, enterprise, subscription, royalty, and maintenance licenses.
•Ensure licensing assumptions match the actual product architecture, development organization, production volumes, ECU variants, and customer-program requirements.
•Prevent unplanned licensing exposure caused by reuse, additional variants, new ECUs, additional development locations, or changing production volumes.
•Maintain transparency of license entitlements, restrictions, renewal dates, maintenance costs, royalties, and future financial commitments.
•Support commercial negotiations and identify opportunities for license consolidation, reuse, volume agreements, and portfolio-level cost optimization.
•Establish transparency of total cost of ownership , including initial license fees, recurring maintenance, royalties, integration costs, upgrades, support, and lifecycle extensions.
•Technical Supplier Governance
•Establish effective technical governance with third-party software suppliers.
•Coordinate technical interfaces between supplier experts and internal Software Architecture, BSW, Platform, Integration, Cybersecurity, Functional Safety, and Application teams.
•Ensure required software releases, configuration packages, documentation, integration guides, release notes, known-issue lists, safety manuals, cybersecurity evidence, and qualification artefacts are delivered as committed.
•Track technical issues affecting integration, performance, stability, compatibility, safety, or security.
•Ensure supplier defects and technical questions have clear priorities, owners, target dates, and escalation mechanisms.
•Coordinate supplier engineering support during integration, debugging, releases, and critical customer-program phases.
•Escalate supplier-side technical blockers where response time or resolution quality threatens program milestones.
•Software Release and Configuration Governance
•Maintain visibility of third-party software versions and configurations used across platforms and customer programs.
•Coordinate supplier releases against internal platform and customer-program release schedules.
•Ensure changes between supplier software versions are understood, documented, and impact-assessed before integration.
•Coordinate evaluation of supplier release notes, known issues, compatibility changes, and migration impact.
•Limit unnecessary software-version and configuration proliferation across programs.
•Promote reuse of qualified third-party software versions where technically and commercially appropriate.
•Ensure required historic versions, patches, documentation, licenses, and technical support remain available for products already in production.
•Product Lifecycle and Obsolescence Management
•Manage third-party software throughout the required automotive development, production, and service lifecycle.
•Understand supplier product roadmaps and identify End-of-Life, End-of-Support, technology-obsolescence, and dependency risks early.
•Ensure maintenance and support commitments are compatible with automotive production and service-life expectations.
•Coordinate lifecycle-extension agreements, migration strategies, or alternative solutions where supplier support ends before internal product commitments.
•Track dependencies between third-party software and microcontrollers, operating systems, compilers, toolchains, cybersecurity mechanisms, and other platform components.
•Establish mitigation plans for supplier discontinuation, acquisition, strategic change, or product obsolescence.
•Cybersecurity and Vulnerability Management
•Ensure third-party software suppliers provide required cybersecurity information and vulnerability-management support.
•Coordinate known vulnerabilities, supplier security advisories, and applicable CVEs with Cybersecurity teams.
•Establish supplier processes for vulnerability notification, assessment, remediation, patch delivery, and security updates.
•Ensure contractual agreements define expectations for cybersecurity incident notification and vulnerability response.
•Track security-related supplier actions through closure and escalate critical vulnerabilities appropriately.
•Support software-composition and third-party-dependency transparency, including required component and version information and SBOM-related information where applicable.
•Functional Safety and Compliance
•Ensure suppliers provide the required functional-safety work products and evidence where third-party software contributes to safety-related functionality.
•Coordinate the availability of Safety Manuals, qualification evidence, assumptions of use, configuration constraints, and other required documentation.
•Facilitate reviews between supplier specialists and internal Functional Safety teams.
•Ensure technical and contractual responsibilities for required compliance evidence are clearly defined.
•Integrate functional-safety and cybersecurity requirements into the applicable ACQ.4 supplier-monitoring activities.
•Supplier Performance Management
•Define measurable supplier KPIs covering product quality, release adherence, technical support, issue resolution, documentation, cybersecurity response, commercial performance, and lifecycle support.
•Establish regular supplier-performance reviews based on objective evidence.
•Monitor response and resolution times for critical software issues.
•Track committed versus actual software-release dates.
•Monitor recurring defects, integration issues, documentation gaps, and escalation frequency.
•Establish measurable improvement plans for suppliers that fail to meet agreed expectations.
•Provide evidence-based supplier status and risk reporting to Engineering and Program leadership.
•Use supplier-performance trends as input to both sourcing decisions and ACQ.4 process improvement .
•Risk and Escalation Management
•Maintain visibility of technical, commercial, licensing, cybersecurity, lifecycle,

Browse all jobs by role, city or company