注册一亩三分地论坛,查看更多干货!
您需要 登录 才可以下载或查看附件。没有帐号?注册账号
x
昨天和GOOGLE的HR聊了下 然后这个HR给了我好多准备面试的材料 给大家分享下 希望对大家有帮助
Here are a few tips for interviewing with Google as well as some links to check out:
The interviewer(s) will be interested in the specifics of your past projects, implementations and how you arrived at your conclusions. The name of this game is Interaction!!
We strongly encourage you to review the following videos. The videos feature Googlers who have been both interviewers and interviewees sharing their unique perspective on how to prepare for Google's technical interviews! The principles are applicable to a technical phone interview as well.
:
Review your resume and be prepare to discuss your experiences and past projects! Often times it will help drive the discussion and gives you an opportunity to share situations where you solved a complex problem.
Your background is important, so utilize it to your advantage by sharing interesting points that can help you and the engineer work through the discussion as efficient as possible.
1.) Algorithm Complexity: You need to know Big-O. If you struggle with basic big-O complexity analysis, then you are almost guaranteed not to get hired. For more information on Algorithms you can visit:
2.) Coding: You will be expected to write some code in at least some of your interviews. You will be expected to know a fair amount of detail about your favorite programming language. well as your approach to problems and solutions. Ask specific questions if you need more clarification. Our engineers are not looking for the right answer, but the right approach and methods of thinking, within relevance, say EVERYTHING you are thinking!!
As you prepare, build toward thinking about ways to improve the solution you'll present. In many cases, the first answer that springs to mind may need some refining. It is worthwhile to talk about your initial thoughts to a question. A brute force explanation will be received less well than taking time to compose a more efficient solution. Ask clarifying questions if you do not understand the problem or need more information. Many of the questions asked in Google interviews are deliberately underspecified because our engineers are looking to see how you engage the problem. In particular, they are looking to see which areas leap to your mind as the most important piece of the technological puzzle you've been presented.
Also, one of our senior engineers has recommended candidates read Programming Interviews Exposed: Secrets to Landing Your Next Job by John Mongan and Noah Suojanen to give you an edge. It's a good book to have in general. Two other books that may be helpful are: "Programming Pearls" by Jon Bentley - Programming questions that get you thinking outside of the box; and lastly, "Cormen/Leiserson/Rivest/Stein: Introduction to Algorithms" or the CLR textbook.
|