Background
2021 Grad
Experience-: 9 month
Interview Experience
I got a call from a recruiter in the month of April 2022, at that day I got a rejection email from another company.
The recruiter give me 3 to 4 weeks for preparing for the onsite round after that my onsite round is scheduled in May 2022. In my all round, the guys who took my interview all are from Switzerland ( Zurich Google office) sometimes I faced issues in understanding questions due to their accent. But the good thing is you can ask questions until you didn’t understand properly. Google recruiter is really helpful in everything like-: you can discuss your strategy and also give advice on how you write the code and which things you have to keep your mind during the interview.
Points remember for preparing the coding round-:
- focus your prep more on DS and Algos
- try to solve the problem as independently as possible
- consider optimising the solution proactively
- consider tradeoffs/ overlapping replacements in algorithms before coding
- Be vocal/ verbalise your thought process (please don't be silent)
- proactive variety of test cases ( don't wait for the interviewer to hint you)
- keep a tab on speed of coding considering 45 mins slot
Before google interview some points you have to keep in mind-:
- Always first understand the question properly, with no doubt
- If you have doubt you can ask your doubt
- They are also checking that you have to identify the parameter which is missing in complete question, like they say the question in such a way that some points they didn’t mentioned at that time and interviewer expectation is that you have to ask this point from your side.
- Also, you can ask for some hints if you are stuck somewhere
- Don’t forget base case never (I forgot in one round)
- First dry run the code then you can say to your interviewer is done
- Always use an optimized data structure
- You have a clear understanding that which data structure is used
- Discuss time complexity and space complexity with your interviewer before start writing the code
- Write code of production level like-: write code in the short module
- Bug-free code
First Onsite round
Q1. given a 2d array in which 0 or 1 is present, you have to count the maximum length of the straight line
In diagonally, antidiagonally, and horizontal and vertical.
Result-: Leaning hire
I am little pressure and due to this i didn’t think at optimize level and I wrote lengthy code. After the end of interview The optimal code came in my mind lol.
After this round i thought i am not prepared for google interview so, i was not preparing anything after this round.
First Round after one week of onsite round
Q1. Given a 2d array and you have to count no of path possible from when you go from bottom left to bottom right. You can go either horizontal or diagonal or antidiagonal.
Q2. This question is follow up of previous question, in this interviewer give list of bad index (i,j) which should not be present in that path. Then find the total no of path.
Result-: Leaning hire
Second round
Q1. Given an array of n elements of array a, you have to find total count of pair of index where
|a[i]-a[j]|=i-j where i,j index of an array
Q2. This question is follow up of first question, you have to find total count of pair of index where
|a[i]-a[j]|=|i-j| where i,j index of an array
Result-: Leaning hire
Third round happen after 2 days of the second round
Q1. Divide two integers without using division operator.
Result-: Leaning hire
Fourth round happened after one week of third round
Fourth round is googlyness round
Final Result-: Rejected
But the recruiter again schedules 2 more coding rounds for reconsideration, In meanwhile, I joined another firm so can't proceed with the next 2 more coding rounds.
Final Conclusion
Giving google interview is different experience, hope next time i will clear google interview.