Instacart·Software Engineer·Technical Phone Screen
- Implement a function to decode an encoded password string.
“Had seen something like this before so the solution came together pretty fast.”
Large Enterprises
Most of these Instacart write-ups come from Software Engineers (45), then Machine Learning Engineers (5) and Data Scientists (3). The most reported rounds are the technical phone screen (45), the system design round (5), the onsite coding round (2) and the online assessment (1).
54 interview notes · updated Jun 2026
“Had seen something like this before so the solution came together pretty fast.”
“Took me a minute to see that binary search was even applicable here.”
“The greedy part seemed straightforward but the T-shape tripped me up.”
“Basically a ranked filter problem.”
“Felt straightforward at first so I jumped straight to the API signature without thinking about the storage layer.”
“I got the basic case working pretty quickly with a stack, pushing characters and repeat counts as I scanned through.”
“The O(log n) constraint is basically telling you to run binary search twice.”
“This is basically the whole interview wrapped into one prompt.”
“The core math wasn't bad, overlap of two intervals is just max(start1, start2) to min(end1, end2), multiply by rate.”
“Levels 1 and 2 felt manageable, just wrapping a map of maps and wiring up the three operations.”
Candidates most often report a technical phone screen (45 write-ups), a system design round (5), an onsite coding round (2) and an online assessment (1).
Across 45 technical phone screen write-ups, the most tagged question topics are Algorithms & Data Structures (48 questions), Technical Trade-offs (37) and System Design (34).
45 notes