Former managers usually make the strongest job references. They can speak to your work quality, how you took feedback on hard projects, and whether they'd hire you again. Colleagues and clients can fill those gaps.
Want a contact who actually helps the hire, or just a name on a form?
Most U.S. employers still call a real person, even if you applied through LinkedIn, Indeed, or a company applicant tracking system. Those tools often wait until later. Keep a short list ready. Don't paste names into every Easy Apply box.
Who employers want to hear from
Hiring teams prefer people who supervised you, because a manager can confirm performance, initiative, and team behavior in a way your resume cannot. MIT's career office says a colleague's view is useful. It's still less valuable than a supervisor's take.
A former manager knows if you owned problems or vanished when the work got messy. That's hard to fake on a phone screen.
Peers see the daily grind and can describe whether you shared credit or left people hanging. Use a peer when you can't name a current boss, or when the job is heavy on collaboration.
Professors and advisors fit recent graduates. Career.io notes that a former professor or advisor works if paid experience is thin. Clients work for freelancers, as long as they saw delivery, not only a pitch deck.
Mentors, volunteer leads, and coaches sit in a gray zone. CareerSidekick groups teachers, academic advisors, volunteer leaders, and coaches with personal references that can speak to character when work history is light. Don't lead with them if you have real supervisors.
Thing is, recency beats a fancy title. Someone who managed you last year will sound sharper than a VP who barely remembers your name.
Professional vs personal references
Employers want professional references first. Personal names are a backup for character, not a stand-in for work proof.
| Type | What they can say | Weak spot | Best use |
|---|---|---|---|
| Professional (managers, clients, senior colleagues) | Performance, reliability, rehire potential | They may mention real problems | Almost every application |
| Personal (friends, family, mentors with no work tie) | Character and interpersonal style | Easy to dismiss as biased | Rare, and mostly for thin work history |
Skip family. Skip friends who never sat on a project with you. A mentor who actually oversaw your work is closer to professional than personal.
You don't have to name your current manager. The University of Colorado graduate career guide is blunt about that. Quiet job searches stay quiet for a reason.
How many names to keep ready
Three professional references is the usual request. Colorado's guide treats three as standard.
Some postings want two. A few want five. Build a bench of three to five people so you're not scrambling the night before an offer call.
Keep the names off your resume. Many application flows collect contacts after a phone screen. Listing them up front invites calls nobody agreed to.
Store a simple sheet with name, current title, organization, phone, email, and how you know each person. That's the set Colorado says you can assume you'll need.
Picks that fit the job, not a generic stack
Entry-level campus hires should favor a professor who saw actual projects if the role is technical. A shift manager who only tracked punctuality will not speak to code or analysis. Ask while the class is still fresh.
Freelance and contract work lives or dies on client voices. One client who can describe a shipped result beats a pile of people who only liked your invoices.
Career changers need someone who can explain a short stint without making it sound like you bounced around. A department lead or a client often does that better than a distant executive who never saw the work.
Remote roles put weight on people who watched you deliver without a manager hovering. Autonomy comes up on those calls. So does written communication. A supervisor who managed you across time zones is useful. A coworker from an office job in another era is not.
Skills-based screens put extra pressure on references who can confirm tools you listed. If the posting wants Python or Salesforce, pick someone who saw you use it.
Turns out the same three people are not the right match for every posting. Reorder the list. Match the job.
What hiring teams actually ask
Reference checks exist to confirm you didn't inflate the story. The Balance notes that some questions are dry and factual: title, dates, sometimes pay. Others go after performance problems, why you left, whether you got along with coworkers, and if you were a team player.
You can't script another adult's answers. You can stop them from being blindsided.
Hiring teams tend to circle the same themes:
- What was their role, and how did they perform in it?
- What were their strengths and weaknesses?
- Were they reliable, and how did they work on a team?
- How did they take feedback?
- Why did they leave, and would you rehire them?
- How did they handle pressure or messy decisions?
- Did quality, attendance, or interpersonal issues show up?
RecruitCRM's recruiter-oriented roundup also pushes cultural fit and specific examples instead of vague praise. That's one vendor's framing, not a law. Assume a single concrete negative story can stall an offer.
Share the job description. Name two or three skills you need illustrated. If the role is remote, say so. MIT's advice is to put yourself in the reference's shoes and send the details that would help you give a useful call if you were them. Put that context in the email.
How to ask and brief people
This is a sequence. Treat it like one.
- List recent, relevant people. Prefer former managers. Add a colleague, then a client or professor if the job needs that angle.
- Ask permission before you share a number. A surprise call is how you get a lukewarm "they worked here."
- Tell them the company. Tell them the title too, and why you thought of them for this role, not for every job you've ever wanted, because a generic please-be-a-reference email is how you get a generic call.
- Send your resume and the job description. Flag two or three points. Don't write their script.
- Confirm the best phone, email, and time zone.
- After you reach late interviews, send a one-line heads-up that a call may come this week.
- Thank them either way. If you get the job, tell them.
Ask in writing so they can decline without a hallway freeze. MIT's note on follow-up is practical. People forget. Hiring drags on.
A lot of applicants treat the reference list like leftover paperwork and then panic when a former boss says something true but unhelpful, they were fine, a little slow on deadlines, which is not what you want sitting in a recruiter's notes after a strong final round, so brief people even when it feels like overkill.
Letters vs a live call
Most employers want a human they can phone or email, because a live conversation lets them ask whether the person would rehire you and how you handled messy work. Letters just sit on the page. They help in academic packets and some formal applications, yet they can't answer follow-up questions in real time.
If someone offers a letter, keep it as backup. Still ask if they'll take a call.
A LinkedIn recommendation is not a reference. It's a public blurb. A recruiter might glance at it on LinkedIn. They'll still want a conversation.
Background checks and your rights in the U.S.
A casual call to your old boss is not the same thing as a third-party screening report. When a company uses a background firm, the Fair Credit Reporting Act can apply. FTC guidance for employers says they need your written permission before they pull that kind of report, and they must apply the same standards to everyone.
FTC guidance for job seekers says they must give you a copy of the report and a summary of your rights before they reject you based on it. The CFPB has warned that background dossiers and algorithmic scores used in hiring can count as consumer reports under that same law.
That's the floor, not a tactic. Don't lie on the application. Don't ask anyone to lie for you. Honest negative comments from a former employer are generally in a different bucket than a made-up rave.
Some firms only verify dates and title. Others go further. You often find out which when the ATS drops a consent form.
People who will hurt a live file
Skip anyone who already has a problem with you. If one former boss is a risk, add a skip-level, a peer, or a client instead of hoping the call goes fine.
Your current manager doesn't belong on the list unless they already know you're leaving.
A person who barely remembers you will give a thin answer. That's worse than one fewer name.
Part-time and short gigs can still work if someone saw your work up close. Decade-old jobs usually don't, unless that's the only relevant stretch you have.
The fastest way to wreck a late-stage offer, to be honest, is a reference who is annoyed you never asked first.
FAQ
How many references should I list on a job application? Three is standard. Give them when the employer or the ATS asks, not as a resume footer.
Is a coworker as strong as a supervisor? No. Supervisors still carry more weight. A coworker is a solid second for teamwork, or when a boss is off-limits.
Can I use a professor or a client? Yes, for entry-level and freelance roles. They need specifics.
Do I have to give my current boss? No. Colorado's career guide says you don't need to supply your current manager.
What if the company runs a background check? If a third party prepares a report, federal rules generally require written consent and a notice before an adverse decision. Read the portal form before you click agree.
Make a three-person list this week. Ask each person in one short email. Save their details next to your resume so the next application form doesn't send you hunting for a phone number at midnight.