5.0 Reference

Real reference checks.
Not chased emails.

Beyond the curated list
the candidate gave you

Rob maps the LinkedIn social graph across your team to find mutual connections, shared companies, and shared education. Warmest-path ranking flags who has the best shot at an honest conversation.

FIG. 1.1
Social graphAlex Chen

Candidate-named references

Maria T. (former manager)
James P. (team lead)
Li W. (direct report)

Curated — always positive

Backchannel discovered

Sarah K. → former colleague1st degree
Priya R. → shared company2nd degree
Tom W. → shared education2nd degree
Consent statusGranted

Your team's network, mined systematically

Rob maps LinkedIn connections across every active Jobsly user at your company — mutual 1st/2nd degree connections, shared companies, shared education — and flags who has the warmest path.

FIG. 1.2

Rob to candidate

"We'd like to run a backchannel reference check. This means we'll reach out to people in your professional network — not just the references you provide."

Candidate response

I consent

Discovery proceeds

I decline

Named refs only

Consent recorded

Backchannel discovery can now begin

logged

Candidate-consent workflow

Runs before any discovery. Rob explains what's about to happen, gets explicit consent. Candidates who decline keep the default: named references only.

FIG. 1.3
From:
SarahSarah Kim
via Rob
To:Mark Thompson · Former colleague
Re:Quick question about Alex

Hey Mark — hope you're doing well! I'm working with Alex

on something and wanted to get your perspective on what it

was like working together. Would you be open to a quick

5 minute call this week?

Sent from Sarah's inboxdrafed by Rob

Backchannel outreach drafting

Rob drafts the message. Your team member — the one with the warmest path — sends it from their own inbox. Replies sync back via two-way email.

FIG. 1.4

Rob → Mark Thompson

Voice reference · 4m 32s

LIVE

Signals detected

↗Tone shift⏸Hesitation↔Elaboration→Follow-up triggered

Voice-led conversations

Captures tone and hesitation that written forms miss. Rob follows up on vague answers and surfaces concerns directly rather than letting them pass.

FIG. 1.5
2 flags surfaced from backchannel
Delivery under pressure
warning

“Tended to go quiet when deadlines hit. You wouldn't hear from them until things were overdue.”

— Backchannel ref #2 · Former team lead

Stakeholder communication
critical

“Would skip updates when things were hard. Stakeholders found out about problems late.”

— Backchannel ref #1 · Former PM

Red flags with quoted evidence

Concerns are named with quoted evidence, not softened. You get the actual signal — not the polite version that hides what matters.

Structured against
the rubric

Probes for the things that actually matter — not polite affirmations. Voice-led conversations capture tone and hesitation. Each reference treated as a separate signal.

FIG. 1.6
Call structureRubric-mapped

Probing areas

Communication under pressure
Technical decision-making
Team dynamics contribution
Reliability and follow-through

Follow-up triggers

Vague answer → probe deeper
Hesitation → note and revisit
Contradiction → surface directly

Signal captured

Tone & hesitationRecorded

A signal you can actually weight

Each reference is summarised, rubric-mapped, and aggregated across voices. Concerns are named with quoted evidence. The summary maps directly to the rubric so reference signals update the candidate's overall score.

FIG. 1.7
84Composite
Communication
8588
Experience
8084
Motivation
7882

Full rubric integration

Reference signals update the candidate's score in the dimensions they touch — communication, experience relevance, motivation and fit. The composite score moves accordingly.

FIG. 1.8
Outreach sentEmail drafted & sent
Call scheduledCalendar invite accepted
Call completedTranscript generated
Report deliveredSynced to Rob pipeline

End-to-end scheduling

Rob handles outreach, scheduling, and follow-up. No phone tag, no chasing — references are completed in days, not weeks.

Summarises honestly.
Concerns named directly.

A structured summary per reference with rubric mapping. Red flags surfaced with quoted evidence. An aggregated summary across all voices.

FIG. 1.9
Reference collection

3 references run

Named + backchannel

Aggregated summary

Rubric-mapped signal

Score updated

Composite moves accordingly

From scattered notes to unified signal

Multiple references aggregated into a unified signal. Rubric-mapped summaries feed directly into the candidate's overall score. You get a clear signal, not a wall of notes to interpret.

FIG. 1.10
Marcus RiveraSenior Product Designer
Voice transcript32 min · 4,218 words
Structured summary5 dimensions · 12 signals
Rubric mappingMapped to 4 competencies
Consent recordExplicit opt-in · timestamped
Tier-2 minimum — never fully autonomous

Full audit trail

Transcript, summary, rubric mapping, and consent record — all on the Candidate Profile. Tier-2 minimum on every outreach, never fully autonomous.

FIG. 1.11
Pipeline configuration
Senior / Staff EngineerBackchannel + Named
Trust-critical RolesExtended (3+ refs)
Junior HiresSkipped
or
Disable for all rolesReference stage removed entirely

Every pipeline stage optional

Reference is a stage, not a hard requirement. Turn it off for junior hires, leave it on for senior or trust-critical roles. Independently configurable.

What Reference
replaces

No more references that never happen, all-positive calls from curated lists, or vague summaries nobody reads.

FIG. 1.12
Today

References nobody actually does

All-positive call from candidate's list

Chasing phone tag for two weeks

Reference summary

Vague, nobody reads it

Backchannel intelScattered

Your team has it but never shares

From box-tick to real signal

Skipped references, phone tag, and vague summaries are replaced by systematic backchannel discovery with rubric-mapped summaries that actually influence the hiring decision.

FIG. 1.13
Connections surfaced by Rob
David ChenFormer manager at Stripe
Strong
Lisa ParkCo-founder, prev startup
Warm
Tom ReevesEng lead, same team '21
Direct
Outreach drafted for SarahReady to send

Systematic network mining

Your team has backchannel intel but never shares it. Rob surfaces the connections systematically and drafts outreach for the right person to send.

FIG. 1.14
Former manager
Co-founder
Eng lead
Signal
Comm.
3/3
Technical
3/3
Reliability
2/3

Aggregated across voices

Multiple references aggregated into one clear signal. Consistent themes elevated, concerns named with frequency and quoted evidence.

Under the hood

Everything Reference handles, from social graph mapping to rubric integration.

LinkedIn social graph mapping

Maps connections across all active Jobsly users at your company.

Backchannel reference discovery

Beyond the candidate-curated list — people they didn't name.

Warmest-path ranking

Which team member has the best shot at an honest conversation.

Candidate-consent workflow

Runs before any discovery. Explicit permission required.

Backchannel outreach drafting

Drafted from the team member's own voice, sent from their inbox.

End-to-end scheduling

Outreach, scheduling, and follow-up handled automatically.

Voice-led conversations

Captures tone and hesitation that written forms miss.

Structured summary per reference

Rubric-mapped with strengths and concerns cited.

Red-flag surfacing

Quoted evidence, not softened language. Concerns named directly.

Aggregated summary

Across multiple references — a unified signal, not scattered notes.

Full rubric integration

Reference signals update candidate score in dimensions they touch.

Tier-2 minimum

Never autonomous on outreach. Always requires human approval.

Full audit trail

Transcript, summary, rubric mapping on the Candidate Profile.

Questions
and answers

Do you backchannel without the candidate knowing?

No. A candidate-consent workflow runs before any backchannel discovery. Rob explains what’s about to happen, gets explicit consent, and only then maps the graph. Candidates who decline keep the default: reference calls only with people they named.

How is this different from just asking the candidate’s references?

Candidate-named references are curated by the candidate. Backchannel contacts are people the candidate didn’t list, like former colleagues who sat next to them or managers they didn’t stay in touch with. That’s where the honest signal is.

Who does the backchannel outreach?

Rob drafts the message. A team member from your company, the one with the warmest path to the contact, sends it from their own inbox. Replies come back the same way and sync to Rob via two-way email.

What if the candidate has no connections to our team?

Reference checks still run against the candidate-provided list, structured against the rubric. Backchannel is a bonus when the graph overlaps, not a requirement.

How does a reference call actually change the score?

Reference signals update the rubric dimensions they touch: communication, experience relevance, motivation and fit. Concerns are named with quoted evidence, not buried. The composite score moves accordingly.

Can we skip reference checks entirely for some roles?

Yes. Every pipeline stage is independently configurable per role. Reference is a stage, not a hard requirement. Turn it off for junior hires, leave it on for senior or trust-critical roles.

1.0 Brief

Turn a role into a hiring plan

2.0 Source

Find candidates who actually fit

3.0 Screen

Every application read and scored

4.0 Interview

Interviews that build on context

6.0 Hire

Close the hire, not just the loop

“We stopped chasing candidates and started closing them. Rob handled the entire pipeline while we focused on building.”

Mira Johansson

VP Engineering, Vercel

“Six hires in two months with zero recruiter hours. That's not an optimization — it's a different model.”

Daniel Kraft

Head of Engineering, Ramp

Jobsly powers hiring for fast-growing teams. From early-stage startups to scaling enterprises.

Customer stories

Built for the future.
Available today.

Get startedContact sales