Profiled

After a couple of weeks of talking to (and community stalking) hiring managers, tech recruiters and sourcers, I have a reasonably clear idea of the workflow and pain points for screening GitHub profiles. I am not entirely convinced about the severity of these pain points. However, my theory is that whatever is built with hiring managers in mind can be transformed into something that technical sourcers will want. Sourcers are in the market for anything that enables them to align with the hiring managers they have as clients.

Built a simple Chrome extension in ~ 6 hours that will insert relevant information like other social profiles (complete with semantic analysis to see what topics interest them) into a candidate's GitHub profile.

I intend to keep this free and use it as a growth channel for the main app.

I've been working on SourceSort for a month or so. It's gone reasonably well, with 4k visitors in the first month and around 50 trickling in every day with no further effort. I built SourceSort to improve on the solutions for developers to find open source projects to contribute to. I think I've done that, but I've also build something that a) has no reason for people to come back with any frequency and b) has no viable business model in the short term and c) has a fairly small total addressable market.

I knew all these things when I started and just wanted to solve the problem in front of me. SourceSort is more or less automated already and I now need to return to trying to build something that will make me financially independent.

The idea for Profiled is to do what I did for open source projects - surfacing useful insights - for developer profiles. There's no money in contributing to open source but there's lots of money in hiring developers.