Hiring workflows
Pipeline & kanban
Stages per job, drag-and-drop cards, bulk actions, a live-updating board, SLA clocks, and structured rejection reasons.
Stages
Each job has an ordered pipeline (for example Applied → Screen → Interview → Offer → Hired). Drag application cards between columns on the kanban board. SLA timers highlight candidates who have waited too long in a stage.
Filter the board by name, title, or tag. Every move shows an Undo toast for a few seconds, and failed moves roll back automatically.
Editing a job
Open a job and use the Overview tab (or Edit job from any other tab) to change the title, department, location, workplace, employment type, openings, salary range and currency, and the description. Changes save automatically a few seconds after you stop typing, and when you leave the page; the form shows Saving… / Saved.
If a teammate changes the same field while you're editing, Otter shows their version instead of silently overwriting it; your other edits are kept. Open, close or archive a job from the status menu at the top of the page. Recruiters, admins and owners can edit any job and its Hiring team; hiring managers can edit the jobs they're on.
Working from a candidate profile
The top of a candidate profile shows the application's stage with the date it entered each stage, plus quick actions:
- Move to <next stage>, or the menu beside it to pick any stage.
- Reject — asks for a reason, like the board.
- Previous / next arrows step through the other candidates in the same stage (“3 of 13 in Screening”), so you can review a whole column without going back to the board.
If someone is in more than one job, the quick actions follow the job you opened the profile from (otherwise their active application).
Resumes
- Adding a candidate: on New candidate, drop a resume at the top of the form. Otter reads it and fills in the empty fields (name, email, phone, links, headline); check them and save.
- Existing profile: open the Resume tab and use Upload resume. Otter reads it, fills only fields that are still empty (it never overwrites what your team typed) and shows a confirmation. Uploading a newer resume makes it the main one; older versions are kept.
- PDF, Word (.docx, .doc), .txt or .rtf, up to 25 MB when you upload in the app (4 MB on the public careers form).
AI match scores
Each application gets a 0–100 fit score with the job's requirements the resume shows, the ones it doesn't, and a one-line reason. You'll see it on pipeline cards (hover for details), on the candidate profile, and as an AI match column and Best AI match sort on Candidates.
- It's a guide, and a person decides. Scores never move, reject, hide or filter anyone out.
- Before anything is sent to the AI model, Otter removes the name, photo, contact details, links, address, school names, dates that reveal age, and lines such as date of birth, gender, nationality or marital status. Only skills, job titles, experience and qualifications are compared with the job title and description.
- Scores are saved and worked out again when the job description or the candidate's resume changes.
- Owners and admins can switch scores off in Settings → Compliance (on by default). Off hides existing scores and stops new ones; the change is recorded in the audit log.
Bulk actions
Tick the checkbox on any card (or focus a card and press X). Select all picks every card the current filter shows. A bar appears at the bottom of the screen with these actions:
- Move to… — sends every selected card to the chosen stage (appended in order).
- Add tag — adds a tag to each selected candidate (skips anyone who already has it).
- Add to pool — adds each selected candidate to a talent pool (skips existing members). Talent pools are on Starter and above; recruiters, admins and owners can use it.
- Remove from pool — when the Candidates list is filtered to one pool, removes the selected people from that pool.
- Reject — moves applications to the job's Rejected stage. A reason is required; an internal note is optional. No email is sent.
The same bar works on the Candidates list. Tagging, adding to a pool and rejecting work on any selection; filter the list by a job to move stages in bulk, or by a pool to remove people from it. Up to 100 at a time. Every bulk action is permission-checked per job, recorded on each candidate's timeline, and written once to the workspace audit log.
Talent pools
Pools hold people you want to hire someday. Open a pool to search members, select rows, Add to a job (pick the job and starting stage — people already in that pipeline are skipped), or Remove from pool. From a candidate profile you can also add them to a pool from the sidebar. See Talent pools & campaigns for when to use a pool versus a campaign.
Offers (stub)
When someone reaches the Offer stage (or you already recorded an offer), the candidate profile shows an Offer panel. Mark the offer as extended, accepted, or declined with a date and optional internal note. Once the candidate is hired, a recorded offer stays on the profile as a read-only record. No e-sign, no candidate email, and no billing yet — just a clear record on the profile and timeline. The hiring funnel on Reports already tracks the Offer stage.
Rejection reasons
Rejecting always asks for a reason — whether you drag a single card into Rejected or reject fifty at once. Admins edit the list in Settings → Pipeline → Rejection reasons (rename, remove, add). Renaming keeps past rejections linked. The reason shows on the candidate profile and timeline.
Interview scorecards
Admins configure scorecards in Settings → Pipeline → Interview scorecard: the criteria (like Communication and Role fit), the rating scale (1–4 by default: 1 Not there yet, 2 Some gaps, 3 Meets the bar, 4 Exceeds the bar; or 1–5), and whether an overall recommendation and notes are required. After a panel, interviewers open the candidate's Scorecards tab and submit feedback attached to that interview. The profile aggregates averages and overall recommendations. Each submission is written to the timeline and audit log.
Once an interview has ended, anyone on the panel who hasn't submitted feedback sees it under Scorecards Due on Home and My Work, oldest first, for up to 30 days. Cancelled and no-show interviews are skipped. Click one to jump straight to the candidate's Scorecards tab.
Duplicate candidates
Open Candidates → Duplicates to review likely matches (same email, same phone, or a similar name with the same college, LinkedIn or email name). Owners and admins can merge one group, or select several groups and choose Preview merge for a dry run with today's data before anything changes. The suggested profile to keep is the one furthest along, then with more applications, a read resume, notes and more filled fields. Applications, notes, resumes, contacts, tags, pools and emails move to the kept profile; its filled fields are never overwritten. When both applied to the same job, the further-along application stays and the other stays on the archived profile, so nothing is rejected. Type MERGE to confirm. Every merge is audit-logged and can be undone from Recent merges; undo puts back only what nobody has changed since. Nobody is emailed.
Live board
When a teammate moves a card, tags someone, or a new application arrives, open boards update on their own — no refresh. The board checks for changes about every 10 seconds while the tab is visible and pauses while you are dragging or mid-action, so it never interrupts you. The Live badge turns to Paused if the connection drops; refresh to catch up. Each viewer only ever sees changes to candidates they already have access to.
Keyboard
- ⌘K — command palette
- g then h / m / j / c / p / i / r / s — Home, My work, Jobs, Candidates, Pipeline, Interviews, Reports, Settings
- c / j on their own — new candidate / new job
- On a candidate profile: [ / ] — previous / next candidate in this stage; Shift+→ / ← — move to the next / previous stage; R — reject (asks for a reason)
- ? — shortcut cheat sheet
- On the board, focus a card (Tab) then Shift+← / → — move it one stage; Space picks it up for drag-by-keyboard; X selects it for bulk actions; Esc clears the selection
Moves that run automations
When moving a candidate (or a group) would set off automations, Otter shows a lightning-bolt line first: “N automations will run”, with what they do. Choose Cancel, Move without automations or Move and run. Moves with no automations happen straight away, as before.
Download all resumes for a job
The Resumes button in a job's header downloads one ZIP with the main resume of everyone in the job's pipeline, plus a manifest.csv listing who is in it and who had no resume. Rejected and withdrawn candidates are left out. It needs the Download resumes permission, and each download is written to the audit log.
Joining details and CTC
In a job's Application form settings you can ask for experience, notice period (including “serving notice” with a last working day), current city, and current and expected CTC. Each field can be hidden, optional or required. Workspaces in India start with experience and notice period required and city and CTC optional; elsewhere they start hidden. In Indian rupees, CTC is shown in lakhs per year.
The details show on a Joining details card on the profile and as columns and filters on Candidates (for example notice period up to 30 days, or open to relocate). Recruiters can edit them; their edits are kept if the candidate applies again, and changes are logged without amounts. CTC is only shown to people with the See salaries & offers permission, and the same rule applies to CSV and workspace exports, compare and share links. The API and AI connector never return CTC.
Where this job is live
Every job shows a Where this job is live panel: your careers page, Google for Jobs, the Indeed and Glassdoor feeds, and LinkedIn sharing, each with its status and a link to check it. When you publish a job, a Your job is live dialog gives you the public link and share buttons.