3 ms·

Seconded. Learning basic CS concepts will be more useful in the long run but for the specific goal of passing google-style interview you are better off practisi

Seconded. Learning basic CS concepts will be more useful in the long run but for the specific goal of passing google-style interview you are better off practising directly for that. All suggestions here are great but don't forget that whiteboard coding is the main part but not the only part of the interview. Practice answering architecture questions (conveniently, they can be practised without actually building any services) and other types of questions (find out which ones). Also think hard about your goal. "Getting into Google" is too abstract. Google has all sorts of teams, from the ones doing hardcore legacy maintenance to the ones doing some crazy cutting-edge stuff. The catch is that competition to get into more prestigious ones is crazy. Try to figure out (don't know how to do it though) if you have a chance of making a team that does something that you personally find interesting, or you are bound to be disappointed.

pennaMan 10y ago
> Practice answering architecture questions What are some good resources to learn about system architecture?
- dunkelheit 10y ago
  (disclaimer: I haven't done the interview dance for quite some time.) I find suggestions in part 4 of this article: http://blog.triplebyte.com/how-to-pass-a-programming-interview http://blog.triplebyte.com/how-to-pass-a-programming-intervi... quite reasonable. The rest of the article is also excellent. And it is short! The key here seems to be breadth - even if you have designed a few successful systems yourself, your breadth may be inadequate to talk smoothly about a system design problem which is unfamiliar to you in an hour-long interview. So learn your building blocks, get some ideas from architecture talks and blog posts by tech companies and sharpen your talking and hand-waving skills.
- dreistdreist 10y ago
  Microsoft Application Architecture Guide https://msdn.microsoft.com/en-us/library/ff650706.aspx https://msdn.microsoft.com/en-us/library/ff650706.aspx Domain Driven Design (The book is hard to read, but worth it I think) http://martinfowler.com/tags/domain%20driven%20design.html http://martinfowler.com/tags/domain%20driven%20design.html This uncle bob talk is not too bad https://www.youtube.com/watch?v=WpkDN78P884 https://www.youtube.com/watch?v=WpkDN78P884 I think the microsoft guide is the most comprehensive, but don't limit yourself to it.

pennaMan 10y ago

> Practice answering architecture questions What are some good resources to learn about system architecture?

dunkelheit 10y ago
(disclaimer: I haven't done the interview dance for quite some time.) I find suggestions in part 4 of this article: http://blog.triplebyte.com/how-to-pass-a-programming-interview http://blog.triplebyte.com/how-to-pass-a-programming-intervi... quite reasonable. The rest of the article is also excellent. And it is short! The key here seems to be breadth - even if you have designed a few successful systems yourself, your breadth may be inadequate to talk smoothly about a system design problem which is unfamiliar to you in an hour-long interview. So learn your building blocks, get some ideas from architecture talks and blog posts by tech companies and sharpen your talking and hand-waving skills.
dreistdreist 10y ago
Microsoft Application Architecture Guide https://msdn.microsoft.com/en-us/library/ff650706.aspx https://msdn.microsoft.com/en-us/library/ff650706.aspx Domain Driven Design (The book is hard to read, but worth it I think) http://martinfowler.com/tags/domain%20driven%20design.html http://martinfowler.com/tags/domain%20driven%20design.html This uncle bob talk is not too bad https://www.youtube.com/watch?v=WpkDN78P884 https://www.youtube.com/watch?v=WpkDN78P884 I think the microsoft guide is the most comprehensive, but don't limit yourself to it.