Real, anonymous reports from people who interviewed for Frontend Engineer at Intuit Management Consultancy, newest first and distilled into what to expect across the loop.
Get your personalized Intuit Management Consultancy Frontend Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
After the application, the process moved through Uptime Crew and felt pretty structured. My first checkpoint was a proctored online assessment with three parts: a LeetCode-style DSA problem, then SQL, then a Bash section. I remember the Bash part being trickier than I expected, and the DSA question sitting around the harder end of “medium/hard.” For the OA, I had a limited window to start (somewhere around a week/90-minute timing), and the platform proctoring made it feel more high-stakes than just a casual coding test.
A recruiter screen followed, and most of it revolved around how I actually used AI while building—what tools I used, how I prompted, and how I applied it to a project end-to-end. I also talked through the work I’d done in a way that connected AI usage to feature implementation rather than treating it like magic. Next came a take-home build challenge. It lasted a few hours for the main build portion and was open-ended enough that it needed a real build process, not just one throwaway script. After submitting, I went into a technical review/discussion stage where I had to walk through my approach and answer follow-ups about the design choices.
> 1 year
Difficult Negative United States
My process started normally with recruiter and tech phone screens, but the on-site was where everything fell apart for me. The on-site was a virtual format with five modules, including building a front-end app from product requirements in my local dev environment and then presenting the project to a panel, followed by three separate deep-dive sessions.
The first module involved 90 minutes of coding. I appreciated being able to work silently in my own environment, but it got derailed when I was suddenly told to copy and paste my work into a shared text editor with only about a minute left as the panel began joining. My code and everything I’d created—helpers, fixtures, components, tests, and styling—ended up dumped into a single place, which made the demo and walkthrough feel chaotic.
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
