- Published on
Intuit | SE2 | Frontend
- Author
- Shared Anonymously
Intuit Experience for Frontend SE2 Role:
Round I:
The interviewer was SE2 only, he asked questions around what I do in my current project, asked many questions around how can you improve web performance and asked me to explain technically.
Asked questions on web security, web vitals, how to improve web vital score, if I have written test cases.
He asked me to write currying function implementation.
Then he gave a few js snippet on the concepts of for loop, promise, settimeout, hoisting, closures.
At the end he asked me to write a memorization function.
Round 2:
Then after a day I recieved mail for carft round, the question was to prepare an event management system. I was given around a week+ time to prepare well for the next rounds.
I almost spent the whole time preparing the project + ppt + test cases.
Then My interview was scheduled by interviewer after a week, guys take time and prepare well for this round as the first 3 rounds are the most imp and elimination round the last 2 rounds just check the same and behavioural.
On this day my 4 rounds were scheduled back to back, 1st was craft demostation, 2nd was assessor round, 3rd was team member round and 4th was manager round.
In the Craft demonstration round, there were 4 panelist from which only 2 joined we waited for 5 min then started the interview, started with introduction then they asked me to explain problem statement and I presented the ppt that i had prepared, then they wanted me to run through the code the same thing that i explained them on ppt. they asked me questions around the code why this and why that, they expect everything the fallback page for any error which I had done, so they asked me to show that too which I showed.
They asked some question which I was not aware of so I said I am not so aware of this but yes we can use this and I explained what i was aware of this was the first not answered question, then they asked me to show test cases but I had written those only to show coverage and not related to the conditions which I had also not done earlier and I was not aware of that so they said then what is the use of the test case if you can't check condition. i think this was 2nd bad thing not sure if 1st one can be considered as one, depends on interviewer.
Then comes the 3rd interviewer, he asked me to change few things in code, which I did and worked properly. Then he asked me to sort the response and show on screen, which was hapening only render was remaining and time was up. So then we concluded the interview with me asking few questions to them.
I think interview went 80 - 75% well, but then no one joined the next call, so I called HR and she said that the response was not positive so will not go ahead with other rounds. Did not recieve detailed feedback.