Using GitHub to get a better job

Dd24adb5a3a430fed83a33ed552fe1b5?s=47 Paul McMahon
June 01, 2014
1.6k

Using GitHub to get a better job

Presented at GitHub Kaigi

Dd24adb5a3a430fed83a33ed552fe1b5?s=128

Paul McMahon

June 01, 2014
Tweet

Transcript

  1. Using GitHub to get a better job Paul McMahon Doorkeeperגࣜձࣾ

    @pwim
  2. @pwim 41% of GitHub Kaigi attendees connected GitHub account to

    Doorkeeper 59% 41% Connected Not Connected
  3. @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
  4. @pwim http://www.githubarchive.org/

  5. @pwim Ideal Job for Developer • Valued by your company

    • Do interesting work • Can freely contribute to open source on the job • Get paid well
  6. @pwim Companies like this are looking for developers who •

    Talented • Passionate • Self-motivated • Contribute to open source
  7. @pwim Github is a portfolio site for developers

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

  9. @pwim Recent Example - I helped a company who was

    looking for • Internationally minded Japanese • Rails developer • Bonus: Spree experience
  10. @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
  11. @pwim Having a good GitHub profile can increase your job

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

  13. @pwim Invest 4 hours / month in your public profile

    • Give a lightning talk • Write a blog post • Make a pull request
  14. @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
  15. @pwim An Employer’s View of Your GitHub Profile

  16. @pwim 1. Your Profile Photo • A professional looking photo

    is best • Don’t have offensive photo
  17. @pwim 2. Public Contributions • Regular contributions looks best! •

    Try to have one or two commits a month
  18. @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
  19. @pwim I rolled my own page using GitHub API

  20. @pwim 4. Popular repositories • Most developers aren’t the author

    of a famous library: that’s fine • Any code is better than no code
  21. @pwim 5. Name • Use your real name • You

    want potential employers to be able to find your GitHub account
  22. @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
  23. @pwim Thanks!