Intuit Software Engineer Phone Screen Questions
19+ questions from real Intuit Software Engineer Phone Screen rounds, reported by candidates who interviewed there.
What does the Intuit Phone Screen round test?
The Intuit phone screen typically lasts 45-60 minutes and evaluates core Software Engineer fundamentals. Candidates should expect 1-2 algorithmic problems, basic system design discussion at senior levels, and questions about relevant experience. The goal is to confirm technical competence before bringing candidates onsite.
Top Topics in This Round
Intuit Software Engineer Phone Screen Questions
First Round: 75-Minute In-Store Interview Not LeetCode, encountered the same questions as on the forum: The following content requires a score higher than 200. You can already view it. Implement Custo
Max Score Brackets
I was asked this question in a phone interview recently. posting it here if it helps anyone :) Question: Given a string of "(" and ")" brackets. return the maximum score where...
Intuit Interview | Set 4 (For SSE)
I recently cleared Intuit Interview. It was a life changing experience and I am very happy to crack the interview for SSE. Below are the questions asked :Round 1: Java ba...
Intuit Staff Software Engineer Interview Experience – Mountain View, CA
**Role:** Staff Software Engineer **Location:** Mountain View, CA **Phone Screen (75 mins)** * **Behavioral & Coding:** Covered standard behavioral questions and a straightforward LeetCode Medium codi
Intuit Interview | Set 9 (On-Campus)
Intuit came for on-campus hiring for 2016 batch and internship offerings for 2017 batch in our college last week.Round One (Online round, 90 minutes):The shortlisting was ...
Intuit visited our campus for summer internship for positions of Software developer and Software Quality Engineering. I was among the 5 people to be selected for the inter...
Intuit Interview Experience (On-Campus)
Intuit Came on July for our campus They Filtered the applied students by criteria CGPA8.5 ( Around 200 Students)1. Round 1 ( Coding )Total Questions - 04 - 90 MinsQn1 : 2D...
Adding my Intuit interview experience. It was a full stack role (4 year experience) interview for bangalore location. 1. I had an online coding round that comprised of 1 LC easy...
Intuit | SSE | Bangalore | 2021 | Selected
Round 1: Glider Find all sets of palindromes in a string. Round 2: Craft Demo Demo on question: All subtrees formed once a node in a given tree is removed. Question was...
Status: 3 years Experience in Product Based Companies, B.Tech (CSE) Tier 3 College Position: SE2 at Intuit Location: Bangalore, India Date: April 20, 2022 Technical Phone Screen Round (1 hour) - Find Next greater...
Intuit Frontend | Rejected
There were a total of four rounds of interviews, Before Interview: The recruitment team will share the small project requirements, that need to be completed before the interview process. Round 1: You need to...
Intuit | NOV 22 | PE | Reject
Round 1 : HLD and LLD of Appointment scheduling system . can be used for Hospital appointments. Round 2: Craft demo - Rental bike system . Rejected in this round . 4...
Intuit SDE-2 | December | 2021
Round 1:- Online Hackathon in Geektrust.It was a machine coding round I was asked to design a water management system. Round 2:- Crafts demo round.(1 hr):- The interviewer asked about the...
FB phone interview
https://leetcode.com/problems/binary-tree-vertical-order-traversal/ The first one I did a BFS followed by a sort.. 1st solution on leetcode. I was too nervous, going to the second solution would be intuitive if I weren\'t...
Round 1 : Property Hunt Problem Statement Build a console application for a Property Management Business where you can expose features like register a property, list a property and search properties based on...
Status: SDE in a non-faang Position: SDE2 (frontend) at Intuit Location: Banglore, India Date: 1 October 2021 There aren\'t many frontend interview experiences on leetcode so I\'m posting my experience. The interview process and...
Status: Final year student, Tier2 college Position offered: SDE Intern at Intuit Location: Bangalore, India Date: August 2021 Round 1: Online coding 1. FInd maximum number possible after doing k swaps 2. Given a boolean expression...
I recently found myself in a technical phone interview (2nd stage) and blanked when I got presented the question. Here is the question I got asked: Given a 2D grid cells with...
## Problem You have `n` support agents and a stream of incoming tickets. Each ticket has a priority (1-5, higher is more urgent) and an estimated handle time. Agents take one ticket at a time. Assign each incoming ticket to the agent who will be free soonest; break ties by agent index. Simulate the schedule and return the finish time of the last ticket. ```python def schedule_tickets( n_agents: int, tickets: list[tuple[int, int]] # (priority, handle_time) ) -> int: """Return the timestamp when the last ticket finishes.""" pass ``` ``` Input: n_agents=2, tickets=[(5,3),(3,5),(4,2),(2,4)] Output: 9 # t=0: Agent0 takes ticket0 (free at 3), Agent1 takes ticket1 (free at 5) # t=3: Agent0 free, takes ticket2 (free at 5) # t=5: Agent0 and Agent1 both free, Agent0 takes ticket3 (free at 9) # Last finish: 9 ``` ## Follow-ups 1. How does a min-heap on `(free_time, agent_id)` efficiently find the next available agent? 2. Should priority affect which ticket is assigned next, or which ticket each agent picks up? Explain your design choice. 3. How would you modify the simulation to support ticket escalation if wait time exceeds a threshold? 4. Extend to agents with different skill sets where only certain agents can handle certain ticket categories.
What to Expect in the Intuit Phone Screen Round
The Intuit Software Engineer Phone Screen round has a specific calibration purpose distinct from other rounds in the loop. Across 19+ verified reports on LeakCode for this exact round type, the consistent expectations: clear scoping of the problem before diving into a solution, explicit reasoning about complexity, structured handling of edge cases, and the ability to discuss trade-offs between two reasonable approaches.
Reports tagged with the Phone Screen round at Intuit show recurring patterns in difficulty and topic distribution. The Phone Screen round is typically 45-60 minutes; the interviewer is calibrated against a specific rubric. The discriminator between candidates who advance and candidates who do not is rarely the final correctness of the answer. It is the path: did you clarify, did you verbalize your approach, did you handle edge cases, and did you communicate throughout.
How To Prepare for This Specific Round
Filter the questions below to the most recent reports (past 6-12 months). Questions tagged for this exact round type from this exact company at this exact role level are the highest-signal data available. Older reports may reference questions that have since rotated out of the company's pool.
Practice 4-6 representative problems from this set under timed conditions. The goal is not memorization (companies rotate questions); the goal is to internalize the patterns the interviewer typically reaches for and the depth of follow-up to expect. Reports on LeakCode also tag the typical follow-up depth at this round type, which is the discriminating signal between hire and no-hire calibration.
Phone Screen Round Timing and Format
The Phone Screen round at Intuit typically runs 45-60 minutes. Use the first 2-3 minutes to clarify requirements; you should never start coding or designing without verifying the input/output format, constraints, and edge cases out loud. Use the next 5-7 minutes to verbalize your approach before writing any code. The middle 20-30 minutes are implementation. Reserve the final 10 minutes for testing with concrete examples and discussing optimization or trade-offs.
Time budget discipline is one of the most reliable senior-vs-junior discriminators in this round. Strong candidates verbalize where they are in their budget out loud ("I've used about 20 minutes, I have 15 minutes left for testing and one optimization"). This signals engineering maturity to the interviewer and creates positive feedback they can capture in writing.
Common Failure Modes in This Round
Reports tagged "no hire" at Intuit Software Engineer Phone Screen commonly cite: coding silently without verbalizing approach, jumping to implementation before clarifying requirements, missing edge cases (empty input, single element, very large input), producing working code that the candidate cannot refactor when asked, and failing to test their solution with concrete examples before declaring done.
The single most predictive failure mode in 2025-2026 reports: not asking clarifying questions. Interviewers at all FAANG companies are explicitly trained to weight this dimension. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's notes.
See All 19 Questions from This Round
Full question text, answer context, and frequency data for subscribers.
Get Access