The person behind the product
Jimenez Julien, founder and product lead of MentorPairing
I build and maintain the software that association and university mentoring programs use to pair participants, log meetings and report on the year.
Why I built MentorPairing
I started this product after watching a volunteer board member spend an entire Presidents Day weekend at her kitchen table with 178 printed application forms, four highlighters and a legal pad. She was matching mentors and mentees for a professional association in the Midwest. She was extremely good at it. She also had no way to hand that skill to the person who would take the role from her in eighteen months, and no way to prove to her board that the program had produced anything at all beyond a warm feeling and a photograph from the launch breakfast.
That is the problem I care about. Mentoring programs are almost always run by one person who already has another job. The matching is the visible work, so it gets the attention, but the part that decides whether a cohort succeeds happens in the quiet months afterward: whether the first meeting actually took place, whether anyone noticed when a pair went silent in November, and whether there is a record in March when the finance committee asks what the program is for.
So MentorPairing is deliberately not an ambitious platform. It does four things. It takes applications with the criteria you care about. It ranks and proposes pairs so you spend your Saturday on the twenty hard calls instead of all two hundred. It collects meeting logs in a way that a busy mentor will actually complete on her phone between appointments. And it turns those logs into a report you can defend without hedging.
What I learned about this trade
Three things changed how I build. First, coordinators do not want the algorithm to be clever, they want it to be legible. Every suggested pair has to show its reasons, because sooner or later a participant asks why she was matched with this person and "the system decided" is not an answer anyone accepts. Second, the mentee will not chase. If a pair has not met by week four, the program has to move, not the twenty three year old who is worried about being a bother. That is why the thirty day flag exists and why it is on by default. Third, reporting is a political document, not an analytics exercise. The figures that matter are participation, meetings held, hours contributed and retention through the term, because those are the four numbers a sponsor or a provost recognizes.
I also learned what to leave out. There is no social feed, no badge system, no discussion board. Every program that asked for one abandoned it within a cohort, and it cost them the trust of participants who had already been asked to join one more thing.
How I work with program coordinators
Setup is a conversation, not a form. We start with the application you already send, because it encodes years of hard won judgment about what makes a good match in your particular program. I translate that into weights with you on the call, and you keep the wording. During your first pairing run I stay available, and I look at the pairs you override, because a pattern of overrides usually means a weight is wrong rather than a coordinator being fussy. Programs on the Institution plan get a data review once a year where we look at retention by cohort together and decide what to change.
Experience and expertise
- Fifteen years building operational software for organizations that run on volunteer time and thin staffing.
- Direct work with 168 US mentoring programs across professional associations, alumnae networks, chapter federations and university student success offices.
- Practical familiarity with the constraints these programs carry: FERPA aware handling of student records, sponsor reporting cycles, board approval calendars and procurement paperwork.
- Founder of MLJ, SASU, the company that publishes MentorPairing and stands behind its support commitments.
How this product is built and maintained
MentorPairing ships small changes weekly and never on a Friday. Anything that touches the matching engine is released between cohorts, never mid cycle, because a change in scoring during a live program would quietly alter the record. Participant data lives in US data centers, is encrypted in transit and at rest, and is never sold or used to train a model. Support is answered by people who understand mentoring programs, with a one business day commitment on every plan.
The writing on this site follows the same rule as the product. Every number published here comes from platform data or from a customer who agreed to be quoted by name, title, organization and city. When a figure changes, the page changes. If you find something on this site that does not match what the product does, write to me and I will correct it or explain it, in that order.
Published articles
Everything I have written for The Pairing Desk, the MentorPairing magazine for program coordinators, is listed here with its publication date.
Contact the author
Email me at jimenezjulien42@gmail.com. I read everything that arrives, including the messages that tell me a feature is wrong. If you would rather see the product than read about it, the demo request form is the fastest route, and I run most of those calls myself.