Section Lead ADAS & Base Vehicle

§ Lead the business, development and daily operation of ADAS, parking and Base Vehicle Abstraction & communication function in the team. (Parking, Android Vehicle Abstraction, communication with QNX, VCPU and cross domains, Settings)

§ Organize and manage the driving function section team to fulfill the projects’ requirements and targets on time with good quality.

§ Manages the customer requirements from HQ and China local CFO/FOs.

§ Owns the software system requirements (definition, maintenance, process and progress)

§ Lead the communication and collaboration of software/system requirements and development.

§ Responsible for the clear definition and specification of the logics and sequences of software functions and features.

§ Responsible for the system architecture and software architecture design of driving functions.

§ Responsible for intelligent cockpit communication and software interface definition.

§ Responsible for sorting out the underlying software, middleware, application software solutions and interface design of the intelligent cockpit; (Connectivity, Vehicle functions, Driving Functions, AD, ADAS, Parking, android framework and related IVI applications)

§ Responsible for well planning and utilization of team budget and resources.

§ Lead the business, development and daily operation of ADAS, parking and Base Vehicle Abstraction & communication function in the team. (Parking, Android Vehicle Abstraction, communication with QNX, VCPU and cross domains, Settings)

§ Organize and manage the driving function section team to fulfill the projects’ requirements and targets on time with good quality.

§ Manages the customer requirements from HQ and China local CFO/FOs.

§ Owns the software system requirements (definition, maintenance, process and progress)

§ Lead the communication and collaboration of software/system requirements and development.

§ Responsible for the clear definition and specification of the logics and sequences of software functions and features.

§ Responsible for the system architecture and software architecture design of driving functions.

§ Responsible for intelligent cockpit communication and software interface definition.

§ Responsible for sorting out the underlying software, middleware, application software solutions and interface design of the intelligent cockpit; (Connectivity, Vehicle functions, Driving Functions, AD, ADAS, Parking, android framework and related IVI applications)

§ Responsible for well planning and utilization of team budget and resources.

Education

· Bachelor degree or above (including degree), major in electrical engineering, computer sciences, automation, mechatronics, vehicle engineering, electronics or software

Experience

· At least 5 years working experience in the software development of infotainment/ADAS domain in OEM/Tier 1.

Knowledge

· Good knowledge and experience in Vehicle Abstraction, Parking, Settings functions and cross system (QNX, vCPU, ethernet), cross domain (AD/ADAS, Body and etc.) tof infotainment system.

· Experience in real production level lifecycle of software architecture and software development.

· Good knowledge in requirements, specification of infotainment related functions

· Good knowledge and experience in working with agile development methodology and worked with scrum teams and sprint planning, user cases, user story creation.

· Experience in defining the function and business logics of software feature/functions, module and components.

· Have good understanding of infotainment, instrument cluster, ADAS/AD, driving related terminology, process and collaboration with partners, suppliers and various departments in OEM

· Proficient in the functions and systems of the Internet of Vehicles and intelligent cockpit field, familiar with the basic principles of each system, system functions, interface design, etc.;

· Have good knowledge and experiences in product definition, customer facing product design, rollout and customer handling, or AI related solution application, AI solution integration and landing would be preferred.