27.10.2014 Views

Cracking the Coding Interview, 4 Edition - 150 Programming Interview Questions and Solutions

Cracking the Coding Interview, 4 Edition - 150 Programming Interview Questions and Solutions

Cracking the Coding Interview, 4 Edition - 150 Programming Interview Questions and Solutions

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> | Frequently Asked <strong>Questions</strong><br />

Absolutely not. Responses can be held up for a variety of reasons that have nothing to do<br />

with a good or bad performance. For example, an interviewer could have gone on vacation<br />

right after your interview. A company will always tell you if you’re rejected (or at least I’ve<br />

never heard of a company which didn’t).<br />

Can I re-apply to a company after getting rejected?<br />

Almost always, but you typically have to wait a bit (6 months – 1 year). Your first bad interview<br />

usually won’t affect you too much when you re-interview. Lots of people got rejected<br />

from Google or Microsoft <strong>and</strong> later got an offer.<br />

How are interview questions selected?<br />

This depends on <strong>the</strong> company, but any number of ways:<br />

1. Pre-Assigned List of <strong>Questions</strong>: This is unusual at bigger companies.<br />

2. Assigned Topics: Each interviewer is assigned a specific area to probe, but decides on<br />

his/her own questions.<br />

3. <strong>Interview</strong>er’s Choice: Each interviewer asks whatever he / she wants. Usually, under<br />

this system, <strong>the</strong> interviewers have a way of tracking which questions were asked to a<br />

c<strong>and</strong>idate to ensure a good diversity of questions.<br />

Approach #3 is <strong>the</strong> most common. This system usually means that interviewers will each<br />

have a “stock” set of five or so questions that <strong>the</strong>y ask c<strong>and</strong>idates.<br />

What about experienced c<strong>and</strong>idates?<br />

This depends a lot on <strong>the</strong> company. On average though, experienced c<strong>and</strong>idates will slightly<br />

get more questions about <strong>the</strong>ir background, <strong>and</strong> <strong>the</strong>y might face higher st<strong>and</strong>ards when discussing<br />

system architecture (if this is relevant to <strong>the</strong>ir experience). For <strong>the</strong> most part though,<br />

experienced c<strong>and</strong>idates face much <strong>the</strong> same process.<br />

Yes, for better or worse, experienced c<strong>and</strong>idate should expect to go through <strong>the</strong> same coding<br />

<strong>and</strong> algorithm questions. With respect to <strong>the</strong>ir performance, <strong>the</strong>y could face ei<strong>the</strong>r higher<br />

st<strong>and</strong>ards (because <strong>the</strong>y have more experience) or lower st<strong>and</strong>ards (because it’s likely been<br />

many years since <strong>the</strong>y worked with certain data structures).<br />

CareerCup.com<br />

4 2

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

Saved successfully!

Ooh no, something went wrong!