They provide a skeleton Android project with some missing pieces that need to be completed in order for the program to work. This is a live coding session so it has to be done in the interview and not beforehand. You are able to look at the project however. I'll first say, I f*ing crushed the implementation. Chose to use the coroutine api functions and implemented a view model leveraging the Dagger dependency injection. Took me aprox 20 min to get it all in place and test it out. Solution worked first run. Interviewer was curious about why there were duplicates in the list of items from the backend. I debugged the response payload to show him they are all duplicates. Then he asked a followup question about data persistence when the user closes the app. I correctly answered using Shared Preferences. Overall it was really good, guess they went with someone more senior.

The recruiter initially reached out with several screening questions and scheduled a 1-hour live Android coding interview. I completed all the functional requirements asked by the interviewer within the allotted time. However, the recruiting coordination felt disorganized. In the initial outreach email (sent January 29), the recruiter included a forwarded template message stating that interviews would be paused for the rest of December due to holidays and resume on January 5th. This appeared to be a copy-paste oversight and gave the impression that my application was not reviewed carefully. While the technical interviewer was professional and the problem was reasonable, the overall candidate experience felt inconsistent. I would recommend more attention to detail in recruiter communication to improve candidate experience.