職場面面觀:面試時的10大經典錯誤

Practicing on a Computer
只在電腦上練習

If you were training for a serious bike race in the Mountains, would you practice only by bik-ing on the streets? I hope not The air is different The terrain is different Yeah, I bet you’dpractice in the mountains
如果你正在準備山地自行車比賽，你會在馬路上練習嗎？我想肯定不會吧。因爲兩者的氣溫，地形有很大的差異。所以我打賭你會在山地上練習！

Using a compiler to practice interview questions is like this - and you’ve basically been bikingon the streets your entire life Put away the compiler and get out the old pen and paper Usea compiler only to verify your solutions
那麼用編譯器來幫你準備面試，就像在馬路上練習山地自行車一樣。還是老老實實的拿出塵封已久的筆和紙來練習吧。編譯器還是留到最後驗證答案的時候用。

Not Rehearsing Behavioral Questions
不準備行爲面試

Many candidates spend all their time prepping for technical questions and overlook the behavioral questions Guess what? Your interviewer is judging those too! And, not only that- your performance on behavioral questions might bias your interviewer’s perception of your technical performance Behavioral prep is relatively easy and well-worth your time Lookingover your projects and positions and think of the key stories Rehearse the stories Seepg 29 for more details
很多應聘者花了大量的時間準備技術問題，忽視了行爲問題。知道嗎嘛，面試官一樣看重行爲問題。而你行爲問題方面的表現會影響面試官對你問答技術問題的評價。況且準備行爲問題也非常的簡單，性價比很高。瀏覽你簡歷上涉及的項目和職位信息，總結下每個項中的重要信息。具體的方法在之前的章節已經介紹過了。

Not Doing a Mock Interview
不做模擬面試

Imagine you’re preparing for a big speech Your whole school, or company, or whatever willbe there Your future depends on this And all you do to prepare is read the speech to your-self Silently In your head Crazy, right? Not doing a mock interview to prepare for your real interview is just like this If you’re anengineer, you must know other engineers Grab a buddy and ask him/her to do a mockinterview for you You can even return the favor!
假想下你正準備一個演講，全學校或者全公司的都會來聽，不管怎麼說這次演講對你至關重要。如果你只是每次都對着自己默唸來準備的話，是不是覺得很傻？不做模擬面試就和這件事情一樣傻。隨便拉一個同事過來，讓他給你模擬面試一次。你們也可以相互面，禮尚往來嘛。

Trying to Memorize Solutions
背答案

Quality beats quantity Try to struggle through and solve questions yourself; don’t flip di-rectly to the solutions when you get stuck Memorizing how to solve specific problem isn’tgoing to help you much in an interview Real preparation is about learning how to approachnew problems
質量勝於數量。通過自己的努力去解題；不要一碰到不會的就直接翻答案。直接背答案的話在面試的時候對你幫助真不太大。準備面試的目的不是去背答案，而是學會解決新問題的方法。

Talking Too Much
話太多

I can’t tell you how many times I’ve asked candidates a simple question like “what was thehardest bug on Project Pod?”, only to have them ramble on and on about things I don’t understand Five minutes later, when they finally come up for air, I’ve learned nothing - exceptthat they’re a poor communicator When asked a question, break your answer into three parts (Situation / Action / Response, Issue 1 / Issue 2 / Issue 3, etc) and speak for just a couple sentences about each If I want more details, I’ll ask!
問了應聘者一個簡單的問題，例如“這個項目中最棘手的bug是什麼？”，結果他唧唧歪歪唧唧歪歪半天也沒有說到重點，我卻霧水什麼都沒聽懂，最後只能得出結論：這個人的溝通能力有問題。這樣的情況都不知道遇到多少次了。在面試時回答問題前心中最好能有個提綱(情形-行動-結果或者1,2,3點的形式)，每點說一兩句就夠了。如果面試官想知道細節，他們自己會問的。

Talking Too Little
話太少

Psst - let me tell you a secret: I don’t know what’s going on in your head So if you aren’t talk-ing, I don’t know what you’re thinking If you don’t talk for a long time, I’ll assume that youaren’t making any progress Speak up often, and try to talk your way through a solution This shows your interviewer that you’re tackling the problem and aren’t stuck And it lets them guide you when you get off-track, helping you get to the answer faster And it shows yourawesome communication skills What’s not to love?
嗯，告訴你，我是永遠猜不到你腦袋裏面在想什麼的。在面試的時候如果你不開口說話，我就不知道你在想什麼。如果你一直不說話，我就會簡單認爲你卡殼了。多開口說話，在解題過程中就多講講你的想法。這樣面試官才能知道你是在解題而不是發呆。而且如果你的思路有問題，面試官還能根據你說的給你些提示。此外多和麪試官交流，他們會認爲你的溝通能力還不錯，何樂而不爲呢？

Rushing
急匆匆

Coding is not a race, and neither is interviewing Take your time in a coding problem - don’trush! Rushing leads to mistakes, and reveals you to be careless Go slowly and methodically,testing often and thinking through the problem thoroughly You’ll finish the problem in lesstime in the end, and with fewer mistakes
寫代碼不是比賽，面試也一樣不是。面試寫代碼的時候千萬不要匆匆忙忙的。寫的太快容易出錯，錯誤會讓面試官覺得你粗心大意。慢慢寫代碼，系統的測試自己寫的代碼，吃透問題。慢慢寫最後會讓你完成得更快，而錯誤更少。

Not Debugging
不調試

Would you ever write code and not run it or test it? I would hope not! So why do that in aninterview? When you finish writing code in an interview, “run” (or walk through) the code totest it Or, on more complicated problems, test the code while writing it
你平時寫完代碼就直接完事的嗎？我想肯定不是吧。那面試的時候寫的代碼也一樣對待吧。面試的時候雖然沒有電腦讓你“Run”，但是過一遍代碼。如果代碼複雜一些的話，最好能設計一兩個測試用例來，邊寫邊測。

Sloppy Coding
爛代碼

Did you know that you can write bug-free code while still doing horribly on a coding question? It’s true! Duplicated code, messy data structures (i e , lack of object oriented design),etc Bad, bad, bad! When you write code, imagine you’re writing for real-world maintain-ability Break code into sub-routines, and design data structures to link appropriate data
你覺得你在解決一個難題的時候，能不能寫出沒有錯誤代碼嗎？肯定不行吧！重複代碼，混亂的數據結構，等等不好的代碼習慣。在面試的時候就假設自己真正的在開發。什麼提取含函數啦，設計模式啦能用上的就別不好意思用！

Giving Up
放棄

Have you ever taken a computer adaptive test? These are tests that give you harder ques-tions the better you do Take it from me - they’re not fun Regardless of how well you’re actually doing, you suddenly find yourself stumbling through problems Yikes!
你做過這樣的測試嗎？測試題的難度根據你的表現一步一步提高。告訴你這樣的測試沒有意思的。別以爲你自己平時有多厲害，你也會突然卡在一個難題上的。

Interviewing is sort of like this If you whiz through the easy problems, you’re going to getmore and harder problems Or, the questions might have just started out hard to begin with!Either way, struggling on a question does not mean that you’re doing badly So Don’t give up or get discouraged You’re doing great!
面試也是這樣的。如果你秒了簡單題，那麼接下來迎接你的就是難題了。還有可能你上來就碰到一個巨難的問題。不管什麼樣情況，努力的解題並不說明你做的不好。所以千萬別在做題的時候氣餒和放棄。你做的很好！