Priya Nair
Warm path · ex-ZS network · Python cluster
91%
Strong fit plus a direct introduction route through a current engineering lead in the target team.
referral partner pilot · myro for warm introductions
Turn referrals into a trusted hiring layer.
Give alumni, employees, and trusted connectors a clean dashboard: who matches which JD, where the proof is, and what happens after the intro.
Warm introsMatch confidenceReferral statusTrust ledger
- Connector view
- high-signal only
- Feedback loop
- applied → shortlisted
- Shared language
- same L2 skill graph
warm-path preview
Backend hiring · referral queue
Karan Verma
Warm path · alumni connector · data backend
86%
Best suited when the referrer can frame analytics depth and production cloud work together.
Neha Bansal
Warm path · manager referral · FastAPI stack
82%
Good candidate for teams that want recent backend build proof and a connector willing to vouch actively.
pilot workflow
Referral workflow
The referral layer should not become Slack chaos. Myro can narrow the queue, show who is actually aligned, and keep outcomes visible for the person making the introduction.
- Start from open JDs and surface only candidates who already clear the L2 skill threshold.
- Show the warmest connector path and the candidate context needed for a credible intro.
- Track whether the intro became an application, a shortlist, or a dead end so trust compounds over time.
workflow
Built to reduce hiring noise, not decorate it.
Pick the role first
Referrers should work from real open JDs, not vague asks. Myro can anchor every intro to an actual hiring need.
Choose the warmest path
The system can sort candidates by match strength and connector confidence so referrals stay selective and credible.
Keep the loop accountable
A referral dashboard becomes useful when it shows status, feedback, and repeatability instead of vanishing after the message is sent.
product layers
Useful surfaces we can attach before the full dashboard lands.
Connector trust layer
Referrers should see only candidates worth backing. The dashboard can filter down to people they can introduce with confidence.
Outcome ledger
Track intros, responses, shortlists, and dead ends so the system learns which warm paths create real hiring movement.
Referral-ready briefs
Each candidate row can package the exact proof a referrer needs: fit summary, key skills, and why this role makes sense.
Reward and access hooks
This layer can later power referral rewards, premium reports, or network participation without changing the underlying skill mirror.
the mirror
The referral side should sit between candidate proof and recruiter action.
That makes it a real operational mirror: seekers build signal, referrers route signal, recruiters consume signal, and everyone stays inside one shared skill language.
- Referral partners read the same candidate skill data that powers the user score and readiness view.
- Only candidates aligned to the JD's L2 cluster appear, so intros stay structured rather than social-only.
- Recruiters receive a filtered, trusted dataset because referral flow sits on top of the same mirrored candidate records.
next step
Make every introduction count more than once.
This gives Myro a referral operating layer that feels useful in a crowded HR-tech market: not just sending intros, but structuring, sorting, and learning from them.