Software Architect

Project description This opening is for an ADAS Domain Controller project for a prestigious OEM, where Luxoft is working with the OEM teams to deliver a next-generation Platform solution based on AUTOSAR Classic, AUTOSAR Adaptive and QNX working together as a system interacting with a host of cameras, ultrasound sensors, internal and external Radars. Luxoft is collaborating on Signal and Service Management, Diagnostics, SW Update, Vehicle Config, QNX/Middleware and Software Architecture areas with the OEM directly. Luxoft is expected to delivery quality and expert support in the above areas, drive topics independently, liaise with other OEM stake holders to remove blockers. The ideal candidate needs to have endless curiosity and can pair a global mindset with locally relevant execution. You should be a gritty problem solver, have a never-give-up attitude and be a self-starter who can think of an out-of-the-box solution. The successful candidate will be a team player, display a balance of hard and soft skills, including the ability to respond quickly to Client's changing needs. Responsibilities Define services for in-vehicle platform software based on the requirements. Define Autosar Adaptive software components with communication between them. Define Architecture and design diagrams for software components and their interactions. Understand and optimize runtime and resource usage. PREEvision tool customization for imports, exports and model updates using Java Creation of automated consistency rules and table-based editors in PREEvision Definition, modeling and generation of different ARXML files for AUTOSAR Adaptive SKILLS Must have 5+ years in automotive: - ASPICE knowledge and hands-on experience in C++ - Linux/QNX/Android Automotive alongside classic microcontrollers 3+ years experience with Adaptive software clusters, with strong understanding of: - Adaptive Autosar-based software development and Architecture - Autosar Adaptive Software Components and Communication Experience in SOME/IP network binding, Automotive Ethernet, and DoIP Strong experience working with PREEvision for SoA modelling Strong knowledge of the PREEvision metamodel Strong knowledge of Diagnostic Log and Trace (AUTOSAR / COVESA) context: - DLT protocol internals: standard/extended header, ECU ID, App ID, Context ID, log levels - COVESA/GENIVI dlt-daemon ecosystem: dlt-viewer, libdlt, control messages, offline trace, gateway mode for multi-node setups - AUTOSAR specifics: Classic (Dlt) and Adaptive (ara::log) Nice to have 1. ECU Calibration 2. IPC Communication 3. Ethernet Stack 4. Automotive Safety