Tell us what role you’re hiring for. AI recruiter sources qualified candidates, screens them against your requirements, sends personalized outreach, tracks replies, and books interviews directly on your calendar.
Replies
Best
Congrats! Open Jobs AI is awesome product. Good luck!
@yuvraj_xyz This is fundamentally a complex noise-reduction problem. We tackle it by aggregating multi-dimensional data to improve the accuracy of information, all within appropriate and compliant boundaries of course.
Our goal is to surface better, more relevant candidates and bring them into the interview process. For candidates, building their own credibility over time matters just as much. We are continuously exploring and pushing forward. Thank you.
If you have any ideas or thoughts, we would love to hear them. Thank you so much.
@yuvraj_xyz The right question for 2026. Resume noise is no longer noise, it's the default.
Our take: stop treating the resume as ground truth. Mira triangulates against artifacts that are hard to fake, GitHub commits, papers, patents, OSS contributions, actual shipped products, and uses conversational screening to probe depth. Ask a real builder about a tradeoff they made and they go ten minutes. Ask an AI-optimized profile and it collapses in two turns. The asymmetry we're betting on: AI can write a resume, but it can't fake a track record of actually building things. The polish gets you in. The conversation gets you out.
@yuvraj_xyz thanks for your comments ! AI-optimized resumes are becoming the norm, so we don’t rely heavily on resume keywords alone.
At OpenJobs AI, we look much deeper into “builder signals” — things like actual project history, execution patterns, technical depth, consistency across experiences, public work, hiring context, and how candidates communicate/problem-solve over time.
A polished resume can help someone get discovered, but it’s very hard to fake real output, real momentum, and real domain understanding at scale. That’s where our agents focus.
@carlvert Thank you for your interest. We will keep improving. The Agent has made such a tremendous difference for us, and we hope it can do the same for many more teams down the road.
@blink_66 You can describe your hiring needs just like you would in a conversation with a seasoned recruiter, and the right candidates end up booked directly on your calendar. This is not automation for the sake of automation. This is what the hiring process was always meant to be. It starts with what the Hiring Manager actually needs, and ends with the right candidate scheduled for an interview. Thank you so much.
Thanks! Funny enough, the most common reaction we get is "wait, was that actually an AI?", and not in the bad way. Candidates tell us it felt more specific and thoughtful than 90% of recruiter outreach they get. The design principle is simple: every message is generated per-candidate per-role, references real signals from their actual work, and the candidate can reply with real questions (comp, team, scope) and get real answers back. It's a conversation, not a blast. The bar we hold ourselves to: would a thoughtful senior recruiter on their best day send this? If not, Mira doesn't.
@thea5 Feel free to try it with a real open role. You will find that candidates can be scheduled for interviews the same day. It is an incredibly efficient experience — moving straight to booking, confirming a time on the calendar. It really is that simple. Thank you.
Hiring as a startup founder is exhausting — sourcing, outreach, follow-ups, scheduling… it never ends. Love that MIRA handles the full loop, not just the sourcing part. Will give it a shot for our next role.
@yehan_xiao Founder hiring is brutal, you're hiring while doing everything else. Sourcing is the easy half. The follow-ups, the scheduling, the chasing, that's where founder time actually goes, and that's the part we built Mira to take. DM me when you're ready, I'll personally help you set up the first role.
Honestly, I never imagined we'd be on Product Hunt at this stage, much less Hunted by Rajiv himself. Every single one of us has been heads-down solving real hiring problems for our customers, not building decks or chasing visibility.
We're not a team that likes to talk loud. We're pragmatic, we sit inside our customers' workflows, and every part of Mira is built around problems we've watched recruiters and founders actually struggle with, not problems we imagined from a whiteboard.
So today is genuinely surreal. Thank you, Rajiv, for the trust. And thank you to everyone showing up in this thread, every comment, upvote, and piece of pushback is shaping what we build next.
We're listening. And we're just getting started.
Report
Congratulations on the launch. Tried it. How do you find if the candidate is really fit for the job and is actually looking for the job?
@lokesh_motwani1 Thank you! We look at two separate problems: fit and intent.
For fit, Mira evaluates candidates beyond keyword matching — including trajectory, project relevance, skill overlap, and likely success in similar environments.
For intent, we use a mix of activity signals, responsiveness patterns, and inferred openness to opportunities, so recruiters spend less time reaching out to people who are unlikely to engage.
@lokesh_motwani1 Lokesh, thanks for trying it. You're naming the two problems that actually matter, and most "AI sourcing" tools mash them together. They're not the same.
Fit is: could this person do the job well if they joined? Intent is: would they actually take it if asked? A great candidate who isn't looking is a wasted ping. A motivated one who isn't a fit is worse, because nobody catches it until everyone's already burned hours on interviews. We score them separately.
For fit, we don't match on resume keywords. We reason about it. Which past projects actually demonstrate the role, which gaps are real, which ones a keyword filter would kill but a smart recruiter would push through.
Replies
Congrats! Open Jobs AI is awesome product. Good luck!
OpenJobs AI
@hello_leo Recruiting remains a significant challenge — one we're committed to tackling head-on, for both our team and our AI Agent.
OpenJobs AI
@hello_leothanks leo for your comments !
OpenJobs AI
@hello_leo we will do it better!
BiRead
The problem framing is spot on. Every founder I know has that quiet list. Good luck with the launch!
OpenJobs AI
@luke_pioneero
Thank you very much! We will continue to support startups and look forward to our startup program.
OpenJobs AI
@luke_pioneero thanks luck for your comments!
OpenJobs AI
@luke_pioneero Thanks for the good wishes!
How does it handles Resume noise? Like handling if Candidate has an AI optimised resume or he is a real builder?
OpenJobs AI
@yuvraj_xyz This is fundamentally a complex noise-reduction problem. We tackle it by aggregating multi-dimensional data to improve the accuracy of information, all within appropriate and compliant boundaries of course.
Our goal is to surface better, more relevant candidates and bring them into the interview process. For candidates, building their own credibility over time matters just as much. We are continuously exploring and pushing forward. Thank you.
If you have any ideas or thoughts, we would love to hear them. Thank you so much.
OpenJobs AI
@yuvraj_xyz The right question for 2026. Resume noise is no longer noise, it's the default.
Our take: stop treating the resume as ground truth. Mira triangulates against artifacts that are hard to fake, GitHub commits, papers, patents, OSS contributions, actual shipped products, and uses conversational screening to probe depth. Ask a real builder about a tradeoff they made and they go ten minutes. Ask an AI-optimized profile and it collapses in two turns. The asymmetry we're betting on: AI can write a resume, but it can't fake a track record of actually building things. The polish gets you in. The conversation gets you out.
OpenJobs AI
@yuvraj_xyz thanks for your comments ! AI-optimized resumes are becoming the norm, so we don’t rely heavily on resume keywords alone.
At OpenJobs AI, we look much deeper into “builder signals” — things like actual project history, execution patterns, technical depth, consistency across experiences, public work, hiring context, and how candidates communicate/problem-solve over time.
A polished resume can help someone get discovered, but it’s very hard to fake real output, real momentum, and real domain understanding at scale. That’s where our agents focus.
KnowU
Really like the multi-agent angle here. Most tools stop at sourcing. Congrats on the launch, will be keeping an eye on this.
OpenJobs AI
@carlvert Thank you for your interest. We will keep improving. The Agent has made such a tremendous difference for us, and we hope it can do the same for many more teams down the road.
OpenJobs AI
@carlvert thanks for your conments, please give it a try and we appreciated any further suggestions.
OpenJobs AI
@carlvert Thanks. Sourcing is the easy half, the rest is where time actually goes. That's the wedge. We'll be here when you're ready to look closer
Congrats!
Curious how candidates experience the outreach
does it feel automated or more natural?
OpenJobs AI
@blink_66 You can describe your hiring needs just like you would in a conversation with a seasoned recruiter, and the right candidates end up booked directly on your calendar. This is not automation for the sake of automation. This is what the hiring process was always meant to be. It starts with what the Hiring Manager actually needs, and ends with the right candidate scheduled for an interview.
Thank you so much.
OpenJobs AI
@blink_66
OpenJobs AI
@blink_66 thanks for your question, so far, most of the human felt they are talking to a human recruiter.
how long does it typically take to get the first batch of candidates sourced after setup?
OpenJobs AI
@thea5 Feel free to try it with a real open role. You will find that candidates can be scheduled for interviews the same day. It is an incredibly efficient experience — moving straight to booking, confirming a time on the calendar. It really is that simple.
Thank you.
OpenJobs AI
@thea5 the fastest result we recorded is half an hour
OpenJobs AI
@thea5 generally speaking, we may receive about 10-15 candidates within 72 hours.
Naoma AI Demo Agent
Guys, good luck! Cool product!
OpenJobs AI
@dmitry_zakharov_ai many thanks!
OpenJobs AI
@dmitry_zakharov_ai Thanks Dmitry!
OpenJobs AI
@dmitry_zakharov_ai Thank you so much
Hiring as a startup founder is exhausting — sourcing, outreach, follow-ups, scheduling… it never ends. Love that MIRA handles the full loop, not just the sourcing part. Will give it a shot for our next role.
OpenJobs AI
@yehan_xiao
Have an efficient conversation with the Agent,everything becomes simple and clear! A new way of recruiting has begun.
OpenJobs AI
@yehan_xiao please give it a try! thanks for your comments
OpenJobs AI
@yehan_xiao Founder hiring is brutal, you're hiring while doing everything else. Sourcing is the easy half. The follow-ups, the scheduling, the chasing, that's where founder time actually goes, and that's the part we built Mira to take. DM me when you're ready, I'll personally help you set up the first role.
OpenJobs AI
Honestly, I never imagined we'd be on Product Hunt at this stage, much less Hunted by Rajiv himself. Every single one of us has been heads-down solving real hiring problems for our customers, not building decks or chasing visibility.
We're not a team that likes to talk loud. We're pragmatic, we sit inside our customers' workflows, and every part of Mira is built around problems we've watched recruiters and founders actually struggle with, not problems we imagined from a whiteboard.
So today is genuinely surreal. Thank you, Rajiv, for the trust. And thank you to everyone showing up in this thread, every comment, upvote, and piece of pushback is shaping what we build next.
We're listening. And we're just getting started.
Congratulations on the launch. Tried it. How do you find if the candidate is really fit for the job and is actually looking for the job?
OpenJobs AI
@lokesh_motwani1 Thank you! We look at two separate problems: fit and intent.
For fit, Mira evaluates candidates beyond keyword matching — including trajectory, project relevance, skill overlap, and likely success in similar environments.
For intent, we use a mix of activity signals, responsiveness patterns, and inferred openness to opportunities, so recruiters spend less time reaching out to people who are unlikely to engage.
OpenJobs AI
@lokesh_motwani1 Lokesh, thanks for trying it. You're naming the two problems that actually matter, and most "AI sourcing" tools mash them together. They're not the same.
Fit is: could this person do the job well if they joined? Intent is: would they actually take it if asked? A great candidate who isn't looking is a wasted ping. A motivated one who isn't a fit is worse, because nobody catches it until everyone's already burned hours on interviews. We score them separately.
For fit, we don't match on resume keywords. We reason about it. Which past projects actually demonstrate the role, which gaps are real, which ones a keyword filter would kill but a smart recruiter would push through.