[edit] At the time I asked this the HN title was "Freelancing, solved."
[edit] At the time I asked this the HN title was "Freelancing, solved."
My co-founder (sabalaba) and I have been working on Hackerlist (http://hackerlist.net) - a selective network of great freelance engineers. This seems like something many of you have been looking for as there are a shocking number of "freelance" posts (from both clients and programmers) on HN each month -- HN ids: 4596379, 4463692, 4323612, 4214767, 4184757, 4053078, 3914001 3783658, 2539892, etc. We admit, at this stage Hackerlist is an experiment. We're only asking for your time and patience -- we'll help you land contracts with top companies, handle the logistics, and you'll keep 100% of your earnings. No catch. We'll handle the vetting process, source contracts, and continuously work one-on-one with you to improve our tech until it serves your needs. Unfortunately, to preserve high quality, we're unable to accept more than 32 candidates and 6 of these spots are already filled. If you'd like to be considered for Hackerlist, email me at michael.karpeles@gmail.com or submit your github username on http://hackerlist.net Our long-term vision is to create a realtime system (think the intersection of mechanical turk, stackoverflow, oDesk) where trusted freelance engineers can immediately clone a git repo, start hacking on a technical problem, and upon completion, get paid what they're worth. P.S. Suggestions and feedback are appreciated -- we don't want to build something you don't need.
Edit: Nice, just noticed changes on your site. You guys are fast.
In the future, we'll provide an interface which is very similar to oDesk. The main difference will be, we plan on changing the process to remove a lot of the pain points that clients and freelancers currently face (vetting, interviews, payment, and all the other time wasting blockers).
If you'd like to setup a time to chat, I'd be happy to tell you more about our next steps and would love to listen to your suggestions and needs. (michael.karpeles@gmail.com)
So just curious how you are planning to make this marriage work?
As suggested before, we're keeping our first batch of acceptances small so we can better understand the challenges which you face and help you overcome them.
cheers!
I'm in a similar position to Ewan, so this comment comes as a relief to me. I have a portfolio site that's also limited to only projects clients have approved to be made public. Whereas my LinkedIn has more information on what I've done.
I've sent an application with my LinkedIn.
where trusted freelance engineers can immediately clone a git repo, start hacking on a technical problem, and upon completion, get paid what they're worth
The problem needing to be solved in this field is not exactly where you're aiming. I can count on one hand the number of good clients I've had who had a DVCS ready to clone and work on :)
The market you mention is probably fairly small, and not hugely lucrative. (as you noted, you are keeping your initial pool of hackers small)
But if you want a wider problem to solve: there are many many small companies looking for hackers to come in and get them on the right track (DVCS, proper deployment mechanisms, backups, security, etc.).
Just food for thought, good luck with the site!