Note: Google interview invitation asks the candidates to honor their non disclosure policy of interview questions. I'm choosing to honor it.

Status: 1.5 years experience.
Position: SDE2 at Media.net, Mumbai from July 2019. (Joined as SDE1 in July 2018)
Location: Bangalore, India
Date: Feb 2020

Technical phone screen (45 min):- October, 2019
Question - One question on data structure related
Received feedback after around 2 weeks. It was a borderline pass.
Observation - Interviewer feedback is pretty informative. They note down almost everything. Your different approaches, mistakes you did (even if you find and fixed them yourselves), communication skills, your comfort in the coding language (you choose your language), speed of coding, best practices in the language you coded.
Since it was a borderline pass, I checked with my recruiter if the interview is of qualifying nature or is it examined thoroughly during hiring decision. The telephonic interview is also examined during hiring decision and they check if mistakes in telephonic are repeated in onsite interviews.

Onsite (5 rounds): February 2020
Each round was exact 45 mins
Was provided with a laptop, paper pad and whiteboard. Free to use anything. But was advised to stick to one thing in a round because few interviewees end up wasting time by duplicating work on whiteboard and laptop.

Round 1: Algo round (Face to face)
LC Medium
Takeaway: Please note details of the question on the whiteboard or paper. I didn't note a detail of question and ended up coding a solution to a more general problem. Since I solved a more general problem, I think, it didn't affect negatively. But it could easily have been a disaster.
Tip: If the questions seems easy, try to finish as soon as possible. The interviewer may have some planned follow up.

Round 2: Googlyness (Hangout call)
Questions were focused on behavior, interest and experience in the current organisation. They don't ask about the projects in the current organisation. It is more about knowing if I've collaborated enough with other people and the challenges I face when interacting and working with others.

Lunch interview
A googler took me for lunch in the office. It is not a formal interview. No feedback is submitted by the lunch interviewer. You can freely ask him any questions and clear up any reservation you may have. Tip: ask him about different teams and work done in that office.

Round 3: Algo round (Face to face)
Medium/Hard - DP
Was to able to provide code in 25 minutes. Was asked a follow up, completed it in rest.

Round 4: Algo round (Face to face)
Medium - DFS,Binary Search
Again two codes. First for a simpler problem. Second for a harder follow up question.
I got last 5 mins to ask him about google.

Round 5: Algo round (Face to face)
Medium - Adhoc, Implementation
Coded the solution in 30 mins. The interviewer told me to check for a missing case. I reiterated through all my solutioning phase cases and ran multiple times through the code. I told him I thought there were none. I then gave another try and again told him I wasn't able to find and it seems all cases are handled.

Takeaway: If interviewer asks you to check for a case, there is one. Take a minute break. Drink Water. Unburden yourself. And then focus on finding that goddamn case. My mind hit the missing case 10 minutes after I left the building. I was very tempted to go back to my interviewer and say eureka. But decided against it.

Overall:
All the interviewers were very polite. The process was very efficient. Not even a single minute of my time during my stay in the office felt wasted. After end of every interview, I was handed off to another interviewer (actually the interviewer comes to your assigned room) who was already waiting outside the room. Each interviewer does their bit to calmn you down and make you comfortable. I think feeling comfortable made me solve problems faster. Google really knows what makes people efficient.
It was exact opposite to my experience at Amazon, Hyderabad in September, 2019. I spent 8 hours in Amazon's office to give two one-hour rounds. (I vowed to never apply for Amazon again.) Just had to mention this.

After the interviews
I was contacted by my recruiter on the same day to let me know the initial feedback received was positive. The recruiter contacted me two weeks later to let me know my feedback was positive and thus worthy to be sent to hiring committee.
Did a team-matching interview. I liked the team and manager also approved of me. After this, my feedback was sent to the hiring commitee.
Received hiring commitee approval two weeks later.
Recruiter contacted with proposed compensation numbers.
On accepting the numbers, the offer letter was released the next day.

Preparation:

1. Cracking the Coding Interview by Gayle Laakmann McDowell -> I didn't read it in the college days thinking the book was for noobs since I was majoring in computer science. Big blunder. The book's extremely helpful for everyone. Please go through it atleast once. (Or I'm also a noob. :) )
2. Interviewbit -> Solved google tag questions. I solved every question again in leetcode. Leetcode problem set is definitely a super set.
3. Leetcode problem set-> Bought leetcode premium for two months. One month before telephonic in September. Another before onsite in mid Jan. Solved exclusively google tag hard questions (mainly from the google top50 list). Didn't solve easy and medium questions from the problem set. Read the past experiences to find the topics which are to be practiced more.
4. Leetcode mock interview -> Gave leetcode mock interviews for google. It mostly contains mix of easy and medium questions and sometimes a hard question. Gave 5-6 interviews 2-3 days before my onsite. Gave me a confidence boost before my onsite interviews. It gives you a score relative to googlers present on leetcode.
5. *** -> Gave and took a single mock interview. Sitting at the seat of interviewer gives a fresh perspective. You should take a interview of friend or colleagure or find someone online.
6. *** -> If a question exists, you will find something for it on ***. Touch base on topics you've forgotten.
7. Wikipedia -> I almost every time opened a tab of wikipedia and *** for every topic I read. Sometimes I read the topic through CLRS.
8. LeetCode Discuss -> Reading details about fellow candidates offers/rejects provided some valuable tips.
9. People on leetcode who have solved almost every question on the platform or whose activity graph shows daily submissions. It motivated me to solve questions everyday.

Miscellaneous Tips
The process after the onsite interview is a long one. You can't do anything about it. My recruiter kept me informed of the delay. You can ask your recruiter to do the same, but don't be disappointed if he/she doesn't. You can't do anything about it.

If you're looking for certain hike or promotion from google, better have a competiing offer from another reputed company. From what I've read no competing offer, no negotiation. I didn't have certain hike or level expectations so didn't take the pain of trying other companies. (Please do try for other companies simultaneously and don't be lazy. People exists who got offers beneath their expectations ).

Be confident and hopeful about your future. No company defines you. You get in or not, you've your life. You've to make the best of it. Not getting it is not the end. Getting it is also not the end. Either way move on, figure out what you want and try your best to do it.