mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-01-25 23:11:02 +08:00
Merge pull request #3946 from kylepeng93/master
"20160225 How to add open source experience to your resume is "is translated by kylepeng93 下回记得在文末的“译者 ID”处写上你的 ID。
This commit is contained in:
Xingyu.Wang
commit
ee0e1ad5cf
@ -1,92 +0,0 @@
|
||||
kylepeng93 is translating!!!
|
||||
How to add open source experience to your resume
|
||||
==================================================
|
||||
|
||||
|
||||
|
||||
|
||||
In this article, I'll share my technique for leveraging open source contributions to stand out as a great candidate for a job in the technology field.
|
||||
|
||||
No goal can be accomplished without first being set. Before jumping into a new commitment or spending the evening overhauling your resume, it pays to clearly define the traits of the job you're seeking. Your resume is a piece of persuasive writing, so you have to know your audience for it to reach its full potential. Your resume's audience is anyone with the need for your skills and the budget to hire you. When editing, read your resume while imagining what it's like to be in their position. Do you look like a candidate that you would hire?
|
||||
|
||||
I personally find it helpful to make a list of the key traits that the ideal candidate for my target job displays. I gather this list from a combination of personal experience, reading job postings, and asking colleagues in similar roles. LinkedIn and conferences are great places to find people happy to offer this sort of advice. Many people enjoy talking about themselves, and inviting them to tell part of their own story to help you expand your knowledge makes everyone feel good. As you talk to others about their career paths, you'll gain insights not only into how to land the jobs you want, but also into which traits or behaviors correspond to ending up in situations you'd rather avoid.
|
||||
|
||||
For example, the list of key traits for a junior role might look like this:
|
||||
|
||||
### Technical:
|
||||
|
||||
- Experience with CI, Jenkins preferred
|
||||
|
||||
- Strong scripting background in Python and Ruby
|
||||
|
||||
- Familiarity with Eclipse IDE
|
||||
|
||||
- Basic Git and Bash
|
||||
|
||||
### Personal:
|
||||
|
||||
- Self-directed learner
|
||||
|
||||
- Clear communication and documentation skills
|
||||
|
||||
- Experience working on a multi-person development team ("team player")
|
||||
|
||||
- Familiarity with issue tracker workflow
|
||||
|
||||
### Apply anyway
|
||||
|
||||
Remember, you don't have to meet every single criterion listed in a job description to get an interview.
|
||||
|
||||
The job description describes whoever left the role, and if you start out knowing everything you've likely signed yourself up for a few years that don't challenge or expand your skill set. If you're nervous about missing a particular technology on the list, do some research into it to see whether comparable skills from another experience would apply. For example, someone who's never used [Jenkins][1] might still understand the principles of continuous integration testing from working on a project that uses [Buildbot][2] or [Travis CI][3].
|
||||
|
||||
If you're applying at a larger company, they probably have an entire department and comprehensive screening process to make sure they don't hire any candidate unable to succeed in a role. That means it's your job to apply and their job to decide whether to reject you. Don't prematurely reject yourself from the job by refusing to apply.
|
||||
|
||||
Now you have an idea of what job you want and what skills you'll need to impress your interviewers. The next steps to take will vary based on how much experience you've already got.
|
||||
|
||||
### Tailoring existing involvement
|
||||
|
||||
Start by making a list of all the projects you've been involved with in the past few years. One way to get a quick list of things you've worked on lately is to navigate to the **Repositories** tab of your GitHub profile and filter the list by clicking on **Forks**. Additionally, look down your [Organizations][4] list for places you might have been engaging in leadership roles. If you already have a resume, make sure you've included everything from these lists under experience.
|
||||
|
||||
Consider any IRC channel where you have special permissions as a potential leadership experience. Check your Meetup and Eventbrite accounts and add any events that you organize or volunteer at to your list. Skim your calendar for the past year and note any volunteering, mentoring, or public speaking engagements.
|
||||
|
||||
Now for the hard part: Map the list of required skills onto the list of experiences. I like to assign a letter or number to each trait needed for the job, then mark the same symbol next to every piece of experience or involvement where you demonstrated the trait. When in doubt, claim it anyway—your problem is more likely a reluctance to brag than actual incompetence.
|
||||
|
||||
This is the point in the process at which resume writers are often fettered by reluctance to risk overselling their own skills. It often helps to re-frame the question as: "Did someone who organized a meetup show leadership and planning skills?" Rather than: "Did I personally show these skills when I organized that meetup?".
|
||||
|
||||
If you've been sufficiently thorough at figuring out where your free time has gone for the past year or two and you code a lot, you might now be facing a surprising problem: Too many items to fit on a single-page resume! If anything on your list of experiences didn't demonstrate any of the skills you're trying to showcase, cross it off. If an item demonstrates few skills and you don't have any stories that you enjoy telling about it, cross it off. If this abridged list of things you've done still won't fit in the format of a resume, prioritize the experiences from which you gained a relevant story or extensive experience with a desired technology.
|
||||
|
||||
At this point, it should be obvious if you need a better piece of experience to hone a particular skill. Consider using an issue aggregator like OpenHatch to find an open source project where you build and practice your skills with the tool or technology that you're missing.
|
||||
|
||||
### Make your resume beautiful
|
||||
|
||||
A resume's beauty comes from conciseness, clarity, and layout. Each piece of experience should be accompanied by enough information for a reader to immediately know why you included it, but no more. Each type of information should be formatted consistently throughout the document—it's distracting to have some dates italicized or right-aligned and others not.
|
||||
|
||||
Typeset your resume using a tool that makes these goals easy to achieve. I enjoy using [LaTeX][5], since its macro system makes visual consistency easy and most interviewers recognize it immediately. Your tool of choice might be [LibreOffice][6] or HTML, depending on your skills and how you want to distribute your resume.
|
||||
|
||||
Remember that a digitally submitted resume might be scanned for keywords, so it can help to use the same acronyms as the job posting when describing your experiences. To make your resume easy for your interviewer to use, place the most important information first.
|
||||
|
||||
Coders often struggle to quantify balance and layout when typesetting a document. My favorite technique for stepping back and assessing whether my document's whitespace is in the right place is to fullscreen the PDF or print it out, then look at it in a mirror. If you're using LibreOffice Writer, save a copy of your resume then change the font to that of a language you can't read. Both of these techniques forcibly pull you out of reading the content, and allow you to see the overall layout of the document in a new light. They take you from a "That sentence is poorly worded!" critique to noticing things like "It looks funny to have only a single word on that line."
|
||||
|
||||
Finally, double check that your resume displays correctly in the media where it will be seen. If you're distributing it as a web page, test it at different screen widths in multiple browsers. If it's a PDF, open it on your phone or a friend's computer to make sure all the fonts it needs are available.
|
||||
|
||||
### Next steps
|
||||
|
||||
Finally, don't let the content that you worked so hard on for your resume go to waste! Mirror it to your LinkedIn account—complete with the buzzwords from the job posting—and don't be surprised if recruiters start reaching out to you. Even if the jobs they're describing aren't a good fit right now, you can leverage their time and interest to get feedback on what's working well about your resume and what isn't.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/business/16/2/add-open-source-to-your-resume
|
||||
|
||||
作者：[edunham][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/edunham
|
||||
[1]: https://jenkins-ci.org/
|
||||
[2]: http://buildbot.net/
|
||||
[3]: https://travis-ci.org/
|
||||
[4]: https://github.com/settings/organizations
|
||||
[5]: https://www.latex-project.org/
|
||||
[6]: https://www.libreoffice.org/download/libreoffice-fresh/
|
||||
@ -0,0 +1,56 @@
|
||||
怎样将开源经历添加到你的简历中去
|
||||
==================================================
|
||||
|
||||
在这篇文章中，我将会分享我的一些方法，目的是让你因为曾经为开源事业作出贡献的经历使得你在技术领域的求职中脱颖而出。
|
||||
凡事预则立，不预则废。在你即将进入一个新的领域或者正准备花费整个晚上来彻底完善你的简历之前，先来定义你正在寻找的工作的特征是值得的。你的简历是一张有说服力的作品，因此你必须了解你的观众，从而让它发挥出所有的潜力。看你简历的可能是任何需要你的技能并且恰好能在预算之内聘用你的人。当编辑简历的时候，读一读你的简历上的内容，同时想象一下它们最应该被书写的位置。你看起来像是一个你将会聘用的候选人吗？
|
||||
|
||||
在我看来，我发现对于我所要求的目标职位的所有理想候选人，针对他们每个人的特点列出一张清单有时候是很有帮助的。我将他们每个人的特点清单合并到他们的个人经历中，并阅读工作记录，然后以同样的角色询问同事们。人际关系网和会议是很好的地方去寻求一些乐意提供这种建议的人。一些人喜欢谈论他们自己，并且邀请他们去讲述他们自己的故事的一部分来帮助你去拓展你的知识面，通过这样方式可以使每个人感觉更好。当你和其他人谈论他们的职业路线时，你不仅将会明白怎样去得到你想要从事的工作，而且还能知道你应该避免哪些容易让你失去工作机会的情况和行为。
|
||||
例如，对于一个差劲的角色，有关于他的关键特性列表可能看起来像下面这样：
|
||||
###技术：
|
||||
- 拥有计算机从业方面的经验，更加容易受到Jenkins的青睐。
|
||||
- 深厚的脚本编写背景，如Python和Ruby
|
||||
- 精通eclipse的使用
|
||||
- 基本的git和bash知识
|
||||
###个人而言：
|
||||
- 自我学习者
|
||||
- 良好的交流和文档技巧
|
||||
- 在团队开发方面富有经验
|
||||
- 精通事件捕捉工作流
|
||||
###以任意方式应用
|
||||
记住，你没有必要为了得到一份工作而去满足上面的工作描述列表中列出的每个标准。工作细节描述了任何人都可以离开这个角色，如果你已经知道你即将签约并为之工作几年的公司的全部信息，并且这份工作并不会让你觉得有什么挑战性，或者要求你去拓展你你的技能。如果你对你无法满足清单上的技能列表而感到紧张，那么检查一下自己是否有来自其他经历并能与之媲美的技能。
|
||||
例如，即使有些人从来没有使用过Jenkins，那他也可能从之前使用过Buildbot或者travis CI的项目经验中明白持续集成测试的原则。
|
||||
如果你正在申请一家大型公司，而他们可能拥有一个专门的部门和一套完整的筛选过程来确保他们不会聘用任何不能胜任职位的候选人。也就是说，在你求职的过程中，你所能做的只是提交申请，而决定是否拒绝你是公司管理层的工作。不要过早的将工作拒之门外。
|
||||
现在你已经知道了你的任务是什么，并且还知道你将需要哪些技能去完成这次面试。下一步要做的取决与你已经获取到的经验。
|
||||
### 制造已经存在的事物之间的关联
|
||||
列出一张你过去几年曾经参与过的所有项目。下面是一条快速得到这张清单的方式，生成一个跳转到你的github上的库的导航器，但是需要过滤掉你从其他地方复制过来的项目。除此之外，检查下你的清单上是否有曾经处于领导地位的项目。如果你已经有了一份简历，那么请确保你已经将你所有的经历都列在了上面。
|
||||
考虑下任何一个你曾经作为一个潜在的领导经历并拥有过特权的IRC项目。检查你的会唔和聚会并将你曾经组织过或者作为志愿者参与过的事情添加到你的清单上面。略过你前几年的日程并且标注所有志愿行动或者有作为导师的经历又或者有接触过的公共演讲.
|
||||
现在进入了比较艰难的环节了，将清单上列出的必备技能与个人经历列表上的内容一一对照，我喜欢给工作需要的每个特性用一个字母或者数字作为标记，然后在每一段你经历或参与过并表现出了某一特性的地方标记相同的符号。当你产生怀疑的时候，无论如何也要加上它，尽管这样做更像是在吹嘘，但也好过显示出你的无能。
|
||||
在我们写简历的时候常常被这样的情况所困扰，就是我们不愿冒着过分吹嘘自己的技能的风险。这通常会帮助我们重新考虑这个问题，比如我们会考虑那些组织了会晤的人会表现出更好的领导才能和计划技巧吗？而不是当我组织这个会晤的时候我是否展示出了这些技巧。
|
||||
如果你已经充分了解了你在过去的几年里的业余时间都是怎么度过的或者你写了很多代码，那么你可能现在正面临着一个令人奇怪的问题，你已经拥有了太多的经验以至于一张纸的简历已经无法容纳下这些经验了。那么，如果那些列在你的清单上的经验无法证明你尝试去表现的任何技能的话，那么请扔掉它们吧。如果这份已经被缩短的简历清单上的内容仍然超过一张单页纸的容量的话，那么将你的经验按照一定的优先级排序，例如根据你获得了相关的故事或丰富的经验与所需的技术。
|
||||
在这一方面，显而易见，如果你想要磨练一个独特的技能，那么你就需要一个不错的经历。考虑使用一个类似OpenHatch的问题聚合器，并用它来寻找一个通过使用你从没使用过的工具和技术来锻炼你的技能的开源项目。
|
||||
让你的简历更加漂亮
|
||||
一份简历是否美观取决于它的简洁度，清晰度和布局。每一段经历都应该通过足够的信息来展示给读者并让他们立刻就能明白为什么你要将它包含进去，而且恰到好处。每种类型的信息都应该使用一致的文档格式来表示，一份含有斜体格式或者右对齐格式的或者其他与整体风格不协调的数据绝对会让看的人十分反感。
|
||||
使用工具来给你的简历排版会使之前设定的目标更加容易实现。我喜欢使用LaTeX，因为它
|
||||
的宏系统能够使可视化一致性变得更加容易，并且大量的面试官都能一眼就认出他。你的工具的选择可能是LibreOffice或者HTML，这取决于你的技能和你希望怎样去发布你的简历。
|
||||
记住一点，一份以数字方式提交的简历可以通过关键字被浏览到。因此，当你需要描述你的工作经历的时候使用和工作招聘告示一样的英文缩写对你的求职会有很大的帮助。为了让你的简历更加容易被面试官所使用，首先就要放上最重要的信息。
|
||||
程序员通常难以在为文档排版时量化平衡和布局。我最喜欢的技术是回退并评估我的文档的空格是否处于正确的位置，而这样做的目的就是我的PDF可以全屏显示或者打印出来，然后
|
||||
在镜像里面查看它。如果你正在使用LibreOffice Writer，保存一份你的简历的副本，然后将你的简历中的字体换成一种你无法阅读的语言。这两种技术都强制将你从阅读的内容中脱离出来，让你以一种新的方式查看文档的整体布局。他们把你从一个”那句话措辞不当！”对注意到的事物的批评，比如“在这条线上只有一个字，看起来很有趣”。
|
||||
最后，再次检查你的简历是否在它将要的展示的多媒体上看起来完全正确。如果你以网页的形式发布它，那么在不同屏幕大小的浏览器中测试它的效果。如果它是一份PDF文档，那么在你的手机或者你的朋友的电脑上面打开它，并确保它所需要的字体都是可用的。
|
||||
接下来的步骤
|
||||
最后，不要让你辛苦做出来的简历被浪费了，利用你的LinkedIn帐号把它做成一个镜像。当招聘人员找到你的时候也不要感到奇怪。尽管他们描述的工作内容并不是恰好适合你，但是你可以利用他们的时间和兴趣来得到关于你的简历中有哪些地方好与不好的反馈信息。
|
||||
--------------------------------------------------------------------------------
|
||||
via: https://opensource.com/business/16/2/add-open-source-to-your-resume
|
||||
|
||||
作者：[edunham][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/edunham
|
||||
[1]: https://jenkins-ci.org/
|
||||
[2]: http://buildbot.net/
|
||||
[3]: https://travis-ci.org/
|
||||
[4]: https://github.com/settings/organizations
|
||||
[5]: https://www.latex-project.org/
|
||||
[6]: https://www.libreoffice.org/download/libreoffice-fresh/
|
||||
Loading…
Reference in New Issue
Block a user