The process took 5 days. I interviewed at Intuit (Bengaluru) in Jul 2012
Interview
There was one telephonic round which lasted for 25 minutes. Started with usual introduction and was asked few technical questions.
I was called for a 1:1 after 4 days. It consisted of 2 technical rounds and one managerial round. I was asked to write programs during the technical rounds which tested the fundamentals of pointers.
In the initial 10 minutes itself I was sure that I am not doing satisfactorily because it involved writing the actual code and not just outlining the logic was sufficient. The interviewers wanted the fully working code to be written.
Interview questions [2]
Question 1
Write a function to perform string copy using pointers
The process took 1 day. I interviewed at Intuit (Mountain View, CA) in May 2011
Interview
I had 7 interviewers spanning a broad range of job functions and areas of focus (engineers, architects, product managers, directors). One interviewer commented after looking at the schedule that the loop might be uncommonly thorough. They asked me questions around technical ability, prioritization, strategy, and situational leadership.
The group was very transparent about the challenges facing the team (after starting here, I can confirm that what they portrayed is indeed reflective of the situation on the ground). Most of the interviewers were very polished, asking questions that really made me think, truly respecting areas of my experience I was not at liberty to talk about, and ensuring a pretty smooth flow to the conversation. One of my interviewers was a little too blunt with the behavioral interviewing best practices, but this had the hallmarks of someone new to interviewing rather than a serious red flag. I wish the loop had gone deeper on hard technical capabilities, as I felt there were some relevant depth of skillset on coding and design that was not quantified as well as it could have been.
Overall a long, challenging day but very positive experience.
Interview questions [1]
Question 1
The most challenging (and interesting) question was about a strategy for finding signal in a noisy and poorly understood data set. Asking a software engineer a data science question really stretches the mental muscles.