The process started off with a basic non-technical phone screen. The recruiter asked how soon I would ideally like to make a decision (to determine how the fast the interview process will go). I really liked this attention to detail as other companies have reeaaally drawn the process out over several months through slow scheduling and decision-making.
After that, I moved onto the technical phone screen with a back-end engineer where I was asked a few questions about data structures and some of my projects. The meat of this phase was a coding session in CoderPad which was mostly object oriented stuff like creating a few classes and adding a data structure in the mix. Not too bad I thought.
Then part 1 of the on-site interview came along, there were two technical sessions within a Java (Spring Boot) setup and a session with the director of backend engineering. The first session was pair programming an algorithmic feature related to the companies area and the second was more related to database design and ORM. Could've executed my thoughts a bit more clearly in these two parts. Then the third session was a straightforward Q&A. Unfortunately though, I didn't make it to part 2.
What is a database?
The following metrics were computed from 2 interview experiences for the Betterment Software Engineer, Backend role in New York, New York.
Betterment's interview process for their Software Engineer, Backend roles in New York, New York is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Betterment's Software Engineer, Backend interview process in New York, New York.