Moved some interview prep to bottom.

This commit is contained in:
John Washam 2016-06-07 11:56:41 -07:00
parent 70c709e351
commit 056c3c0808

View File

@ -15,25 +15,25 @@ to use this the same way. If you search/replace, there are a couple of places to
* - Videos: * - Videos:
* - https://www.youtube.com/watch?v=oWbUtlUhwa8&feature=youtu.be * - https://www.youtube.com/watch?v=oWbUtlUhwa8&feature=youtu.be
* - https://www.youtube.com/watch?v=qc1owf2-220&feature=youtu.be * - https://www.youtube.com/watch?v=qc1owf2-220&feature=youtu.be
- https://www.youtube.com/watch?v=8npJLXkcmu8 * - https://www.youtube.com/watch?v=8npJLXkcmu8
Articles: * - Articles:
- http://www.google.com/about/careers/lifeatgoogle/hiringprocess/ * - http://www.google.com/about/careers/lifeatgoogle/hiringprocess/
* - http://steve-yegge.blogspot.com/2008/03/get-that-job-at-google.html * - http://steve-yegge.blogspot.com/2008/03/get-that-job-at-google.html
- all the things he mentions that you need to know are listed below - all the things he mentions that you need to know are listed below
* - (very dated) http://dondodge.typepad.com/the_next_big_thing/2010/09/how-to-get-a-job-at-google-interview-questions-hiring-process.html * - (very dated) http://dondodge.typepad.com/the_next_big_thing/2010/09/how-to-get-a-job-at-google-interview-questions-hiring-process.html
- http://sites.google.com/site/steveyegge2/five-essential-phone-screen-questions * - http://sites.google.com/site/steveyegge2/five-essential-phone-screen-questions
Additional (not suggested by Google but I added): Additional (not suggested by Google but I added):
- https://courses.csail.mit.edu/iap/interview/materials.php
- http://www.coderust.com/blog/2014/04/10/effective-whiteboarding-during-programming-interviews/
- https://www.youtube.com/watch?v=rEJzOhC5ZtQ&feature=youtu.be
- https://www.youtube.com/watch?v=aClxtDcdpsQ&feature=youtu.be
- https://www.youtube.com/watch?v=2cf9xo1S134&feature=youtu.be
- https://www.youtube.com/watch?v=YJZCUhxNCv8
* - https://medium.com/always-be-coding/abc-always-be-coding-d5f8051afce2#.4heg8zvm4 * - https://medium.com/always-be-coding/abc-always-be-coding-d5f8051afce2#.4heg8zvm4
* - https://medium.com/always-be-coding/four-steps-to-google-without-a-degree-8f381aa6bd5e#.asalo1vfx * - https://medium.com/always-be-coding/four-steps-to-google-without-a-degree-8f381aa6bd5e#.asalo1vfx
* - https://medium.com/@dpup/whiteboarding-4df873dbba2e#.hf6jn45g1 * - https://medium.com/@dpup/whiteboarding-4df873dbba2e#.hf6jn45g1
* - http://www.kpcb.com/blog/lessons-learned-how-google-thinks-about-hiring-management-and-culture
* - http://www.coderust.com/blog/2014/04/10/effective-whiteboarding-during-programming-interviews/
- https://www.youtube.com/watch?v=rEJzOhC5ZtQ
- https://www.youtube.com/watch?v=aClxtDcdpsQ
- https://www.youtube.com/watch?v=2cf9xo1S134
- https://www.youtube.com/watch?v=YJZCUhxNCv8
########################################################################################## ##########################################################################################
## Knowledge: ## Knowledge:
@ -299,6 +299,22 @@ System design:
- simplicity and robustness - simplicity and robustness
- tradeoffs - tradeoffs
Performance analysis and optimization Performance analysis and optimization
Familiarize yourself with unix-based souped-up code editor: emacs & vi(m)
vi(m):
- https://www.youtube.com/watch?v=5givLEMcINQ&index=1&list=PL13bz4SHGmRxlZVmWQ9DvXo1fEg4UdGkr
- set of 4:
- https://www.youtube.com/watch?v=SI8TeVMX8pk
- https://www.youtube.com/watch?v=F3OO7ZIOaJE
- https://www.youtube.com/watch?v=ZYEccA_nMaI
- https://www.youtube.com/watch?v=1lYD5gwgZIA
emacs:
- https://www.youtube.com/watch?v=hbmV1bnQ-i0
- set of 3:
- https://www.youtube.com/watch?v=ujODL7MD04Q
- https://www.youtube.com/watch?v=XWpsRupJ4II
- https://www.youtube.com/watch?v=paSgzPso-yc
- https://www.youtube.com/watch?v=JWD1Fpdd4Pc
Testing Testing
------------------------------------------------------------------- -------------------------------------------------------------------
@ -330,11 +346,19 @@ Machine Learning:
--- ---
Be thinking of: Be thinking of for when the interview comes:
Think of about 20 interview questions you'll get, along the lines of the items below:
have 2-3 answers for each
Have a story, not just data, about something you accomplished
Why do you want this job?
What's a tough problem you've solved?
Biggest challenges faced Biggest challenges faced
Best/worst designs seen Best/worst designs seen
Ideas for improving existing products Ideas for improving an existing Google product
How do you work best, as an individual and as part of a team?
Which of your skills or experiences would be assets in the role and why?
########################################################################################## ##########################################################################################
## Videos: ## Videos:
@ -439,8 +463,12 @@ Additional (not suggested by Google but I added):
## Coding exercises/challenges: ## Coding exercises/challenges:
########################################################################################## ##########################################################################################
Recommended: LeetCode: https://leetcode.com/ - https://courses.csail.mit.edu/iap/interview/materials.php
Recommended: LeetCode: https://leetcode.com/
TopCoder: https://www.topcoder.com/
More:
HackerRank: https://www.hackerrank.com/ HackerRank: https://www.hackerrank.com/
Codility: https://codility.com/programmers/ Codility: https://codility.com/programmers/
Project Euler: https://projecteuler.net/index.php?section=problems Project Euler: https://projecteuler.net/index.php?section=problems