Design an in-memory online url-shortening system, specifically database layout and necessary hardware. Scale to 1 university (50K users). Followups: - SQL specifics - Estimate message and request sizes - scale to 1 million users - "what about locality?" --> route & shard requests depending on user location
Based on String manipulation (not meant to reveal the specific questions as requested by Google). I spend a lot of time revising tree's and search/sorting algorithms, but tripped up on some relatively straight forward String manipulation questions. I have time for 1 and a half questions, the first one being simple and the second requiring a new solution to a more complex version of the same problem. The interviewer was fairly friendly and they will hint at you when you make mistakes, and look at how you go through to error check your code. In general this was a really nice interview process even though I messed up my question. My main advice would be to do a lot of practise on coding without an IDE, and problem solving questions. The recruiter within google will send you a bunch of great revision materials, and using this is definitely more than enough to be prepared.
Search
General questions. What do you do when you have conflict with a colleague, what are your strength/weaknesses etc
What are the advantages and disadvantages of using streams?
Have you worked with distributed systems before?
What are your strengths and weaknesses?
Classes, Inheritance, Data structures, previous project/work experience
Q: Scenario based Questions
They walked through your codility assessment with you. Fairly relaxed interview, all other questions were related to past project experience and behavioural questions.
Viewing 2491 - 2500 interview questions