Slide 1

Slide 1 text

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

Slide 2

Slide 2 text

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

Slide 3

Slide 3 text

@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

Slide 4

Slide 4 text

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

Slide 5

Slide 5 text

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

Slide 6

Slide 6 text

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

Slide 7

Slide 7 text

@pwim Github is a portfolio site for developers

Slide 8

Slide 8 text

@pwim I’ve used GitHub to help companies find developers

Slide 9

Slide 9 text

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

Slide 10

Slide 10 text

@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

Slide 11

Slide 11 text

@pwim Having a good GitHub profile can increase your job opportunities

Slide 12

Slide 12 text

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

Slide 13

Slide 13 text

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

Slide 14

Slide 14 text

@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

Slide 15

Slide 15 text

@pwim An Employer’s View of Your GitHub Profile

Slide 16

Slide 16 text

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

Slide 17

Slide 17 text

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

Slide 18

Slide 18 text

@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

Slide 19

Slide 19 text

@pwim I rolled my own page using GitHub API

Slide 20

Slide 20 text

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

Slide 21

Slide 21 text

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

Slide 22

Slide 22 text

@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

Slide 23

Slide 23 text

@pwim Thanks!