The interview consisted of two 30-minute sessions.
The first session was behavioral, with typical questions about projects and preferred tasks. I was also presented with higher-level design questions, such as how to programmatically represent a family tree and describe various use cases.
The second session was Java-heavy, involving descriptions of keyword differences and some structure manipulation.
After I finished, and was told I answered everything correctly, I was informed that my major made my design views not align with typical engineers. I disagreed and asked for a chance to prove myself. They called in a manager, asked another question, and continued adding constraints until I could no longer solve it. At this point, I felt they were not interested and were merely making the problem harder to push me out of the interview.
I got an arrogant vibe from the technical interviewer, which is not the first time I've heard about Intuit. Their higher-ups were pleasant, but they were unable to give me a clear reason as to why I couldn't move on.
Remove an item from a singly linked list.
Next: Do it with no additional memory usage.
The following metrics were computed from 3 interview experiences for the Intuit Software Engineer role in Rochester, New York.
Intuit's interview process for their Software Engineer roles in Rochester, New York is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Intuit's Software Engineer interview process in Rochester, New York.