Employee Referrals

Refer Someone

• Every workspace member can refer, including interviewers and viewers. Use Refer on a job, or open Referrals in the sidebar.
• Pick an open job (public or Internal), add their name and email, and optionally a phone, LinkedIn, their resume (up to 4 MB; read to fill in their profile) and a note for the hiring team.
• You can’t refer yourself: your own email is refused, and applying through your own referral link counts as a normal application, not a referral.
• Same email, same person: if they’re already a candidate, the referral is linked to their profile and they’re added to the job if needed. No duplicate is created.
• Each person can be referred to a job once. The first referral counts.
• Otter never emails the person you refer.

Personal Referral Links

On the Referrals page, Get my link gives you a link to a public job, like otter.diy/careers/<slug>/<job-code>?referral=<token>. Anyone who applies through it is tagged as your referral. Internal jobs have no public page, so they have no link; refer people to them directly.

What Referrers See

Only their own referrals, with a simple status: In review, Interviewing, Hired or Not selected. Never interview notes, scorecards, stage names or other candidates. They can open the profile only if their role already lets them.

What the Hiring Team Sees

• A notification in My Work when someone is referred to their job (the job’s hiring team, or owners, admins and recruiters if the job has no team).
• “Referred by” and the note on the candidate profile, and on the pipeline card. Type “referral” or the referrer’s name in the board filter.
• Candidates → Source → Referral includes everyone who was referred.
• Reports → Referrals: referrals by person and by job, and hires from referrals.
• An optional Referral bonus line on the job (e.g. “$1,000 after 90 days”) is shown to teammates when they refer. It’s text only: Otter doesn’t pay bonuses, and it never appears on the careers page.

API, MCP and Webhooks

• GET /api/v1/referrals (filter by job_id, candidate_id, referrer_user_id), GET /api/v1/referrals/:id and POST /api/v1/referrals with job_id, name, email and optional phone, linkedin, note, referrer_user_id.
• MCP tools: list_referrals and refer_candidate.
• Webhook event referral.created with data.referral (id, referrer name, source). The note stays in Otter.