谷歌軟件工程師

by YK Sugi

由YK Sugi

這是我曾經在Google擔任軟件工程師的簡歷。 (Here’s the résumé I used to get a job at Google as a software engineer.)

Hi everyone!

嗨，大家好！

On my programming-education YouTube channel called CS Dojo, many people have asked me to explain how I would go about writing a résumé for software engineer positions.

在我的編程教育YouTube頻道CS Dojo上 ，許多人要求我解釋如何編寫軟件工程師職位的簡歷。

So, here’s my article about it.

所以，這是我的文章。

In this article, I’m going to first walk you through the résumé I personally used to get a software engineer job at Google.

在本文中，我將首先向您介紹我個人用來在Google獲得軟件工程師職位的簡歷。

Then, I’m going to show you how I would change it today based on what I’ve learned since then.

然后，我將向您展示根據我從那時以來所學到的知識，今天將如何對其進行更改。

I’m also going to give you some general tips and advice on how to build your own software engineer résumé.

我還將向您提供有關如何構建自己的軟件工程師簡歷的一些一般性提示和建議。

I don’t really consider myself an expert on résumé writing, but hopefully I’ll be able to provide some insights based on my personal experience, as well as some research I’ve done to write this article.

我并不是真的認為自己是簡歷寫作的專家，但是希望我能夠根據我的個人經驗以及為撰寫本文所做的一些研究提供一些見解。

在這里查看我的簡歷。 (See my résumé here.)

If you’d like, you can download my résumé here as you follow along with this article.

如果您愿意，可以在閱讀本文的同時在此處下載我的簡歷。

結構 (The Structure)

First of all, let’s quickly go over what sections I have on my résumé. Then, we’ll go over each of them in turn to talk about them in more detail.

首先，讓我們快速瀏覽一下簡歷中的哪些部分。 然后，我們將依次介紹它們中的每一個，以更詳細地討論它們。

From the top, I have:

從頂部開始，我有：

• Experience
  經驗
• Education
  教育
• Technical Skills
  技術能力
• Other Skills
  其他的技能
• Awards
  獲獎情況
• Projects
  專案

經驗 (Experience)

This is the part where you include the work experience you want to show. You don’t have to include every single position you’ve ever held. That’s why I didn’t include my math tutoring position. It’s less relevant than my other, more technical positions.

這是您要顯示的工作經驗的一部分。 您不必包括您曾經擔任過的每個職位。 這就是為什么我不包括我的數學輔導職位。 它比我其他技術性職位更不重要。

If you have significant non-work experience that’s relevant, you can also include it here. For example, if you led a team for a coding competition, you might want to include it here. You could also include it in the project section, but it will stand out more in the experience section.

如果您有重要的非工作經驗，也可以在此處加入。 例如，如果您領導一個團隊參加編碼競賽，則可能希望將其包括在此處。 您也可以將其包括在“項目”部分中，但在“體驗”部分中會更加突出。

I have four positions in my experience section:

我的經驗部分有四個職位：

• Program Manager Intern at Microsoft
  微軟項目經理實習生
• Data Science Intern at Microsoft
  微軟數據科學實習生
• Founder and President at Data Science Club at UBC (University of British Columbia)
  UBC(不列顛哥倫比亞大學)數據科學俱樂部的創始人兼總裁
• Software Development Intern at Moneytree (a startup in Japan)
  Moneytree(日本的一家初創公司)的軟件開發實習生

Let’s take a look at the first position as an example.

讓我們以第一個位置為例。

In my résumé, it looks like this:

在我的簡歷中，它看起來像這樣：

The headline has the following structure:

標題具有以下結構：

<Title> at <Company>, <Location>, <Date> as in:

<公司>，<位置 >，<日期>的<標題>，如下所示：

Program Manager Intern at Microsoft, Redmond, WA, 5/2015–8/2015

5 / 2015–8 / 2015，華盛頓州雷德蒙德，微軟程序經理實習生

This is a fairly standard format.

這是一種相當標準的格式。

Then, below it, I have a description of what I did:

然后，在下面，我對所做的事情進行了描述：

I was responsible for designing and implementing a specific feature within Microsoft Dynamics CRM with developers and other PM’s. My responsibilities included the initial research, planning the project, designing the product, creating wireframes, and writing and executing on a spec.我負責與開發人員和其他PM一起在Microsoft Dynamics CRM中設計和實現特定功能。 我的職責包括初步研究，計劃項目，設計產品，創建線框以及根據規格編寫和執行。

我今天將如何改變 (How I would change it today)

When you write your résumé, don’t necessarily assume that the reader knows all the technical terms, especially company-specific ones. In the above description, I mentioned Microsoft Dynamics CRM, but many people are not familiar with it. So, I would change it to the following:

在編寫簡歷時，不一定要假設讀者知道所有技術術語，尤其是公司特定的術語。 在上面的描述中，我提到了Microsoft Dynamics CRM，但是許多人對此并不熟悉。 因此，我將其更改為以下內容：

I was in the team that was responsible for Microsoft Dynamics CRM, which is a piece of customer relationship management software. I led the effort to build a feature that allows users to easily keep track of business expenses. My responsibilities included the initial research, planning and managing the project, designing the feature, creating wireframes, and writing out our specs.我曾在負責Microsoft Dynamics CRM的團隊中工作，這是一款客戶關系管理軟件。 我努力構建了一個功能，使用戶可以輕松跟蹤業務費用。 我的職責包括初步研究，計劃和管理項目，設計功能部件，創建線框以及編寫規格。

Note that in addition to clarifying the term Microsoft Dynamics CRM, I added a quick explanation about what exactly I built.

請注意，除了闡明術語Microsoft Dynamics CRM之外 ，我還添加了關于我實際構建的內容的快速說明。

Now, let’s take a look at another position I have in the experience section.

現在，讓我們看看我在體驗部分中的另一個職位。

The headline is: Founder and President at Data Science Club at UBC, Vancouver, BC, 10/2013–5/2014

標題是： 卑詩省溫哥華市，UBC數據科學俱樂部的創始人兼總裁，10 / 2013–5 / 2014

I have three bullet points below it:

我下面有三個要點：

• Responsible for acquiring more than 120 members
  負責獲取120多名成員
• Organized meet-ups to exchange our ideas on data science
  有組織的聚會來交流我們關于數據科學的想法
• Formed a team of several students to work on a machine learning competition on Kaggle
  組建了一個由幾個學生組成的團隊，在Kaggle上進行機器學習比賽

First, note the use of bullet points here. Sometimes it makes it easier to read and skim the résumé.

首先，在這里注意要點的用法。 有時，它使閱讀和瀏覽簡歷變得更加容易。

Also, note how I used a specific number in the first bullet point — Responsible for acquiring more than 120 members. Using a number often makes your accomplishment clearer. Of course, you don’t always have to use a number. Use it when it makes sense.

另外，請注意我在第一個要點中如何使用特定數字- 負責獲取120個以上的成員 。 使用數字通常會使您的成就更清晰。 當然，您不必總是使用數字。 合理使用它。

我今天將如何改變 (How I would change it today)

I wouldn’t make any major edits in this one. Only minor grammatical edits.

在這一部分中，我不會做任何重大修改。 僅進行少量的語法編輯。

教育 (Education)

This is, of course, the part where you list your relevant education.

當然，這是列出相關教育的部分。

Here’s what I have:

這是我所擁有的：

For each university, I have the university name, location, a type of degree (BS — Bachelor’s of Science here), a major, the expected graduation date, as well as the GPA listed.

對于每所大學，我都有大學名稱，位置，學位類型(這里是BS –理學學士學位)，專業，預計畢業日期以及列出的GPA。

關于GPA (About GPA)

According to an article on CareerCup, the general rule of thumb is to show GPA only if it’s higher than 3.0 out of 4.0. I agree with this recommendation.

根據CareerCup上的一篇文章 ，一般的經驗法則是僅在GPA高于4.0時才顯示GPA。 我同意這項建議。

我今天將如何改變 (How I would change it today)

I would keep this section as-is. Let’s go to the next section.

我將保持本節不變。 讓我們進入下一部分。

技術能力 (Technical Skills)

Here’s what I listed under this section on my résumé:

這是我在簡歷中此部分下列出的內容：

• Wireframing: Balsamiq, Microsoft PowerPoint

  線框圖： Balsamiq，Microsoft PowerPoint

• Visual Design: Adobe InDesign, Photoshop, Illustrator

  視覺設計： Adobe InDesign，Photoshop，Illustrator

• Statistical Analysis: R

  統計分析： R

• Machine Learning: Python with NumPy and Pandas, Ruby, Spark (prior experience)

  機器學習： 帶有NumPy和Pandas的Python，Ruby，Spark(經驗豐富)

• Programming Technologies: SQL, MATLAB, Ruby on Rails, Java

  編程技術： SQL，MATLAB，Ruby on Rails，Java

• Programming Technologies, front end: JavaScript, HTML/CSS, LaTeX

  編程技術，前端： JavaScript，HTML / CSS，LaTeX

• Version Control: Git, GitHub, Bitbucket

  版本控制：Git，GitHub，Bitbucket

I would say that I listed way too many things here. I would cut it down to just these two:

我會說我在這里列出了太多的東西。 我將其簡化為以下兩個：

• Data Science: R, Python with NumPy and Pandas, Spark (prior experience)

  數據科學： R，帶有NumPy和Pandas的Python，Spark(經驗豐富)

• Programming Technologies: SQL, MATLAB, Ruby, Ruby on Rails, Java, JavaScript, HTML/CSS

  編程技術： SQL，MATLAB，Ruby，Ruby on Rails，Java，JavaScript，HTML / CSS

I would only list these two, because the other skills were less relevant in this case.

我只列出這兩個，因為在這種情況下其他技能不太重要。

Also, note how I put Spark (prior experience) to show that I have some experience with Spark, but I’m not proficient with it.

另外，請注意我如何使用Spark(以前的經驗)來表明我對Spark有一定的經驗，但是我并不精通它。

其他的技能 (Other Skills)

You can use this section if you want to include other relevant skills. I included Japanese and public speaking in this section.

如果要包括其他相關技能，可以使用此部分。 我在本節中包括了日語和公眾演講。

我今天將如何改變 (How I would change it today)

I would cut this section out entirely since it’s not that relevant to the software engineer position I was applying for.

我將本節全部刪掉，因為它與我申請的軟件工程師職位無關。

獎項與項目 (Awards and Projects)

Include relevant awards and projects in these sections.

在這些部分中包括相關的獎項和項目。

The word “relevant” is important here. If you won second place in a regional karate championship, for example, it’s probably not that relevant.

“相關”一詞在這里很重要。 例如，如果您在區域空手道錦標賽中獲得第二名，那可能就沒那么重要了。

However, you might want to include it if it’s really impressive — for example, competing on a national or international level with karate.

但是，如果它確實是 令人印象深刻-例如，與空手道在國家或國際層面上競爭。

I have one award and three projects on my résumé.

我的簡歷中獲得了一個獎項和三個項目。

獎項 (The award)

Here is the award I have on my résumé:

這是我的簡歷所獲得的獎項：

TELUS / IEEE Student Innovation Challenge

TELUS / IEEE學生創新挑戰賽

我將如何改變 (How I would change it)

I would clarify my wording a bit so it’s easier to read. Maybe something like:

我會澄清一下措辭，以便于閱讀。 也許像這樣：

TELUS / IEEE Student Innovation Challenge

TELUS / IEEE學生創新挑戰賽

專案 (Projects)

Now, in addition to this award, I listed three projects which I thought would be the most impressive.

現在，除了這個獎項之外，我還列出了三個我認為最令人印象深刻的項目。

One of them was this one:

其中之一就是這個：

YamBomb! , August 2014

炸彈！ ， 2014年8月

Note how I used a specific number (70 users) here as well. I also mentioned the tech I used for this project — Ruby on Rails and the Yammer API. (Yammer is a website by Microsoft, and it’s kind of like Facebook that’s used to communicate internally within a company.)

請注意，我也是如何在此處使用特定號碼(70個用戶)的。 我還提到了我用于該項目的技術-Ruby on Rails和Yammer API。 (Yammer是Microsoft的網站，有點像Facebook，它在公司內部用于內部通信。)

我現在將如何更改 (How I would change it now)

No major edits here.

這里沒有重大修改。

我今天將如何編輯整個簡歷 (How I would edit the entire résumé today)

Now, there is one major issue with this résumé I used back then — it was too long. It’s about 2 pages, and ideally, it should be one page.

現在，我當時使用的這個簡歷存在一個主要問題-太長了。 大約2頁，理想情況下應該是一頁。

Let’s see if we can get it down to a single page.

讓我們看看是否可以將其簡化為單個頁面。

I was, in fact, able to get it down to one page. Here are some of the major changes I made:

實際上，我能夠將其縮小到一頁。 以下是我進行的一些主要更改：

• I took off Founder and President at Data Science Club at UBC from the experience section. It’s good, but less relevant than the other ones.

  我從經驗部門接任了UBC數據科學俱樂部的創始人兼總裁 。 很好，但與其他主題的相關性較差。

• I took off Suffolk University from the education section. It’s not too relevant since I had already transferred out of it.

  我從教育部門起飛了薩福克大學 。 因為我已經轉移了它，所以它不太相關。

• I combined the awards and projects sections into just Projects, and listed only 2 projects.

  我將獎項和項目部分合并為Projects ，僅列出了2個項目。

Now, what I omitted would’ve been perfectly good information to show on my résumé. It’s just that they were less impressive and relevant than the other things I listed.

現在，我所忽略的將是在履歷表上顯示的非常好的信息。 只是它們沒有我列出的其他東西那么令人印象深刻和相關。

Just by omitting those pieces of information, my résumé became much easier and quicker to read.

只需省略這些信息，我的簡歷就變得更容易，更快捷地閱讀。

好的，這是我的簡歷的編輯后的一頁版本： (Okay, here’s the edited, one-page version of my résumé:)

• PDF

  PDF格式

• Word (.docx)

  Word(.docx)

• Pages (.pages)

  頁數(.pages)

Feel free to use it as a template.

隨時使用它作為模板。

現在，這里是一些關鍵要點。 (Now, here are some key takeaways.)

1.把自己放在招聘者/招聘經理的鞋子上。 (1. Put yourself in the shoes of the recruiter/hiring manager.)

Don’t automatically assume that they will be familiar with every technical term you are familiar with. Think about what’s commonly used and not so commonly used in your particular field.

不要自動假設他們會熟悉您熟悉的每個技術術語。 想一想在您的特定領域中哪些是常用的，哪些不是常用的。

Also, keep refining your paragraphs so they are easy to read. Use short sentences. Clarify what’s not clear. It’s probably a good idea to have a friend of yours read it for you to make sure everything is clear.

此外，請不斷完善您的段落，以使其易于閱讀。 使用簡短的句子。 澄清不清楚的地方。 最好讓您的一個朋友讀一遍，以確保一切都清楚。

2.忽略任何不太相關的內容。 (2. Omit anything that’s not too relevant.)

Speaking Japanese is a good skill, but it wasn’t relevant for the particular position I was applying for. So, I didn’t really have to list it.

說日語是一種很好的技能，但與我申請的特定職位無關。 因此，我并沒有真正列出它。

3.與數量無關。 關于質量。 (3. It’s not about the quantity. It’s about the quality.)

If you show 4 projects instead of 2 projects, is it always better? Well, not necessarily.

如果顯示4個項目而不是2個項目，它總是更好嗎？ 好吧，不一定。

Having more information on your résumé clutters it out, and it makes it harder to find important information.

在簡歷中獲取更多信息會使其雜亂無章，這使查找重要信息變得更加困難。

但是，您可能會說-您仍然沒有做任何一件事情就得到了這份工作！ (But, you might say — you still got the job without doing any of these!)

Yes, that’s true. I think it’s important to build an easy-to-read résumé, but it’s even more important to build strong skills and experience first to show on your résumé.

是的，這是真的。 我認為構建易于閱讀的簡歷很重要，但更重要的是首先構建強大的技能和經驗以在簡歷中顯示。

一些其他提示/建議 (Some additional tips/advice)

我應該首先列出教育程度還是工作經歷？ (Should I list education first, or work experience first?)

The general rule of thumb is, list whichever one’s more impressive/relevant.

一般的經驗法則是列出最令人印象深刻/相關的內容。

For me, I had some good experience with Microsoft, which was more impressive than my education. That’s why I listed it first.

對我來說，我在Microsoft方面有一些很好的經驗，這比我受過的教育更令人印象深刻。 這就是為什么我首先列出它。

If you’re still in school, my default choice would be to show your education first. But if anything from your experience stands out, then put the experience section first.

如果您還在上學，我的默認選擇是首先顯示您的學歷。 但是，如果您的經驗中有什么與眾不同，則將“經驗”部分放在第一位。

我應該包括我的電子郵件地址，電話號碼和位置嗎？ (Should I include my email address, phone number, and location?)

You should always include your email address, but other than that, it’s up to you.

您應該始終包括您的電子郵件地址，但除此之外，這取決于您。

I only included my email address in my résumé to keep it simple. However, if you want to show that you’re in a certain location, or if you want to include your phone number, go ahead and do so as well.

為了簡化起見，我只在簡歷中包含了我的電子郵件地址。 但是，如果您想表明自己在某個位置，或者想要包括您的電話號碼，請繼續進行。

如果我還沒有那么多經驗可以顯示呢？ (What if I don’t have that much experience to show on my résumé yet?)

Basically, you should think about all the skills and experience you’ve gained up to this point, and think about how they might lead to the next step.

基本上，您應該考慮到現在為止獲得的所有技能和經驗，并考慮它們如何引導您邁向下一步。

As an example, here’s how I did it:

例如，這是我的操作方法：

• I had next to no experience a few years before I applied to Google.
  在申請Google幾年之前，我幾乎沒有任何經驗。
• So, I built a simple website with Ruby on Rails, which I learned on my own.
  因此，我使用Ruby on Rails建立了一個簡單的網站，這是我自己學習的。
• Using this project, I got my first technical internship in Japan.
  通過這個項目，我在日本獲得了第一筆技術實習。
• Using this, combined with my statistics background, I got a data science internship at Microsoft.
  結合我的統計背景，我在Microsoft獲得了數據科學實習機會。
• Using that experience and the connections I built there, I got my second internship at Microsoft.
  利用這些經驗以及在那建立的聯系，我獲得了第二個微軟實習機會。
• Using all of these, I got my full-time software engineer job at Google.
  使用所有這些，我在Google獲得了專職軟件工程師的工作。

I like to think of it sort of like a snowball.

我喜歡把它想像成一個雪球。

It might be just tiny at the beginning, but if you keep building on it, it will just keep growing.

一開始它可能只是很小，但是如果您繼續在此基礎上發展，它將不斷增長。

以下是編寫軟件工程師簡歷的一些其他資源： (Here are some additional resources for writing a software engineer résumé:)

• There’s a nice overview about this topic on CareerCup here.

  有關于CareerCup這個話題很好的概述這里 。

• My friend Zhia Hwa Chong, who is a software engineer at Twitter, has a nice article about it here.

  我的朋友Zhia Hwa Chong是Twitter的一名軟件工程師，在這里有一篇很好的文章 。

• Quincy Larson, Teacher / Founder of freeCodeCamp, also has a nice article on this topic here.

  昆西拉爾森 ，老師/ freeCodeCamp的創始人，也有關于這個主題一個很好的文章在這里 。

Okay, good luck, and thank you as always for reading my article!

好的，祝您好運，并一如既往地感謝您閱讀我的文章！

If you have any questions about this or anything else, please feel free to let me know in a comment below or on Instagram or Twitter (@ykdojo on both).

如果您對此有任何疑問，請隨時在下面的評論中或在Instagram或Twitter (兩者均為@ykdojo)上讓我知道。

翻譯自: https://www.freecodecamp.org/news/heres-the-resume-i-used-to-get-a-job-at-google-as-a-software-engineer-26516526f29a/

谷歌軟件工程師

總結

以上是生活随笔為你收集整理的谷歌软件工程师_这是我曾经在Google担任软件工程师的简历。的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯，歡迎將生活随笔推薦給好友。