Lead System Architect (TCU)

Objective of Job Responsible for the definition, optimization, and end-to-end technical alignment of telematics system architecture, with strong focus on both hardware and software architecture as well as the integration of peripheral components and in-vehicle interfaces. As lead system architect, drive the full lifecycle from

analysis, architecture concept development, technical specification, and design review to supplier implementation follow-up, system integration, and validation. Define and maintain the architectural framework for core TCU hardware building blocks, embedded software layers, operating environment, communication paths, power and wake-up behaviour, and the interaction between the TCU and integrated/peripheral components such as antennas, GNSS, microphones, speakers, USB, Ethernet, CAN, and other connected ECUs. Ensure that hardware architecture, software architecture, and interface definitions are technically consistent and scalable across vehicle projects, and support reliable realization of connectivity, telematics, diagnostic, and remote service functions. Clarify architectural dependencies between main-stream modem suppliers with NAD/SiP, MCU/SoC, memory, power supply, bus systems, base software, middleware, application functions, and external components to achieve robust system behaviour and production readiness. Main tasks

1. 01

   Design and own the end-to-end TCU system architecture, including hardware architecture, software architecture, and technical integration with peripheral components and in-vehicle interfaces. Define the overall TCU system architecture, including core hardware building blocks, computing and communication domains, software layers, interface concepts, and system partitioning principles. Specify the architectural design and interaction of key TCU hardware and software elements such as modem, MCU/SoC, memory, power supply, operating environment, base software, middleware, and application functions. Define and maintain technical interfaces between the TCU and peripheral components, including antennas, GNSS, microphones, speakers, USB, Ethernet, CAN, and other connected ECUs, ensuring signal flow, compatibility, and robust integration behaviour. Develop system requirements and subsystem specifications covering architecture concepts, interface definitions, communication paths, power and wake-up behaviour, diagnostics, performance, and failure handling. Assess technical feasibility and architectural consistency across TCU hardware, embedded software, vehicle E/E architecture, and peripheral component integration, and drive solution decisions for complex cross-domain issues. Define architecture validation scope and review implementation maturity for hardware/software integration, interface robustness, system stability, sleep/wake-up behaviour, and interaction with external components and vehicle networks.

2. 02

   Co-drive the architectural alignment of TCU system design with backend, cloud, and external interfaces, with focus on hardware/software architecture implications and integration boundaries. Support the definition and evolution of external communication architecture where backend services, cloud functions, and offboard interfaces impact TCU software architecture, data handling, and system interaction behaviour. Review architectural impacts of backend and cloud interface changes on TCU system design, including software partitioning, communication paths, signal flow, diagnostics, and interaction with relevant ECUs and peripheral components. Support cross-domain issue analysis and solution alignment when remote services, diagnostic communication, or cloud-related functions affect TCU hardware/software integration, external interfaces, or peripheral component behaviour.

3. 03

   Support China regulation related topics from the perspective of TCU system architecture, including hardware/software architecture and peripheral component integration. Review China-specific regulatory and data compliance requirements for their impact on TCU hardware architecture, software architecture, interface design, and system integration concepts. Evaluate architectural implications for communication paths, data handling, diagnostics, network topology, and interactions between the TCU, connected ECUs, and peripheral components. Provide feasibility assessment and implementation impact analysis for required architecture adaptations, interface changes, and integration constraints in China-specific vehicle projects.

4. 04

   Co-shape future TCU system architecture concepts with focus on hardware/software architecture evolution and robust integration with peripheral components and vehicle networks. Monitor technology trends relevant to next-generation TCU architecture, including hardware platforms, software stack evolution, communication frameworks, network topology, and system partitioning concepts. Benchmark architectural solutions for TCU interaction with peripheral components and external interfaces, including antennas, GNSS, audio components, USB, Ethernet, CAN, other ECUs, and connected vehicle services. Provide technical input for future TCU system architecture direction, covering hardware/software integration, interface design, power and wake-up concepts, data communication, diagnostics, and scalability across vehicle projects.

5. 05

   Support management team in technical decision-making from the perspective of end-to-end TCU system architecture, including hardware architecture, software architecture, and peripheral component integration. Provide technical recommendations on TCU architecture strategy, including hardware/software partitioning, interface concepts, vehicle network integration, and the interaction between the TCU and peripheral components. Support roadmap planning and solution reviews for key architecture topics such as hardware platform evolution, software stack design, power and wake-up concepts, diagnostics, communication paths, and interface robustness. Support decision-making with technical assessment, risk evaluation, trade-off analysis, and solution comparison across TCU hardware architecture, software architecture, external interfaces, and peripheral component integration. Qualification Education MS/BS in Computer Science, Electronic Engineering, Communication Engineering, Automotive Engineering or similar education. Solid background in embedded systems, E/E architecture, IP networking, vehicle connectivity, or telematics system development. Experience More than 8 years of experience in automotive telematics or TCU development at OEM or Tier 1 level. Solid experience in TCU system architecture design, including hardware architecture, software architecture, and system integration. Experience in vehicle E/E architecture and TCU integration with ECUs, CAN, Ethernet, diagnostics, and key peripheral interfaces. Experience across complete vehicle development projects and supplier collaboration from architecture definition validation and release. Specific Knowledge Strong knowledge of end-to-end TCU system architecture, including system decomposition, functional partitioning, and architecture trade-offs. Strong knowledge of TCU hardware architecture, including NAD/SiP modem, MCU/SoC, memory, power supply, and key peripheral interfaces. Strong knowledge of TCU software architecture, including embedded software layers, base software, middleware, diagnostics, and application functions. Good knowledge of vehicle E/E architecture, ECU integration, CAN, Ethernet, and diagnostic communication. Good knowledge of TCU interaction with peripheral components such as antennas, GNSS, audio, USB, and other connected ECUs. Good knowledge of requirement engineering, technical specification, and architecture-related validation. Strong analytical, coordination, and communication skills for cross-domain architecture topics and supplier collaboration.