Lead Middleware Architect

Job description

**12+ years in embedded software; 5+ years in automotive cockpit or ADAS domain in a senior/lead engineering role Deep expertise in QNX RTOS: IPC mechanisms (pulse, channel, message passing), memory model, process lifecycle, hypervisor fundamentals** Hands-on experience with Android Automotive OS: VHAL architecture, HAL interface design (HIDL/AIDL), CarService internals, multi-display management Strong Adaptive AUTOSAR knowledge: ara::com, ara::exec, ara::diag, ara::phm, ara::nm, ara::crypt – including manifest/ARXML authoring and deployment SOME/IP protocol: service discovery, event/field/method primitives, timing contracts, and integration with Classic AUTOSAR COM stack via ComXf and S2S transformers **Hypervisor middleware patterns: virtio device model, shared-memory IPC across VM partitions, display compositor integration, boot sequencing** Demonstrated ability to produce and own architecture documentation: block diagrams, interface specifications, timing analyses. Practical knowledge of Ethernet networking in automotive: VLAN, AVB/TSN, CAN/LIN; familiarity with AUTOSAR Ethernet stack configuration Security fundamentals: TEE (OP-TEE or TrustZone), HSM integration, SecOC, authenticated boot chains, key provisioning ISO 26262 awareness: understanding of ASIL decomposition, software safety requirements, and their implications for middleware partitioning