I had a great experience during my interview process. A recruiter approached me, but at the time, I didn't think it was the right opportunity. The company offered to connect me with a manager who gave me insight into the company, the opportunities available, and answered a ton of questions. The next step was a take-home assignment; it was Android-specific. The task itself was straightforward and comparable to those given by other companies. After the assignment, they invited me for an onsite (pre-COVID-19 😢) interview. I interviewed with three engineers, a director, and the hiring manager, and the recruiter. I also had lunch with another manager. They gave me a verbal yes the same day of the interview, and an official offer the week after. The entire process ~6 weeks, but I was also taking it slow.

Phone screen round consisted of implementing a Card game with some rules defined. Logic was simple to implement. 2nd part of question consisted of making the game flexible. For eg: Variable number of cards and variable numbers of players instead of 2. It was already 4 pages of code with first part of question and no time left to implement extensions. It felt like a typing speed test instead of a programming exercise. I focused on modularity, readability and class designs but looks like these were less relevant as compared to able to get to the 2nd part of the question. It would have been a better strategy to directly go for the extension of the problem with bit less focus on clean programming style. Also, it was strange to expect to account for a standard deck of card to extend beyond 52 cards. Either don't use 52 cards standard deck in the problem or mention that it is not a standard deck. Interviewer was junior and asked to print the output while there were already methods returning the desired output. Interrupted many times to initialize things in other classes which were not part of the current code flow. I usually leave the initialization and wiring for the end.