intuit logo
Intuit· SDE II

Intuit | SDE2 | Bengaluru | Rejected

Result
Rejected
Location
Bengaluru
Experience
3 years
Posted
14 Aug 2024
393 reads

Summary

I applied for an SDE-2 role at Intuit through a referral and went through five rounds, including coding, system design, and behavioral questions. Despite a strong performance in technical assessments like LRU Cache and system design for BookMyShow, I was ultimately rejected after the final team member rounds.

How it went

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.

Questions asked (11)

  1. 01

    Design APIs for a BookMyShow-like Platform

    System Design

    Design APIs for a platform similar to BookMyShow, discussing the approach and answering follow-up questions.

  2. 02

    LRU Cache

    Data Structures & Algorithms · Medium

    Discussion on the approach, pseudocode, and time complexity for implementing an LRU Cache.

    Open the problem
  3. 03

    Differentiate PUT vs PATCH

    Other

    Explain the differences between HTTP PUT and PATCH methods.

  4. 04

    Differentiate Path Param vs Query Param

    Other

    Explain the differences and use cases for Path Parameters vs Query Parameters in REST APIs.

  5. 05

    Product of Array Except Self

    Data Structures & Algorithms · Medium

    Solve the "Product of Array Except Self" problem.

    Open the problem
  6. 06

    Write SQL Statements

    Other

    Write SQL statements based on a given problem statement.

  7. 07

    Discussion on Monolith vs Microservice

    System Design

    Discuss the advantages, disadvantages, and trade-offs between Monolithic and Microservice architectures.

  8. 08

    Discuss Design Patterns

    System Design

    Discuss various software design patterns.

  9. 09

    Discuss Caching Mechanisms

    System Design

    Discuss different caching mechanisms and their use cases.

  10. 10

    Why Leave Current Organization?

    Behavioral

    Why are you looking to leave your current organization?

  11. 11

    How to Debug a Production Issue?

    Behavioral

    Given a production issue, describe your approach to debugging and resolving it.

Know someone preparing? Send it to them:WhatsAppLinkedInX

Interviewed at Intuit recently?

Write up your rounds while you still remember the questions. It helps the next person more than you would think.

Share your experience
Discussion 0

Questions for the author, or how your own interview compared.

Join the discussion

Sign in with Google to comment or ask the author a question.

No comments yet

Be the first to share your thoughts and start the discussion!