Cracking the Coding Interview (Video Preview)

Cracking the Technical Interview (Video) is one-hour long video to show you what a Google/Microsoft-style interview is like, and what you should and shouldn't do. You can purchase the full-length video at http://www.careercup.com.

PURCHASE THE FULL VIDEO AT www.careercup.com

Watch Gayle Laakmann (Founder and CEO of CareerCup) interview a candidate, just like she did over 100 times for big companies like Google and Microsoft. The candidate doesn't know how to solve the questions at first, so he's just like you. How does he handle it? What should you do in this situation? Watch this interview to find out!

This video will:
* Expose you to what a real Google / Microsoft / Amazon interview is like.
* Show you how to handle questions when you don't know the answer.
* Teach you what Google, Microsoft and Amazon look for in an interview.

Contents of the video include:
* Overview of what companies like Google, Microsoft and Amazon look for.
* Discussion of the candidate's resume, to show you how to discuss your resume and what you're likely to be asked.
* Technical interview questions (including white-boarding coding). This candidate didn't know the answers, so you can learn how to handle this situation.
* The candidate asking for help in an appropriate way, which is expected in an interview.
* The interviewer (Gayle Laakmann, Founder and CEO of CareerCup) going over the interviewing, saying what was good and bad.

Category:

Science & Technology

Tags:

• careercup
• technical interview
• interview
• programming
• programmer
• coding
• microsoft interview
• apple interview
• google interview

[ebaychatter0]

0:35 aren't you supposed to stop the interview on the spot, when he mentioned "array", as arrays are EVIL

[careercup]

@ebaychatter0 Well, no. First, you never stop an interview on the spot, no matter how poorly the interview is going. Second, the "arrays are evil" idea is about C++, not about all languages. This candidate happened to implement this in Java, so there's no issue with using arrays. Third, even if the candidate happened to use C++, I wouldn't have marked down the candidate substantially for using C++. I care more about their intelligence and skill set than their knowledge of a particular thing.

[bdgftw]

I'm impressed with the example question and how the interviewer led the candidate through the tradeoffs between different approaches (summary at 3:37).

When I interviewed at Microsoft, we'd use ambiguous questions like this one to see how well candidates probed for necessary details. The candidate does a good job asking questions, but maybe shouldn't have dived into the array approach so quickly without considering sparse polynomials like 2x^300+1.

[MrCuddlyable3]

@QuanSai maybe you need to get past having any problem talking with a left handed young American female who knows her stuff, because there are many.

[9b8]

@zionen01 There is definitely a social issue with that approach. I mean, almost everyone has a certain reserved character when you are conversing with a bunch of 'strangers' about something deep or profound. Surely Google has a few psycology experts that understand these social notions for their interviews. At any rate, when I'm comfortable, I have NO PROBLEM doodling on a whiteboard, designing and brain storming. Its tough to shake that human tendency! Cruelly unfair, no doubt!

[careercup]

@redmoon7777 @redmoon7777 You can purchase it (and several other videos) at careercup. (Sorry, it won't let me post a link - but go to careercup and click on the main image.)

[zionen01]

I had a similar interview consisting of 5 hours in front of a whiteboard solving problems. The problem with it, is that it doesn't test your skills as much as it tests how you handle on-the-spot decisions and working under pressure. I was surprised that simple questions at that point in time were tripping me up, whereas I could have easily solved them in a different setting. I much prefer the typical pencil and paper testing.

[z2arjum]

This was nice....

[maxx666mayhem]

ahh we simply need a link list to solve this much easier