Guide to Tech Interviews
kchodorow.com
Guide to Tech Interviews
1–10 of 29 posts
Re: Guide to Tech Interviews
#2If 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 there, and you come back down to normal level, you feel like you can leap over a car. Same with coding, you feel like you can code blindfolded. And your ability/productivity increases by an order of magnitude.
Re: Guide to Tech Interviews
#3Great tips, thank you. One tiny thing I -partly- disagree with:
"you absorb more info when you’re doodling than when you’re just listening" I think this differs a lot per person. I find creative types tend to be bad at focussing on one thing, and can focus better if they are distracted by something they control like doodling. Personally I tend to think very linearly and once I'm distracted by something, that immediately means I'm not focussing anymore.
Re: Guide to Tech Interviews
#4i personally think you should get rid of that pirated book link.
Re: Guide to Tech Interviews
#5Great tips, thank you. One tiny thing I -partly- disagree with: "you absorb more info when you’re doodling than when you’re just listening" I think this differs a lot per person. I find creative types tend to be bad at focussing on one thing, and can focus better if they are distracted by something they control like doodling. Personally I tend to think very linearly and once I'm distracted by something, that immediat…
I think she's actually referring to this http://www.guardian.co.uk/science/2009/feb/27/doodling-doodl... rather than making a purely subjective statement. Having said that, I don't know of any studies that have replicated that finding so it may not be valid.
Re: Guide to Tech Interviews
#6i 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.
Re: Guide to Tech Interviews
#7Your site was throwing some DB connectivity errors...
Re: Guide to Tech Interviews
#8Great tips, thank you. One tiny thing I -partly- disagree with: "you absorb more info when you’re doodling than when you’re just listening" I think this differs a lot per person. I find creative types tend to be bad at focussing on one thing, and can focus better if they are distracted by something they control like doodling. Personally I tend to think very linearly and once I'm distracted by something, that immediat…
I think she's actually referring to this http://www.guardian.co.uk/science/2009/feb/27/doodling-doodl... rather than making a purely subjective statement. Having said that, I don't know of any studies that have replicated that finding so it may not be valid.
Anecdotally, it's how I functioned best in a classroom setting.
Re: Guide to Tech Interviews
#9I 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 not in Silicon Valley) but I get a great deal of logic questions or draw this abstract concept out on the board. And it is hard for me to deal with NOT knowing a problem.
For example, if SQL is on the job description, might as well cover every aspect of SQL which aren't really covered in the technical interview books. How do indexes work, etc, etc? Venn diagram outer joins.
Re: Guide to Tech Interviews
#10If 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…
Some even recommend writing the on paper, I find it hard to do.