Pretty standard recruiter screen followed by a portfolio review, then a take home design exercise. After that I had an onsite to present the challenge to a panel and some 1:1 interviews with cross-functional members on the team.
I applied online. The process took 3 weeks. I interviewed at Intuit (Mountain View, CA) in Mar 2024
Interview
The interview process was 3 stages according to the call with the recruiter. Based on that call, the first stage was going through the job description and requirements. This was with the recruiter. The next step was LeetCode style questions with one of the senior developers. I asked for a SDEII role, but they pegged me down for the senior role for whatever reason. Finally, the last stage was a take home assignment and panel style review and discussion on system design/tradeoffs.
Bad rating because I specifically asked for an SDEII role, and they interviewed me for a much higher role that I wasn't aware I had to prepare for.
Interview questions [1]
Question 1
Asked to implement a rate limiting step into an api call, via a sliding window algorithm.
I applied through a recruiter. The process took 2 weeks. I interviewed at Intuit in Aug 2024
Interview
Craft demo followed by interview rounds.
My biggest gripe is that the interview setup is all wrong, and I advise candidates to not go for craft demo. The initial question which was asked in the demo was not part of the requirement itself. That is still ok. But during the interview, one person asked few questions which was like either you have used the tool or not used it. If that was the expectation, then why did Intuit make me do the craft demo, and not set this round first.
My advice to candidates is don't go for craft demo, especially for senior candidates. The same thing could have been conducted as a simple design round of one hour.
Interview questions [1]
Question 1
How do you debug a blocked application in Kubernetes?