Intuit Software Engineer II interview questions

1. Recruiter Screening (for team matching) If any hiring manager is interested in your profile the recruiter would revert with the details and the first round of interviews. 2. Round 1: Techincal Assessment (1hr) - first 30 minutes: Team intro and your background discussion. - remaining 30 minutes: A LC easy/medium question. Discuss your approach. Bonus points for solving the problem. No language constraints. If the interviewers think you're good enough, the recruiter would reach out with the feedback and discuss the next steps. A problem statement will be shared by the recruiter they call it a craft assignment, it is an open-ended assignment. You can reach out to the recruiter if you have any questions, they're very helpful. Cover all the points mentioned in the requirements, you can show off your skills and be as creative as you can. Your solution doesn't have to be perfect but then it should not be just a plain one. Prepare the design diagram and a presentation about yourself, and key highlights. 3. Round 2: A long (~3.5hrs) virtual onsite interview. - 1 hour - presentation about yourself and craft demo. Follow-up questions on the craft demo. Prepare all the choices you made and be ready to talk on many why-ies. - 1 hour - LC medium. - 1 hour - JS concepts (as this role was more for a front-end team), APIs, etc. - 30 mins - hiring manager round with behavioral questions and some high-level technical discussions.

The recruiter called me to give me all the info she thought I would need. They would give me a backend or a full-stack assignment, and I would have 90 min to solve it. The expectation was to implement the main part of the assignment during that time, and she said that candidates can't deploy the application due to the small amount of time. I implemented the backend assignment. I set up a database, used an ORM, and set up 2 endpoints which I was able to demo, and they worked as they should. I was starting to set up my first unit test when my time went up. Because I was told an interviewer would go over the problem later and I would be able to implement missing pieces, the unit tests, for example, I didn't think that would be a big deal. However, the hours that were previously reserved to go over the assignment and make adjustments or finish the testing implementation, ended up being to solve different coding questions. I was able to solve both questions. In the last interview with the manager, I honestly could tell he didn't like me right the way. He was trying to challenge me with DevOps questions on the demo. I nailed all his questions about the project that I implemented, so he started to test my limits, I thought ok, but that shouldn't be expectations. In the last interview with him, he told me Intuit was going more for a new model of engineering where all the engineers would master all aspects, including DevOps as well, and on his team that was something new and they were learning those skills as they are migrating for that style. I was never told I should have DevOps skills for that role at Intuit, I would never be willing to waste 5 and half hours of my day to do the onsite if that was one of the requirements. It is quite rare to find a full stack with DevOps experience, and I didn't lie about it, I told you I didn't have that experience yet, but I would love to have the chance to learn. The recruiter said they didn't make an offer because I didn't have DevOps experience. Also said I didn't demonstrate programming fundamentals skills. I solved everything they gave to me. What a waste of time.