Creating events

A live event is the unit of recruiter activity on Jobby.dev. You attach roles, set a window, and run interviews during that window. Here's how to think about scheduling, branding, and event cadence.

Event types

Three rhythms recruiters typically pick from:

Recurring weekly drop-in (e.g. every Tuesday 14:00-17:00). Best for active hiring teams with steady inbound; becomes a known reference point seekers can plan around.
One-off hiring sprint (e.g. a single 4-hour Friday for a specific senior role). Best when you have an interview-ready hiring manager block and want concentrated throughput.
Burst-on-demand — flick on for 30 minutes when you have a slot to fill, flick off when done. Useful for senior roles where the candidate pool is small and you want a tighter window.

Scheduling

Pick a window. Events go through three states: scheduled, live, ended. Scheduled events are visible in the discovery feed with a countdown — seekers can "join when live" to be auto-queued the moment you go live. Live events accept queue joiners and run the matchmaker. Ended events don't appear in discovery anymore; their data persists for reporting.

Recommended buffer: open the event 5 minutes before you actually want to start interviewing. The queue fills, the matchmaker scores, and you start your first interview within a minute of going live.

Branding

Each event card shows your company logo, name, one-line description, and an optional event-specific tagline. Power Play tier unlocks per- event branding (colors, intro video). Lower tiers inherit the company-level branding from setup.

Attaching roles

Every event needs at least one role. Multi-role events run all attached roles through the matchmaker — a seeker matches against the best-fit role in your event, and you see which role they were matched against in the candidate card. See posting roles.

Pacing

Keep your live-event windows realistic for your team's bandwidth. Two recruiters running one 4-hour event will run ~12 interviews; one recruiter running two 2-hour events on different days will see better-rested interviewer signal and a fresher queue.

Pause / resume

Mid-event you can pause the queue (no new joiners, no new matches) without ending the event. Useful when you need a 10-minute break or you're draining a backlog. Resume reopens the queue without losing seekers who joined during the pause.

Driving from an agent

Every event action above maps to an MCP tool:

jobbydev_create_event — schedule the window.
jobbydev_job_create — attach a role.
jobbydev_event_go_live — flip to live.
jobbydev_event_pause / _resume — temporary halts.
jobbydev_event_end — close the event.

See MCP tools reference.