The #talenthunch job suggestion generator appears to be working! As shown in the graph below, the average number of generated suggestions that are dismissed is trending downwards, so far.
I hope to keep dismissals below 75% and likes above 25% for starters, but will set some solid KPIs once TalentHunch has been running for a bit longer. 6 days worth of data isn’t enough to make any long term forecasts.
Started a Twitter Ads campaign with 2 #talenthunch tweets. Set a max budget of $100 ($10/day) with a job search related target audience in Aus and NZ. Nearly a thousand advert impressions today, but very few clickthroughs to date (and no registrations). Will let this campaign run out and then reassess.
- 77 homepage/registration page uniques
- 11 new users (14.29% conversion)
- 39 total users
32 skills added
56 new job suggestions (generated from user’s skills, Likes and Favourites)
31 pending suggestions (generated, but not seen yet)
1,113 dismissed suggestions
- 9 favourited suggestions
- 46 liked suggestions
- 1,168 total choices made (engagements)
While #talenthunch is in a holding pattern until the new site goes up, here are the February 2017 stats:
- 28 registered candidates
- 3 new candidate signups
- 8 skills added
- 5 previous positions added
- 43,888 job matches generated
- 20,067 unique job matches
- 20,431 new job listings
- 55 uniques to landing page (signup conversion rate was 5.45%)
- Top traffic sources: Direct, Facebook
Adding search to #talenthunch made very little difference, because I basically stopped marketing it during Feb. In its current form, TalentHunch isn’t sticky enough for users to keep using it and for them to recommend their friends to it.
Have been working on a pivot for the past week which once launched will be closer to my original vision.
Running some analysis on the current #talenthunch data, and teaching myself how to use D3.js at the same time.
This graph shows the candidates (red) and their selected skills (blue). The bottom left cluster of nodes are all software related, which demonstrates an interesting possible niche market idea for TalentHunch.
In other news, I crashed and burned in a technical phone interview on Thursday. It turns out that having over 10 years of experience isn’t enough if you don’t know the fundamentals of computer science/software development (which I would have gained had I stayed in University).
I can clearly code and produce solutions to client’s/employer’s problems quickly, but it’s a whole different ball game when the hiring company’s core product is software.
As a result of this failed interview I had a pretty low Friday with a few rough moments, but distracted myself with some more TalentHunch coding. #laterlog
Spent the last few days trying to refactor the main #talenthunch job match creation script because it was taking 6 hours to run (yes, you read that right. 6 hours). After a lot of false starts and testing locally I think I’ve finally cracked it and hopefully it will now run quicker. Will find out tomorrow when the cron job runs next.
Sent out 2 #talenthunch emails this morning:
- A notification to the 4 candidates that haven’t added any skills to their profile yet about how TalentHunch works (i.e. no skills = no matches)
- A welcome email to all the new signups in Jan to say hi and asking them to share TalentHunch with their job hunting friends.
#talenthunch January 2016 stats
- 25 registered candidates
- 25 new candidate signups
- 133 skills added
- 26 previous positions added
- 14,332 job matches generated (220.50% of estimated 6,500)
- 9,650 unique job matches (52.16% coverage of all jobs added in January)
- 18,501 new job listings (68.52% of estimated 27,000)
- 154 uniques to landing page (signup conversion rate was 16.23%)
- Top traffic sources: Direct, Hacker News, Twitter, organic search, Facebook
I think I’ve finally worked out one way to increase #talenthunch candidate registrations; allow unregistered users to search for jobs from the homepage, but limit the search results shown to only 10. This, combined with some creative call to actions, should hopefully incentivise more candidates to register to see more search results (and generate their matches).
The quicker I can get more candidates onto the platform, then the more motivation advertisers will have to post on TalentHunch (when this functionality is complete).
Deployed the #talenthunch password functionality. Also testing Headway as method for conveying feature updates. For example https://headwayapp.co/talenthunch-changelog/password-resets-14622
Finished the #talenthunch password reset functionality today and will hopefully deploy it tonight or early tomorrow morning.
Stats for the first week:
- Unique homepage views: 85
- New candidates: 13
- Total skills added: 45
- Unique skills added: 36
- Total positions added: 12
- Total job matches: 2,402
- Total jobs added: 5,206
Was trying to hold off on today’s log because I’m really close to hitting the 1,000 #talenthunch job matches mark (and wanted to use the milestone tag), but alas it’s sitting on 980 matches.
I worked on revising the homepage design so it’s more descriptive, includes a product screenshot, and also has an FAQs section to answer questions like: “Why do you need my full name?”. Will hopefully push this live tomorrow.
Just finished the final (yes, actually the final this time) candidate to job matching code for #talenthunch today. I can can successfully match a list of my skills and previous job titles to a database of jobs, and then return those matches with their associated match strength score.
Finishing off the site’s front-end tonight and tomorrow with the goal to go live before the end of the year (yes, I know, it’s another deadline but anything is possible).
A very late #laterlog:
- My wisdom tooth operation went well.
- Achieved very little #talenthunch dev during my work leave/recovery time.
- Last Saturday I moved into the house I’ll be house/cat sitting for the next 5 weeks (within walking, instead of driving, distance to the CBD).
- Achieved a good chunk of TalentHunch dev in November, but still a bit to do.
- Will be finishing up at my real job on the 21st December, so will need to find something to do next year (which might be TalentHunch, depending on the timing).
I didn’t go ahead with the idea for content writers that I came up with a week ago.
I struggled to explain the concept to potential users and the overall feedback wasn’t very positive (as in, “I don’t really need this”).
In other #laterlog news; at my day job yesterday I had to move my workspace from my teammate’s office out into a common area to make way for a new staff member starting on Monday. Was also told that I couldn’t attend an all staff 3 day meeting/getaway because I’m only a temp. Wasn’t the best Friday I’ve ever had.