A: Each office works on full-cycle projects and teams often collaborate with teams in other offices. For specifics, visit our city-specific jobs websites to learn more. Project assignments are determined close to start date, using your input on what you'd like to work on along with the needs of the different engineering projects. Our interview process evaluates your core software engineering skills: coding, algorithm development, data structures, design patterns, analytical thinking skills. If you are a strong software engineer, you can potentially work on a number of different Google Engineering projects.
A: Please take a look at our Corporate Company Profile for the official numbers. The number of employees from our individual locations varies and is not disclosed in the interest of privacy.
A: Our Product Managers are very technical, and have years of software engineering and coding experience. If you are interested in both roles and also have a passion for forward-thinking product development, we welcome you to speak with a recruiter about the role that fits you the best.
A: We encourage individuals to meet their full potential. If that involves a PhD for an individual then we encourage that, but we have roles for graduates at every level.
A: Google takes an innovative approach to career progression, putting career development in the hands of the individual. That said, we do have Managers, structured review processes, and offer educational resources and other opportunities for you to shape your future. It’s a place where you can get the guidance you want, and avoid the hierarchical structure that you don’t need in order to do your job well.
A: It varies depending on the role and the office. We can’t promise you an offer next week but if you have a competing offer and need to make a quick decision, please let your recruiter know and they will do what they can to make sure you have the information you need in order to make a decision.
A: You should expect to spend most of the time answering technical questions that could range from designing algorithms and systems, possibly tackling puzzles, and demonstrating your thinking about how you solve technical problems.
A: Visit our Google corporate website, and get familiar with our products and the papers we have published. Explore problem solving questions and algorithm questions to get your mind ready for the exercise. It’s important for you to think out loud during the interview, so, if you’re not used to it, practice thinking out loud. Relax, get a good night’s sleep and arrive on time!
A: You will meet Software Engineers with different backgrounds and levels of experience who will test your technical capabilities for the role. This is likely to be complex and interactive. You should expect to write code on a white-board and express your knowledge and inventiveness in detail.
A: Individual interviews usually take between 30 minutes to an hour and you may have up to 4 in one day, with breaks, of course.
A: That's a great idea – let your recruiter know who it is and if he or she is available, we will set it up for you.
A: Your recruiter will follow up with you and explain the next steps.
A: Once you’ve had initial contact, your recruiter will be in constant contact with you. If you have not heard from him or her in a few days, please feel free to initiate contact yourself.
A: We don’t know exactly which project you will work on yet since everything at Google moves and changes quickly. It’s essential to be flexible and adaptable, but rest assured we will consider your background, interests, and skills when choosing your project and team. Your team will enable you to get up to speed and settle in – likely with a small starter project.
A: The amount of travel is largely determined by you in conjunction with your manager. Travel for training purposes might be necessary; for example, Engineers placed in our Norway office spend 2 weeks training in a larger office. In addition, if you are working with a team in a different office then travel may be necessary.