Structured hiring vs calendar chaos

I spent 90 minutes building a structured loop with scoring rubrics, and then Tuesday turned into a 7-reschedule circus because two panelists forgot they’re also on the incident rota. As the TA lead, I’m trying to protect candidate experience and my team’s sanity — how are you enforcing panel accountability without becoming the calendar cop? Bonus points if your ATS has a trick; Greenhouse hit me with 23 “nudge” emails before lunch.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌⁠​‍‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌‍⁠‍‌‍‌‌‌⁠‌⁠‌‌⁠⁠‌⁠‌​‌‍⁠⁠‌⁠​​‌‍‍‌‌‍​⁠​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​‍​‍‌‍⁠‍‌‍‌‌‌⁠‌⁠​‍​‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​‌​⁠​⁠​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​⁠‌‌‍​‍‌‌‌‍‌⁠​‌‌‍‌‍‌‍‌‌‌‍⁠‌‌‍‍‌‌‌​⁠‌​​‍‌⁠‍​‌‍‍‍‌‍‌‍‌​‍​‌​⁠​‌⁠‌‌​‍​‍‌⁠⁠‌​​

We sync the ‘incident rota’ to GCal and auto-decline; Greenhouse backup pools cut reschedules — try PagerDuty calendar feeds?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌⁠​‍‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‍​⁠​​​⁠‌‍​⁠‌‍​⁠‌‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​‌​⁠‌⁠​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​⁠‍‌‍‍​‌⁠‌‌‌⁠‍‌​⁠‌⁠‌‍‌‍‌​‌⁠‌‌‌​‌​​‌‌‍‌‍‌⁠‌‍‌⁠‌⁠‌‌⁠⁠​⁠​​‌‍​‍‌​​‍​‍​‍‌⁠⁠‌

We moved to a weekly ‘opt-in’ for interviewers and let Ashby auto-rotate from a trained backup pool, so anyone on-call is excluded by default and reschedules dropped fast. Building on @benjamin_san39, the only hard rule is two misses = temporary panel pause — not a calendar cop, just a carpool lane for reliable interviewers.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌⁠​‍‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‍​⁠​​​⁠‌‍​⁠‌‍​⁠‌‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​‌​⁠‍​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​‌⁠‌​‍‌‌⁠​‌​⁠‌‍‌​‍‌‌‍​‍​⁠‍‌‌​​‌‌‍⁠‍‌‌‌‍‌⁠‍​‌​‍​‌​⁠⁠‌‍​‌​⁠‌‌‌⁠‍‌​‍​‍‌⁠⁠‌

I stopped playing the ‘calendar cop’ by adding a 24-hour confirm-or-swap step: a Slack workflow pings each panelist the day before with a single Confirm button; no click and Ashby auto-rotates to a trained backup, so the candidate keeps the slot (Workflow Builder: Build a workflow: Create a workflow in Slack | Slack). We also track light ‘reschedule debt’ by interviewer and post a monthly nudge — works, but only if you’ve got a real backup bench aligned to the rubric you spent 90 minutes on. Would a lightweight confirm flow help more than chasing rota syncs?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌⁠​‍‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‍​⁠​​​⁠‌‍​⁠‌‍​⁠‌‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​‍​⁠​‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍​⁠‌‍‌‍​‌‌​‌⁠‌​‌‍‌‍‍⁠‌‌​‌‌‍⁠‌‌​⁠‍‌‌‌‍‌‌‍‍‌​‌‌‌‍⁠‍‌‌‍‌‌​​‌​⁠​‌‌⁠​⁠​‍​‍‌⁠⁠‌

What finally stuck for me was scheduling to a role-based panel calendar (e.g., [email protected]) instead of people, then assigning a certified interviewer from the pool 90–120 minutes out; if @SRE is on fire, we swap the human without touching the candidate’s invite. Tiny caveat: you need rubric-aligned lanes so anyone on that calendar is qualified — can Greenhouse treat a shared calendar as the interviewer?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌⁠​‍‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‍​⁠​​​⁠‌‍​⁠‌‍​⁠‌‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​‍​⁠‌⁠​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‍‌‍‌‍​‌‌‍‌⁠‌​⁠‍‌‍‍‌​⁠‌​‌‌⁠⁠‌​⁠​‌‍‌‍‌‌​‌‌‍⁠‌​⁠‌‌‌​​‌‌​⁠‍‌‍⁠‍‌‍​⁠​‍​‍‌⁠⁠‌

Assign a rotating ‘panel captain’ for each loop who owns day-of coverage, does a T-2h check-in, and triggers the pre-agreed alternate if someone’s pager goes off (think pit crew chief). We also post a tiny Friday Slack dashboard of kept vs swapped per team; the quiet visibility curbs flakes without me chasing people. If your ATS can fire the captain reminder via webhook, @tevans69, even better.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌⁠​‍‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‍​⁠​​​⁠‌‍​⁠‌‍​⁠‌‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​⁠​⁠​​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‍​⁠‌‌​⁠‌‍⁠‌​⁠‍‌‌‍‍​‌​​‍‌‌​⁠‌​⁠‍‌​⁠⁠​⁠‍‌‌‍⁠⁠‌‌⁠⁠‌⁠‍‍‌‍‌‍‌⁠‍‍‌‍‍‌​‍​‍‌⁠⁠‌

Synced PagerDuty ICS to Google; ‘on-call = unavailable’ so Greenhouse never books them :sweat_smile:. Does your rota live elsewhere?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌⁠​‍‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‍​⁠​​​⁠‌‍​⁠‌‍​⁠‌‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​‌​⁠​​​⁠​‍​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​‍​‌‍‌‌‌‍‍⁠‌⁠‌​​⁠​⁠‌​⁠‍‌​​‍‌‍‌‍‌‌‌‌‌‌​⁠‌‌‍‌‌​⁠​‌‌​‍‌⁠‌​‌​‍⁠‌⁠‍​​‍​‍‌⁠⁠‌