發表時間:2012-11-16-上午 9:55 | 評論:320條新浪微博 149條騰訊微博
【搜狐IT消息】11月15日消息，谷歌公司的面試題在刁鑽古怪方面相當出名，科技博客BusinessInsider貼出了15道谷歌面試題，並一一給出了答案。
第一題：多少只高爾夫球才能填滿一輛校車？（職位：產品經理）
解析：通過這道題，谷歌希望測試出求職者是否有能力判斷出解決問題的關鍵。
網友的答案：我想，一輛標準大小的校車約有8英尺寬、6英尺高、20英尺長——我能知道這些數字完全是因為我曾經無數次被堵在校車後面。
據此估算，一輛校車的容積約為960立方英尺，也就是160萬立方英寸。一個高爾夫球的半徑約為0.85英寸，我認為一個高爾夫球的體積約為2.6立方英寸。
用校車的容積除以高爾夫球的體積，得到的結果是66萬。不過，由於校車裏面還有座位等等各種東西，而且高爾夫球的形狀使得不同的球之間會有不少空隙。我的最終估算結果是50萬。這聽起來有些荒唐。如果我直接猜的話，我給出的答案肯定是10萬以下，不過我相信我的數學水準。
當然，如果這裏的校車是小布希當年坐過的那種，結果還要除以2，差不多是25萬個。
第二題：讓你清洗西雅圖所有的玻璃窗，你的報價是多少？（職位：產品經理）
答案：這一題我們可以玩點花招，我們的答案是“每扇窗10美元”。
第三題：有一個人們只想生男孩子的國家，他們在有兒子之前都會繼續生育。如果第一胎是女兒，他們就會繼續生育直到有一個兒子。這個國家的男女兒童比例是多少？（職位：產品經理）
答案：這一題引發了不少爭議，不過我們發現，這一題的解答步驟如下：
1、假設一共用10對夫妻，每對夫妻有一個孩子，男女比例相等。（共有10個孩子，5男5女）；
2、生女孩的5對夫妻又生了5個孩子，男女比例相等。（共有15個孩子，男女兒童都是7.5個）；
3、生女孩的2.5對夫妻又生了2.5個孩子，男女比例相等。（共有17.5個孩子，男女兒童都是8.75個）；
4、因此，男女比例是1:1。
第四題：全世界共有多少名鋼琴調音師？（職位：產品經理）
答案：我們的回答是“要看市場情況。如果鋼琴需要每週調音一次，每次調音需要1個小時，且每個調音師每週工作40個小時。我們認為每40台鋼琴就需要一名調音師。”
這個問題又被稱為“費米問題”（Fermi problem）。費米提出的問題是“在芝加哥有多少鋼琴調音師”。一個典型的答案是包括一系列估算資料的乘法。如果估計正確，就能得到正確答案。比如我們採用如下假設：
芝加哥約有500萬人居住；
平均每個家庭有2人；
大約有1/20的家庭有定期調音的鋼琴；
平均每台鋼琴每年調音一次；
每個調音師調整一台鋼琴需要2小時；
每個調音師每天工作8小時、每週5天、每年50周。
通過這些假設我們可以計算出每年在芝加哥需要調音的鋼琴數量是：
(芝加哥的500萬人口)/(2人/家)×(1架鋼琴/20家)×(1架鋼琴調整/1年)=125000
平均每個調音師每年能調整的鋼琴數量是：
(50周/年)×(5天/周)×(8小時/天)/(1架鋼琴/2小時)=1000
芝加哥的調音師數量是：
(芝加哥需要調音的鋼琴數量125,000)/(每個調音師每年能調整的鋼琴數量1000)=125
第五題：馬路上的井蓋為什麼是圓的？（職位：軟體工程師）
答案：圓形的井蓋在任何角度都不會掉下去。
第六題：為三藩市 (San Francisco) 設計一個緊急撤離方案（職位：產品經理）
答案：這又是一個考察求職者是否能夠發現問題核心的題目。我們在回答之前首先要問的是，“撤離方案應對的是什麼樣的災難”。
第七題：一天之中，時鐘的時針和分針會重合幾次？（職位：產品經理）
答案：22次。
重合的時間點分別是：上午，12:00、1:05、2:11、3:16、4:22、5:27、6:33、7:38、8:44、9:49、10:55；下午12:00、1:05、2:11、3:16、4:22、5:27、6:33、7:38、8:44、9:49、10:55。
第八題：請闡述 “Dead beef” 的意義。（職位：軟體工程師）
答案：網友給出的正確答案是，在大型機和組合語言的時代，“DEADBEEF”是調試電腦時所使用的一個十六進位值，以便於在大量的十六進位中斷資訊中標記和查找特定的記憶體資料。大多數電腦科學專業畢業生都應該會在組合語言的課程上見過這個概念。
第九題：有人把車停在旅館外，丟失了他的財物，他接下來會幹什麼？（職位：軟體工程師）
答案：下車踏到人行道上。
第十題：你需要確認朋友鮑勃是否有你正確的電話號碼，但不能直接問他。你須在一張卡片上寫下這個問題，然後交給愛娃，由愛娃把卡片交給鮑勃，再轉告你答案。除了在卡片上寫下這個問題外，你還必須怎樣寫，才能確保鮑勃在給出答案的同時，不讓愛娃知道你的電話號碼？（職位：軟體工程師）
答案：既然只需要核對鮑勃手中的號碼是否正確，你只需要讓他在某個特定的時刻給你打電話，如果他沒打過來的話，就能確認他沒有你的號碼。
第十一題：假設你是海盜船的船長，船員們即將對黃金的分配方案投票。如果贊成票不到半數的話，你會被殺死。你怎樣才能在保證自己存活的情況下拿到最多的黃金？（職位：軟體工程師）
答案：將黃金平均分給最有權勢的51%的船員。
第十二題：有八個大小相等的球，其中有一個重量比其他球略重。如何在只用天平稱兩次的情況下找出那個不一樣的球？（職位：產品經理）
答案：從八個球中取出六個，在天平兩邊各放三個。如果平衡，把剩下的兩個球分別放在天平兩邊，就能找出較重的球。如果不平衡，較重的球就在天平下沉的一邊，從這三個當中取出兩個稱量，若不平衡，下沉的一邊較重，若平衡，剩下的就是較重的球。
第十三題：你拿著兩個雞蛋站在100層的大樓上。雞蛋或許結實到從樓頂掉下也不會摔破，或許很易碎，在一樓摔下就破碎。最少試驗多少次可以找出雞蛋不會被摔碎的最高樓層？（職位：產品經理）
答案：14次。從14樓丟下第一顆雞蛋，如果破碎了就逐層往下試驗，共需14次。如果沒有破碎，往上走13層；在27樓第二次丟下第一顆雞蛋，如果碎了，換第二顆雞蛋往上走12層測試，若仍沒碎，往上走12層試驗第一顆雞蛋；以此類推，直到走到第99層。如果雞蛋要到100層高度落下才會破碎，總共需要14次嘗試。
第十四題：如果用三句話向你8歲大的侄子解釋什麼叫資料庫？（職位：產品經理）
答案：這一題考察的是求職者用簡單的語言闡述複雜概念的能力。我們的答案是“資料庫是一個能夠記住關於很多東西的很多資訊的機器。人們用它來幫助記住這些資訊。出去玩吧。”
第十五題：你被縮小到只有硬幣厚度那麼點高，然後被扔到一個空的玻璃攪拌機中，刀片一分鐘後就開始轉動。你會怎麼做？（職位：產品經理）
答案：這一題考察的是求職者的創造性。我們會嘗試把電動機弄壞。
Google Interview Questions & Reviews
( http://www.glassdoor.com/Interview/Google-Interview-Questions-E9079.htm )
Software Engineer In Test at Google (測試方面的軟體工程師)
Accepted Offer – Interviewed in Mountain View, CA Sep 2012 – Reviewed Oct 22, 2012
Interview Details – I had previously interviewed with Google during my final year as a Computer Science Engineering undergraduate student. I didn't get an offer, but the recruiter said that it was a close call and that she would follow up with me after two years once I had more experience. I joined Microsoft right out of college instead.
Exactly two years later (literally same day/month), a new recruiter followed up and I began the interview process again. A week later, I had a phone screen. After 4 days, the recruiter informed me that I passed and could move on to the on-campus interviews. I was assigned a new recruiter. Two weeks later, I flew out and had a total of 5 interviews at Google's headquarters in Mountain View, CA. Two weeks later, the recruiter informed me that I passed the hiring committee. One week after that, the recruiter informed me that I had passed the final executive review and I was provided offer details. In general, the recruiter was polite and knowledgeable, though late to call me on a few occasions when we had chats scheduled. Also, the recruiter began discussing relocation and job perks, as if I had the job, before an offer had been extended (after approval by the hiring committee, but before executive review). It sounds as though a fair number of candidates are rejected at this stage, and as such I feel this was somewhat inappropriate.
I found the on-campus interviews to be very academic-slanted. Though I had only been working in industry for one year, I expected more focus on what I had learned and accomplished there, rather than my knowledge of algorithms and data structures (most of which I hadn't touched since graduating from college). I don't know whether I will use these algorithms much in my day-to-day work, but I feel as though I am qualified for the job because of how I approach real-world software engineering problems, not my knowledge of algorithms and data structures.
My first on-campus interviewer was about 15 minutes late, but he had a sufficiently geeky excuse and I wasn't annoyed. Although some may find this lack of "professionalism" frustrating, I didn't mind, and he turned out to be my favorite interviewer.
A couple of the interviewers asked me to implement (in full or in part) algorithms to solve board games/strategy games. Think of the category of games that use a board with a grid of values, where solving the game consists of putting the right values onto the grid, or extracting knowledge from the existing grid arrangement -- this is what I'm talking about. Per my NDA I won't get into specifics. These questions were very in-depth and it took the majority of the time for me to come up with solution (or a sufficiently-developed line of thinking that would lead to a solution). In each case, my solution was incomplete or had minor errors/inefficiencies that the interviewers called me out for. I then used the interviewers' hints to refine the solution.
Another interviewer proposed a hypothetical product (a web application, with some sort of user interface, some amount of business logic, and a database backend, with a set of interesting scalability features) and asked me to talk through the process of testing it. This was an open-ended question which I enjoyed very much -- I felt like I was able to demonstrate my breadth of testing knowledge by touching on a number of potential test angles, and I went into detail on the ones that the interviewer found interesting.
Another interviewer asked me to design and implement a data structure that had constant-time performance for two specific operations. The constraints weren't satisfiable by any single simple data structure -- the solution involved a hybrid of two different ones. I believe this type of question is common at Google -- I had a very similar question (though with different data structures) two years earlier. I talked through the problem with the interviewer and, with a few hints, arrived at the correct solution and implemented it.
I didn't deliver perfect answers to any of the problems. I think I received an offer because I was able to talk through what I was thinking and doing as I was doing it. This allowed the interviewers to follow along, ask clarifying questions, and get me back on the right track when I made a mistake. I was able to demonstrate that I'm a competent programmer and pleasant to work with, even though I'm not an algorithm or data structure rockstar. I believe that better programmers than me get rejected because the interviewers are only able to evaluate their raw technical competency, rather than their people skills or problem solving process. If you are able to converse freely with them, as if you were tackling the problem with coworkers, they will feel much more comfortable overlooking minor technical flaws in your answer.
Best of luck, and hopefully I'll see you inside! :)
Negotiation Details – I didn't negotiate. With only one year of industry experience, the offer provided was slightly higher than a new college graduate offer, which is acceptable since I'll be learning an entirely new technology stack after working at Microsoft for a year, and therefore I consider myself to be a "new college graduate"-caliber hire.
Account Strategist at Google (會計策略長)
Accepted Offer – Interviewed in Dublin, Dublin (Ireland) Oct 2012 – Reviewed 2 weeks ago
Interview Details – Was invited to an on-Campus interview at a Career fair at my University
1. Interview (On-Campus) 30mins. with recruiter (only personal fit questions)
Extremely positive experience, probably the most relaxed interview I have ever been in (coming from Management Consulting I've been through quite a few).
Recruiter explicitly made an effort to "just have a little chat about life at Google" and the specific role as Account Strategist.(Though I didn't buy too much into the "just relax" atmosphere and tried to stay focused on the inside)
Q1: Why Google?
Q2: What qualities would you bring to the team?
Q3: What are your mid/long-term professional expectations?
Q5: Could you imagine working & living in Dublin?
Q6: How do you deal with a high-pressure working environment? Additionally a couple of specific questions about my CV, what I did in different jobs/internships etc...
Again: very open conversation, she also told me a lot about life at Google in general and seemed very enthusiastic and endowed with a positive-attitude which actually motivated me even more, as I initially was a bit skeptical about the position. As our conversation was very pleasant, she invited me to an on-site interview right on the spot for the upcoming week.
Called me next day, confirmed invitation to on-site interview and forwarded me all details I needed to know via mail.
7 working days after initial contact, arrived in Dublin, 3 hours time between arrival and beginning of interviews. Was greeted by the recruiter who had invited me who briefly showed me around the building and once again made a big effort to make the experience as pleasant as possible.
Interview with two people: AdWords Manager & one recent hire: (40mins)
(The manager asked all the questions, while the staff member only listened and took notes)
Q1: Walk me through your CV, highlighting the most impt. and relevant points!
Q2: What brings you here today, why do you want this job?
Q3: What kind of expectations do you have of this job and where do you see yourself in 10 years (I hate this question, how should I know?)
Q4: Scenario: online shoe retailer, repair & service wants to increase e-commerce and repair services, what advice would you provide?
Q5: How would you convince a small business owner to invest into online marketing? Why should he/she use AdWords? What other solutions from Google's product range could be offered? (Mock sales pitch)
Q6: Say you have a customer portfolio of 3000 individual customers, how would you prioritize your tasks?
Q7: We have many excellent people applying, what makes you stand out? Why should we want you on the team?
2. Interview with one person: Sales Manager (35 mins)
Q1: Do you want something to drink?
Q2: Do you want to ask questions first, or do you want to go through a couple of my questions and then ask me questions?
Q3: First Scenario: You just bought 10000 Tablet computers in Taiwan and shipped them to (insert any European country). You want to get rid of them asap via online sales using AdWords - determine CPC! (Walk me through the process on the white board, providing numerical examples)
Q4: A customer complains about diminishing ROI in online sales, determine possible causes and provide solutions respectively.
Q5: Provide 5 examples of how you would decrease CPC as a business owner.
Q6: Within one week online sales have suddenly decreased more than 50%, why? What are possible causes?
Q7: Can you imagine working on problems similar to the ones above on a daily basis? Would you enjoy this?
3. Interview with two people: Team-Lead & another recent hire (45 mins)
Again many standard personal fit questions, very detailed questions regarding CV, past time challenges, leadership and conflict situations at work.
4. Next working day, call from recruiter updating me that I had passed. Informed me about the next steps (Hiring Committee) and provided - to my surprise - already all details about the employment package. At this point I found this a little early, as it made the impression that I had already received an offer - even though my data still had to go through the hiring & exec. committees’ review process. Additionally asked me about any other offers I may currently have and what they were.
Sent in all my additional info requested by the HC (basically they ask you to spell out major achievements, providing references and transcripts)
Received call + offer after 7 additional working days.
Time from first interview to job-offer: just 14 working days!
Overall a very fair interview process and positive experience. Extremely good communications with the recruiter in charge ( kept me in the loop all the time) and overall a very straight forward and efficient process.
(And in case you wonder, I directly wrote down all questions as soon as I had finished the interviews)
Interview Question – You just bought 10000 Tablet computers in Taiwan and shipped them to (insert any European country). You want to get rid of them asap via online sales using AdWords - determine CPC! (Walk me through the process on the white board, providing numerical examples) Answer Question
Senior Business Analyst at Google (高級商業分析師)
Accepted Offer – Interviewed in Mountain View, CA Jun 2012 – Reviewed last week New
Interview Details – Recruiters are effective. Get an interview via employee referral, you at least get a recruiter call. I was rejected for an initial phone screen based on fit but the recruiter passed me on to another recruiter in another area and that was a better fit.
Process is slightly slow due to the hiring committee and Comp committee involvement. Google (currently) can afford (may seem) to be arrogant in not negotiating but the fact is that recruiters and hiring managers have little leverage. The secret to negotiate at Google is to have a competing offer from a company that they care.
Interviews are not as scary as some reviews put them out to be. The bar for hiring is lower in the non-engineering is my guess (without specific knowledge). They are looking for smart folks, pedigree seems to count, all my peers are from top universities like harvard, stanford, and top european, chinese and indian schools.
Interview Question – Case question ... Profits = Revenue - costs. Look up any case interview prep. Be ready for adwords questions. Set up an ad words account and learn about product features. Answer Question
Negotiation Details – Google (currently) can afford (may seem) to be arrogant in not negotiating but the fact is that recruiters and hiring managers have little leverage. The secret to negotiate at Google is to have a competing offer from a company that they care.
Software Engineer - New Grad at Google (軟體工程師, 大學剛畢業的)
No Offer – Interviewed in Irvine, CA Sep 2012 – Reviewed Oct 6, 2012
Interview Details – I applied for google's new grad position that is available on Sep 1. They contacted me a few weeks later to set up a phone interview.
They gave me a list of categories to choose from (that I specialize in). Here were the choices: (choose 3)
* Advanced Algorithms
* Audio/video
* Billing/payment testing
* Compilers and software tools (linkers, debuggers, IDEs, etc.)
* Computer vision
* Concurrency, multi-threading, synchronization
* Database internals
* Distributed systems
* Embedded software and real-time systems
* Front end
* Graphics and imaging
* Information retrieval and data mining
* Internationalization
* Load and performance testing
* Mac and iPhone development
* Machine learning and AI
* Natural language processing
* Networking (TCP/IP and OSI stack)
* Object-oriented analysis and design
* Operating systems
* Production Systems
* Project Management
* QA
* Security and cryptography
* System administration
* Test automation
* UI design and implementation
* Web applications and multi-tiered systems
* Windows development
* Wireless applications
They also wanted you to choose your top 3 languages.
*********************PHONE INTERVIEW QUESTIONS:*****************************
BASED ON WHAT YOU CHOSE, they will ask you to know certain things... I chose the software side, so my questions were focused on:
1.) Big-O and Algorithms
2.) C++, Java, C#
3.) System Design
4.) Sorting:
5.) Hashtables:
6.) Trees:
7.) Graphs:
9.) Discrete Math
10.) Operating Systems: processes, threads and concurrency issues. Know about locks and mutexes
BOOKS RECOMMENDED (by Google) :
1. Review of Basic Algorithms: Introduction to the Design and Analysis of Algorithms by Anany Levitin
2. Programming Interviews Exposed; Secrets to Landing Your Next Job (Programmer to Programmer) by John Mongan, Noah Suojanen, and Eric Giguere **HIGHLY RECOMMENDED**
Besides the questions listed below, they also asked:
--Which would be better for situation X, Merge Sort or Quick Sort?
Interview Questions
Write a function that finds the median of a set of three numbers, also find the Big O. Can it be done with only 2 comparisons, or do you need 3? View Answers (7)
If you had a savings account with $1, at a 100% interest rate, at what year would you have 15 billion dollars? View Answers (4)
When would you want to use a hash table over a binary search tree? What are the Big O's? View Answers (1)
What IS Big O? View Answers (2)
What happens if one resource is waiting on another resource to finish, but that SAME resource happens to be waiting on that other same resource.... View Answers (2)
Software Developer at Google (軟體開發師)
No Offer – Interviewed in Zürich (Switzerland) Oct 2012 – Reviewed 8 hours ago New
Interview Details – Incredibly professional. Started with 2 phone calls, trying to take as much detail from my professional life as possible. After the phone calls, they want to schedule technical phone interview, which I scheduled 7 weeks later ,not any problem for them at all, will consist of several technical programming questions. 1 week after, they want to schedule another technical interview, again technical programming questions, this time only one question regarding more complex question. At the end of the interview, the interviewer kindly thanked me for my patience and collaboration and told me they will call me back in a week and they did, telling me to come Zurich for an onsite interview which includes a travelling request form.
After filling out travel request form, they booked my plane and hotel and covered all of my expenses from until my interview time. They told me that I can book my plane departure any time I want but they will cover only one night's expenses which I was completely okay. So I arrived Zurich one night before my interview and went straight through my hotel. They thought everything. A dream like hotel, free wi-fi, one drink from hotel bar, relaxing music, a giant plasma tv with every possible input for you to plug in to your laptop if you want, fully automatic lights in the room, relaxing mints on top of the bed for a good nights sleep! It's like they are saying: We are not giving you any excuses, show us your best.
On-site interview consists of 5 separate interviews which are grouped as 3-2. Interviews are tough, I mean it's not like anything you one handed done on your phone interview. Each interview consists of 45 minute mind bending process with one employee and you will have 3-4 minute break between each interview. We have been to lunch after 3 interviews, cafeteria are great, facilities are already known for it's luxury. And then final 2 interviews. After the interviews they thanked me and told me that they will give me a response in 10 days.
The important part, Interview questions: I'm obligated to not give you the interview questions but I can describe you the concept. First, it's a little bit intimidating in the room, some interviewers doing kinda stress test during the interview. They give you a problem, a real world problem, with an easy overlay, and you derive a solution to it, by talking first, you can write some code if you want and you should want it. After that, they want you to improve it, what if there is 1 million entries on it? how much space will it take? What is the time complexity? You have done it in 2 loops, there is a way to do it in one loop, can you find it? This algorithm will not give correct result for this input because you have assumed friendship is a symmetric-transitive relation, how can you fix this issue? The thing is, they push you. They push you until you don't know the answer, and they want you to think what you didn't thought before. They give little clues, breadcrumbs, to lead you to right way and you can surely see their satisfaction if you can follow that lead.
To sum up, It is good, it feels good, but it is hard. Definitely worth it.
Interview Question – Interviewer came with a deck of cards. It is a simple game, cards put on top of each other, at every step you take the top card out and then take another card from the top and put it into the bottom. Repeat this until all cards are discarded. In how many of those iterations will you get the starting sequence as discarded sequence? View Answers (1)
Account Strategist at Google (會計策略師)
No Offer – Interviewed in Wrocław (Poland) Nov 2012 – Reviewed yesterday New
Interview Details – The recruiting process was performed very professional hence communication style was really enjoyable. Appointments were agreed on flexibly and interviews were conducted on time with high level of professionalism. Feedback was provided quickly after results were achieved etc.
First steps included a personal interview with an recruiter on campus. Several Position were discussed to identify the potential best fit between job requirements and my profile, contact details were provided for and I was forwarded to the recruiter in charge for the position available in Wroclaw.
Further communication with the recruiter in Wroclaw was really smooth and professional, the complex recruiting process was held highly transparent.
Interview Question – Describe a professional situation in which you have introduced a creative approach or idea successfully! View Answers (1)
BOLD Intern at Google (BOLD 實習)
No Offer – Reviewed yesterday New
Interview Details – I made it to the final round of Google's BOLD Internship program. It consists of two phone interviews, about 20-30 minutes each. Most questions were standard, with the exception of two "Google" questions mentioned below. The interviewers asked some questions specific to their product (e.g., "What would you change?), which is sometimes one of Google's more obscure products. One of my interviewers worked on Google Product Forums. Be very well-versed in their product line.
Interview Question – One of my interviewers asked two "Google" questions, the other did not ask any. Search online for examples; these are impossible questions designed to see how you approach problems. Answer Question
Software Development Engineer at Google (軟體開發工程師)
Accepted Offer – Interviewed in Cambridge, MA Nov 2012 – Reviewed yesterday New
Interview Details – I was contacted by a recruiter from Google over a year ago when I wasn't in the job market. This year, when I entered the job market, I got back in touch with him, and he set things up for me.
Since I work right next to the Google office in Cambridge, they skipped phone interviews and I was invited for an onsite interview directly. There were five technical interviews that covered coding, algorithm design and analysis, software design, and system design
Interview Question – My most difficult question was on system design. I have been in academia until now, and so thinking about enterprise-style system-design and scalability issues was very difficult for me. Answer Question
QA Engineer at Google (品質保證工程師)
No Offer – Reviewed 2 days ago New
Interview Details – 1. Resume submission
2. Recruiter contacted me
3. On site interview
-first session includes question about my CV, and basic white board coding question - which has no perfect answer for it.
-second session includes basic paper based coding
Interview Question – Give me counter examples to your solution View Answers (1)
Software Engineer Practicum at Google (軟體工程實習生)
Accepted Offer – Interviewed in Cambridge, MA Nov 2012 – Reviewed 4 days ago New
Interview Details – The interview wasn't as challenging as I thought it would be in the sense that the coding questions were not that challenging, but conceptual questions were very interesting. I was asked to explain how someone could check for duplicate files in a 20GB directory, for instance.
Interview Question – How can you find duplicate files in a 20GB directory? View Answers (1)
留言列表
國家自強 (1)
