Roles
Starling Bank
Android Engineer - Engine by Starling
Explore roles
This role has expired
Starling Bank
Android Engineer - Engine by Starling
Multiple locations
Hybrid
Description
Hybrid requirements: This role has flexible working patterns.
Engine by Starling engineers are excited about helping us take our award winning banking platform to countries all over the world, regardless of what their primary tech stack may be. Hear from the team in our latest or our case studies with .
We are looking for engineers at all levels to join the team. We value people being engaged and caring about customers, caring about the code they write and the contribution they make to banking worldwide. People with a broad ability to apply themselves to a multitude of problems and challenges, who can work across teams do great things here at Engine, to continue changing banking for good.
As an Engineer you will:
Contribute to our award winning Android app and internal tooling
Build new features and products from scratch in a configurable way
Share your knowledge with those around you, contributing to our learning culture
Own your projects, working in small teams across the bank to collaboratively deliver
Aim for greatness in everything you do, staying curious and inquisitive
Be part of a scaling team and organisation as we change banking for good
You are empowered to make the decisions necessary for the project and to provide insight to the team leads. You’ll also be working closely with other Android engineers with a variety of experience levels and interests, helping us improve and develop our Android app, CI automations and tooling. You’ll be committing, reviewing and shipping new code right from the first week!
Requirements
As an Android engineer, you’ll report to and catch-up regularly with a mobile lead engineer who will support you on your journey in Engine. We have a strong collaborative and open culture here so you’ll find support outside your team too.
As a fully digital bank, we are looking for engineers that are able to understand and prioritise security when implementing new features, fixing bugs or making technical improvements, across all the layers. Our team is designing, building and releasing new screens every day, for this reason we are interested in people with a particular focus on Accessibility along with writing clean and maintainable code.
The way to thrive and shine within Engine is to be a self-driven individual and be able to take full ownership of everything around you: From building the code, shipping and maintaining it, to sharing knowledge with your colleagues and making sure all processes are efficient and productive to deliver the best possible results for our customers.
Our aim is to deliver stable, resilient and high quality code, that is why testing is another key quality we look for when expanding our team. We use Espresso to write our UI/E2E Test and JUnit to write our Unit Tests across all layers of the application, as well as manually test all features before they go into production. We also work closely with QA engineers to ensure we have an additional level of testing when working on complex feature delivery.
The Android world
In the Engine Android project we are proud to be working with some of the latest technologies in the industry. When adopting new technologies we always consider as a team whether it’s the best choice for our product and our users.
We are currently in the process of building a number of SDKs for our clients utilising the modules we’ve already created in the Starling UK App. We’ll be using these to support the development of an app in Romania with SaltBank and build an entirely new banking app for one of our partners in Australia called AMP Bank, a really exciting opportunity! In the Engine SDKs we generally aim to use the latest technology as our clients would expect, but, we also rely heavily on the existing Starling codebase which uses some older libraries too, so you’ll need a good understanding of a wide range of libraries and technologies. We use Dagger, Realm, Retrofit, Coil, Compose, Coroutines and Compose, but there’s still a lot of work to do migrating from XML layouts and RxJava2.
Building SDKs that we plan to launch internationally can present some new challenges, so if you’ve ever had experience maintaining a library, contributing to OSS, or have dealt with Internationalisation we’d love to hear about it. If that’s all new to you, don’t worry, we’re learning too!
We want our app to look great for the Android platform and have worked closely with our designers to set up a component library and have themed our app accordingly. Feature parity is important to us so Android and iOS apps are often built alongside each other.
As a team we meet together every week to talk through pain points and potential improvements we’ll like to make to the project. We regularly meet in real life to attend conferences and meet-ups together too!
Role tech stack
Starling Bank
Android Engineer - Engine by Starling
London
This role has expired