I was interested in building a product for which 1. the agent is the whole product, not just a component of it; and 2. solves a specific problem out of the box.
Tavi is a deep people search agent that lives in Slack. We used it to find our founding engineer and our first customers are a mix startups, recruiters and VCs.
I'm building this: https://teeming.ai/jobs. It aggregates jobs in AI startups enriched with investor-grade info. Can be navigated with a chat agent, filters, and has automatic CV/Linkedin matching.
I am building something in this space: teeming.ai/jobs
While we are focused specifically on technical roles in AI startups, and we don't "verify" per se, we do enrich jobs data with investor-grade intelligence on the startups themselves, so you can see which companies have legitimate backing.
I'm working on https://teeming.ai, trying to solve the information asymmetry problem in the job market.
The project has been a huge learning curve for me - I started out as a skeptic of how generative AI could solve real problems (rather than just create noise) but now think that, like the internet, it can create a new kind of abundance that will be harnessable in all sorts of interesting ways.
OP here. Appreciate the honesty. I actually agree - I think the same way and I'm realising now that we don't do a good enough job of communicating the need to the user. Thank you for taking the time to comment.
OP here. Appreciate the feedback - the login barrier is definitely something we will take on board. I think some level of identity authentication is a must to counter the scourge of bot traffic, but we will think of ways to be cleverer about this.
With regard to job posting accuracy - absolutely this is a problem. Normalising what different job descriptions actually _mean_ is one of the key challenges we want to solve.
Hi, OP here. Really like your approach! Like you we want to solve for talent-first. We believe we can add value for hirers beyond just charging to post jobs. Please get in touch if you'd be interested in discussing further (email in bio).
Hi, OP here. This is the "catch-22" of job sites. If they are open to the web they become swamped with bot traffic. If they are closed then users have to overcome a barrier to use them. We have tried to find a middle ground and use the lowest-effort way (for users) to demonstrate authenticity in the form of a Google login. But we understand this might be putting users off so we are looking at ways we can give away a bit more before requiring a login. Appreciate your feedback.
Hi dang, I'm the OP and a longtime user of HN so I appreciate your fair-handedness on this. We have a small circle of enthusiastic early-users and we made them aware of our 'debut' without explicitly soliciting votes or comments.
Hi, OP here. One of the problems we want to solve is the proliferation of bot traffic on job sites. Requiring a Google login is the simplest way to achieve this for the time being.
Hi, OP here. One of the things we've discovered is that companies post their jobs in a number of locations but often forgot to take them down when the jobs are filled. Compounding this is the fact that some job sites automatically take down ads after a set number of days (say 30 or 60). Working out whether or not a job is "live" is therefore non-trivial but something we actively want to solve.