i personally think you should get rid of that pirated book link.
Agree. In the PDF, there is this little statement: Copyright © 2008 - 2010 by Gayle Laakmann. All rights reserved. This means something. The author needs to respect it.
Guide to Tech Interviews
11–20 of 29 posts
Re: Guide to Tech Interviews
#12Your site was throwing some DB connectivity errors...
Re: Guide to Tech Interviews
#13If you are using an IDE like Eclipse or anything with auto code completion, syntax color-highlighting, and syntax error highlighting, get rid of that while coding up the exercises in the PDF. Use Notepad++ or kwrite and disable those features, if your coding speed grinds to a halt under these conditions, good! That's the point of the exercise, like trying to jog at 30 thousand feet, as you overcome the hindrance up t…
Re: Guide to Tech Interviews
#14This is good technical interview advice, but I've never gotten a job that only had technical interviews. Programmers might not appreciate a thank you note or call, but managers probably will. They're trying to figure out whether you're someone who will follow up and be responsible rather than someone who knows what a binary tree is.
Re: Guide to Tech Interviews
#15I asked this on reddit. The one thing about tech interviews. They could ask anything. Literally any facet of technology. How do you prepare for being asked anything? In the Gayle book, they go from binay trees, to bit manipulation to queues, etc, etc. Of course that won't even get touched in some technical interviews, it will be more knowledge based, (Describe polymorphism). I rarely get the complex algorithms (I am…
Some interviews are just unfair and there isn't really anything you can do to prepare, so don't waste your time worrying about it. Try to get a good story out of it and pity the company (I know, cold comfort if you need a job).
Decent interviews will stick to what's on your resume: "you say you spent 10 years working on networking internals, can you tell me about how you'd design a reliable network protocol?"
You can find lists of common interview questions online for almost every technical topic, so look up "SQL interview questions" and make sure you can answer the common ones if you're worried about them.
Re: Guide to Tech Interviews
#16Earlier quoted context omitted.
Agree. In the PDF, there is this little statement: Copyright © 2008 - 2010 by Gayle Laakmann. All rights reserved. This means something. The author needs to respect it.
I'm trying to track down the link I got it from. It's freely available (I downloaded it from Google career site) I just can't figure out where, now.
You might consider that just because you were able to download a file from somewhere does not give you the right to redistribute it. It is possible that the site you got it from may or may not have had the right to distribute it themselves!
Re: Guide to Tech Interviews
#17If you are using an IDE like Eclipse or anything with auto code completion, syntax color-highlighting, and syntax error highlighting, get rid of that while coding up the exercises in the PDF. Use Notepad++ or kwrite and disable those features, if your coding speed grinds to a halt under these conditions, good! That's the point of the exercise, like trying to jog at 30 thousand feet, as you overcome the hindrance up t…
Re: Guide to Tech Interviews
#18Re: Guide to Tech Interviews
#19This is so well thought-out and I think your advice is bang on. Thanks for posting!
Re: Guide to Tech Interviews
#20Only interview there if you are ready to waste 3 days of your life and ~$1400 and think Justin Biber jokes are funny ( really? ).
Edit: Anyone know what I can do about recouping the money I spent, I sent all the receipts and filled out their candidate reimbursement form. They wont respond to my email.