Preparing for an interview? Check out Cracking the Coding Interview
Published on

Intuit | SSE - Full Stack | Bengaluru | August 2023 [No Offer]

Author
  • Shared Anonymously

Status: 2018 post graduate from Tier 1 College
Position: engineer at a startup
Years of Experience: ~5 years
Current Base: 30lpa
Location: Bengaluru
Interview Period: 18th July to 1st August, 2023

I recently participated in a FullStack SSE interview with Intuit and would like to share my experience. I applied for the position via LinkedIn and was contacted by a recruiter the following day to arrange the first interview, which took place one week later.

Round 1: Initial Interview

The first round was a conventional interview. Questions asked included:

  1. What type of data structure would you use to store sensitive information, such as credit card details?
  2. Can you define a static variable inside a class method in Java?
  3. Several basic MySQL queries were asked on the glider portal, focusing on count(*), count(distinct), and join operations.
  4. I was asked to write a function to calculate library fines based on criteria such as the number of days, months, or years overdue.

Most questions were answered, and the interviewer was supportive throughout.

Round 1 Result: Advanced to next round

Upon completion of the first round, the recruiter promptly assigned a full stack assignment to be completed within 3-4 days. I sought clarification via email, and my queries were answered the following day.

Round 2: Craft Demo Round

For this round, I created a service in Golang for the backend (my area of expertise) and used React for the frontend, despite the instructions specifying Java for the microservice.

The craft demo round included the following steps:

  1. I introduced myself using a ppt, during which I highlighted my achievements and significant projects. [ppt is optional]
  2. As my strength lies in backend development, I began by explaining the backend before moving on to the frontend.
  3. I was asked follow-up questions concerning the non-functional requirements I had considered while building the system. I was also required to implement a different functionality on the spot.
  4. I also prepared a low-level design (LLD) diagram illustrating how I would have implemented it with more time, using multiple microservices instead of a single one.
  5. Several follow-up questions were asked about both the frontend and backend.
  6. Topics covered included efficient search implementation on the frontend and state management between different databases for microservices.
  7. It was pointed out that the backend was written in Golang not in Java

Round 2 Result: Advanced to next round

After Round 2, it was clear to the panel that my strengths lie more on the backend side. However, a suitable panel wasn't immediately available, resulting in a rescheduling of further rounds two days later.

Round 3: Assessor Round

Two panel members conducted this round. They:

  1. Asked DSA question based on dynamic programming of medium difficulty. Question link
    https://leetcode.com/problems/longest-increasing-subsequence/
  2. Asked about my experience with Java and Springboot [Again I have minimal experience in this]
  3. Asked about REST standards, path parameters, query parameters, and the HTTP 503 status.
  4. Discussed load handling in the context of heavy traffic events like major sales.
  5. Explored Design Patterns and the Orchestrator Microservice Pattern.

I solved the DP question using an O(n2) approach, dp approach I was able to think but was not able to code.

Round 3 Result: Advanced to next round

Round 4 began just 15 minutes after Round 3.

Round 4: Team Member Round

Questions in this round revolved around:

  1. Again asked on my experience with Java, Spring Boot, microservices, etc.
  2. Details about one of my projects.
  3. The internal workings of the ArrayList, particularly its dynamic size increase.
  4. How will you implement rate limiting/api throttling
  5. How to make a Java class immutable.

Round 4 Result: Not selected

Unfortunately, I was not selected for the final round [Hiring Manager Round]

Reflecting on my experience, Intuit's interview questions were of average difficulty. However, they heavily focus on Java and React, so proficiency in both would be a considerable advantage. As my Java skills weren't particularly strong, this was a drawback. I was also more backend-oriented with only a functional knowledge of frontend, which was another concern. In hindsight, I should have applied for a backend role.

The assignment stage can be challenging if you're already a working professional. However, Intuit is currently hiring aggressively, and I would encourage you to apply. For the craft demo, I recommend focusing on either backend or frontend as a strong part, but make sure to complete every given functionality, also as it's a full stack assignment you should create both frontend and backend . It is a critical round that can make or break your application.

Yet to recieve the feedback on the interview, will add the feedback as well here

Report • Mark as Helpful