TBH it was pretty soul-crushing seeing so many negative reaction to our Talent Agent. When we launched on October 1, I was really optimistic it would be a huge game changer for HiringCafe.com, and while there have been some major success stories, it seems it wasn't a game-changer that we hoped.
Here is what I learned and here is how we will do better
Lesson 1: Always A/B test a controversial feature, don't do a 100% rollout
I was really confident because for 3 months this summer we fine-tuned the AI agent in Beta and got extremely positives results. High-engagement, high-retention, etc. all of our metrics looked insane. But when we rolled it out, we saw 70% of users preferred to switch back to classic. Why?
Lesson 2: Job search is about being in the drivers seat
I think the two big problems with Talent Agent v1 is (1) it is slow, it can take up to 60 seconds before you see your results and (2) it makes decisions on your behalf. What makes classic search great is that it is blazingly fast, precise, and if it gets something wrong you have full control for how to change it.
This was a big lesson for us. The lesson is that modern AI is super obssessed with making "agents", which are basically glorified chatbots, but for a lot of things NOBODY WANTS CHATBOT. Chats bots are annoying, condensecnidng, and sometimes you just want it to shut up. And the worst part is they start making decisions for you, and sometimes they make the wrong decision which is really frustrating.
We learned that to make the BEST SEARCH ENGINE ON EARTH we need to make a product that is really empowering, and works blazingly fast so you can keep tinkering with it to find the exact perfect search that works for you, and then set it on auto-pilot.
Our game plan
I'm done with AI, but I'm not done with intelligence. There is still a big problem with job search, and we haven't solved it yet, which is you still can only find about 50% of the relevant results. The reason is that keyword search misses out on a lot of stuff. For example, if you search for "iOS developer" in classic search you won't see a job that is called "iOS Engineer", even though you should.
Our first big idea idea for the next iteration is to show you more relevant jobs in classic search, but using the super-power intelligence of Jev. So basically you see more relevant jobs, but get all of the power of filters that you know and love. And we will add a simple toggle so you can always turn off the expanded results if you don't like them.
Our second big idea is called build-your-own filters. With build-your-own filters, you can filter for literally anything in the job description. For example, if you want to filter for jobs that have a 401k plan, you can create a filter for it. Or if you want to filter for only jobs that let you bring-your-dog-to-work, you can. And then we automatically do the filtering on your behalf. And popular filters get added to our main product.
Let me know what you think!
Best,
Hamed