Today we’re rolling out Phase 1 to our GitHub Jobs search engine. Under your Account Settings page, there’s a new tab called Job Profile.
There you’ll see a simple text area to paste in your resume (or whatever you’d like really), along with a checkbox to confirm you’re available for hire. This is an opt-in program, if you’re not looking for work there’s nothing to do.

We think the code you’ve put on GitHub is an extremely valuable tool in finding you a great place to work, so now is the time to dust off the code you’re afraid to push and get people excited about it. Also, make sure you’ve filled out your profile information: your name, location, blog/website, and email. All of that information is going to be help you find work.
Phase 2 of the GitHub Jobs rollout is to expose this information via a private search interface, but we need to know if you’re available for hire first. Please note that none of the data you enter will leave GitHub.
Step 1 to finding a new job is just a checkbox away!


s/may sure/make sure/
s/be help you/help you/
Excellent idea!
great idea..
Killer idea!
Do you plan to charge employers for running searches?
"We think the code you’ve put on GitHub is an extremely valuable tool in finding you a great place to work"
Nice, couldn't agree more.
whohoo great! that was my idea too ...
http://support.github.com/discussions/feature-requests/50-job-board-for-githubbers
let's roll phase 2 on first year anniversary! :)
it would great if you could get a preview
It says: "Please note that none of the data you enter will leave GitHub." If that's the case, how will someone find it and give me a job? Or is this only for getting jobs working for you?
@rjumunro The implication here is that it'll be exposed to people searching for you, through a private search interface that they'll (probably) bill companies and recruiters to use.
A little bit like Working with Rails, but hopefully with a pay barrier to prevent recruiter spam. More akin to StackOverflow's careers CV section.
+1 on the preview button. i never get markdown 100% right on the first try.
This is fantastic. However, I second the idea about having a paywall to minimize span from recruitment agencies.
I always get Markdown right first try (ahem), but I usually tweak it for what feels like several hours. Also, frankly I'm happy to have my job profile public.
I know there's a lot of support in the comment so far, but I don't like this. I don't like this, because it's a distraction from what I come here to do.
I understand that GitHub is a lot of things to a lot of people, but those things are heavily focused around one concept: hosting code. Everything that we have so far: graphs, issues, gists; they're all about enabling the coder to perform their work in a better way.
Jobs seems like a somewhat bizarre add-on to this mentality. I like the fact that you're trying to help a certain group, but I don't understand why this is being incorporated into the main site instead of, say, being a separate sub-site, a la Haystack. Why do I have a "Job Profile" section in my account settings? It's annoying, an empty box waiting to be filled out, but already it feels appendicital, it feels like bloat.
I guess what I'm saying is, don't cater to a fringe group at the expense of the average user. Having said that, I simply don't know what the breakdown is for people looking for work versus people who aren't, so maybe I'm being unfair.
I love GitHub, I continue to enjoy working with it, and I say this because I love everything that it stands for and don't want to see it turn into a convoluted hybrid of an idea.
I have seen some employers ask for a prospect's GitHub account name in order to view their code, so it just seems like a natural progression.
For those of you wanting markdown previews... try this. If all goes well with the javascript parser, live preview should start showing up on the site everywhere we use GFM.
@Aupajo perhaps I'm one of those "fringe users", but the first thing I've done when applying for a job is link to my GitHub profile. I feel my code speaks volumes about me that I cannot do myself. I feel that the last two jobs I've landed was mostly thanks to my code on GitHub (yes, the second job was with GitHub, but I still think my code helped immensely).
I agree with @Aupajo. Github is about social code hosting not a recruitment tool or a way to land your next big thing. The latter two are byproducts.
If anything, build a separate app using Github's API to handle the recruitment tools and resume stuff.
WONDERFUL
Hmm, now if I could link my StackOverflow and GitHub profiles...
@tekkub By all means. I'm not expressly opposed to the idea, just the choice to integrate it into the main site.
I indeed agree with @Aupajo and @revans about this. Github should indeed be all about the code. There is definately something behind the 'Do one thing and do it well', and though that in the end means having to use lots of different systems, i indeed have no problem with having to link them all together.
IMHO, this is just more scope creep, or god forbid 'feature bloat' that in the long run will just make github's job more complex. and i thought it was complex enough already...
@lenary : I'm not sure the unix philosophy "one task, one app" apply to something like a social network. Since a social network is meant to be "a place where to live", it seems quite natural to me that it has many features. Or github shouldn't be a social network at the first place, just an hosting system for git repositories (I like it as it is now, personally).
@pjhyett : may you consider adding a checkbox "Available for freelancing", too?
I don't get why people think this feature is antithetical. GitHub is all about "social code hosting." Finding a job is a social process. Code is an important part of that process for programmers. This adds another social, code-focused element to GitHub.
@gaustin, it's not that there isn't a need or doesn't make sense for Github to pursue. It's the way in which it is pursued. IMHO, the github application itself is social code hosting. That's how it has been branded. It works really well in the area.
Adding recruitment tools and resumes to github itself doesn't make sense as it pollutes the purpose of this specific app. However, that doesn't mean the whole idea should not be pursued. Instead, building a new application, that focuses on recruitment, resumes, etc and leverages github's API, seems to me to be the smarter choice.
Encapsulating an idea into an app and keeping it "real" instead of throwing all your ideas all into one app, makes the most sense - at least to me.
Again, it's not the idea that is a bad one, it's where the idea is being placed (github application).
@Aupajo, @revans and anyone else... you do realize that we have not yet built the app, right? The only thing we've introduced so far is the resume/description field that will be linked to the user's GitHub account... sort of like how Gist and Pages is linked to your account. There's a good possibility that the actual app will be hosted on a separate subdomain, like jobs.github.com or something similar. We're taking in everyone's feedback and will give it all heavy consideration before we proceed. I'm sure you're aware that programmers can be a picky bunch, consider this first step to just be "testing the waters". Who knows, we may move the resume field out of the GitHub account settings page and put it somewhere else as we proceed.
@tekkub actually no I didn't know if you guys had started or not. I didn't notice anywhere in the above where it stated it either way. It just sounded (assumption on my part admittedly) like this will be within github itself.
Hi, I'm a partner in a small web app design & development firm, and we're hiring — I'd love to try the search when you have it ready. Please let me know!