Describe to the employer what experience you have and get interesting career offers! Let other users advise you on your choice.
SPARROW EMOBILITY is looking for employees for positions:
lead software engineer
lead software engineer
Working hours
full-time
Responsibility
ultimate ownership of the Android software components of the product including design, development, testing and integration
work alongside our C/U/I-X designers in ensuring we develop a user-centred, functional and beautiful product
ensuring delivery of high-quality software with automated testing and builds CI/CD etc
bidirectional integration with lower level software and hardware including OS/RTOS/VHAL
as our Senior AOSP Software Engineer you will be responsible for setting the direction of and implementation of the complete end-to-end AAOS system including high-level consumer “apps”, and cloud connectivity components
work with the Head of Engineering and Head of Product in leveraging the features and benefits of AAOS to create an extensible, future proofed product suitable for multiple clients with varying requirements
with our Electrical Engineer, plan, design and build a software a hardware emulated vehicle, allowing integration testing of the electrical components through to the AAOS layer and cloud
Requirements
at least 8 years experience with development in Android and related technologies with a very strong understanding of Android's architecture
proficient with Java and Kotlin
A passion for technology and using it for positive change in our world
commercial knowledge of AAOS, or AOSP at a very minimum
experience of integration with cloud services and APIs and ideally will have been involved in helping to spec these services
experience of integration with low-level hardware through VHAL/CAN/LIN/Ethernet etc
experience of working in a multidisciplinary team including C/U/I-X designers and Product Owners
you have a genuine passion in developing full-stack applications, technical architecture, business logic, UI, clean code, automated testing and best practices for long-term product development and support
The page has changed.Please, click here to reload page