4

I crash and burn during coding interview questions. Every. Time.

I just do. It's terrible. It doesn't matter how much I tell myself to slow down and just think it through first before coding...I end up coding first after a short period of thinking about it. Don't get it right, freak out...and well I crash and burn.

It bums me out. The worst part is that I'm so distraught about it that I take a break, and sit down and solve it in like 10 minutes...of course it doesn't matter since it happens after the interview.

I just need to practice solving these things to get that mindset right.

Comments
  • 1
    Same here!

    I am kind of fed up with their demand on writing a program on paper.

    For all of my career, I am good at thinking with keyboard and they wanted to judge develoepr on how well he can write a sorting algorithm on paper.

    Dear interviewer, you can't judge a driver if he failed to answer

    "What you should do first on a corner, turning the wheel or pressing the clutch?"

    Look at his past records, if he would be the bad driver then how can he survive in this industry for so long. Think.
  • 1
    I have no experience with coding interviews. Do they present you with a poorly described problem and want you to figure out what the problem is rather than coding it?
  • 0
    @512GB No! it is a same old question, write a bubble sort or quick sort on a single piece of paper. With couples of other question.
Add Comment