
Synthesized from 5 candidate submissions for ALL.
The SDE-2 interview process at Intuit is designed to evaluate a candidate's technical depth, problem-solving ability, and practical engineering skills. The process includes an Online Assessment (OA), phone screens, onsite rounds, and a craft project or system design discussion. Key themes include DSA problem-solving, API design, error handling, system design, and behavioral alignment with Intuit’s engineering culture.
Format: Two rounds, each focusing on DSA problems.
Questions Asked:
Expectations:
Format: Four rounds covering backend development, DSA, engineering fundamentals, and hiring manager fit.
GET /api/playersGET /api/players/{playerID}Format: 60-minute session with a panel of 4 interviewers.
Task: Present a detailed PPT covering:
Follow-up Questions:
PUT and PATCH.Format: 45-minute round focused on problem-solving and system design.
Questions Asked:
Sources: LeetCode Discussions (SDE-2 Intuit Interview Experiences)
The candidate went through five rounds of interviews for an SDE-2 role at Intuit. They were rejected after completing all rounds. The process included a phone screening, a craft project round, an assessor round, and two team member rounds (one technical and one behavioral).
A 60-minute round focused on the candidate's current team's work, including drawing a High-Level Design (HLD) diagram and discussing it. Additionally, the candidate was asked to design APIs for a BookMyShow-like platform and solve the LeetCode problem 'LRU Cache' (discussion on approach, pseudocode, and time complexity).
Draw a High-Level Design (HLD) diagram for the candidate's current team's work.
Design APIs for a BookMyShow-like platform.
Solve the LeetCode problem 'LRU Cache' (approach, pseudocode, and time complexity).
A 60-minute round involving a panel of 4 interviewers. The candidate presented a PPT detailing assumptions, functional and non-functional requirements, tech stack, HLD, LLD, APIs (tested via Postman), database schema, and more. Follow-up questions covered corner cases, edge cases, PUT vs PATCH, path parameters vs query parameters, database design, and authorization.
Explain the assumptions and requirements for the craft project.
Discuss corner cases and edge cases handling.
Differentiate between PUT and PATCH.
Explain the difference between path parameters and query parameters.
Database design-related questions.
Authorization-related questions.
A 45-minute round focused on problem-solving and system design concepts. The candidate solved the LeetCode problem 'Product of Array Except Self' and wrote SQL statements for a given problem statement. Additionally, there was a discussion on Monolith vs Microservices.
Solve the LeetCode problem 'Product of Array Except Self'.
Write SQL statements for a given problem statement.
Discuss the differences between Monolith and Microservices.
A 30-minute round focused on the candidate's current project and design patterns. The candidate discussed their current project in their organization and answered questions on design patterns and caching mechanisms.
Discuss your current project in your organization.
Explain design patterns.
Discuss caching mechanisms.
A 30-minute behavioral round. The candidate was asked about their motivation for leaving their current organization and how they would debug a production issue.
Why do you want to leave your current organization?
Given a production issue, how would you debug it?
The candidate progressed through multiple interview rounds but received negative feedback primarily due to improper error code usage and exception handling in API implementations. The feedback emphasized the importance of attention to detail and robust implementation practices.
Online Assessment (OA) with 2 DSA questions (medium difficulty: linked lists and arrays) and 5 MCQs on core technical concepts. Scored 94% and advanced to phone screen rounds.
Two rounds focused on solving DSA problems. First round involved a graph-based problem similar to 'rotten tomatoes'. Second round involved a medium-level DSA problem similar to 'finding the maximum rectangle in a histogram'. Both rounds required approach discussion, implementation, and successful code execution.
Four rounds covering project discussion, API implementation, DSA, engineering fundamentals, and hiring manager fit. Tasks included implementing a POST API for player details, integrating an LLM API, solving a DSA problem similar to 'next permutations of an array', implementing pagination on a GET API, and discussing day-to-day responsibilities and cultural fit.