The phone screen with the hiring manager covered past projects and some high-level NoSQL concepts.
I had five 1:1 interviews:
After all the interviews, I got the distinct impression they were looking for someone with fixed, narrow skills and desired specific answers to questions. The two interviews with the developers were eye-opening, and I was left with the impression that their interviewing skills were immature or untrained. I also came away feeling there was no clear career path and it was an "every man for himself" environment.
The era of asking for printf format specifications has long passed. Any half-competent programmer will figure out these tricks through repeated use of the compiler. I don't understand what is to be gained by asking these kinds of questions.
Also, having more lines of code for Fibonacci doesn't matter much due to compiler optimizations (unless, of course, you are building embedded systems and such).
You cannot have questions like these being asked when the position description asks for 8+ years of development experience. At the end of the day, I felt I had wasted time by applying for this position.
The following metrics were computed from 68 interview experiences for the Intuit Senior Software Engineer role in United States.
Intuit's interview process for their Senior Software Engineer roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having negative feelings for Intuit's Senior Software Engineer interview process in United States.