Both now find candidates, from different evidence. Metaview's AI Sourcing searches professional profile data and the candidates already in your ATS, drafts an ideal candidate profile from the job description and learns from your interview outcomes; its core remains interview notes and scorecards. StarHunt only sources, and only engineers, ranking them on what they shipped on GitHub in the last twelve months. Metaview fits a team that wants one product from sourcing to debrief; StarHunt fits a technical search where public code is the strongest signal.
What Metaview does
Metaview's original product joins interviews on Zoom, Google Meet or Microsoft Teams, transcribes them, and turns the conversation into structured notes and scorecards that flow into applicant tracking systems such as Greenhouse, Lever and Workday.
AI Sourcing, added in late 2025, works from a description of the role: Metaview drafts an ideal candidate profile, searches profile data gathered from public professional profiles and data providers, along with the people already in your ATS, and returns a ranked list. It can look for people similar to candidates who interviewed well, and it adjusts to your hiring decisions over time. In September 2026 the company raised a Series C to extend these agents to outreach and scheduling.
What StarHunt does
StarHunt indexes GitHub, starting from the repositories that define each technology, and ranks their real contributors by 12-month contributions, the languages in their own repositories, their most starred project and how recently they pushed code. You describe the role in plain English or upload the job description, and get a ranked shortlist of engineers with the public contact details they chose to publish.
It does nothing after the shortlist: no notes, no scorecards, no ATS sync beyond Ashby and a CSV export.
Where the two searches differ
A profile database knows what people wrote about themselves: title, employer, skills listed. That covers every job family, and it covers the engineers who never publish code, which a GitHub-based index cannot.
Public code says something a profile cannot: what an engineer actually built recently, in which language, and whether maintainers of real projects accepted their work. On a Rust, Kubernetes or applied AI search, that ordering is the difference between a list to review and a list to contact.
Metaview's other edge is its own history: it can rediscover people already in your ATS and learn from how your interviews went. StarHunt starts from the outside every time.
Which one fits
- Metaview if you hire across many job families, already run interviews at volume, and want sourcing and interview notes in the same product.
- StarHunt if engineering is the bottleneck, your candidates show their work on GitHub, and you want the search alone at a fixed monthly price.
- Both is a common setup: engineers sourced in StarHunt, interviews recorded and scored in Metaview.
What each costs
Metaview publishes its plans: a free tier with 100 sourced profiles once, Pro at $100 per user per month for 200 profiles a month, Max at $300 per user per month with no cap, and custom Enterprise pricing. StarHunt is free for three searches, then $49 per month, or $40.75 per month billed yearly, with unlimited searches and exports.
| StarHunt | Metaview | |
|---|---|---|
| Finds candidates | Yes, engineers only | Yes, every job family |
| Searches | Public GitHub repositories and contributions | Professional profile data and your own ATS |
| Ranks on | Code shipped in the last 12 months | Fit with an ideal candidate profile |
| Interview notes and scorecards | No | Yes, the core product |
| Pricing | Free, then $49 per month | Free tier, then $100 or $300 per user per month |
Frequently asked questions
Is Metaview a sourcing tool?
Partly, since late 2025. Its AI Sourcing searches professional profile data and your ATS from a role description. Its core product is still interview notes and scorecards.
Can StarHunt replace Metaview?
Only for the sourcing of engineers. StarHunt has no notetaker, no transcription and no scorecards.
Which finds better engineers?
For roles where good engineers show their work publicly, a ranking on recent code tends to surface people a profile search misses. For engineers who never publish code, a profile database is the only option.
Try the engineering search on its own
Describe one engineering role and see who ranks first on what they actually shipped. Free for three searches, no card.
Try StarHunt for freeDisclosure: StarHunt publishes this page. Facts about the other tool come from its public pages and public reviews, checked in October 2026. Vendors change their pricing, so check theirs before you buy. Metaview