Real, anonymous reports from people who interviewed for Software Engineer at Instacart, newest first and distilled into what to expect across the loop.
Get your personalized Instacart Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
I experienced a high-difficulty interview slate with three hard coding rounds plus system design and behavioral, and I didn’t get an offer.
Coding (LeetCode-style) x3 — Three LeetCode interviews with hard problems; once the exercise started, interviewers didn’t provide guidance, and I couldn’t lean on support.
5 months ago
Difficult Negative San Francisco, CA
I ran into an unusually rushed assessment-heavy flow that made the process feel frantic, and I ended up not moving forward.
Codesignal test — A 90-minute CodeSignal assessment with many features and code paths to implement; it felt frantic with little time to fully explore.
9 months ago
Difficult Positive Toronto, ON
I interviewed for the Software Engineer role through a virtual onsite where the coding felt fine, but system design is what likely held me back. Recru…
12 months ago
Average Positive Toronto, ON
I had a fair, practice-friendly interview flow with guided system design and standard questions, and while I didn’t report an offer, it felt transpare…
12 months ago
Difficult Negative Toronto, ON
My Instacart process stretched out over months and ended with a positive-feeling onsite, even though the pipeline kept expanding. Unproctored technica…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Coding Rounds
Candidates typically face multiple coding rounds that vary in difficulty, often resembling LeetCode-style problems. Many report that the lack of guidance during these rounds can make them particularly challenging.
LeetCodeCodingDifficulty
System Design Interviews
System design interviews are a significant component of the process, with varying levels of difficulty and expectations for depth, including edge-case considerations. Candidates often find this round crucial for their overall success.
System DesignEdge CasesArchitecture
Behavioral Interviews
Behavioral interviews tend to focus on fit and past experiences, with some candidates feeling that the tone and structure can impact their performance. The effectiveness of these rounds can vary based on the interviewer's engagement.
BehavioralFitEngagement
Assessment Formats
The interview process often begins with an online assessment, which can include timed coding challenges or platforms like CodeSignal or HackerRank. Candidates should prepare for a range of formats and time pressures.
Online AssessmentCodeSignalHackerRank
Interview Flow and Structure
Candidates report a mix of structured and rushed interview flows, with some experiencing long, back-to-back rounds that can feel draining. Clarity and pacing are important for managing the overall experience.
Interview FlowPacingStructure
Outcome and Communication
Candidates often express frustration over unclear outcomes and communication post-interview, with some feeling 'ghosted' despite positive performances. Clear follow-up and feedback can be lacking.
