Proposes, aligns and maintain the technical scenario of the project:
The technical scenario consists in:
1/ A planning integrating all system deliveries planned and
interaction planned between the System, Software, Mechatronic
and System Validation sub projects.
2/ The system deliveries plan (System Release Plan) listing the
content of each planned delivery, in terms of mechatronic
product sample phase, functional content and validation level.
It is initialized to support the acquisition by the acquisition
team, and is their basis for all cost estimations. After awards,
before the kick-off review, the technical scenario must be reviewed
to fully reflect award conditions: this is done by the PACT
workshop, moderated by System PM, where the System TPM acts as
technical referent. For less complex projects, this task is
performed without a full PACT workshop but the system TPM always
brings the necessary technical support to System PM during alignment
with SW TPM, Mechatronic PM and System Validation TPM, as well as
relevant project-external Actors such as P2 Contributors. The system
TPM updates then weekly the corresponding documents, in accordance
with outputs of the reviews done by weekly steering committee
chaired by System PM, in which he acts as technical referent.
Leads the Releases Definition Boards for the detailed definition of
the content for each System Release, at the beginning of each System
Release development cycle.
Defines, tracks and drives countermeasures for technical issues
(including risk mitigation actions) involving several sub-projects
delegated to him by System PM, in his role of technical referent:
Ensures the activities related to Problem Resolution Management such
as Problem Identification and Logging, Root Cause Analysis until
Implementation, Verification/Validation and Closure, using
established and proven problem resolution methods (e.g. 5W,
Six-Sigma, Fishbone …).
Play a central role in the timely implementation of root cause
analysis and accompany the solution process with the appropriate
interface partners.
Reviews the problem resolution process in order to prevent
recurrence and learn any lessons for the future (update Lesson
Learnt Card, i.e Valeo Incident Management Tool - VIM). Furthermore,
he/she shall verify whether problems marked as closed have actually
been eliminated.
Prepares the regular reporting associated to the Main Technical
Referent Role:
Traceability between all Specifications/Use case to System Test
cases across the V Cycle.
Overall System performance in vehicle vs planned system
performance out of System Release Plan.
Performs weekly System sub-project steering meetings to plan and
review progress on tasks within System sub-project needed to achieve
the next system deliveries, and collect and monitor the action list
for each delivery.
Assure assignment and scheduling of needed resources in his team to
generate and review technically all deliverables expected from the
system sub-projects including: Compliance Matrix [CMx],
Configuration Management Plan (Baselining Strategy, Config
Management Items), Architecture & Function Hierarchy definition,
SFMEA, SyRS (function specification), Application data baselines.
Drives change request management activities related to system
sub-project.
Plan System DRs and TRs reviews according to System Metier
recommendations. Assign tasks to SYS Project Team.
Manage the System release plan supporting Sys PM Schedule.
Rate Overall System CCB.
Advise the System PM on the decision to approve product deliveries
to the customer.
Synchronize between Different Functions to enforce corrective
actions when needed.
Escalate at the right level.
Submit Project tailoring request.
REQUIRED SKILLS
Domain & Product Knowledge: Strong background in ADAS / Automated
Driving (Driving, Parking, and Core functions) and/or Automotive Compute
Control Units.
System Architecture & Design: Hands-on experience in system architecture
definition, design-to-cost approach, function distribution across subsystems
(Software, Hardware, Mechanical), and technical risk management.
Requirements Management: Expertise in translating high-level customer
requirements into detailed system and subsystem specifications and ensuring
interoperability across disciplines.
Quality & Industry Standards: In-depth knowledge of ASPICE process
frameworks, standardization enforcement, design review execution, and
knowledge capitalization.
Functional Team Leadership: Skilled in day-to-day management of dedicated or
shared R&D contributors, assigning work packages, and aligning resource
needs with department managers.
Team Motivation: Collaborative team player with a strong drive to mentor,
guide, and motivate engineers in a global matrix organization.
Customer Facing: Demonstrated success representing R&D directly to
OEMs/customers, acting as the primary interface for technical system topics
and cascading customer feedback internally.
Cross-Functional Collaboration: Exemplary oral and written communication
skills to bridge technical dialogues between global system architects,
métier disciplines (Purchasing, Industrial, HW/SW), and stakeholders.
QUALIFICATIONS AND EDUCATIONAL REQUIREMENTS
Bachelor’s or Master’s degree in Engineering (Electrical, Computer,
Automotive, Systems Engineering, or related field).
EXPERIENCE
Around 10+ years of professional experience in automotive R&D
activities.
Proven track record in functional and project management, leading
multi-disciplinary engineering teams across full project life cycles.
POSITION
The position is based in Japan reporting to Business unit in India/Japan.