3-phase interview process. 1. round - initial call with the recruiter (behavioral questions) followed by a short Hackerrank challenge and a questionnaire also requiring code sample. Nothing too complex. 2. round - 1 week coding challenge. Project topic really depends on the team for which you're interviewing. In my case it was a Java web app running in Spring Boot-provided embedded Tomcat and talking to in-memory db. Once again, nothing too difficult. Quite frankly, 1 week might be a little bit of an overkill for an application of this size (my recruiter even gave me 2 extra days as I couldn't get to it earlier) as even if you don't know the stack it will hardly take you more than half a day. I decided to take advantage of the time turning the assignment into my personal project as I haven't touched Spring for several years and thus wanted to know how much did the framework evolve. 3. round - 3 Skype interviews - 2 with Software Engineers, 1 with VP. Questions weren't too difficult (basic algorithm questions from CtCI and a synchronization problem). VP asked exclusively about the project (from 2. round). Everyone is really nice and there's enough time to ask about the company. I ended up getting an offer on the same day - had another offer deadline - but in the end I decided to decline it in favor of a 3rd offer from one of my top 2 company preferences.

As usual, the first interaction is with HR/recruiter. After a first quick screening, I've been asked to complete a coding challenge of medium difficulty, and it was actually fun. After the challenge is evaluated (in a positive way), there is a round of three interviews with three engineers. The interviews focus on basic algorithm, system design and reviewing your own challenge (may be with some questions about modifying it a little). The overall process looked fair and clear.