Communicate Proactively!

• Communicate before you start coding, during coding, anytime you’re stuck, and an analysis after coding
  • Specify why you’re stuck
  • I’m stuck at [so and so] or line 6 or I’m thinking of trying this but I’m not sure how to implement it
  • You want the smallest or most minimal hint as possible
• Do not start coding until you communicate
  • Talk through possible solutions, test cases, etc.
  • Repeat the question, rephrase it in your own words
  • Make sure you understand the input and output of the program
  • Do not assume that a question is the same as one you’ve done before because it looks similar
    • Do not overlook similarities/details
  • Clarify and understand the question thoroughly
• Common questions to ask
  • What type of variable type: char, String, integer, boolean, double, float?
  • Empty data structure? NULL values?
  • Duplicates allowed?
• Use diagrams, draw, illustrate, any way to be the clearest
• Write things down so you don’t forget about things like edge cases

When you don’t communicate…

• Interviewer doesn’t know what you’re thinking
• Interviewer wouldn’t want to work with you
• Most coders do not code linearly, so it’s difficult to know where in the process you are at
• The interviewer is just left to sit there without any sort of conversation/communication