I applied online for the Senior Android Engineer role in May-June 2017 in San Francisco, CA. I had a pleasant phone chat with the recruiter at Instacart and a follow-up interview with a lead engineer on the Instacart Android team.
I was asked to implement a simple Android app for the take-home challenge. While I will not reveal the nature of the app out of respect for Instacart, the challenge is required to be finished within approximately 4 hours and is expected to be of production-level quality.
While this should not be challenging under normal situations, the hard time requirements made it very difficult to plan, design, implement, and test the app within the allotted time.
Had it not been for the hard ~4-hour requirement, I would have gladly spent additional hours to implement a proper mobile architecture (MVP/MVVM), as well as unit tests—things that would be expected of a production-ready app.
Some suggestions for Instacart for improving the take-home challenge experience:
Please remember, there are thousands of different Android devices with differing Android API versions, and candidates do not have the resources to test against many different device profiles. Not everyone has access to a Nexus 6 or a Samsung Galaxy S3 Mini sitting around to test against.
This will increase the quality of submissions and minimize confusion over expectations of this take-home challenge—a win-win for both Instacart and candidates.
Take-Home Challenge: Implement a simple Android app that meets the challenge specifications.
The following metrics were computed from 1 interview experience for the Instacart Senior Android Engineer role in San Francisco, California.
Instacart's interview process for their Senior Android Engineer roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Instacart's Senior Android Engineer interview process in San Francisco, California.