I entered a school challenge to demonstrate coding ability. I was told to bring my laptop to the interview in order to showcase some of my favorite projects.
I never had a chance to get out my laptop during the interview. I even asked to show my projects three times, and I was ignored by the interviewer.
I proceeded to whiteboard coding. The interviewer was on his phone, texting, while I was trying to talk and explain my reasoning about solving the problem.
The interviewer incorrectly stated something about HTML5 that I had known from experience. He even opted for a structure that he thought would be "easy to style" with CSS.
After researching, I confirmed my suspicions: no, it would require tremendous amounts of ugly absolute positioning and weird CSS calculations that are not supported in most browsers.
I successfully completed the second problem but had struggled on the first due to a lack of knowledge on a specific language technicality. I was told that "Whiteboard is King."
What a sad way to recruit talent.
Design a parking garage. The interviewer added constraints without specifying with much detail. I assumed this was because they were too busy on their phone. Once I fully understood the problem, I was easily able to answer the last segment of the question.
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.