1) Focus on practice - Make sure to solve a variety of easy to medium level questions before the screening. 2) Practice coding on Google Docs 3) While practising, make sure you think about all corner cases and cover them in your solution in the first iteration. Do not keep submitting the code, and then covering the cases failing iteratively. 4) While screening, try to cover all these: collecting all the details, discussing approach, writing clean code, writing unit tests.
@@turningturing9217 they skipped my phone screen. I'll be having 2 on sites, one domain specific and one Googlyness round. I provided a tentative date of 6 Nov and recruiter agreed.
could you please help me out like in single round of interview how many question were asked. like only 45 min assigned 2 question and theier respective followup questions?
Yes, one round is always 45 minutes. The number of questions varied for me in different rounds. In one of the rounds, I only got a single question, while in some I had to answer followups.
Hi , which IDE you used in interview and is there any default test cases like leet code ? Before submitting answer , can we run the code (like in leet code ) ?
There is no IDE, you have to code on Google docs. They try to simulate the white board coding experience. There are no default cases, you have to think all the test cases and do a dry run yourself. Make sure that you cover some basic happy cases and all the corner cases.
Does taking a long time between the recruiter call and the first interview affect the chances of getting selected ? Like the position getting filled or getting lesser preference than other candidates ?
Mostly hiring in Google is not done for specific projects, you will be hired for a role and then matched with a project after the interviews. Since, new projects and openings keep coming up, you will most likely find a match even later. Taking time for preparation does not impact the feedback, in my opinion you should never go underprepared.
@@turningturing9217 I may have made a mistake then : ) ; I thought that since I was approached by them it was likely that there is some kind of hiring push going on, so taking too long would decrease the chances (as roles might get filled faster). Another reason was that if I took 2 months, my prep would have been slower and I would have got diminishing return. Anyways, thanks for these videos. I am aiming to get v. good at medium questions and thinking clearly and through before coding so that I can take help of the interviewer in hard questions when stuck
I have a screening round scheduled for Google L4 SWE role on 29th July. Any tips that you can give as to how to prepare?
1) Focus on practice - Make sure to solve a variety of easy to medium level questions before the screening.
2) Practice coding on Google Docs
3) While practising, make sure you think about all corner cases and cover them in your solution in the first iteration. Do not keep submitting the code, and then covering the cases failing iteratively.
4) While screening, try to cover all these: collecting all the details, discussing approach, writing clean code, writing unit tests.
@@turningturing9217 Thanks for the tips! I cleared my screening round! Any tips for the on-sites?
@@turningturing9217 Thanks for the tips! I cleared my screening round! Any tips for the on-sites now?
@@turningturing9217 should I follow the same tips for the on-sites as well?
Hey, what was the verdict?
Scheduled my first interview after 3 months. I am shitting bricks rn
When is your first interview?
@@turningturing9217 they skipped my phone screen. I'll be having 2 on sites, one domain specific and one Googlyness round. I provided a tentative date of 6 Nov and recruiter agreed.
Great! all the best. There are generally 3 tech and 1 googlyness.
could you please help me out like in single round of interview how many question were asked. like only 45 min assigned 2 question and theier respective followup questions?
Yes, one round is always 45 minutes. The number of questions varied for me in different rounds. In one of the rounds, I only got a single question, while in some I had to answer followups.
Number of questions in a round depends on the difficulty of the questions.
very nice explaination bro, your linked in Id?
www.linkedin.com/in/siddharth-s-41953b112
Hi , which IDE you used in interview and is there any default test cases like leet code ? Before submitting answer , can we run the code (like in leet code ) ?
There is no IDE, you have to code on Google docs. They try to simulate the white board coding experience. There are no default cases, you have to think all the test cases and do a dry run yourself. Make sure that you cover some basic happy cases and all the corner cases.
Does taking a long time between the recruiter call and the first interview affect the chances of getting selected ? Like the position getting filled or getting lesser preference than other candidates ?
Mostly hiring in Google is not done for specific projects, you will be hired for a role and then matched with a project after the interviews. Since, new projects and openings keep coming up, you will most likely find a match even later.
Taking time for preparation does not impact the feedback, in my opinion you should never go underprepared.
@@turningturing9217 I may have made a mistake then : ) ; I thought that since I was approached by them it was likely that there is some kind of hiring push going on, so taking too long would decrease the chances (as roles might get filled faster). Another reason was that if I took 2 months, my prep would have been slower and I would have got diminishing return. Anyways, thanks for these videos. I am aiming to get v. good at medium questions and thinking clearly and through before coding so that I can take help of the interviewer in hard questions when stuck
Hi,
How much experience required for this position?
3 YOE is the ideal case, but you can try with 2 YOE as well.
@@turningturing9217 actually i am from service based company and i graduate with bcom so can I eligible
I am not sure, you would have to ask the specific recruiter.
Tumi bangali?
না