The process started with a contact from a recruiter on LinkedIn.
Afterwards, I was given a code challenge on HackerRank. It was a pretty straightforward challenge. Then I spoke with someone from their development team.
Following that, the recruiter contacted me again and set up a code challenge project. It seemed like a project they reuse across interviews. It wasn't too difficult, but it was quite time-consuming.
Afterwards, they invited me for an onsite interview. The onsite included an engineer, a lead engineer, a UX designer, and the recruiter.
We completed a pair programming challenge, followed by standard interview questions with the non-engineers, which felt like a personality assessment. There was no whiteboarding, which was a huge plus.
What was something you did wrong, and how did you fix it?
The following metrics were computed from 5 interview experiences for the Instacart Software Engineer role in San Francisco, California.
Instacart's interview process for their Software Engineer roles in San Francisco, California is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Instacart's Software Engineer interview process in San Francisco, California.