Senior Android engineer shipping shopper lifecycle features that move Instacart's marketplace health

Interview for Instacart's Shopper Activation and Engagement team, owning Kotlin features across the shopper app's activation, onboarding, earnings, ratings, and retention experiences. Expect deep Android architecture questions (Kotlin, RxJava, Dagger, Jetpack Compose) paired with experimentation and marketplace-metrics thinking, given the 5+ years Android and 2+ years consumer-scale bar.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Kotlin, RxJava, Dagger, Jetpack Compose architecture
End-to-end feature ownership with experimentation (A/B testing)
Marketplace/growth metrics thinking
App architecture evolution & modularization
Operational excellence: performance, monitoring, observability
Mentorship and raising engineering standards

Common question themes

A shopper/consumer-facing feature you owned from design through A/B test to launch

RxJava/Dagger architecture decisions and a Jetpack Compose migration you drove

Defining success metrics and instrumentation jointly with Product and Data Science

Improving app stability, performance, or observability at scale

Concurrency and CS fundamentals as applied to a real Android bug

Mentoring engineers or raising code quality/testing standards on a team

How candidates describe it

Real Senior Android Engineer interview stories — retold from candidates' public write-ups, with sources.

Google · L3 Software EngineerOffer

Google L3 software engineer interview: phone screen, four coding rounds, and the Googleyness round

A candidate with two years of experience went from recruiter outreach to offer over about four months. The onsite was four 45-minute coding rounds — three of them featuring binary trees — and one round turned into a 25-minute chain of follow-ups about approximating an optimal solution at scale.

Interviewed June 2020 · Bangalore, IN

Google · L4 Software EngineerNo offer

Google L4 Software Engineer Interview: Eight Rounds, No Offer

An L4 Software Engineer candidate went through two phone screens, three onsite rounds, a culture conversation, and a team-matching call with a Google hiring manager, then watched the process stall for about a month and a half over a tightened experience requirement before an added extended round ended without an offer.

Interviewed February 2024 · Not specified

Google · L5 Software EngineerNo offer

Google L5 software engineer interview: phone screening, three onsite rounds, system design, and a late rejection

A candidate interviewing for an L5 role went through a phone screening, three onsite coding rounds, a mobile system design round, and a Googleyness and Leadership round. Two of the four technical rounds went poorly by the candidate's own assessment, and after roughly two months of silence the recruiter reported that the role had been closed.

Interviewed January 2023 · Not specified

View the original posting

All Instacart interviews