CRACKING THE CODING INTERVIEW里关于面试中的错误的说法# JobHunting - 待字闺中
p*y
1 楼
原文节选如下：
“One of the most pervasive—and dangerous—rumors is that candidates need
to get
every question right. That's not even close to true.”
“When I evaluate how someone performed in an interview...it's about how
optimal your final solution was, how long it took you to get there, and how
clean your code was.”
“In evaluating thousands of hiring packets at Google, I have only once seen
a candidate have a "flawless"set of interviews. Everyone else, including
the hundreds who got offers,made mistakes.”
此外，大部分面试教程都强调要先分析问题，确定了方案以后，再小心地写代码。
按照这些思路做了思想准备后，前阵子去G做了次onsite,发现主考官们对于我逐步推导
的过程没兴趣，感觉他们期待看到的是上来就写代码，写出来就是全对的优化无bug代
码。
所以感到很疑惑，在人人熟读leetcode的今天，CRACKING THE CODING INTERVIEW里这
些说法还适用于FLG吗？我们面试FLG，是不是必须做到不管题目多难，都能不假思索地
写出干净、优化、无BUG的代码，才能得到offer呢？写代码前的讨论和推导，是不是都
是作为扣分点来考虑的呢？写代码过程是不是不应该停下来检查，而是要奋笔疾书，显
示出自己干活非常利索？
“One of the most pervasive—and dangerous—rumors is that candidates need
to get
every question right. That's not even close to true.”
“When I evaluate how someone performed in an interview...it's about how
optimal your final solution was, how long it took you to get there, and how
clean your code was.”
“In evaluating thousands of hiring packets at Google, I have only once seen
a candidate have a "flawless"set of interviews. Everyone else, including
the hundreds who got offers,made mistakes.”
此外，大部分面试教程都强调要先分析问题，确定了方案以后，再小心地写代码。
按照这些思路做了思想准备后，前阵子去G做了次onsite,发现主考官们对于我逐步推导
的过程没兴趣，感觉他们期待看到的是上来就写代码，写出来就是全对的优化无bug代
码。
所以感到很疑惑，在人人熟读leetcode的今天，CRACKING THE CODING INTERVIEW里这
些说法还适用于FLG吗？我们面试FLG，是不是必须做到不管题目多难，都能不假思索地
写出干净、优化、无BUG的代码，才能得到offer呢？写代码前的讨论和推导，是不是都
是作为扣分点来考虑的呢？写代码过程是不是不应该停下来检查，而是要奋笔疾书，显
示出自己干活非常利索？
