Using GitHub to get a better job

Using GitHub to get a better job Paul McMahon Doorkeeperגࣜձࣾ
@pwim

@pwim 41% of GitHub Kaigi attendees connected GitHub account to
Doorkeeper 59% 41% Connected Not Connected

@pwim 21% of GitHub Kaigi Attendees have never made a
pull request 13% 33% 33% 21% 0 pulls 1 - 9 pulls 10 - 99 pulls 100 - 999 pulls

@pwim http://www.githubarchive.org/

@pwim Ideal Job for Developer • Valued by your company
• Do interesting work • Can freely contribute to open source on the job • Get paid well

@pwim Companies like this are looking for developers who •
Talented • Passionate • Self-motivated • Contribute to open source

@pwim Github is a portfolio site for developers

@pwim I’ve used GitHub to help companies ﬁnd developers

@pwim Recent Example - I helped a company who was
looking for • Internationally minded Japanese • Rails developer • Bonus: Spree experience

@pwim How I found them a developer • I organize
Tokyo Rubyist Meetup which connects Japanese and International Ruby developers • Looked through all members who had connected Github account • Contacted a single developer who had created a Spree plugin and blogged about studying English • They hired the developer

@pwim Having a good GitHub proﬁle can increase your job
opportunities

@pwim Most developers don’t have much public activity on GitHub

@pwim Invest 4 hours / month in your public proﬁle
• Give a lightning talk • Write a blog post • Make a pull request

@pwim I don’t have any open source contributions… • Don’t
ask for permission to contribute back a patch to library on the job • Try prerelease versions • Look for libraries that are heavily used, but don’t have so active contribution. E.g., not Rails but RABL

@pwim An Employer’s View of Your GitHub Proﬁle

@pwim 1. Your Proﬁle Photo • A professional looking photo
is best • Don’t have offensive photo

@pwim 2. Public Contributions • Regular contributions looks best! •
Try to have one or two commits a month

@pwim 3. Repositories contributed to • This is where an
employer is most likely to get excited • Unfortunately GitHub doesn’t make it easy to see contributions

@pwim I rolled my own page using GitHub API

@pwim 4. Popular repositories • Most developers aren’t the author
of a famous library: that’s ﬁne • Any code is better than no code

@pwim 5. Name • Use your real name • You
want potential employers to be able to ﬁnd your GitHub account

@pwim 6. Website • If you are a web developer,
you should have your own website • Ideally have own domain • Have information about yourself such as your job history

@pwim Thanks!

Using GitHub to get a better job

Using GitHub to get a better job

Paul McMahon

More Decks by Paul McMahon

Featured

Transcript