2 min lesson
Propose one improvement: before and after
Put yourself in this case. "You've cleaned a messy pipeline and want to propose one process change. What makes a proposal land in this exercise?" Give the clearest next step.
Step 1 of 2
Propose one improvement: before and afterillustrative numbers; automations only if your Ashby setup supports them
Scorecards trickle in days after interviews; HMs ping you to chase each one.
Debrief gets scheduled only once the last scorecard lands.
Median time from final interview to decision: ~5 days.
Scorecard reminder fires automatically 1 hour post-interview; a daily digest flags any still missing at 24h.
Debrief is pre-booked when the loop is built, not after feedback lands.
Target: final interview to decision under 2 days.
Don't declare victory on a hunch. Check two things over the next handful of loops: did median time-to-decision actually drop and did scorecard completion-at-24h go up without interviewers complaining the reminders are noise. Watch for the side effect: an over-eager reminder that pings someone who already submitted. Confirm the automation respects "already done" before you scale it past one team.
- Less interviewer friction
- Automated nudges beat you personally chasing busy engineers, which protects the relationship you need for the next loop.
Show judgment about scope. Pick the one change with the highest friction removed per unit of effort and say why you'd leave the rest alone for now; a giant ATS overhaul is the trap. "I'd ship the scorecard reminder first because it's a small change that fixes the slowest part of our loop. A full kit redesign can wait until we've felt the gain." That restraint shows initiative and judgment together.