Draft smart buddy and mentor pairings for every new-hire cohort, matched on role, location, and experience, with a clear reason for each match. Joy proposes; you review and assign.
Using the new-hire roster and mentor pool in the Knowledge Center, suggest buddy pairings for this [month]'s [cohort], matching on role, location, and experience, and explain each match.
Un ejemplo ilustrativo: tu resultado dependerá de tus fuentes, datos y peticiones.
I matched the six July starters against the twelve available mentors in the pool, weighting same-function first, then time-zone overlap, then a two-to-five-year seniority gap. No mentor is carrying more than two mentees under these picks.
Here are the six pairings. Each buddy is in the new hire's function, within two hours of their working day, and senior enough to help without being a skip-level. Two people had strong alternates, noted below.
| New hire | Role · location | Buddy | Why this match |
|---|---|---|---|
| Priya N. | Backend Eng · Austin | Marcus L. (Sr. Eng, Dallas) | Same stack, one-hour overlap, 4 yrs senior; currently mentoring one |
| Dan O. | AE · Denver | Rosa M. (Sr. AE, Denver) | Same region and segment; ramped two reps last year |
| Aisha K. | CS · Remote (EST) | Tom B. (CSM, Boston) | Same time zone, same book type; light current load |
| Leo F. | Product · SF | Wei C. (Sr. PM, SF) | Co-located, adjacent product area, 3 yrs senior |
| Grace T. | Marketing · Chicago | Nadia P. (Sr. PMM, Chicago) | Same function and city; strong onboarding feedback |
| Sam R. | Backend Eng · Austin | Jordan H. (Sr. Eng, Austin) | Co-located, same stack; keeps Marcus at one mentee |
Two calls worth your eye. Both Austin engineers (Priya and Sam) could have gone to Marcus, but pairing Sam with Jordan keeps everyone at or under two mentees and gives Sam a co-located buddy. And if you'd rather Aisha have a same-region lead than same-time-zone, Dana W. in New York is the alternate.
Say the word and I'll rebalance. For example, cap everyone at one mentee, or prioritize interest overlap from the intake survey over pure function.
Want me to draft a short intro note you can send each pair, or a first-30-days checklist for the buddies to work through together?
Buddy/Mentor Matching reads your new-hire roster and mentor pool from the Knowledge Center and drafts a set of pairings, each matched on role, location, and experience. Every suggestion comes with the reason it makes sense so you can approve at a glance or swap with a follow-up.
Upload or connect the new-hire roster and the list of available mentors (with their roles, locations, tenure, and current mentee load) to the Knowledge Center.
Tell Joy what matters: same function, overlapping time zones, seniority gap, and the maximum mentees per buddy. Add any must-avoid pairings.
Joy returns a table of matches with a short reason for each. Rebalance with follow-ups like "give Priya a mentee in her own region" or "cap everyone at two."
Copy the final pairings into your onboarding tracker or HRIS and introduce each pair yourself. Joy drafts the matches; it doesn't message people or write to your systems.
Save this ask as a custom command on the assistant your team already uses, so anyone can run it in one step.
Balances role, location, experience, and interests instead of pairing by whoever's free.
Every pairing comes with a plain-language reason you can sanity-check in seconds.
Caps mentees per buddy so your most helpful people don't quietly burn out.
Swap or re-pair anyone with a follow-up. No rebuilding the whole grid.
Weight time-zone overlap heavily so distributed hires get a reachable buddy.
Pair on the specific skills a new hire needs to ramp, not just their title.
Match senior sponsors outside a new hire's team to widen their network.
Pair new hires with veterans to share fresh tools and perspectives both ways.
Joy reads your new-hire roster and mentor pool from the Knowledge Center and proposes pairings weighted by the rules you set: function, location, seniority gap, and mentee load. Each match comes with a short reason so you can approve or swap it quickly.
Yes. Tell Joy what matters most (same team, overlapping time zones, a seniority range, a cap on mentees per buddy) and it applies those rules. You can rebalance any pairing with a follow-up instead of starting over.
It respects the mentee cap you set and shows the trade-offs when two new hires want the same buddy, so you can spread the load. In the example, it routes a second Austin engineer to a different mentor to keep everyone at two or fewer.
No. Joy drafts the pairings and can draft an intro note for you, but you send the introductions and record the assignments in your onboarding tool. Joy doesn't message people or write to your systems.
Random assignment ignores function, geography, and workload, so new hires often get a buddy who can't actually help or has no time. This proposes reasoned matches and shows why each pairing works, which you can adjust before assigning.
Únete a la lista de espera y sé de los primeros en probar este flujo de trabajo cuando JoySuite se lance.