Interview Experience at Google | Tech Dose

Key Takeaways

[Music] [Music] so hello everyone welcome back to geeksforgeeks my name is another interview experience and today we have a very special guest with us so before we start with the webinar just confirm me in the comment section if i'm perfectly visible and audible so that you know there are no network glitches in this entire webinar the entire webinar is going to be really helpful to all of you so just give me a thumbs up and we'll wait for another two minutes maybe so that more people can join us and then i'll add my guest to the stream yeah hello everyone i can see a lot of people have already joined so yeah just give me a thumbs up and quickly add my guest cool everything okay fine i'll add surya to the stream hello surya how are you doing yeah hi hi everyone yeah i'm doing great how are you yeah i am doing great as well so i can see people are already very excited in the comment section so before i get started with the webinar i know that most of the people will already know you because of the amazing work that you are doing but still for those of you who do not know you can you give us a brief introduction about yourself yeah yeah hi uh i am surya pratap and uh i am a creator at tech dose so i had started creating videos that in 2017 while i was staying in college in my masters and then i joined samsung samsung bangalore in 2019 and i did two years on embedded system after that i i was a full-timer i take those and i was also i am currently the instructor there for the live classes and apart from that i like to create videos and do one-on-one sessions and all so i have been doing that full-time in from the last one year and now in march i have joined google i got an opportunity to actually appear for the interview so i took it and appeared for the interview and that's how i joined google and i'm i'm just going through some training and uh soon i will be starting up my work yeah yes that is really great also definitely check out his videos they're really helpful like that was my go-to channel when i used to you know solve the essay questions and whenever i used to get stuck anywhere i was like okay i used to see your videos and definitely check out the youtube channel so my next thing would be can you tell us a bit about your coding journey like how did you come across coding or like was it from school days or did you come across it afterwards tell us a bit about the coding journey basically yeah so for my journey part actually i like to i mean i liked about technology when i was killed i mean still in school when i didn't know anything like right from the very beginning like from class one or two i didn't know how to become a computer engineer and i ended up becoming a metallurgical and mechanical engineer so i never knew what to do i didn't have any any idea about what i was doing and uh after that like once i was into my b-tech i did my b-tech and passed out in 2016 and after that i decided that i will have to change my department to computer science which was not allowed in india actually you if you see most of the colleges will not allow you to do that suddenly i found a college after going to hundreds of glossary i found one college where it was allowed provided if i can clear the rounds of interview so i did that and i got masters in computer science the software engineering to be to be exact so that is how i actually went into the software engineering i wanted to do coding but i never started it until my i started my masters so it was only in 2016 to 17 when i actually got started and when i when i started actually i was adding two numbers finding maximum and all these things so it was pretty basic pretty simple and then i started i mean hearing about code chef and stuff and i started doing it but i couldn't solve any question that only one or two questions at max so suddenly i i found that the schedule of interviews are coming in the in the four to five months and and that's how i actually left comparative programming which i never started and right now as well i have never started comparative programming so uh people i see that on linkedin i have been sitting for seeing fights on competitive programming and all this so yeah i have not been commenting there but if you personally believe me you do not need any competitive programming to get any job and if you like it if you develop your skills uh i mean if you want to develop your thinking ability want to challenge yourself what developed in various various tools on and and mathematical tools how to code and how to think you can go with competitive programming very good you will be pretty good in coding as well but if you are someone who is just concerned about getting a good job and then as soon as you get a job i don't care too much about coding i will care more about the technology part the development part and once i want to switch then again i will switch back to the boarding do some practice and again get a good job if you are that kind of a person then actually i would not recommend you to do competitive programming so i never did it so i my first uh journey when i started was with for gigs why in 2017 it was a very small website back then with a very handful questions so i could complete it in like six to seven months right now it is pretty big so you cannot complete it even if you have the entire time you have to hand the books yourself so yeah i mean geeks for gigs was the go-to website for those preparing for interview right from the very beginning because there was no such website and there was another website interview bit but their test cases were not good enough so i guess right now it is geeks for weeks or lead code also i 100 agree with your point that competitive programming can definitely help you but it is not like if you not do competitive programming you will not get selected in any company like even i try to do competitive programming like in my first year and second year but then i understood that it is something that does not interest me and i left it eventually because i see a lot of first years they're like treating it as something mandatory like they have to do competitive programming no matter if they find it interesting or not they have to do it i see some of my freshers asking can we finish competitive programming in one month you cannot finish it in like one or two months it's a continuous process yeah right yes then uh talking about the interview rounds at google that this webinar is all about so can you tell how many interview rounds did you go through and a brief about each and every round uh yeah so people who had appeared in my time uh actually went through five dsa around to be frank and the first one was actually named as a telephony crown but it was also a face-to-face round where you will get a question and you will be just if you are good enough to actually uh spend you spend time and actually go through the all the rounds should they schedule so that is like a screening round face to face of 45 to 45 minutes to one hour where you will get a question or maybe more than one question generally you get one or two questions if you get one question you get more follow-up questions on that and uh yeah it is just like a discussion so you just discuss whatever you know and uh whatever feasible things you can do and the interviewer will judge obviously you will have to write a clean code modular code and all these things are applicable in all the rounds and apart from that the first round and then you get the result that do do they want to actually proceed with you do they find potential in you if if they if they feel that you can do it so they will schedule all the possible rounds so i was scheduled with another four rounds of dsa followed by uh one round of googliness which is basically like an hr and after that your case will be submitted to the hiring committee where the committee will decide about if they want to hire you depending on the feedback on all the rounds and if you have worked on your negative points so every round will have some negative points about you and if you did something negative you will you should not repeat it basically in the next in the in the upcoming rounds if you are repeating it you will get rejected if you are not repeating it and did not do blunders then actually you will get selected so that is what they look and once you get selected then you will be attending the fit calls with the with the different team managers and if the manager likes you and you like the manager then that is how a match happens and you get hired so that is the over overview of the process but currently speaking right now they have reduced the number of rounds since they are trying to hire more people so so you will face only three rounds of dsa right now so right now it is the time to move if you want yeah also like what is the level of difficulty of the dsa questions if you have to rate it on easy medium hard late okay i mean the first round is generally medium medium to medium hard and the questions you you you should not expect the questions very straightforward like you do on lead code so what they do is they will they will possibly take a lead code question scramble it up in such a way and uh maybe give some more intuition into it so that it will seem like a different problem but then it is the the your first responsibility is whenever you see a question can you relate to some question which you have already done possibly you might you must have done it most people have done it but can you convert that question to the other one that is the most important question i think many people just uh under pressure they are not able to do it and some people are not able to get that intuition of how to convert the given question to something which you had already done and that is where the problem comes some people also get their issues when they actually do not remember the implementation and so they are they are not too confident that if i know the algorithm can you write the entire clean code so many people just feel in i mean in that part of the room so i think i think i mean it is not it is not very difficult but still you can expect medium hard and once you proceed to the to the second half you can expect harder questions if you get a medium question you will get a harder follow-up for the medium question that is how they actually do it so one question may be followed up by four or five follow-up questions and you should be ready in your mind while even solving the question you should be ready on you should think about what follow-up question they might ask and you should prepare even while answering the current question at hand so that you get some time and obviously you should not stop thinking about what is the answer for this i mean this is not a verse i hundred percent agree like i gave an interview recently so that was a very simple linked list question but the interviewer gave me like 10 to 15 lines question and i had to figure out that i simply have to reverse the linked list but yeah so that figuring out took me 15 minutes solving the question took me two minutes but figuring out that i had to do this thing and the logic exact logic took me a lot more time so yes definitely i think that is what the interviewers are looking for that are we able to relate to the question that we have already solved as you told yeah yes also i have seen that writing a code in an interview is very different to what we do in uh like what we solve on lead code or code forces or any other platform right because many times students are able to solve the question but they are not able to write clean code or what the interviewer actually expects so what will be your suggestions like how should we write the code in an interview yeah okay i think writing the code in an interview is all about keeping house so i mean i never practiced writing on a notepad but i felt i i wrote it in the interview directly even you don't need to prepare writing on a notepad because i i don't feel like writing anything on a notepad to be frank so if you are prepared you know that you know the answer obviously they are not going to run the code but they are but since they have prepared the question themselves and they are going to ask the same question they they remember the entire answer flow they know all the things they know all the edge cases so even if they don't run it they'll catch you if you miss any case so it is like you will get get some escape or something but obviously on the syntax part of it you might get an escape route they will not force you too much into syntax like why have you written print and why not c out or something i mean you can get get away with that because you can just google it out and see but when it comes to the actual logic part you have to write it clearly and you have to handle all the cases so they just i mean there are multiple things they look while while you are doing an interview the first thing is what is your behavior the first thing is how you actually behave how you present yourself the second thing is how confident you are confidence actually comes with your own preparation if you are prepared with on the topic from your question then you will be more confident and with confidence you will be actually able to convey your ideas more clearly if you are not confident then actually just for the sake of speaking out you will seek out anything and that will confuse the interviewer and that will actually go against you because they will give you a rating something like this guy is not good in communication even though he speaks english but he is not good in making others understand about uh what he is thinking so you you did not answer the question as well as you get a negative review in actually communication part that should not happen communication is even more important than writing a code so you cannot communicate you cannot work in a team and so you are not required in the software industry communication is more important than your coding how cleanly you really write how less complex you write the code it doesn't matter i mean in the interview it matters about the most optimal solution but it won't actually bother about such a complex algorithm which actually does not solve for interviews but only for comparative programming they don't expect that then they are also not expecting anything uh which others don't know right you must be knowing the solutions you must be knowing everything others also know but it is all about how cleanly you write how less ambiguous ambiguously write how modular you write how well you take the variable do you follow the camel case and all those conventions and whatever makes the code more readable right so uh would be the higher complexity and more readability is more preferred in industry rather than a faster code with no readability at all so i mean these points are taken care even if i mean many of my students have cleared all the questions but still they do not get selected because they just clear the question they just pass the question fastest way okay then but but still their code is not readable they take them temp as they as a variable name i think we are used to taking temp or t or whatever save and next whatever we should not do all these things obviously while practicing as well i mean i would i would recommend you to actually uh take meaningful variable names when when the interview is closed and competitive programmers actually do not actually put so much attention into it because of the time constraint they want to take the smallest variable name so that they can write the code faster so i mean that is somehow going against the software norms software development so yeah i would recommend these things because eventually we have to work in a team like our code has to be like readable so that you know our team members can also understand i think that is the whole point like what the interviewer is looking for yeah so an interviewer will actually not hire a genius person who just works alone because no project can benefit so even if you're just you cannot get hired but if you are a good team worker not a genius just a normal person you will get hired for sure yes definitely so one of my friend i was talking so she just told me that she used ijk in the interview and obviously she did not get selected so yeah these are small little things that interviewed these actually have points as well i guess like the interviewer is masking you so just make sure you do not make these mistakes and take proper variable names yeah yes so the next and very important thing is resume i think resume is something that reaches to the company before even we like we are able to reach to the interviewer so what will be your tips for resume like how can we make a resume in such a way that it stands out from the rest of the resumes that are already there yeah so actually uh when the recruiter i mean the the best possible way to actually get an interview at google will be if the recruiter reaches out to you you not taking any referral but the recruiter actually reaches out to you then you can be 100 sure that your interview will happen now how can a recruiter open open your profile and get interested into that so the first thing is what work have you done okay what work have you done so the first thing which attract them the most is have i mean do you have the same background of work of whatever they are looking for so if they are looking for back end do you know anything about back end the second thing which improve the recruiter is which company you have worked for so if you have worked for good companies even though your profile is not matching still they will they they will reach out to you the third thing is what college you have passed out from if you have passed out from a good college then no matter where you work actually recruiters might reach out to you then there are several other factors of i mean how much active you are and i mean i mean how well you have done how much faith they they actually think the community have so all these things combined the most important is actually what companies you have worked for i i feel like i feel like this is the most important again it google always always uh i mean works on diversity even if you are not from a computer science background they will hire you not like the other companies which will actually be skeptical so they they are going to hire you if you do well in the interview it is just about getting the interview call and the resume should actually be clean you don't have to fake your resume you don't have to take that you might have heard somewhere that back-end openings are more in google so i will write my resume in such a way that it will show that i i know back end right so i mean it doesn't make sense i mean you might have like i have worked on embedded systems embedded systems very less opening in google and i have been hired in the search team which is like totally disjoint from from the from the work which i have done no i mean nothing in common so even even if you have done that i mean one of my colleagues actually from a finance background not even an engineer he is also hired so if you have done in well in their interview you are had that's it right so just write whatever you know in the resume i've seen a lot of students this right everything in the resume and don't make that too complex i mean people should see the resume and they should understand make out of make out what you actually want to say so people just write so dense resume and use two two columns if you can do it in one column just do it in one column don't make two columns and fill up everything all the possible details don't give so much detail that just by looking at it it looks like he has to put a lot of effort in reading that resume right so it should be effortless reading your resume should be effortless and it should only contain the most relevant things you want to showcase because even if you have done 10 projects nobody cares about it just write the top two or top three so i personally prefer to make a single column i have made my resume just a single column very very short resume even if it was i mean i shortlisted it in such a way that it even one page was not filling and i have seen my students filling up multiple pages and making it so tense so i mean it is not required to be friendly yeah i think making a resume is an art like what i do is i just get my resume reviewed from multiple people and then i get the feedback and improvise it like whatever feedback i am getting so this is something that i follow and it has helped me a lot to curate my resume so yes maybe you guys can also do the same like get your resumes reviewed from people who are already working in the company or like your seniors or someone yeah right yes uh then we were talking about projects so many students are confused like what project should they work on should they work on one complex project or like three simpler projects so what will be your suggestion like what kind of project should can students work on i would say that uh i mean any project is fine i would not suggest you to actually do very complex projects whatever interests you you should just do that if you are not interested in something and somebody is saying that this is more in demand you should not you should not actually do that because you never know what you do will never be aligned to whatever you have done you should be sure about it because very very few people are there who will actually get the same work what they have done previously the domain keeps on shifting keeps on changing and software industry is also very volatile and google is also very volatile in terms of technology they keep on changing all the documentation everything keeps on changing the tools as well so you will have to constantly keep learning they also know that and their company is not static at all they it keeps it is very dynamic and keeps on changing every day so they they would like to have such kind of people who have shown that uh you can actually uh jump from this domain to the other domain and have done well so if you are ready ready for a change then only it is a plus point for you you should not say that i have done this so i will just get get into the same department because i mean even if you want that you should keep it inside you when you actually clear the interview and when you get the fit calls with the manager then you select that team but until then you should you should not speak about it once you speak about it it shows that you are not open to change and so according to requirement you might not change and you you might leave or you might not do well so they will not hire you for that also like is there any referral system in google like can employees refer other students for in google yeah so definitely everyone working at google can refer people both for internship and for full time full-time openings are a lot as compared to internship internship doesn't have too many openings and generally for internships they like to hire from a tier one college but for a job they do not see any college they do not have any college reference for job they will just see your cv profile and will actually give you a call if you are good enough and matching with the profile which you have applied so actually you can take a referral from any employee and once they refer you for a job then you have three options currently you have three chances three job ids you can apply different different independent job isds independent country it doesn't have to be india all the time and and just for your knowledge i will say that even if you apply in any country all the interview levels are same so it is not like you apply in switzerland or germany it is a different uh i mean it will be harder than india i mean it is that everywhere it is the same they follow a standard difficulty standard uh which is if you see lead code and have given lead code contest then i would mark it as six marks question are the most frequent ones you have seven marks question as well which you should generally not expect but the six marks in harder version are too hard hard uh questions only too hard and another one is just hard so you should focus on the hard questions and the medium questions in an interview can you tell like any three things that uh students should not do while they are appearing for a google interview or any interview in general yeah so uh the most i mean i have also taken multiple interviews and what people uh keep repeating is if they do not know they just speak they just start speaking anything i mean if they are not sure about something they start speaking anything which even they don't remember what they are saying no some people just try to confuse the interviewer and that that has actually two negative points obviously the interviewer is not a fool so he will know that you do not know the answer or you do not know the question if you you did not either understand the question and if you did then you do not know the answer so first thing is you do not know the answer even if you fake it you speak it they will know that you don't know it and the second thing is if you speak trash and try to fool the interviewer or try to speak any anything garbage then it will also be pointed out that you are not good at actually skill that maybe you want to explain me something but you are not able to explain that may also be there is a negative point third negative point is you are not accepting your fault and that is actually not tolerated at google so if you are at fault you should accept it if you are not sure you should say i'm not sure but i i would recommend uh doing this or that it is fine you won't get a negative mark getting zero is better than getting a negative marks don't get a negative negative mark this is one thing second thing is even if you know the answer you should not be too hasty into implementation you should properly lay out the you should properly discuss your idea with the interviewer if he is if he feels that it is a good enough solution he will ask you to actually implement it don't just go ahead and implement and while implementing line by line you should speak about what you are doing and why did you do a certain step it it will it will always give you a positive impact that you have the complete understanding and the complete control of your code because some people just learn it that let's say some algorithm is implemented in this particular way but they don't know why so if you keep it line by line then the interviewer will know that you have complete control of what you are doing and what you are saying this is one more thing another thing is again your fourth quality the code quality you should make modular functions make the different different functions for different different jobs so you don't write you don't give multiple jobs to a single function and whenever you see that let's say a validity check has to be done for the boundary case of a matrix where you cannot go in all the four directions then you can write a validity check function and you can send your coordinate into that and return true or false instead of writing a long check of let's say four conditions and and also appending some more conditions it will make make it less readable so try to make the code more readable and try to make it more modular and try to use the camel case convention and try to write the most optimal solution whatever you know one more suggestion would be to before appearing for a google interview you should go through their documentation so their documentation whatever the recruiter shares with you actually says that google is a is actually a search business it is a search business and search whatever search engines do are they care about the fastest possible solution they they should have minimum latency so i mean they also want their employees to be the fastest one and to write the fastest possible code so google interview is a little different than let's say amazon interview because in amazon you would start from approved course and keep reading your solution up in google you give the best solution you know so you don't have to build it in a broadcast way and even their documentation source shows that so this we keep keep these things in mind and if you if you are confused about anything you can always talk to the recruiter because they also want you to get hired because they have their own incentive in them right right yeah yes i hope everyone who is watching this may please keep note of all these points i think these are very valuable points in the last point that you mentioned about the brute force approach and the most optimized approach i think it is very important and you know it is very company specific so definitely you know keep that in mind when you are appearing for a google interview yes then now there are so many questions in the comment section i'd like to take uh like as many questions as i can yeah sure right [Music] maybe you can send your questions once again because you know if you send the questions at the very beginning i might miss your question so please send your questions once again i think one of them is confused about the system design round so actually around three to four years of experience you do not need system design as i said you just need to clear the ds around that's it right then vishali has asked this gap year matter for full time i think oh gap year doesn't matter i i also have a gap year of one year after my b day so it doesn't matter i have two two years of gap one for my personal reason another year for just changing my department that's it so you have to be actually frank with whatever you have done don't lie anything they will actually not bother about if you have given a gap or not given a gap or what is your age they don't care about it uh okay then there's a question by saul nadeef that what topic do they prefer more i think he's asking tsa topics if there are any specific topics that are answered so i would say the most asked topics are one round you will get definitely on graph their favorite topic is graph one round on on anime programming and another round will be a mixed round and that round will basically be on the selection algorithms like quick select binary search and uh combined with some greedy algorithms like sorting and stuff all of these combined into a single round so definitely graph and dp you cannot clear without doing graph and db yes then this is asked that what to say if he or she doesn't know the answer to a question like straightforward no or should he or she try give it a try first and then just say it so if you don't know i don't think you you will you will ever face this situation if you are prepared so i would suggest that you prepare so well that actually you can speak out something uh even even if you see some question which actually doesn't hit in into your mind what type of question is this so actually you can you can discuss on the requirements of the question you can discuss more on what this question wants try to give your own test cases to the interviewer which will actually clarify the question and if you have understood the question still you can't do it then actually i mean you should give it a try because they will not they will not change the question so you can say that i do not have too many too much of idea into it but again i i will try to try to i mean i will like to give my try so you will try and then he will also try to give you a little more hints once he knows that you actually don't have idea about it and if you can do it it will be very positive for you but if you can't do it then anyway you are not you are actually not aware about that question so in in any google round if you can't do a question you will be rejected for sure so you have to do the questions even people doing all the questions are rejected so you can't expect that in any round if i don't give an answer and do i have a chance or no you will not have a chance there for sure yeah it is very competitive so try to answer like all the questions as many things yeah so because they have so many interviews so many if almost everyone tries to apply for google so many referrals are there but still so less people are had so competitive competition wise you have to do you have to be on the top yes then ask that how do you motivate yourself when the code doesn't work like not with point of interview i think in general okay i think when the code doesn't work i mean i personally do not need any motivation because uh i mean i like to do it that's it so if you don't like to do it then you you need a motivation for it so people who don't who don't actually care about coding their motivation should be what is their target why are they doing this coding for the interview right so everyone has a different motivation my motivation uh is like i just like it that that's how i i keep myself motivated like it is just a refresher for me not a headache actually so if you find it to be a headache then you can think about why i'm coding and that will give you some motivation right also i think looking at the solutions is not not a bad thing like initially i used to think that if i'm looking at the youtube tutorial or i'm looking at the solutions or the date go discuss section then it is not right and i used to waste a lot of time just thinking about the question but i think you can you know always follow some videos or look at the discuss section if you're not able to solve a question after some time yeah i mean that is very subjective to how much time you actually have in hand so somebody in college can spend more time into the thinking part but somebody who is working actually cannot give so much of time only half an hour should be enough and don't spend more than that time or if you have an interview at hand if the campus hiring is going on you cannot hope to actually spend too much time but if you are in a first or second year you should actually not directly jump to the solution but you can spend some more time so it is a very subjective thing depending on how much time you have in hand right yes so sumit is asked that he is from a non-cse background how should he prepare for companies like google okay so even if he is from i mean that the everything the process remains the same i mean they don't care about your background so i i was also from a non-csc background so i guess you just prepare for your dsa if you are appearing for sd1 or sd2 rolls after that i mean design is required but google just focuses on the code so if you are well prepared with your coding part i think once once your cv is picked up or you have got a referral then i think you you will have to just clear up their dsa route so no specific preparation is required just like everyone on the csc with a cse background you will be preparing the same thing and no and they will not actually ask some concepts some groups concepts or anything outside of dsa is not required for google right i could see a lot of questions on this as well like do we need to prepare for anything apart from dsa so i think you answered it like master dsa well and i think you're good to go uh from where we can apply monsieur's aspect for the various openings that you mentioned oh so you have to you have to actually get a referral because just by application your cv will not be picked up because so many people have actually applied for google through referral that that hrs are just busy with the referral handling the reference there are too many reference and also hr are like looking out for some experienced people if you are experienced you have a high chance if you have less experience then actually you will have to take a referral for sure or you can you can actually ping to a recruiter recruiters inboxes are also pretty much full with hundreds of pending messages so they are not able to read it i am sure about that so try to try to connect with an employee because an employee referral will be a very easy one and i think that is your best chance to actually get an interview scheduled right then avinash has asked that is lead code sufficient for google yes i would say lead code is more than sufficient for any company even even if you are a competitive programmer you will come back to lead code before appearing for the interview just to tune yourself with the with the type of questions there they are asking so that you don't overfill the interview question because if you do an overkill again you will get rejected because something which the interviewer is not expecting if you answered that you will not get selected for sure right okay i think i tried to cover most of the questions okay uh people are asking do we get the feedback like if we are rejected uh do we get the feedback afterwards or more yeah you get feedback after each round so it is not like the other companies you don't get a feedback you always get up back the recruiters are very humble very good so you can always call them connect with them they will always help you with what you should do what you should not do and how was your last interview what do the interviewer think about you and what is your negative point what is your positive point and where should you improve what you should not repeat the next round every feedback you will get after each round so you can always connect recruiter yeah i think i think it is a very good point like like we get a chance to improve ourselves and work on our weaknesses and even if you're not getting a feedback directly you can always reach out to the recruiter as you already mentioned by your own and then you can ask for the feedback from him yes so talking about the projects we have already discussed the projects in just one second uh yes we have already discussed about the projects maybe you can watch the video afterwards we discuss what projects should we work on and like about those [Music] okay then is asked is the essay most important to appear in any interview or like should we prepare for anything apart from dsa as well i think we discussed this also like as i mentioned very very company specific so for google only dsa if you have less than 5 years experience and appearing till l4 then only dsa if you appear any anything above l4 and with experience 5 plus years then with the design as well right also people asking how do we get referral i think linkedin is the most appropriate answer you can try reaching out to your seniors or linkedin and from there if you have someone you know already or some of your seniors you you will have a best chance to actually get a referral but i have seen that people generally do not reply to your queries people are also not very active on on linkedin whoever works in google so you have you may have to reach out let's say 30 to 50 people and uh then you might get one referral but before i mean people are just reluctant to refer even i am reluctant to refer because i have referred like 10 plus guys and nobody actually cleared so it is a negative against against my referring capability as well so i cannot refer anybody whom i do not know because if they have done well like into my batches who have done well i have referred them but still they got out but they had they had their chances but somebody and i i do not know whatever they have written in their cv i do not know if it is hundred percent right correct or whatever they are referring to is correct i mean i i would like to refer why not any employee will would like to refer if you are good because we also get our share if you if you crack it so why not i would like to refer but if you have if you have something to showcase like a good rating that is where it helps that if you have setting but if you know somebody you you do not require any rating because i have referred my friends who do not have any rating they do not have any chance of cracking it but still they are my friends so that's why i prefer them so if you can just find somebody who is your friend or your senior they will refer to you but if you are good in coding and you have something to showcase then you can actually reach out you can also reach out to me if you want but you but since i don't know you i will judge you based on your rating which i should not do actually but still yeah i think that is the only way you can tell with like how good a person is at coding right like there's no other means people who are doing uh competitive programming or doing lead code uh contest they they they must be having some ratings to showcase and uh recruiter actually doesn't understand what ratings you have they are generally from uh commerce background non-technical background whatever you write five-star four-star three-star stuff in your linkedin doesn't matter nobody understand that those who hire do not understand those who don't have their they understand so i just ask these people who are you showing off these ratings too so actually my recruiter who who had come she didn't understand what this three-star four-star is and and does the mo star means something else so i told her that no it is it is nothing so i mean people don't understand this that the most credible thing why they are writing is to showcase the recruiter but the recruiters are non-technical and they don't understand it so only only we are the guys who understands so i mean it is not helpful even if you write it so this is helpful to get a referral from somebody you do not know and he doesn't know you like i don't know you so i will i will judge you based on your ratings or something i mean that is the only criteria which i can do right i mean it is not a correct criteria actually people do not have any rating still that they are selected even i am selected without having any rating but but still i mean it is the only criteria i mean how i can judge you right yeah also people if like they're asking if i don't do competitive programming then what maybe you can share your lead code profile like like the questions you have solved and everything and that's how people can know that yeah i think i think you actually do not need to do anything apart from lead code so i will suggest that you if you have a premium account you just solve the most frequent question if you do not have the premium account you solve the last 50 questions uh from all the companies like the top 10 company we will end up doing like 300 to 400 questions that is more than enough apart from that you just keep doing every birthday and weekly test and try to solve maximum of three questions even the fourth question is not required to be done and this is how you can crack any company nothing else is required so i i don't see i mean it is not a big deal to actually crack any company so you should be actually consistent for like three to four months that is the only consistency that is what i keep telling people that you should not get demotivated if you are consistent solve two to three questions every day that is good enough for just three to four months consistency you will see that you have solved around 250 problems and uh that is so one of my friend on linkedin you will see him as sorrow and he is also in in google l4 he has solved total of 188 lead code questions only 188 in in his life and he also got selected because i told him that you you just need to do these many questions you don't need to do thousand questions right so and even one of my friend thousand plus questions got rejected in the screening round so it doesn't make sense to actually do a lot of question but to be aware about the recent trends and actually keep in touch right so take a small target try to give up on your luxuries for some time i try to work for two three months and then once you are good enough you can keep up that pace of practicing like one or two question every day once you are good enough and then you can like start appearing for the interviews so i'll suggest consistency is the key to getting selected this is the key and actually people cannot give up on their luxuries for too long people think that i will prepare for six months i will prepare for one year but when you start preparing you will you will feel the pain and when you start thinking in your head that this pain has to last for six months or one year and that is where you get motivated and actually you cannot do anything so i will say that once if you are giving up giving up on your uh luxuries then actually you cannot give it so you should always uh take a short target of completing something so i think for tracking any interview you do not need more than three months so i mean yeah three months is something which where you can like not watch netflix not go on tours uh i mean don't spend too much time with with your friends and still you will be kind of okay in three months but if you if you are beyond three months you will get restless and you will feel that just get it done somehow i just want to get rid of this in having preparation part that is where it hits right yes like being consistent is i know like i i tried to be consistent for two to three months while i was preparing for my company so yeah i know the pain it's really easy you cannot be consistent for a year you can be consistent for three months so that is what we keep telling everyone very very few people actually are able to do and be consistent even if you talk about solving one question per day being consistent for one year is extremely difficult but if you if i tell you that you you do three to four questions per day three questions per day and for three months you do the same number of questions and you will be consistent it will be less painful than doing it one question every day for one year for one yeah yes definitely so guys try to be as consistent as possible and like not just for one week but for at least two to three months and then definitely i think you can crack any company that you want right so we have covered i think most of the questions that were there so now lastly i would like to thank you for coming to geeksforgeeks and sharing about your experience i hope it helps a lot of students who are you know planning to give interview in companies thank you so much yeah and i would also also like to ask people uh i mean i can refer some of you guys who have good rating actually so they can actually come and share their profile on to my linkedin message possibly i might pick some of you and refer you guys as well if you have good rating obviously i'm i will be a critic there so if you don't have anything to showcase then i mean i cannot refer actually but still if you have if you know if you are very good in dsa and you are actually not finding somebody to refer then you can always reach out to me either on watson or on linkedin anywhere or even on we'll put the instagram to your social media and there's everything in the description box below in case you guys want to reach out yeah yes so thank you so much with this weekend and the webinar thank you once again okay yeah thank you for having me thank you bye thank you thank you bye yes lastly thank you guys for joining i could see that there were around 140 to 150 people consistently from the start of the webinar so thank you so much for joining and as i already mentioned i will put the link to his social media handles in the description box below you guys can reach out to him and ask any other questions if we missed out in the webinar thank you