12
votes
8answers
1k views

In an interview, is it better to code a brute-force solution to a tough question, or to spend the interview examining the question carefully?

Sometimes interview questions are hard, whether the interviewer intends them to be, or not. It can come down to a choice of whether to use the limited interview time to code up an ugly, inefficient, ...
18
votes
3answers
1k views

How to avoid jumping to a solution when under pressure?

When under a particularly strict programming deadline (like an hour), if I panic at all, my tendency is to jump into coding without a real plan and hope I figure it out as I go along. Given enough ...
8
votes
6answers
987 views

How do the algorithms to solve problems encountered in interviews translate into real world solutions?

I have recently finished an undergraduate course in computer science and I am looking for a job. During the search I encountered several interesting (and tough) problems that needed clever algorithms ...
18
votes
11answers
4k views

Is “White-Board-Coding” inappropriate during interviews?

This is a somewhat subjective quesiton but I'd love to hear feedback/opinions from either interviewers/interviewees on the topic. We split our technical part into 4 parts. Write Code, Read & ...
39
votes
12answers
2k views

Is thinking out loud during an interview really the best strategy?

In another question I asked recently about best practices for whiteboarding, there was general consensus that thinking out loud while coming up with the answer was the best strategy. Indeed, long ...
1
vote
3answers
629 views

Importance of algorithms in a telephonic interview

I had taken a telephonic interview and the interviewer has given some problem for which I was supposed to give him the algorithm. Since its was a telephonic interview and I had no paper or pen, so I ...