Managing the queue

Once you're live, the queue fills with seekers whose skills overlap your attached roles. Your job is to accept the strong ones, decline cleanly, and pace yourself so candidate quality doesn't drop. Here's the rhythm.

Accept

When the matchmaker pairs you with a seeker, you see a candidate card with their headline, skills, years-of-experience band, and compensation expectation. The role they were matched against is labeled. You have ~30 seconds to accept before the slot rotates.

Once you accept and the seeker accepts, the live video room opens. See after the interview for what happens when the room closes.

Decline

If the candidate isn't a fit, decline cleanly. Decline reasons feed back into the matchmaker — if you decline three seekers in a row for "below experience band", the matchmaker tightens the band filter for your active session.

Decline reasons are private — the seeker doesn't see them. They only see "the recruiter passed". Be honest in the reason field; the matchmaker uses it to improve your match quality.

Pace

A focused recruiter runs roughly one interview per 30 minutes — that includes 20-25 minutes of live conversation, 5 minutes of notes, and a small breath between. Twelve interviews in a 6-hour event is a tough day; 8 is sustainable. Pushing past 12 in a day is when candidate quality assessment degrades.

Pause

Mid-event, you can pause the queue without ending the event. Useful when:

• You need a bathroom / coffee / lunch break.
• The queue is backed up and you want to drain matches before more pile in.
• A matched candidate has technical issues and you need a few minutes to triage.

Resume reopens the queue without losing seekers who joined during the pause.

Multi-recruiter teams

On Pro and above, multiple recruiters share a single live event. The matchmaker round-robins matches across available recruiters — whoever is free gets the next candidate. You see your own queue view; teammates see theirs. Shared decline reasons feed back into all team members' match quality.

Driving from an agent

• jobbydev_match_accept — accept a pending match. Only callable from a session, not from a PAT — see the humans-only rule.
• jobbydev_match_decline — decline with a reason. PAT-callable.
• jobbydev_event_pause / jobbydev_event_resume.

Decline-reason taxonomy

Decline reasons feed back into the matchmaker for your active session. Use the structured options where they fit; free-text is fine for nuanced calls. The matchmaker keys on these:

• below_experience_band — used 3+ times in a session, the matchmaker tightens the experience-year filter for your queue.
• skills_mismatch — pair with the specific missing skill; the matchmaker adjusts skill-overlap scoring for the session.
• comp_misalignment — used 2+ times, the matchmaker raises the comp-overlap floor.
• visa_unavailable — one-and- done filter; the matchmaker stops pairing visa-needing seekers for your session.
• communication_concerns— doesn't feed matchmaker; seekers with repeated decline-reasons of this shape get a feedback nudge on their profile-improvement page.
• cultural_fit_concerns — same as above. Use sparingly — vague culture-fit declines feel like bias when they pile up.
• not_interested_right_now — recruiter is full / triaging; seeker stays in queue.
• other— free-text only. Doesn't feed matchmaker.

Pacing reference

For a 4-hour live event with one recruiter:

For a 4-hour event with two recruiters in parallel: roughly double the "sustainable" column, but each recruiter sees their own queue.

Related reading

• After the interview — report cards, advance / pass, ATS sync.
• Troubleshooting — empty queues, declined candidates piling up.