Babylon Android Engineer interviews, decoded.

First, there was a phone call. Then, they sent a link to a GitHub repo for the Android team, which had the tasks to do and a list of potential questions for the in-person interview. I requested a week for the take-home exercise, where I could either submit an existing app or complete their described project. I got feedback on it within a few days, which was helpful. After that, I had a half-day onsite interview with several parts, covering Kotlin, Android UI and architecture, reactive functional programming, and how I'd fit with the team culture. They were transparent throughout the process, gave me detailed feedback, and extended an offer about a week after the final stage.

My pet project was so well-documented and complete that they let me skip the initial tech test and go straight to the final onsite interview. The onsite was about 4 hours long, with breaks, and I met with various people from different teams in about 45-minute blocks. Since it's a big company with diverse roles, these mini-interviews make sense to see how everything connects and for you to get a feel for it. They are very open about the hiring process, so if you prep using their playbook, you should be good.

The interview process is laid out in the Babylon Android Playbook on their github page and they stick to it. It was pretty enjoyable, I got to chat with different people like designers, product managers, and other engineers. Before the on-site interviews, there's a take-home coding test that seems to be a good way to gauge a candidate's skill level.