I applied through a recruiter. I interviewed at Intuit (Bengaluru) in Aug 2025
Interview
Round 1
DS ALGO
Once you clear this round they will schedule 1 day interview which will run for 3-4 hrs
Round 1
Machine coding round. You will be asked to code a problem in your selected language and framework. You need to write complete APIs with testing
Round 2
AI coding
You need to write an agent which can solve the given problem using llm
Interview questions [1]
Question 1
You need to write an agent which can solve the given problem using llm
I applied online. The process took 3 weeks. I interviewed at Intuit (Bengaluru) in Dec 2025
Interview
I have recently applied for the Staff Software Engineer position at Intuit, and I had also applied for the same role in the past.
However, the interview process has been extremely disappointing each time.
They expect candidates to build a fully working, almost production-ready application purely for interview purposes.
With existing professional responsibilities, it is unrealistic and impractical to spend that level of time on developing a complete application.
I have gone through this interview process 3–4 times, and on every occasion, I lost interest during the craft (coding) round due to this requirement.
As a result, I have decided that I will not be applying to Intuit again in the future.
Interview questions [1]
Question 1
1st round 1.5 hrs. with problem solving, system design, behavioral questions and current projects.
2nd round - craft round -> never developed fully working application because of its time consuming and less interested.
Some 2-3 more round, who cares.
I applied through a recruiter. The process took 4 weeks. I interviewed at Intuit (Mountain View, CA) in Aug 2025
Interview
The panel lacked basic diversity in communication style and perspective. All three interviewers on the craft panel approached questions in a very similar way, which limited the opportunity to demonstrate adaptability and broader skills.
Interview questions [1]
Question 1
Debug the repo that was provided in advance.
NOTE: Your best shot at success is to run the project locally days before the actual interview, and play around with it. Make sure the output is what you expect. Try to break it, and fix it. For example, does the UI display the correct key value pairs? If not, why?