System Solution Architect
Role Summary
The solution architect is responsible for defining end‑to‑end system architecture for automotive electronic domains including digital instrument cluster, connectivity & telematics, in‑vehicle audio/infotainment, and vehicle control unit (VCU). The role bridges OEM requirements, system design, and software/hardware implementation, ensuring scalable, secure, and future‑ready vehicle platforms.
Key Responsibilities
- System Architecture & Design
- Define end‑to‑end architecture for:
- Digital Cockpit / Instrument Cluster
- Telematics Control Unit (TCU)
- Connectivity (4G/5G, Wi‑Fi, Bluetooth, GNSS, V2X)
- Audio/Infotainment systems
- VCU interaction with powertrain and vehicle domains
- Create logical, functional, and technical architecture
- Define SoC selection, OS strategy (QNX, Linux, Android), middleware, and abstraction layers
- Cluster & Cockpit Systems
- Architecture for:
- Instrument Cluster (CAN/LIN/Video/Ethernet inputs)
- HUD interface coordination
- Graphics pipelines (GPU, display controllers)
- Ensure compliance with ASIL, ISO 26262, safety and security mechanisms
- Performance optimization (boot time, frame rate, startup latency)
- Connectivity & Telematics
- Design telematics architecture including:
- OTA (SOTA/FOTA)
- Remote diagnostics, vehicle tracking
- Cloud integration (AWS, Azure, proprietary OEM clouds)
- Define security architecture:
- PKI, Secure Boot, HSM, TLS, certificate lifecycle
- Work with backend/cloud teams for API and data flow design
- Audio & Infotainment Systems
- Define infotainment and audio system architecture:
- Android Automotive / Linux‑based head units
- Amplifier and speaker topology
- Audio pipelines (AEC, ANC, beamforming)
- Support voice assistants, media streaming, wireless projection
- (Android Auto, CarPlay)
- Ensure user‑experience KPIs (latency, sound quality, reliability)
- Vehicle Control Unit (VCU)
- Interface definition between VCU and:
- Powertrain, BMS, ADAS, Body Control
- Define communication architecture:
- CAN, LIN, Automotive Ethernet
- Support drive modes, torque arbitration, fail‑safe behavior
- Standards, Safety & Compliance
- Ensure compliance with:
- ISO 26262 (Functional Safety)
- ASPICE
- UNECE R155/R156 (Cybersecurity & OTA)
- Lead concept phase → system design → SOP readiness
- Conduct architecture reviews and technical risk assessments
- Stakeholder & Program Leadership
- Act as technical authority for OEM and Tier‑1 discussions
- Translating customer requirements into technical solutions
- Guide development, testing, validation, and integration teams
- Mentor engineers and contribute to architecture best practices
Technical Skills
- Automotive EE/E&E architecture
- Embedded systems (C/C++, Yocto, Android Automotive)
- Automotive networks: CAN, LIN, FlexRay, Ethernet
- AUTOSAR (Classic & Adaptive)
- Telematics & Connectivity stacks
- Audio systems and DSP basics
- OTA and cloud integration
Education & Experience
- BE/BTech or ME/MTech in Electronics, Embedded Systems, or Automotive
- Typically, 10+ years in automotive electronics with solution/architecture ownership
- Experience working with OEMs or Tier‑1 suppliers
Good to have
Ability to communicate effectively with Japanese or German