????原谷歌軟件工程師，《程序員面試金典》（Cracking the Coding Interview: 150 Programming Questions and Solutions）作者蓋兒?拉克曼?麥道威爾的回答。

????這個問題的答案應該分成三個部分：積累合適的經驗，編寫一份出色的簡歷，通過適當的方式提交簡歷。

????積累合適的經驗

????如果你畢業于一所好學校，或者在一家備受尊敬的公司工作，這將給你帶來極大幫助。不過，求職者可以通過一些項目為簡歷增添色彩。

????開發iPhone應用、網頁應用，無論什么都可以！實話實說，你在開發什么不重要，重要的是你正在做這樣的項目。有效的編程語言包括Java、Python、Ruby on Rails、C++等。不過我建議你避免使用.NET，并非因為它不是一款完美的工具，而是因為這種語言存在被人詬病的地方。

????例如，如果你是一名花旗銀行（CitiBank）的程序員，參與這些項目尤其重要。雖然你沒有純正的“血統”。但這些項目能夠給你加分。

????1. 你可以在一個周末構建一個內容豐富的項目。這意味著如果有3至4個周末的工作，你可以讓自己的簡歷從平庸變成出色。這絕非虛言——我見過許多人這么做。

????2. 參與編程馬拉松。

????3. 創建一個網站或個人作品集。展示你的經驗。

????編寫一份出色的簡歷

????只需要一頁即可。如果你的簡歷達到兩頁，很顯然，你只是在其中添加了一些無關緊要的內容。當面試官只花15秒瀏覽你的簡歷時，“總體內容”并不重要，重要的是平均內容。

????? 使用正規的簡歷格式。不要自我創造——這會浪費空間，而且看起來非常草率。

????? 列舉你的項目、編程馬拉松等。別擔心有些內容是否“適合出現在簡歷上”。如果這樣的內容能給人留下更深刻的印象，那就寫上吧。

????? 盡量陳述項目的文字——每一項1至2行即可。3行或3行以上的文字陳述，看起來像段落，不會有人愿意讀。

????? 重點是成績，而不是責任。每一項的第一行應該是一個詞，例如建立、創建、執行、設計、構建、優化等。

????? 量化你的成績。你進行過某個項目的優化？好，那請告訴我你優化了多少。

????? 不要總結。總結只能告訴我你想申請什么職位，但這一點我早已知曉，除此之外，它毫無用處。

????提交你的簡歷

????太多人只會使用一種途徑。他們只申請一次，然后認為這就足夠了。你應該嘗試所有可以使用的途徑。

????? 如果你是代碼托管網站Github或開發人員問答網站Stack Overflow的活躍用戶，招聘人員很有可能會主動找到你。但求職者沒有理由等著雇主找上門。

????? 在線申請。雖然不容易，但確實有人通過在線申請被雇主選中。

????? 詢問你的朋友。有人在谷歌（Google）工作嗎？或者認識某位在谷歌工作的朋友嗎？如果有人推薦，對你的求職會有很大幫助。

????? 嘗試在Twitter、Quora或其他社交媒體上聯系谷歌的工程師。記住，與他們的第一次聯系就是你的求職信。不要簡單地說“你好，我對谷歌很感興趣，能向公司推薦我嗎？”聯系他們，告訴他們你做過的事情，然后將簡歷的鏈接發送給他們。

????再說一遍，這些建議適用于所用公司，其中大部分也適用于多個崗位。（財富中文網）

????譯者：劉進龍/汪皓

????Answer by Gayle Laakmann McDowell, former software engineer at Google and author of Cracking the Coding Interview: 150 Programming Questions and Solutions

????There are really three parts to this answer: getting the right experience, creating a good resume, and submitting it the right way.

????Getting the Right Experience

????If you come from a good school/work for a well-respected company, that’ll help you a ton. But anyone can boost their resume with some projects.

????Build some iPhone apps, web apps, whatever! Honestly it doesn’t matter that much what you’re building as long as you’re building something. Good languages include Java, Python, Ruby on Rails, C++, etc. I would encourage you to stay away from .NET. Not because .NET isn’t a perfectly good tool, but there’s a stigma.

????Doing these projects is especially important if you’re, say, a programmer for CitiBank. You don’t have the right “pedigree.” But projects will help you a ton.

????1. You can build a fairly meaty project in one weekend. This means that with about 3 to 4 weekends of work, you can make your resume go from so-so to fantastic. Seriously — I’ve seen lots of people do this.

????2. Participate in hackathons.

????3. Build a website / portfolio. Show your experience.

????Building a Great Resume

????One page only. When you go onto two pages, you add weaker content to your resume, by definition. And when your resume is only read for about 15 seconds, it’s the average content that matters, not the “total amount of content.”

????? Use a real resume format. Don’t create your own – it tends to waste space and look sloppy.

????? List your projects, hackathons, etc. Don’t worry about whether or not something is ‘resume appropriate.’ Does it make you look more impressive? Then include it.

????? Keep your bullets short — 1 to 2 lines each. Bullets that are 3 or more lines look like paragraphs and won’t be read.

????? Focus on accomplishments, not responsibilities. The first line of each bullet should be a word like built, created, implemented, designed, architected, optimized, etc.

????? Quantify your accomplishments. Did you optimize something? Okay, then tell me by how much.

????? No summaries. They don’t tell me anything other than what position you’re applying for and I already know that.

????Submitting Your Resume

????Too many people stop with just one avenue. They apply once, and then figure that’s enough. Try all available avenues.

????? If you’re active on Github, Stack Overflow, etc, there’s a chance a recruiter will come to you. But there’s no reason to wait for that.

????? Apply online. It’s tough, but people do get their resumes selected that way.

????? Ask your friends. Do any work at Google? Or know someone who does? It’s a huge help if someone will refer you.

????? Try reaching out to Google engineers on Twitter, Quora, or other social media. Remember that your first contact with them is, effectively, a cover letter. Don’t just say “Hi, I’m interested in Google, will you refer me?” Reach out to them and tell them about some of the things you’ve done, and then link them to your resume.

????Again, this advice applies to all companies, and much of it to many positions as well.