1. LandOffer
  2. Blog
  3. All articles
  4. Professional References for Job Applications: Choose, Ask, and Prepare the Right People

Job search

Professional References for Job Applications: Choose, Ask, and Prepare the Right People

Choose professional references who know your work, ask permission before sharing contacts, and prepare an accurate role-specific brief and reference list.

9 min readLandOffer team

Choose references who have directly observed work relevant to the role, ask whether they are willing, and get permission before sharing their contact details. Prepare a short factual brief with the job, your submitted resume, and the collaboration they actually know. Follow the employer's requested number and relationship types. A senior title cannot replace firsthand knowledge. Keep a request marked pending until the person agrees, and confirm which contact details you may share.

LandOffer publishes this guide and offers recent tech job discovery. We checked official career and employer guidance on October 13, 2026. Jordan, the employers, reference candidates, permission states, contact details, and drafts below are fictional teaching examples. No person was contacted, reference information shared, application submitted, or reference check triggered.

A candidate compares role evidence with a small set of professional contact folios, keeping an unanswered permission request separate. Editorial illustration, not real reference records.

Identify the kind of help the employer is requesting

A professional reference can discuss work they observed: how you approached a problem, collaborated, handled feedback, or completed an assignment. A referral is a request for someone to introduce or recommend your candidacy through a hiring process. Employment verification establishes records such as dates or title. One person might perform more than one function, but agreement to one does not establish agreement to all of them.

CareerOneStop's reference guide describes employment, professional, academic, and personal references and advises choosing people who honestly know your work. For a software role, identify who saw the engineering decisions or collaboration you want assessed. Do not label a classmate as a supervisor or a networking acquaintance as a former manager.

Read the employer's instructions before compiling names. It may specify former supervisors, permit peers or clients, request academic contacts for early-career applicants, or ask for written recommendations instead of a contact list. If the instructions are unclear, clarify the accepted relationships and format rather than submitting an impressive but unsuitable list.

For example, the University of Washington's reference-check policy requests at least three professional references and describes supervisor-focused selection, with alternatives for people with limited experience. Those are that employer's instructions, not a universal rule that every tech application requires three people or accepts the same alternatives.

Select observers by the evidence they can discuss

Jordan has five years of backend experience and is considering a fictional NorthPier API engineering role, job ID NP-318. In this example, the employer requests three references, including a former supervisor, and permits technical peers and product collaborators for the remaining places. Jordan compares six possible contacts against those stated requirements.

Possible reference Directly observed evidence Selection decision
Asha, former manager Delivery planning and API release handoff Ask as former supervisor
Ben, former technical peer Migration tests and code review Ask as technical collaborator
Priya, former product partner Validation trade-offs and support handoff Ask for third place
Victor, senior acquaintance One conference conversation Exclude: no observed work
Lea, current manager Current work performance Hold: confidential search
Former course instructor Earlier academic project Reserve if employer accepts it

The first three cover different parts of Jordan's experience. Asha can discuss delivery decisions, Ben can discuss implementation and review, and Priya can discuss how technical constraints were communicated. None needs to claim they observed every project in Jordan's career.

Victor's senior title does not repair his lack of direct knowledge. The instructor may be useful for a suitable early-career or academic example, but is not automatically a substitute for NorthPier's required supervisor. Jordan keeps Lea outside the proposed list while deciding how to handle current-employer confidentiality with the hiring team.

This selection method works when you have little paid experience too. Consider an internship supervisor, project adviser, volunteer lead, or other person who observed relevant work, subject to the employer's rules. Describe the actual relationship, such as internship supervisor or project adviser, and name the work they observed. Do not invent an employment relationship to make a project contact look more professional.

Ask before treating a name as available

Berkeley Career Engagement's internship guidance advises preparing references, asking permission, keeping people updated, and sharing the specific job description when references are requested. A useful request gives the person enough information to decide whether they can help and time to decline or explain a limitation.

Jordan prepares this request for Priya. It remains an unsent example:

Hi Priya, I'm applying for NorthPier's API Engineer role, NP-318. Would you be comfortable serving as a professional reference about our work on request validation and the support handoff at Cedar Systems in 2023–24? The employer has asked for contacts by October 23 at 17:00 UTC. I can send the job description and the resume I submitted. If you are willing, please let me know which contact details I may share and when you would be available. It's completely fine if the timing or request doesn't suit you.

The request names the actual relationship and relevant work. It does not ask Priya to repeat praise she has not offered or imply she already endorsed Jordan. He also checks whether she can provide a performance reference under any rules that apply to her; willingness does not establish what an organization permits her to disclose.

Give the person a practical way to respond. If they are unavailable, uncertain about the work, or limited to confirming dates and title, record that limitation. Check whether it meets the employer's request before treating the person as a suitable performance reference. Do not keep sending reminders until a reluctant answer sounds like approval.

Record permission, contact route, and timing separately

In the fictional example, Asha and Ben have agreed to be contacted about NP-318. Priya has not responded. Asha permits sharing her email for this role; Ben also permits email, but is unavailable until October 21. The requested deadline is October 23 at 17:00 UTC. These are explicit teaching assumptions, not permissions we obtained from real people.

Jordan's private status record identifies the remaining task: he still needs permission for a third accepted reference. Keeping that task visible prevents the two prepared entries from being mistaken for a finished list:

Person Permission for NP-318 Contact and timing Action
Asha Yes Approved email; timing confirmed Prepare entry
Ben Yes Approved email; available October 21 Note availability
Priya Pending No sharing permission recorded Keep details out

He has two approved references against a request for three. He does not place Priya's remembered phone number into the form to make it complete. He can ask whether a later deadline or an accepted alternative is possible, but neither has been granted in this example.

Permission to act as a reference and permission to share a particular number are related decisions. Check the preferred route, especially if your only contact is a personal mobile number or an old work address. Refresh the details before reusing them for another employer. A public profile does not tell you which address the person wants used for this request.

Send a brief that helps memory without scripting judgment

After permission, prepare only the material needed for the requested role. Include the employer, job ID, role description, submitted resume, expected contact route or deadline, and a few factual reminders of work the person observed. Different references may need different reminders.

Jordan's completed briefing note for Ben reads:

Role: NorthPier API Engineer, NP-318. The fictional posting emphasizes API correctness, migration safety, and collaboration with support.

Materials: The submitted backend resume and the exact job description would accompany this note in a real request. No files have been sent in this example.

Shared work: At Cedar Systems in 2023–25, you reviewed my request-validation changes and migration regression tests. I implemented the validation checks and tests; you reviewed the migration approach, and the team chose the deployment strategy.

Relevant reminder: We discussed rejecting malformed requests before processing and documenting recovery steps for support. I drafted the test cases and handoff notes. I do not have a verified revenue or organization-wide reliability result to attribute to that work.

Scope: Please use your own recollection and judgment. If any detail differs from what you remember, let me know so I can correct my materials.

That brief gives Ben something specific to remember without assigning him an opinion. Jordan does not send a proposed statement that he was the strongest engineer on the team, led the whole migration, or produced a business result Ben cannot verify.

For written recommendations, Yale's guidance to faculty and staff distinguishes factual bullet points or an achievement narrative from asking a student to draft the recommender's own letter. Its context is letters, rather than ordinary reference calls, but the boundary is useful: supply accurate context and leave the assessment with the person making it.

Keep confidential work material out of the packet. A plain description of the collaboration can be useful without internal tickets, customer data, repository access, or private performance documents. Share the submitted resume and invite the reference to flag discrepancies in the facts they know. Correct your own materials where needed; do not ask the person to adopt wording that conflicts with their recollection.

A factual work notebook and role brief sit beside two prepared reference folios and a third pending permission card. Editorial illustration, not an endorsement or submitted contact list.

Prepare the requested list without publishing a directory

The University of Washington's industry-resume guidance advises leaving references off the resume unless the posting specifically requests them there. Follow the actual application instructions: a separate document, dedicated fields, and a recommendation-upload request are different formats.

Jordan prepares this fictional entry for the permitted former-supervisor place:

Asha Raman

Current role: Principal Engineering Manager, Harbor Tools.

Relationship: Jordan's direct manager at Cedar Systems, 2022–24.

Contact: asha@example.com — fictional email used only to illustrate an approved route.

Permission: Confirmed for NorthPier NP-318; phone sharing not approved.

The current title and historical relationship are distinct, so the reader can understand where the supervision occurred. In a real record, verify both with Asha. Do not imply she still works at Cedar Systems or supervised Jordan for the full five years of his experience.

Jordan keeps permission notes in his private record and includes the fields the employer actually requests in the outward list. If the form requires a phone number and he only has email permission, he asks Asha or the employer how to proceed. He does not create a dummy number, use his own number, or silently share a different contact route.

Review contact permission again at the submission step

Before entering reference information, read whether saving or submitting the page authorizes contact, and whether the employer describes an automated invitation. A contact form's presence does not establish that references will be approached only after an offer. Check the actual instructions rather than relying on a previous employer's sequence.

Keep current-employer concerns explicit. Ask the hiring team about alternatives and the stage at which current-supervisor contact would become necessary. Do not assume a former-reference list permanently resolves a later condition. Also keep a reference person's agreement separate from any employer release you are asked to read or accept.

Jordan's final decision is hold the three-person list: two approved, one pending. The brief and two entries are prepared, but the application does not become ready by counting an unanswered request as a third reference. He records the next action as resolving Priya's permission or obtaining an accepted alternative before the deadline. If neither is resolved, he seeks clarification or more time rather than submitting unapproved contact details.

When a real reference has helped, thank them and close the loop about the process. For your next role, refresh the job, availability, and permission scope before reusing their details. Start with a role from LandOffer's recent listings, read the employer's reference requirements, and choose the people who can discuss the work that role actually calls for.

Sources and Further Reading