Ashby & Recruiting Ops

An ATS is the system of record for hiring and the Recruiting Coordinator is the person who keeps that record true. When the data is right, recruiters and hiring managers can trust it without re-checking; when it drifts, every decision made on top of it inherits the error.

Strip away the marketing and an Applicant Tracking System is a small set of objects that link together. Learn the objects and how they relate and you can ramp on any ATS in days, which is exactly the story you want to tell if you have not used Cursor's specific tool. Five objects carry most of the weight.

These objects move in one direction most of the time. A candidate enters against a job, advances stage by stage and at each stage an interview kit tells the interviewer what to look for and a scorecard captures what they found.

1. 1Candidate applies or is sourced. They land against a specific job/req and enter the first stage.
2. 2RC schedules the stage. You book the interviewer, send the invite and attach the interview kit so the interviewer arrives briefed.
3. 3Interview happens, scorecard lands. The interviewer submits structured feedback against the role's attributes.
4. 4Recruiter or HM makes the call. They advance, hold or reject - reading the scorecards you made sure got submitted.
5. 5Candidate moves stage or exits. You update the record so the next decision starts from the truth.

Where does the RC sit in that loop? You are not the decision-maker and you are not the interviewer. You are the person who guarantees the machine has clean inputs and that nothing stalls between steps. Two failure modes are yours to prevent: a candidate stuck in the wrong stage and an interview that happens with no scorecard to show for it.

Cursor runs on Ashby and the job description calls Ashby experience a bonus. That word is your cue: name it if you have it and show informed eagerness if you don't, because a coordinator who studied the tool before the interview reads as exactly the proactive type the role wants.

Ashby is an all-in-one recruiting platform that bundles the ATS, scheduling automation, CRM and analytics into one product. Its reputation rests on two things: deep reporting that most ATS tools bolt on as an afterthought and scheduling automation strong enough that coordinators lean on it for complex loops. For an RC, those are the two surfaces you live in daily.

Map what you already know onto Ashby's vocabulary so you can speak it credibly. The concepts transfer almost one-to-one from any modern ATS.

The two areas worth rehearsing out loud are scheduling automation and analytics, because they map directly to the two halves of this role: keep loops moving fast and improve the process with evidence.

Data hygiene is not the cleanup you do when there's slack time. It is the deliverable. Hiring managers decide off the records you keep and Cursor's ~2-week loops leave no room for a stalled candidate to sit unnoticed for days.

Hygiene means a small number of invariants are always true in the system. State them as conditions you actively protect, not chores you sometimes get to.

• Every candidate is in the correct stage - no one parked in a stage they've already cleared or been rejected from.
• No stale records: a candidate who went quiet two weeks ago isn't still showing as active in the funnel.
• No duplicates: one person, one record, even if they applied twice or were sourced and referred.
• Interview kits are attached before each loop and scorecards are routed to the right interviewers.
• Feedback is in before the decision meeting - not chased during it.

Invariants drift on their own. People forget to advance a stage, two sources create two records, an interviewer ghosts a scorecard. The discipline is the audit habit: a regular sweep that catches drift before anyone trips over it.

1. 1Daily: stage sweep. Scan active candidates for anyone mis-staged or stuck longer than the loop should allow.
2. 2Daily: scorecard chase. Flag every interview that happened without submitted feedback and nudge the interviewer.
3. 3Weekly: dedupe + stale sweep. Merge duplicate records and move genuinely dead candidates out of the active pipe.
4. 4Per loop: kit check. Before any onsite, confirm every session has its interview kit attached and the right scorecard mapped.

Frame hygiene the way the role frames everything else: it protects speed. A clean ATS is what lets the team run a 2-week loop without errors, because nobody is wasting a morning reconstructing what's actually true.

Half this role is execution; the other half is making the execution better. The job description asks for someone who brings new ideas without being asked and ships improvements, so the interview will probe whether you're a ticket-taker or an ops-builder.

You don't need a grand reorg to prove the builder mindset. The strongest improvements are small, specific and measurable - a template that cuts an hour of writing, a checklist that kills a recurring error. Four areas are reliable sources of high-impact fixes for an RC.

What separates an idea from an improvement is measurement. If you can't say what got better, you ran a change, not an improvement. Pick a metric before you ship and read it after.

1. 1Name the friction. Be concrete: “interviewers showed up unbriefed twice last month,” not “scheduling feels messy.”
2. 2Pick the metric. Decide upfront what you'll watch - time-to-schedule, error rate, no-show rate, a candidate-experience signal.
3. 3Ship the smallest fix. A template, a checklist, a reminder cadence - change one thing so you can attribute the result.
4. 4Read before/after. Compare the metric over a real window, not a single lucky week.
5. 5Keep or revert. If it moved the number, standardize it; if not, drop it and try another angle.

There's a caution that matters in a fast org: improve the system without breaking what works. Cursor is small and moving quickly, so a heavy new process that the team has to learn mid-sprint can cost more than the friction it removes. Change at the edges, prove it, then expand.

The RC sees almost everything: candidate details, interviewer feedback, offer numbers and who's being considered for what. Discretion is the price of that access and at a small, flat company it's what lets leadership hand you sensitive work without a second thought.

Start from a default and you'll rarely go wrong: need-to-know. Information flows to the people whose job requires it, in the form they need and no further. The hard part isn't the rule, it's the judgment in the gray cases.

Two failure modes sit on either side of good judgment and the role wants you to avoid both. Escalating every tiny question makes you a bottleneck and signals you can't be trusted to think. Oversharing - answering a curious interviewer's “so what'd they offer her?” - breaks confidentiality outright.

• Pause on anything involving comp, feedback or a senior/sensitive candidate before you send.
• If unsure whether something is shareable, ask the recruiter or HM rather than guessing toward open.
• When you can answer from policy, answer - don't escalate trivia just to be safe.
• Assume any candidate could see what you write; keep notes professional and factual.

Discretion compounds into trust and trust is what makes the role bigger. The coordinator leadership relies on for the delicate offer or the confidential exec search is the one who proved, in small moments, that information stops with them.