Android System Software Analyze

Job Description
Required qualifications / skills:
M.Sc in Software Engineering or similar relevant experience.
Experience working in application and/or service layer using Java and/or C++. Python expertise is highly meriting.
At least 5 years of software development in background in a Linux environment, preferably with Android based OS (Android 11).
Experience of non-functional development and requirements (Stability, Robustness, Performance).
Experience in Software analysis and fault tracing.
Experience with AOSP.
Experience in creating integration test cases.
Good English skill (written and spoken)

Meritorious:
Experience in Android stack in an automotive environment.
Python scripting.
QNX
Experience with setting up CI toolchains.
Experience working with power mode functions is meriting.
Driver’s license (B-level)

Job Responsibilities
The team members will work within a cross functional agile team and focus on the integration of android software on a Android Automotive OS-based Infotainment Platform, analyzing performance issues and performing fault tracing of the in-vehicle software and supporting systems.
Main responsibilities will be:
Software development and performance tuning for infotainment platform.
Performance analysis in the Android stack for the infotainment system
Creating test cases for integration testing of new OS updates and features to be implemented in the infotainment

Overall team responsibilities:
The System team will focus on testing non-functional KPIs for the next generation IVI platform.
The team receives KPI (or defines KPIs together with tech leads) that they analyze and create test cases for to produce data and scorecard about how well the system fulfills the system KPIs, e.g. non-functional test cases for system performance, system robustness, and system stability.
System capacity forecast for RAM, storage, CPU (touchpoint with HW team)
System optimization together with the internal Tier1 platform supplier.
The team develops testcases that secures that the system works after integrations event from internal Tier1 platform supplier (KPI acceptance).
Android or QNX bring-up orchestration.
The team is responsible for defining the build configurations.
Ownership of DHU logging functionality
Maintaining CI toolchain.