Ask questions. You want to make sure you understand what you’re being asked to solve.
Talk out loud as you solve the problem. The interviewer wants to know how you think and problem solve. If you remain quiet, it’s harder to ascertain that.
Openly discuss the trade offs in your algorithm decisions. Acknowledging the weak links in your approach demonstrates that you’re aware where potential trouble spots may arise, and offers up why you were willing to make your trade-offs.
Write code. Although you can sketch out pseudo code for an outline, you need to inform interviewers that’s what you’re doing so they don’t assume it’s your final version. After writing pseudo code, you’ll need to hunker down and write the actual code.
Test your code. Interviewers expect to see bugs, so don’t be shy about fixing them. What they’re looking for is how you fix the bugs. If each interviewer notices a pattern where you take a band-aid approach that’s likely to introduce other problems, don’t expect to be hired.
Talk out loud as you solve the problem. The interviewer wants to know how you think and problem solve. If you remain quiet, it’s harder to ascertain that.
Openly discuss the trade offs in your algorithm decisions. Acknowledging the weak links in your approach demonstrates that you’re aware where potential trouble spots may arise, and offers up why you were willing to make your trade-offs.
Write code. Although you can sketch out pseudo code for an outline, you need to inform interviewers that’s what you’re doing so they don’t assume it’s your final version. After writing pseudo code, you’ll need to hunker down and write the actual code.
Test your code. Interviewers expect to see bugs, so don’t be shy about fixing them. What they’re looking for is how you fix the bugs. If each interviewer notices a pattern where you take a band-aid approach that’s likely to introduce other problems, don’t expect to be hired.
No comments:
Post a Comment