смешное письмо из Гугеля
Oct. 16th, 2007 02:25 pmЭто у них, видимо, формочка такая запасена, в предположении, что все в Гугель рвутся аж до усрачки, и будут куда-то специально готовиться.
-------------------------------8<---- cut here -------------------------------------------------
It's advisable to take the Google interview process very seriously as this may need brushing up your fundamentals. Focus in the next 2-3 rounds will be on what level of technology you know and what you are able to articulate during the interview process. Please research and take time to prepare thoroughly about related technologies and put your best foot forward. Here are few guidelines, that may help:
1. Read the Corporate information at Google's About Google page. Sometimes the engineer will see if you know anything about Google, other than the Search engine product. http://www.google.com/about.html http://www.google.com/options/index.html
2. The position requires expertise in Software development, Unix/Linux, and Networking. The Google Engineer will expect you to have a very deep, intimate knowledge in the areas which you rated yourself highly.
3. Try to learn about Google's search technology. Algorithms. Binaries. Data structures. Fast, efficient ways to handle large amounts of data.
4. Read the research papers found at this website: http://labs.google.com/papers/index.html
5. Question topics: networking basics, sys admin basics, sys admin monitoring and troubleshooting, scripting, coding/algorithms/data structures. Review a Unix/Linux reference manual.
6. Sys admin questions could probe how to maintain high availability. Troubleshooting performance issues involving both systems and networks. Keep in mind the vast scale of the Google.com infrastructure and what problems this may present.
7. When you get technical questions where there are more than one possible answer, they are expecting the most effective and efficient solution.
8. Try to be concise in your answers, but also offer succinct explanations to qualify your response.
9. If time permits, ask the engineer for specific details about the position. The interviewing Engineer is a Senior Google.com Engineer. He will be the best source to learn exactly what the role entails.
10. Solid understanding of the networking basics (protocols, nw topologies, nw devices) and knowledge of Unix OS basics is must.
Please focus on your core skills like if you are not a sys admin, you need not spend more time on browsing sys admin reference material, etc.
Engineers who work at Google are here for two reasons: to work with the best engineers who are passionate about technology and to work with cutting edge technology.
Here's a link about interviewing at Google:
http://www.youtube.com/watch?v=w887NIa_V9w
If you have any other questions, please feel free to contact me anytime. I look forward to you becoming a Googler:)
Here are few more links regarding general phone interview preparation:
http://career.thingamajob.com/interview-tips.aspx/Guide-To-Telephone-Interviews.aspx
http://www.happycareer.com/employees/telephone_interview_tips.asp
http://www.onlinecareerinfo.com/category/telephone-interviews/
Some More Useful Links about Google:
http://labs.google.com/why-google.html
http://money.cnn.com/magazines/fortune/bestcompanies/2007/full_list/index.html
http://www.youtube.com/google
http://blog.searchenginewatch.com/blog/060313-161501
Google named #1 company to work for by Fortune Magazine
http://money.cnn.com/magazines/fortune/bestcompanies/2007/snapshots/1.html
San Jose Mercury News-July 2007
http://www.mercurynews.com/business/ci_6410719
http://mercextra.com/video/2007/07/16/inside-the-googleplex/
What's it like to be a Google engineer?
http://www.google.com/intl/en/jobs/working.html
Top 10 reasons to work at Google
http://www.google.com/intl/en/jobs/reasons.html
Google tools and services to be proud of:
http://www.google.com/options/index.html
Google Benefits
http://www.google.com/support/jobs/bin/static.py?page=benefits.html
Google Video about Interviewing
http://www.youtube.com/watch?v=w887NIa_V9w&feature=PlayList&p=12E3C2A3C2C732BC&index=8
-------------------------------8<---- cut here -------------------------------------------------
It's advisable to take the Google interview process very seriously as this may need brushing up your fundamentals. Focus in the next 2-3 rounds will be on what level of technology you know and what you are able to articulate during the interview process. Please research and take time to prepare thoroughly about related technologies and put your best foot forward. Here are few guidelines, that may help:
1. Read the Corporate information at Google's About Google page. Sometimes the engineer will see if you know anything about Google, other than the Search engine product. http://www.google.com/about.html http://www.google.com/options/index.html
2. The position requires expertise in Software development, Unix/Linux, and Networking. The Google Engineer will expect you to have a very deep, intimate knowledge in the areas which you rated yourself highly.
3. Try to learn about Google's search technology. Algorithms. Binaries. Data structures. Fast, efficient ways to handle large amounts of data.
4. Read the research papers found at this website: http://labs.google.com/papers/index.html
5. Question topics: networking basics, sys admin basics, sys admin monitoring and troubleshooting, scripting, coding/algorithms/data structures. Review a Unix/Linux reference manual.
6. Sys admin questions could probe how to maintain high availability. Troubleshooting performance issues involving both systems and networks. Keep in mind the vast scale of the Google.com infrastructure and what problems this may present.
7. When you get technical questions where there are more than one possible answer, they are expecting the most effective and efficient solution.
8. Try to be concise in your answers, but also offer succinct explanations to qualify your response.
9. If time permits, ask the engineer for specific details about the position. The interviewing Engineer is a Senior Google.com Engineer. He will be the best source to learn exactly what the role entails.
10. Solid understanding of the networking basics (protocols, nw topologies, nw devices) and knowledge of Unix OS basics is must.
Please focus on your core skills like if you are not a sys admin, you need not spend more time on browsing sys admin reference material, etc.
Engineers who work at Google are here for two reasons: to work with the best engineers who are passionate about technology and to work with cutting edge technology.
Here's a link about interviewing at Google:
http://www.youtube.com/watch?v=w887NIa_V9w
If you have any other questions, please feel free to contact me anytime. I look forward to you becoming a Googler:)
Here are few more links regarding general phone interview preparation:
http://career.thingamajob.com/interview-tips.aspx/Guide-To-Telephone-Interviews.aspx
http://www.happycareer.com/employees/telephone_interview_tips.asp
http://www.onlinecareerinfo.com/category/telephone-interviews/
Some More Useful Links about Google:
http://labs.google.com/why-google.html
http://money.cnn.com/magazines/fortune/bestcompanies/2007/full_list/index.html
http://www.youtube.com/google
http://blog.searchenginewatch.com/blog/060313-161501
Google named #1 company to work for by Fortune Magazine
http://money.cnn.com/magazines/fortune/bestcompanies/2007/snapshots/1.html
San Jose Mercury News-July 2007
http://www.mercurynews.com/business/ci_6410719
http://mercextra.com/video/2007/07/16/inside-the-googleplex/
What's it like to be a Google engineer?
http://www.google.com/intl/en/jobs/working.html
Top 10 reasons to work at Google
http://www.google.com/intl/en/jobs/reasons.html
Google tools and services to be proud of:
http://www.google.com/options/index.html
Google Benefits
http://www.google.com/support/jobs/bin/static.py?page=benefits.html
Google Video about Interviewing
http://www.youtube.com/watch?v=w887NIa_V9w&feature=PlayList&p=12E3C2A3C2C732BC&index=8
no subject
Date: 2007-10-16 09:42 pm (UTC)no subject
Date: 2007-10-17 02:14 am (UTC)no subject
Date: 2007-10-18 05:31 pm (UTC)no subject
Date: 2007-10-19 02:10 pm (UTC)no subject
Date: 2007-10-19 02:03 pm (UTC)