I had seven interviewers spanning a broad range of job functions and areas of focus: engineers, architects, product managers, and 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 a very positive experience.
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.
The following metrics were computed from 7 interview experiences for the Intuit Staff Software Engineer role in Mountain View, California.
Intuit's interview process for their Staff Software Engineer roles in Mountain View, California is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having mixed feelings for Intuit's Staff Software Engineer interview process in Mountain View, California.