Frontend Interview Experience at Intuit

Overview

This article details a Frontend Software Development Engineer 2 interview experience at Intuit, a leading financial software company known for products like TurboTax, QuickBooks, and Mint. The interview process consisted of five comprehensive rounds designed to evaluate JavaScript proficiency, React expertise, system design capabilities, and problem-solving skills. The candidate discovered the opportunity through a LinkedIn Premium InMail outreach to the recruiter, which led to an initial screening call to discuss the role and interview structure.

Intuit's frontend interview process is notably thorough, emphasising both theoretical knowledge and practical implementation skills. The process tests candidates on JavaScript fundamentals, React ecosystem knowledge, machine coding abilities, and data structure proficiency—all essential for building performant, user-facing financial applications.

Interview Process

The interview process comprised five distinct rounds:

1. JavaScript & DSA Round – 60 minutes
2. Machine Coding & Craft Demonstration Round – 75 minutes
3. JavaScript Deep Dive Round – 90 minutes
4. DSA Problem Solving Round – 60 minutes
5. Hiring Manager Round – Mix of technical and behavioural questions

Each round progressively increased in complexity, with the JavaScript Deep Dive being the most extensive at 90 minutes. The Machine Coding round involved a take-home assignment followed by a live demonstration session.

Technical Rounds

Round 1: JavaScript & DSA

The first round combined data structure problems with JavaScript-specific questions. The candidate was asked to solve the classic 2 Sum problem using JavaScript, demonstrating both algorithmic thinking and language proficiency. After the initial solution, the interviewer verbally presented a 3 Sum variation to assess adaptability and deeper algorithmic understanding.

The conversation then shifted to React fundamentals. The candidate was questioned extensively about the useEffect hook, including:

• Various usage patterns and dependencies
• Object referential equality within useEffect dependency arrays
• Scenarios where referential equality could cause unnecessary re-renders or missed updates

A JavaScript memoization question followed, requiring the candidate to implement a memoize function. The interviewer extended the problem to accept any number of parameters, testing the candidate's understanding of closures and function composition.

The round concluded with a Promise-based problem requiring vanilla JavaScript implementation: