25.03.2013 Views

Cracking the Coding Interview - Fooo

Cracking the Coding Interview - Fooo

Cracking the Coding Interview - Fooo

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

At <strong>the</strong> <strong>Interview</strong> | Top Ten Mistakes Candidates Make<br />

#6 | Talking Too Little<br />

Psst - let me tell you a secret: I don’t know what’s going on in your head So if you aren’t talking,<br />

I don’t know what you’re thinking If you don’t talk for a long time, I’ll assume that you<br />

aren’t making any progress Speak up often, and try to talk your way through a solution This<br />

shows your interviewer that you’re tackling <strong>the</strong> problem and aren’t stuck And it lets <strong>the</strong>m<br />

guide you when you get off-track, helping you get to <strong>the</strong> answer faster And it shows your<br />

awesome communication skills What’s not to love?<br />

#7 | Rushing<br />

<strong>Coding</strong> is not a race, and nei<strong>the</strong>r is interviewing Take your time in a coding problem - don’t<br />

rush! Rushing leads to mistakes, and reveals you to be careless Go slowly and methodically,<br />

testing often and thinking through <strong>the</strong> problem thoroughly You’ll finish <strong>the</strong> problem in less<br />

time in <strong>the</strong> end, and with fewer mistakes<br />

#8 | Not Debugging<br />

Would you ever write code and not run it or test it? I would hope not! So why do that in an<br />

interview? When you finish writing code in an interview, “run” (or walk through) <strong>the</strong> code to<br />

test it Or, on more complicated problems, test <strong>the</strong> code while writing it<br />

#9 | Sloppy <strong>Coding</strong><br />

Did you know that you can write bug-free code while still doing horribly on a coding question?<br />

It’s true! Duplicated code, messy data structures (i e , lack of object oriented design),<br />

etc Bad, bad, bad! When you write code, imagine you’re writing for real-world maintainability<br />

Break code into sub-routines, and design data structures to link appropriate data<br />

#10 | Giving Up<br />

Have you ever taken a computer adaptive test? These are tests that give you harder questions<br />

<strong>the</strong> better you do Take it from me - <strong>the</strong>y’re not fun Regardless of how well you’re actually<br />

doing, you suddenly find yourself stumbling through problems Yikes!<br />

<strong>Interview</strong>ing is sort of like this If you whiz through <strong>the</strong> easy problems, you’re going to get<br />

more and harder problems Or, <strong>the</strong> questions might have just started out hard to begin with!<br />

Ei<strong>the</strong>r way, struggling on a question does not mean that you’re doing badly So don’t give up<br />

or get discouraged You’re doing great!<br />

CareerCup com<br />

4 0

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!