Firstly, keep in mind that on Betterment's blog site, they have a post about how they go about the interview process, and in my experience, they followed that process they describe online almost exactly. Read that, and you should have a good idea of what to expect.
Throughout the process, the technical recruiter, who was the guide through the whole thing, was very clear about timing expectations, and next steps.
The things that other people say here about being surprised to be asked about Ruby, wasn't the case for me. They didn't mention anything about Ruby ahead of time, and I didn't get any questions about Ruby. Everything I had to deal with technically, they gave me a heads up about, and there was nothing that wasn't directly related to Android development in Kotlin.
Technical interview portions were all pretty standard Android development in Kotlin. If you know your stuff you should be fine. I learned RxJava like 2 weeks earlier, and that was definitely helpful.
Non-technical portions mainly focused on my past and personality. They really are looking for good culture-fit; that's a huge part of their focus. They want collaborative people driven to help each other and the users.
The following metrics were computed from 1 interview experience for the Betterment Mobile Software Engineer role in New York, New York.
Betterment's interview process for their Mobile Software Engineer roles in New York, New York is incredibly easy as the vast majority of engineers get an offer after going through it.
Candidates reported having very good feelings for Betterment's Mobile Software Engineer interview process in New York, New York.