Component Requirement Lead

The responsibilities of the Component Requirement Lead (CRL)

include but are not limited to the following:

• Manage, refine and maintain Domain specific System to Software requirement
• Participate in the global architecture design
• Analyze and validate System requirements
• Responsible for the traceability System to Software and Software to SW validation
• Participate to the diversity management with our Product line engineering, in charge of the strategy of domain requirements deployment among different platform and vehicle variants

• Bachelor's degree in Computer Science, Computer Engineering, Electrical Engineering, or a related field
• A minimum of 8 years of experience
• Requirements Engineering:
  Expertise in eliciting, analyzing, specifying, validating, and managing requirements across all levels – stakeholder, system, and software.
• Automotive Standards:
  In-depth knowledge of Automotive standards such as ISO 26262 (Functional Safety), AUTOSAR, ASPICE, and relevant process frameworks.
• Stakeholder Management:
  Proven ability to engage, communicate and negotiate with diverse stakeholders including customers, system architects, software teams, and quality teams.
• System & Software Requirements:
  Experience translating high-level stakeholder needs into system and software requirements suitable for downstream design and development teams.
• Tools & Methodologies:
  Proficiency in requirements management tools like IBM DNG, Polarion. Familiarity with model-based design and SysML/UML is a plus.
• Traceability & Impact Analysis:
  Establish and maintain requirements traceability matrices and perform impact analysis for changes.
• Verification & Validation:
  Collaborate with verification teams to define acceptance criteria and support test planning linked to requirements.
• Communication:
  Strong technical writing, documentation skills, and presentation capabilities.
• Leadership:
  Experience leading a team of requirements engineers or analysts, mentoring and guiding junior members.
• Process Improvement:
  Ability to define and improve requirements processes aligned with industry best practices and organizational goals.
• Define requirement strategy & data model, document and implement the strategy

• Automotive embedded software development lifecycle. Domain experience in minimum one of the domains:
  Body controllers, ADAS, propulsion, cockpit (infotainment, instrument clusters, HUDs, HMI).
• Deep understanding of vehicle network communication protocols such as CAN, Ethernet, SOME/IP, and their implication on requirements.
• Familiarity with software architecture and layered automotive software stacks (Classic AUTOSAR, Adaptive AUTOSAR).
• Experience handling complex multi-domain system requirements and coordinating cross-functional dependencies (software, hardware, mechanical).
• Skilled in managing agile and V-model based projects in automotive software development.
• Knowledge of cybersecurity requirements and integration in automotive embedded systems is an advantage.