loading...
Cover image for Google India — Phone Call Interview Question (Software Developer)

Google India — Phone Call Interview Question (Software Developer)

dg92 profile image Deepak Gupta Originally published at Medium ・2 min read

Before I tell the question, for which you are here, this interview was for a software developer position and mostly working around javascript.

Note: I am still in the process of interviews so not sure if I will able to make it to a face to face interview 🤞, Wish me luck.

The interview lasts for 25 min on a phone call out of which 2–3 min were taken by the interview to explain the responsibilities of the role and later she asked around 12 questions which were a mix of my resume, basic data structure, algorithm, and analytics.

Note: I write articles around javascript concept, Nodejs, React, React-native, GraphQl, System Architecture — @ http://overflowjs.com
Feel free to check out and improve on your skills or comment to cover any topic of your choice.

So, let’s start 👇

  1. Tell me about yourself?
  2. What technologies you have worked on?
  3. Why I switched so frequently in the past 3 years?
  4. Have you done any system design from scratch?
  5. Worst case scenario of quicksort and when will worst case occurs?
  6. Worst case scenario of merge sort and when it will occur?
  7. Which is faster quicksort or merge sort, when and why?
  8. What are Hash tables and how is it different from a dictionary?
  9. What is a balanced binary search tree? Why they are called balanced?
  10. In javascript, the resolution is done by value or by reference and why?
  11. How will you solve or approach to problem 2 raise to power 24?
  12. Any question for me?

Note: Comment down below if you want to me write the answer to these question👇

At last, she told me to wait for a week as she will pass on the answer to the team and will revert back with the feedback.

Hope the above question help someone looking out for some idea around the Google phone call interview question.

Happy Coding ❤️

Posted on by:

Discussion

markdown guide