Data Platform Architect(Vehicle)/电子电器架构数据架构师 ID201957

Objective of job (abbreviated)
To define and drive a robust, scalable, and resource-efficient in-vehicle data architecture on the IVI Android domain,
enabling stable cross-domain data ingestion, transformation, and delivery to both in-vehicle applications.
The role ensures that multi-source vehicle data can be consistently abstracted and consumed under real-world vehicle constraints, while making sound architectural trade-offs based on prior hands-on in-vehicle development experience..
Task description
In-vehicle Data Transformation Architecture & Delivery
• Lead the design and implementation guidance of the low-level data transformation framework in the IVI Android system.
• Perform system-level design for multi-source data ingestion,
• Define and standardize data management and updatae strategies:
• Ensure the data transformation logic can run stably for long periods in a vehicle environment, with controlled and predictable resource usage
Cross-Domain Data Subscription Design & Implementation
• Design and deliver cross-domain data subscription mechanisms at the IVI Android system layer
• Select appropriate communication mechanisms based on vehicle constraints
• Control subscription granularity and frequency to avoid unnecessary impact on vehicle communication bandwidth and system load.
In-vehicle to Cloud Data Pipeline Design
• Lead the design and implementation guidance of data pipelines from vehicle to cloud
• Design for real vehicle network conditions (cellular networks, bandwidth fluctuation):
• Ensure critical data delivery is guaranteed, while non-critical data does not interfere with core vehicle functions
Application-Layer Design & Capability Abstraction
• Design application-layer usage patterns based on IVI Android platform capabilities, including:
• Define clear VAL APIs / SDKs that:
• Ensure applications are decoupled from VAL-layer implementations and can evolve independently.
Test Bench & Issue Diagnosis Support
• Familiarity with test benches / hardware-in-the-loop (HIL) / simulation environments
• For critical issues, provide diagnosis paths grounded in real vehicle behavior, not theoretical assumptions.
Architecture Trade-offs Under Vehicle Constraints
Architecture Governance & Technical Gatekeeping (No Daily Coding)
Qualification
o Education
Bachelor’s degree or above in: Computer Science,Software Engineering, Electrical Engineering, Automotive Engineering;
Continuous learning mindset in:Automotive software architecture, Embedded systems, Data-driven vehicle platforms
O Experience
Must-Have Qualifications：
-Deep understanding of why the VAL layer exists and where its real challenges lie
-Architecture decisions driven by hands-on experience running real in-vehicle systems
-Proven ability to design solutions that are practical, stable, and resource-efficient under vehicle constraints
-8+ years of software engineering experience, including:
A. Hands-on in-vehicle software development experience (must have written production code in the past)
B. First-hand experience with vehicle resource and communication constraints
-Practical experience in at least two of the following areas:
A. VAL / middleware / data abstraction layer design and implementation
B. Cross-domain data subscription or aggregation
C. In-vehicle-to-cloud data pipeline design
-Solid knowledge of in-vehicle communication technologies:
CAN / SOME-IP / DDS / Socket / MQTT, etc.
-Ability to assess and balance:
A. Performance
B. Stability
C. Bandwidth usage based on engineering trade-offs
Nice-to-have:
Experience with VSS or unified vehicle data models
Experience building vehicle status, health, or monitoring systems
End-to-end experience with IVI ↔ Cloud data pipelines
Experience delivering production or pre-production vehicle programs