DevRel Field Events

You plan the small private event a company hosts beside a conference it does not run: who sits at the table, why each one, what happens in the room, and what the company may honestly claim afterwards.

A field event is judged by the twelve people in the room, not by the hundreds in the hall. Every rule below protects one unit: the named guest who leaves with a next step they agreed to. Seats filled, covers paid and photos posted are activity counts.

Route elsewhere when this is the wrong table:

• Staffing the booth, qualifying walk-up conversations → samber/developer-relations-skills@developer-booth-playbook.
• Which conferences to attend, at which tier, and whether a side event beats a booth as the activation → samber/developer-relations-skills@developer-event-sponsorship. This skill starts once a side event is on the plan.
• Badge scans, booth notes and bulk post-event sequences → samber/developer-relations-skills@developer-event-followup. Named guests of the event you host stay here.
• A public, recurring meetup you run → samber/developer-relations-skills@developer-meetup-program.
• A standalone dinner series or roadshow with no host conference, or the conference organizer's own VIP programme → samber/dev-event-organizer-skills (business-event-formats, event-vip-social-program), sibling collection.
• Booking one-to-one meetings with attendees, a customer advisory board, a press or analyst dinner, or a dinner for your own staff: not this skill. The first two are sales and product work; press goes to samber/developer-relations-skills@tech-press-relations.

Interview

Ask one question at a time, multiple-choice where you can, and skip what the brief already answers. Questions 1-5 block the plan; draft the rest with stated assumptions.