[Music] hello and welcome to this video my name is triangle and I work as a software engineer at Google I start this video by showing you something and for that let's go to my LinkedIn profile so I joined Google recently and I posted about that on my LinkedIn profile to my surprise this post got pretty famous and at the moment it has 2.3 million views and 56 thousand likes and it is still growing these are huge numbers now because of this post getting so many views people get to know that I work at Google and I started getting a lot of LinkedIn messages and most of them were about sharing my Google interview experience what was the process and what are the expectations in the interview rooms so here I am and I'll be talking about that in this video I'll start with a bit more introduction about myself so that you can know me well I've done my BTech in computer science and engineering from Indian Institute of Technology PhD Varanasi and I graduated in 2015 and as of now I have a bit more than four years of work experience as a software engineer and since past four plus years I'm living in Bangalore before moving ahead I would like to mention about two things first thing this video is not monetized this means that I'll not be making any money out of this video no matter how many views it will get and this video is kind of a community contribution so that people can get benefit out of my experience second thing is that all the images to the post and music that are used in this video i ro LT free and the links for the same can be found in the video description I am explicitly stating this because I do not want this video to get stuck into copyright issues having said that as something more to share with you I did not get directly and I've given many other interviews before replying to people overall I have given interviews for these five MCS Microsoft Amazon Google Apple and Facebook so I've completed the full interview process for each of these companies which means that I have reached to the on sites for each of these I applied for a general software engineer position for all of these companies and for Microsoft Amazon and Google the location was Bangalore India and for Apple the location was Hyderabad India and for Facebook the location was Singapore so Facebook called me Singapore with all airfare hotels and me the sponsor and that was good the order in which I started my application process in these companies is so the first company where I applied was Facebook I was aware that Facebook does not have any office in India so I have to apply to a different country and this process will take time so I applied to Facebook very early and I applied to Facebook London Dublin and Singapore offices and my application was chosen for Facebook Singapore so I had my whole process for Facebook Singapore for Microsoft in Amazon I had my process for a Bangalore location and after that I applied to Apple for Hyderabad and in the last I applied for Google I'm telling this to you so that you can get an idea about my preparation before I started interviewing at Cooper before moving to my interview experience let me tell you the results of my interviews with these five companies I am very happy I am proud to tell you that I was selected in Microsoft Amazon Google and Apple and I was rejected in Facebook repeating that again I was able to crack the software engineering interviews at Microsoft Amazon Google and Apple but I was rejected into Facebook and Facebook I am not sure why were they rejected because my coding interviews aren't well I think that the system interview around might be the culprit because there is no fixed solution to insist on winter vacation so er addiction happens but in this video I have shared only my Google interview experience also one more disclaimer before I start this video the experience that I'm going to share here is of a four years experienced guy and for a software engineer position so the experience is that you might have heard from your friends relatives or you yourself might have experienced can be different bases on the ESO experience and the position applied also this is my personal experience so comparing it to anyone else will not work I'll follow a step by step process and will tell you in detail about each step in the process so let's start step one which is often the most important step in any interview process can you connect it to the recruiter well in my case I do not have to do anything as one of the Google recruiters who sits in Singapore approached me and I got an email in which she asked if I am interested in applying to Google and mentioned about the available positions for software developer at Google Bangalore office and then all I have to do is to reply to [Music] the next thing that I did was sharing my resume a with the HR I use the same resume a for all of these companies and I was not applying for any specific role and I was applying for a general software engineer position I was aware that my resume is gonna be my first impression to the HR so it was very important for me to build a good resume it I remember that I took around three days for making my resume a and I got it reviewed by a few friends of mine so that I'm sure that I'm not missing one anything I kept the following points in mind when I was making the resume the first and the most important thing is the resume a should be short and crisp so I made a one-page resume a and though in the details of my project I just mentioned the highlights of the projects not the full exact details and then four that I mentioned was having the data the numbers that can show the impact of my work to anyone because when any external person like an HR will just go through a resume a then they'll they can judge you only by the impact of your work second point was that use bullet points and do not write paragraphs this is a big negative nobody get time to read the paragraphs in your resume a so and if anything is going like more than two lines just friggin two more bullet points and just writing a paragraph will not help third thing is that keep the must-see things on the top so in my case I was a furious experienced guy so I put my employment section at the top and then I put my languages and Technology section because I wanted the HR to go through these in a specific order and after that I put my education section and then rest of these and at the point is that do not write everything in your resume and leave something to be discussed in the interviews so it should not happen that if you are in an interview and the interviewer asks you something it should not feel like just reading your resume a another thing was that through a good template and use good fonts and spacing and it should be balanced it should be readable and it should be like it should not be having a lot of data on one side and a lot of spacing on one side it should overall it should look good now that I'm talking about resume I making if you do not have a resume a handy or do you want to prepare your resume a really really quick I have something for you I've shared my resume a template in the docx format in the end of this video so that you can just download it and edit it in the Microsoft Word and your resume is ready really really quick so please do not miss the end so the next step is to screw the call so around one week later I got a call from the recruiter and this call was having a few agendas first thing was for the recruiter to get to know more about my background if I am interested in any specific team at Google or any specific role at Google second thing was something that I didn't expect and that was a kind of rapid-fire round of technical questions these were like one-word answer questions and were pretty easy so if you are preparing for Google interviews these questions should not bother [Music] so after two days on the recruiter call I got an email asking the preferable slots for my technical telephonic interview in that email she also shared a few Docs and videos link so that I can see and get an idea how Google interviews looks like Google is famous for having a very high bar for coding interviews so I thought of taking some time to prepare well for this round and just like any other portion I was having a fear which is the fear of rejection I just don't want to get rejected in this round and wanted to reach at least to be on sites so I took time and I got my telephonic interview scheduled after two weeks this was a 45 minutes round and I was told by my recruiter that this round will be focused on data structures and algorithms here are a few things that might recruit I only shared with me and which I found really helpful and I am sharing with you now so during the interview ask yourself that do you listen well well this is incredibly important when an interviewer tells you occasion to soul they want something from you they want you to catch the hints to be clear about the problem statement and the input and the output so just let the interviewer complete the question and just listen it well do you feel confident with CS fundamentals I think there's kind of self-explanatory so I'm skipping this we know what to ask to clarify the questions so sometimes what happens that the interviewer leaves some ambiguity in the question on purpose so that the candidate points it out and just ask the interviewer to clarify it this gives interviewer an idea that how attentive or you know what is the thought process of the person for example what to expect in the case of overflows what if like if the null values are allowed or not etc 0.4 which is can you find the optimal solution of the complicated coding algorithm problem so a problem can have multiple solutions and it's very obvious that the first solution that you get into your mind is not your Demond one and he will improve the solution over the time and make it more optimal now another thing that comes into picture is that are you able to explain the solution to interviewer or not if you are able to share your thoughts logically I've seen people struggling here if you have developed an extremely efficient algorithm but you are not able to explain it to the interview then trust me it's of no use finally it's the interviewer who has to judge you whether you know what you are writing or not next point which is is your problem-solving encoding speedy and efficient with the perform knowledge in CS fundamentals putting speed is something which matters a lot in Google interviews actually it made us a lot in any other interview when any of the company and the efficient knowledge of CS fundamentals means that I using the correct data structures or not other data structure that you are using to solve the question solve each and every test case each and every corner case and 0.6 heavy covered of edge cases this is also extremely important once you are done writing the code try to dry learn it with multiple inputs I might have a test cases perform null checks check for the overflows and the check for different different inputs and verify of the output is correct and the test the boundary conditions and just make sure that everything is working as expected so on the day of the interview I got the interview call from a Google employee was walking in Google Zurich office a Google Doc was shared between me and the interview so that both of us can see what the other person is typing the expectation was to write a clean madula code not pseudocode the actual code for the quotients asked and then unit tested code and check if it covers all the edge cases or not this call lasted for 145 minutes and I was asked one question and one follow-up for the same question before writing the code for the questions I had a good discussion with the interviewer regarding the possible solutions and once both of us agreed on a solution then only I started coding for that [Music] the result of this interview after two days and the resolve out there I was good to go for the on-site interviews now the control goes to another recruiter who is in Bangalore so my Singapore recruiter get me connected with another recruiter who works in Google Bangalore office and they he took my candidate a forward from this point of time in the process so I had a call with a Bangalore recruiter and they explained me about the next step which was the online interviews a few things that I really like about Google recruiters is that first thing is that they truly understand the candidates situation if the candidate is feeling nervous they'll try to make him come and try to you know just tell them that okay you can take your time they do not force you to give the interviews and you know they don't say like why are you taking so much of time and the why I'm not prepared at this point of time no nothing like that so I told the recruiter that I feel unprepared because these are Google interviews it's very normal for anyone to feel that they are not prepared at the time when I was having Google interviews I was already holding offers from Microsoft Amazon and Apple but still I was feeling unprepared because I was having this in mind that the Google interview that gonna be of an entirely different bar and you know I just need to revise each and every algorithm and though I just need to practice a lot and lot and lot because I just can't go unprepared and you know waste my chance of clearing the interviews so I asked him that I want to take some time and he said yeah okay and I took the date of interviews around three weeks later so that I can get some time to prepare for this interview specifically because I was walking also so I was not getting enough time to prepare for the interviews and give time to this preparation so Lee another thing that I liked is that the recruiters will quote you well and the things that you need to prepare so my Banga recruiter send me an email in which in which there were a few more links of the videos around how I can prepare for the on-site interviews I also asked him a lot about few things like how the ratings work at the Google interviews like how are the interviews gonna read me and what will be the process post the interviews like what happens and how will I get to the offer and he replied to all of it very politely so the strategy that I following these three weeks was to practice a lot on pen and paper this is something important as practicing one pen and paper or on a whiteboard is very much required before the on-site interviews because you know I know that in general whatever code that we write in our company or in college is on an IDE which has the features like autosuggest autocomplete and the indexing and all but when you start writing on a pen and paper all these features are gone so you have to remember syntax you have to manually just go and write the whole syntek saying and the it will not all just Auto suggestion anything so you have to remember the function names and all I know so this thing is pretty important before the entire interview so I had my on-site interviews these were five interviews in a single day and I was aware of the schedule in advance because the recruiter has already shared it with me the she will was something like I was having three coding interviews then a lounge interview which is actually something different that's why it's in blue and then one googliness and leadership integral and then another coding integral I was aware of the Bangor traffic so I left a bit early my day we started at 10:15 a.m. so I had for on-site coding interview rounds in the process for each of them is kind of similar so I'll be sharing what happens and a single coding interview around at Google so this was the 45 minutes round just like I had in the telephoning interview in fact all the coding interview rounds that I had on side for 45 minutes the number of questions that I was asked varies from one to do actually it depends on the interview the cushions can be like it can be either a single question one question and a follow-up or two different questions depending what the interviewer has thought before coming to the interview so the process was that I was given a laptop which was a Chromebook and I have to type my solutions into the laptop so that the interviewer can take a snap and paste it to the having to because I have already given the telephoning interviewers aware that what things to keep in mind while giving the interview so then they restarted and the one Center viewer has explained with the question completely I tried to clarify it if I had any doubts and Digger more about what is the exact requirement in the question and once the clarification is done I use the whiteboard there to discuss all the possible solutions with the interview and I just took some examples for the same question and once the solution and the implementation is finalized I wrote that on the provided laptop and whatever I was typing in my laptop was visible to the endeavour in their screen and though if there is any comment that the interviewer wants to give or if there is anything that they want to point out specifically he can just do their like face to face and once I was done with the code I verified the solution with some test cases and tried checking the edge cases and make sure that the things are working as expected so I had all this and make 45 minutes are gone before coming to the interviews I've heard a lot about the amazing food at the Google Bangalore office and what's more amazing is that I do not have to eat it alone Google has this concept of lungeing wo which is not an actual interview I mean the feedback for this interview is not counted in the final result this is an amazing concept cooller was assigned to me for having lunch it helped me to relax and I asked many questions to my lunch inter were like whatever I have in my mind for example what is the culture of Google Bangalore office and how does the day of our Google Earth looks like and how many teams are there in Google Bangalore and Alok lot of allegations and he just answered it very politely I also had one more round in Google and that was the googliness and leadership Brown who just called on Jillian around and this was around 45 minutes long Rubina says like Google's Norman's nature for behavioral interview if we have a few errs of experience then it becomes really important for the company to get to know that how have you performed in your previous companies and how is a vision about yourself and how will you react in a certain situations so I had my GL and round because I was having for experience Google is a company that is famous for its amazing culture and I think the agenda behind this round is to check that if I'll be able to grow in Google's culture or not it was more of a like of a cultural fit at Google so the cushion that I was asked was based on my past company experience and there were a few hypothetical questions also so the cushion that were based on the past company experience or our behavioral in nature start with something like tell me about a time and the cushion that our pathetical cushions start with something like imagine that for fast experience-based cushions dedicated preparation is very important as this sound is gonna be more about me and i should be very clear about what work i have done and how to communicate it well so when giving the behavioral interviews for other companies before Google I came through an interesting fact then I later used for all of my behavioral interviews that is in a behavioral interview people love hearing stories so when they asked you a question which is a behavioral question just tell them the answer in the form of a stool your story should have STAAR star which is situation task action and result if you will give the answer in this way then the endeavor will completely understand the thing that you're trying to convey and if you want an example just Google a bit for the behavioral interview questions and you will get a lot of sample questions just apply the star method to create your story for that question so this is how you're prepared for the behavioral interviews and you cannot prepare much for the hypothetical questions because they are more to test you as a person so they are more of a personality trait and you cannot change that for any of the interview so like I just went unprepared and like my personality [Music] after giving their dues I was having a feeling that the interviews owned well but again I was aware that like I should never celebrate Diwali I asked a recruiter to expedite my process because of a few things going around so my Bangla recruiter was only so there was another recruiter who was in touch with me for the results and then I remember after one week later I got the call from her and she said that hey Priyanka I have a result and I was like okay and that is and then she said those three magical words guess what you are selected and I was like oh my god can you say that again is it happening for real and then she was like yeah it's happening for real congratulations and then I believed that yeah it's okay it's happening for real I was feeling like an achiever a perfectionist and whatnot and this was like a dream come true and even today this is an understatement and then she just shared the conversation details and I got the final of a letter after two weeks the overall process took around two months and yeah that was my story that how I became an engineer at Google or the Googler or the Googler and now is the time to enjoy some music and cool pictures [Music] [Music] so again as mentioned previously I went through the full interview process for all of these five companies if you want me to share my Devi experience for any of these companies then please let me know in the comment section also if you are interested to hear stories about how I started coding in college or how I prepared for my coding interviews please do comment and let me know also do subscribe to my youtube channel because I will be posting any new video on this channel moving if you want to know more info about me like info about my coding profiles on different competitive programming sites just do a google search for the keyword prehung - double zero double one and then you will get the links to my profiles for code forces coaches spot you know for young - double zero one one is the username that I use for all of the coding sites also you can connect with me on LinkedIn and I have the same username there also okay as told somewhere in the middle of this video there are a few more things around resume meeting so I found this amazing link that I'm going to share with you put your browser and type Carol Capcom slash resuming this is written by Gail L McDowell she is the founder and CEO of carrier cup and author of one of the most helpful books for interview preparation which is cracking the coding interview she has divided this resume by making into different segments and manga few numbers against each of it and then she has explained in detail that what are the tools and don'ts while making a resume I highly recommend you to take a look if you want to prepare a killer and steaming also I've shared my resume template the template that I've used for all of these companies and you can find it here www.tanahoy.com resuming also I've shared this link in the description of this video and you can just go and download my resume in the Microsoft Word doc format and you can just edit it and make your resume a really really fast if you are interested in applying to Google then go to carrier start coopos.com slash teens and then you can find out if there is any open role that is suitable for your profile by selecting a division and then using the filters to trim it out and if you find such a role you can email me as you may and the job link at Priyank dot referrals accurate gmail.com and get a referral please make sure that there is an open role for you else this off no use the referrer will not work I have created this email id specifically for referral purposes so don't mind if this is getting flooded another congratulations you have made it to the end I hope that by now you have a good enough idea that how Google interviews looks like and let me know if you found this video helpful in the comment section and I'll see you in the next video thanks for watching