They provided a skeleton Android project with some missing pieces that needed to be completed for the program to work. This was a live coding session, so it had to be done in the interview and not beforehand. You were able to look at the project, however.
I'll first say, I absolutely crushed the implementation. I chose to use the coroutine API functions and implemented a ViewModel leveraging Dagger dependency injection. It took me approximately 20 minutes to get it all in place and test it out. The solution worked on the first run.
The 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 were all duplicates.
Then, he asked a follow-up question about data persistence when the user closes the app. I correctly answered using SharedPreferences.
Overall, it was really good. I guess they went with someone more senior.
Implement a solution for displaying the data payload from the backend.
The following metrics were computed from 1 interview experience for the DoorDash Android Developer role in Seattle, Washington.
DoorDash's interview process for their Android Developer roles in Seattle, Washington is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for DoorDash's Android Developer interview process in Seattle, Washington.