Preparing for an interview? Check out Cracking the Coding Interview
Published on

Intuit | SDE2 - Worst Interview experience ever [Reject]

Author
  • Shared Anonymously

Adding my Intuit interview experience. It was a full stack role (4 year experience) interview for bangalore location.

  1. I had an online coding round that comprised of 1 LC easy question and 5 MCQs (based on basic design patterns, Rest API, SQL queries). I got a call from the HR 2 days after the test saying that I passed for the onsite rounds
  2. The onsite round 1 was LLD based. Was asked to design DDB schema and talk about API structure. It went well overall.
  3. The HR asked me to complete an "assigment". According to her it would take around 3-4 hours to complete the test. She also scheduled a full day of onsite rounds (4 rounds in all). There was 15 minute breaks between interviews. The first interview of the onsite was assignment review. I had 5 days to complete the assignment.

Although I am not a big fan of take-home assignments - but agreed to it. I had to create a full stack application. The requirements were 3 pages long. It also had UI mocks. How do they expect candidates to spend so much time for a company even though it is uncertain that they will get selected?? But I recalled how the HR initially said it would take 3-4 hours - so I thought i will build a basic running application - maybe the interviewer needs to know whether or not the candidate can code.

HR called me a 2 days before the interview, I was done with the basic app by then. The HR clarified that the app should include unit tests and I also need to prepare a PPT and add design diagrams. At the time I was desperate for a job, I said ok. I spent around 30 hours over the next 2 days to satisfy the ask. I created design diagrams, wrote the code using design patterns, used best security practices on the UI, wrote UTs for UI and backend(~75% coverage)

It was the day of the interview, I had the app up and running. I presented the PPT. The interview asked "But what about requirement X?"- it was something on fetching a modified version of the data from backend. I quickly said that it was not part of the requirement document. He said "Don't you think it is important to have this as part of the application? ". I was out of words. He asked "Where is the API gateway?"- I told them how important API gateway was in production applications but this was just a basic app, hence didn't contain API gateway. He told that it was not acceptable. The rest of the time, I was asked about unrealistic details such as why is code coverage not greater than 85%.

I felt like shit. I had worked my * off just to be humiliated. Right after the interview, the HR called me and said that the feedback was "very" negative (these were the exact words). I asked him to cancel all other rounds as I was not interested anymore.

Retrospection (maybe one day it will help my fellow leetcoders) - It is completely ok if a company asks to complete short take home assignments. It is usually to see if the candidate can work with code. But if the assignment is to create an elaborate production ready code with design diagrams - then it is a red flag. If the company doesn't value your time now, imagine what will happen if you join the company? You will be given unrealistic deadlines/ask. I should have skipped wasting time and said NO as soon as the VERY LENGTHY assignment was given.

ReportMark as Helpful