Android Engineer Engine by Starling
Starling
No recruiters. Founders reply directly.
No recruiters. Founders reply directly.
At Engine by Starling, we are committed to partnering with leading banks globally to foster rapid growth through our cutting-edge technology. Engine is Starling's software-as-a-service (SaaS) business, built upon the technology that powers Starling Bank, and recently established as an independent entity. Engine engineers are integral to our rapid-paced environment, focused on innovation and disruption at the forefront of fintech. Our flat structure empowers decision-making, encouraging innovation and collaboration across all levels.
As an Android Engineer, you will:
We are seeking engineers at all levels who are passionate about customers, code quality, and contributing to global banking. Ideal candidates possess a broad ability to solve diverse problems and collaborate across teams. You will report to and regularly connect with a mobile lead engineer.
Security is paramount in our fully digital environment, so we seek engineers who prioritize it when implementing new features, fixing bugs, or making technical improvements. Given our daily release cycle for new screens, a focus on accessibility and writing clean, maintainable code is essential.
Engineers thrive by being self-driven and taking full ownership of their work, from development and maintenance to knowledge sharing and process optimization.
Delivering stable, resilient, and high-quality code is a key objective, making testing a crucial skill. We utilize Espresso for UI/E2E tests and JUnit for unit tests across all application layers, complemented by manual testing. Close collaboration with QA engineers ensures an added layer of testing for complex feature deliveries.
In the Engine Android project, we leverage modern technologies while also maintaining the existing Starling codebase, which includes older libraries. Therefore, a strong understanding of a wide range of libraries and technologies is necessary. Current technologies include Dagger, Realm, Retrofit, Coil, Compose, and Coroutines, with ongoing migration from XML layouts and RxJava2. Experience with SDK maintenance, OSS contributions, or internationalization is beneficial but not required.
Our interview process is a collaborative dialogue designed for mutual understanding. It generally includes: