dev-event-hiringlisted

Employer-side hiring for tech-event-organizing roles - producer/manager/coordinator, and the community-manager-shaped end of the field. Calibrates the scorecard to operating context (in-house, agency, non-profit/community, or a standing conference business), builds the loop from the general event-planner sequence plus CMX's five-competency set and paid mini-audit work sample, flags the "one hire owns sponsorship, content and production" consolidation pattern seen in postings, sources candidates from general event-industry boards since no tech-specific one exists, and gates compensation on named sources (PCMA, BLS, Glassdoor) rather than a blended figure. Use when the user asks how to hire an event producer or manager, write a posting, design a loop, or hire an event community manager. Do NOT use for candidate prep (samber/dev-event-organizer-skills@dev-event-career) or team org design (samber/dev-event-organizer-skills@event-team-structure).
samber/dev-event-organizer-skills · ★ 2 · AI & Automation · score 76

Install: claude install-skill samber/dev-event-organizer-skills

# Dev Event Hiring Build the artefacts a hiring manager needs to recruit a tech-event-organizing role: a scorecard calibrated to operating context, an interview loop assembled from the field's real (if partial) evidence, a sourcing plan, and a compensation stance that names its source instead of blending numbers. Out of scope, hand off instead: - **Coaching the candidate** - samber/dev-event-organizer-skills@dev-event-career is the mirror image of this skill. - **The standing organizing team's own structure** - legal entity, decision rights, succession, the volunteer-to-paid threshold - samber/dev-event-organizer-skills@event-team-structure. Route "should we hire our first paid role at all" there; this skill answers "how do we hire well, once we've decided to." If the user is job-hunting rather than hiring, say so in one line and route them to dev-event-career. ## Interview Ask one question at a time, multiple-choice where possible. Skip anything already answered. Questions 7-9 re-rank the artefacts below. 1. Operating context: (a) in-house at a company running its own conference or meetup series (b) an event-production agency hiring for client work (c) a non-profit/foundation or volunteer-community-run event making its first paid hire (d) a standing for-profit conference business. 2. Target role shape: (a) producer/logistics-and-production-focused (b) manager, blending production and stakeholder management (c) community-manager-shaped (meetup organizer, developer-comm