Simple process. 1. Initial recruiter phone screen. 2. Technical interview with team lead and team member. (this was very heavily focussed on Android app security after mentioning it on my CV) 3. Simple technical test using some of their API's. (They asked me to additionally implement certificate pinning and also had to show how I would encrypt and store the access token locally on the device). After the test I was ghosted, I followed up with the (previously) very engaged and responsive recruiter and got absoultely nothing, feel like I've dodged a bullet considering they couldn't even be bothered to send a generic rejection email.

In the first instance a recruiter and I had a phone interview call. He was very professional and asked me questions like "what about Starling appeals to you?" I then met with the engineering lead over a video call. He was extremely polite and accepting. He did not ask the usual cliche questions. He asked me why I made certain job transition choices. Anything I said, he was taking into quiet consideration. Overall, he treated me with respect and progressed me onto the next round. The next round was a take-home test using their APIs. Bog-standard stuff. After submitting that, I got a phone call from the recruiter saying they have rejected me based on my test. Very pleased that they gave feedback. They were extremely nitpicky about my code and some stuff like, "too many extension functions" was a bit ridiculous. However, at least they gave proper feedback! My improvements to Starling would be to have more team members join the interview call.