Intuit | SDE2 | Bengaluru | Rejected

I recently applied for an SDE-2 role at Intuit via a referral. My resume was shortlisted, and I was scheduled for a phone screening 5 days later. This initial round lasted 60 minutes and began with an introduction, followed by a 25-minute discussion about my current team's work, where I was asked to draw a High-Level Design (HLD) diagram and answer follow-up questions. Next, I spent 15 minutes designing APIs for a BookMyShow-like platform, discussing my approach and handling subsequent queries. The round concluded with a 20-minute discussion on the approach, pseudocode, and time complexity for the LRU Cache problem. I successfully passed this round and was then assigned a craft project to complete over two weeks.

For the Craft Round, which was a 60-minute session with a four-person panel, I presented a detailed PowerPoint. This presentation covered the assumptions I made for the project, its Functional and Non-Functional requirements, the chosen Tech Stack, High-Level Design (HLD) and Low-Level Design (LLD), API definitions in Postman, and the Database Schema. During this round, I fielded questions specifically about the craft project, how I handled corner and edge cases, the distinctions between PUT and PATCH HTTP methods, differences between Path Parameters and Query Parameters, various database design related queries, and questions concerning authorization.

The Assessor Round, lasting 45 minutes, involved solving the "Product of Array Except Self" problem. I was also tasked with writing SQL statements based on a given problem statement and engaged in a discussion comparing Monolithic versus Microservice architectures.

I then had two consecutive Team Member Rounds, each lasting 30 minutes. The first round primarily focused on my current project within my organization, followed by discussions on Design Patterns and various Caching Mechanisms. The second team member round was a typical Behavioral interview. I was asked about my motivations for wanting to leave my current organization and how I would approach debugging a production issue if one arose. Ultimately, I was rejected from the position.