Events Operations Specialist

We need to output HTML fragment with sections: About the role? Actually the posting includes "Who are we? About LabCentral:" then "What is the role?" then "What will I do?" then "What will I bring?" then "What do we offer?" then "Compensation". Also "Equal Opportunity Employer" etc to be removed. We need headings using

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections when there is real specific content. The posting includes "About LabCentral" (company description) maybe not needed as heading? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map content to these headings. We need to decide which sections to include. We have: - About LabCentral (company overview) maybe not needed as a heading; could be part of About the role? The instruction says do NOT repeat the job title as a heading. It doesn't forbid a company overview heading, but they gave examples. Probably we should include "About the role" heading for description of role and maybe company overview? However they said "About the role" as example heading. Could use that for the role description (What is the role?). - Responsibilities: from "What will I do?" core responsibilities and shared team responsibilities. - Requirements/Qualifications: from "What will I bring?" desired qualifications and work environment. - Skills: maybe from qualifications (proficient in Microsoft Office, event platforms, AI tools, CRM, etc.) Could be part of Qualifications. - Benefits: from "What do we offer?" benefits list. - Pay: from "Compensation" salary range and bonus. - Schedule: maybe from work environment: flexibility to work early mornings/evenings, 40-50 hours per week standard. That's schedule info. We must not include sections with filler like "commensurate with experience". Not present. We must remove boilerplate: EEO, accommodation, etc. We must not include Job ID/requisition numbers. We must preserve all substantive information. We need to output only HTML fragment, no /, no markdown fences. Let's craft:

About the role

... include description from "What is the role?" plus maybe company overview? The "Who are we? About LabCentral:" is company overview; could be included in About the role or separate? Probably include in About the role as context. Thus:

Founded in the heart of Kendall Square in 2013, LabCentral is a network of shared laboratory spaces and scientific communities that serve as a launchpad for high-potential life-sciences and biotech start-ups. We deliver first-class facility and operational support, skilled laboratory personnel, and an expansive events program designed to add value to the community and promote connectivity—as well as the other critical services and support that early-stage companies need to begin start-up operations.

Are you someone who thinks in checklists and timelines without losing sight of the bigger picture? Do you love the puzzle of logistics and want to build the kind of vendor and partner relationships that make sustainable, high-quality event delivery possible? LabCentral is seeking an Events Operations Specialist. This is a collaborative role partnering alongside another Events Operations Specialist and reporting directly to the Director of Partnerships & Strategy. Our program runs more than 300 events a year across our Cambridge sites, from small LabCentral resident gatherings to day-long conferences. You'll be a strong fit for this role if you love building a run of show detailed enough that someone else could execute successfully without your oversight. Bonus points if you've ever quietly straightened the chairs in a room at someone else's event.

Then Responsibilities:

Responsibilities

• Own logistical delivery for events across all formats: conferences, corporate and internal, social and experiential, and virtual and hybrid
• Build and maintain run-of-show documents, production schedules, event timelines, and day-of briefings
• Serve as the primary on-site point of contact for logistics, A/V, setup, vendor coordination, and breakdown
• Coordinate event spaces, materials, and equipment across LabCentral's Cambridge sites
• Oversee virtual event setups using Zoom and Microsoft Teams
• Build and manage relationships with key operational partners: event venues, A/V providers, caterers, production, and staffing vendors
• Lead vendor sourcing, negotiation, and contract alignment with the goal of maintaining existing and building new reliable, high-quality supplier base that supports program volume
• Serve as the operational point of contact for resident companies, sponsors, and external guests during events
• Support groups hosting events by setting clear expectations of process
• Build and maintain the team's operational playbooks, checklists, templates, and onboarding materials
• Identify and implement improvements to event processes and across the events function
• Document information so the team's knowledge is never dependent on any single person
• Manage the events calendar, ensuring accurate scheduling and clear visibility across all sites and teams
• Shared team responsibilities: events calendar management and cross-team scheduling visibility, budget tracking and spend documentation, stakeholder communications and partner updates, on-site troubleshooting and real-time event support

But note the last bullet includes a sentence describing shared responsibilities; we can break into separate bullets. Let's split:

Events calendar management and cross-team scheduling visibility

Budget tracking and spend documentation

Stakeholder communications and partner updates

On-site troubleshooting and real-time event support

Now Requirements/Qualifications:

Qualifications

• 2–3 years of experience in events operations, coordination, or a closely related field (ideally across multiple event formats and volumes)
• Demonstrated experience managing event logistics end-to-end, from planning through day-of execution and post-event wrap-up
• Experience sourcing and coordinating with vendors, venues, or external partners (including scheduling, contracts, and follow-through)
• Proficient in Microsoft Office Suite and experience with event management platforms (Swoogo, Eventbrite, or similar) for registration and calendar management
• Comfort using AI tools in your day-to-day work and interest in finding where they take friction out of event operations
• Familiarity with CRM systems, HubSpot preferred
• Familiarity with the life sciences or startup ecosystem a bonus
• Ability to move through office and event environments during setup and breakdown
• Ability to travel locally between LabCentral sites
• Ability to lift and carry a minimum of 50 pounds
• Flexibility to work early mornings or evenings as needed based on the events calendar (maintaining 40-50 hours per week is standard)

But we also have Skills maybe separate; but we can incorporate skills into Qualifications. However instruction: Use headings like Skills. Could create Skills heading for technical proficiencies. But we already have them in Qualifications. To follow instruction, we could create Skills heading for those technical skills: Microsoft Office, event platforms, AI tools, CRM. But we risk duplication. Better to keep Qualifications and maybe Skills separate for clarity. Let's decide: We'll have Qualifications for experience and background, Skills for technical proficiencies. Thus:

Qualifications

• 2–3 years of experience in events operations, coordination, or a closely related field (ideally across multiple event formats and volumes)
• Demonstrated experience managing event logistics end-to-end, from planning through day-of execution and post-event wrap-up
• Experience sourcing and coordinating with vendors, venues, or external partners (including scheduling, contracts, and follow-through)
• Familiarity with the life sciences or startup ecosystem a bonus

Skills

• Proficient in Microsoft Office Suite
• Experience with event management platforms (Swoogo, Eventbrite, or similar) for registration and calendar management
• Comfort using AI tools in day-to-day work and interest in finding where they take friction out of event operations
• Familiarity with CRM systems, HubSpot preferred
• Ability to move through office and event environments during setup and breakdown
• Ability to travel locally between LabCentral sites
• Ability to lift and carry a minimum of 50 pounds
• Flexibility to work early mornings or evenings as needed based on the events calendar (maintaining 40-50 hours per week is standard)

Now Benefits:

Benefits

• Fully covered medical and dental premiums (including deductible costs)
• Long and short-term disability & life insurance
• Flexible vacation
• Three months fully paid parental leave
• 401K match up to 6% with immediate vestment
• Transportation reimbursements (parking pass, MBTA, or bike maintenance)
• Health & wellness reimbursements for fitness, yoga, massage therapy, and other holistic health practices
• Technology stipend: monthly cell phone stipend and yearly reimbursements for cell phone repairs
• Professional growth stipend for continuing education and training, plus student loan reimbursement
• Fantastic work environment with snacks and in-house programming on thought‑provoking and diverse topics

Pay:

Pay

Salary range: $57,000–$74,000, with potential to earn a bonus of 8% based on company performance. Approximate monetary value of benefits (based on an individual – dependents increase value): $22,000.

Schedule: we already included flexibility in Skills; but we could also have Schedule heading. However we already have schedule info in Skills. To avoid duplication, maybe we keep schedule in Skills and not create separate Schedule heading. But instruction says include a section ONLY when posting has real specific content for it. The posting does mention flexibility to work early mornings/evenings and 40-50 hours per week standard. That's schedule info. Could be placed under Schedule heading. But we already placed it under Skills. Might be better to move schedule info to Schedule heading and remove from Skills. Let's do that. Thus:

Schedule

Flexibility to work early mornings or evenings as needed based on the events calendar; maintaining 40‑50 hours per week is standard.

And adjust Skills to exclude schedule. Now ensure we didn't repeat job title as heading. We didn't. We must not include any boilerplate like EEO etc. We removed. Now output HTML fragment. Check that we have all substantive information: company overview, role description, responsibilities (including shared), qualifications, skills, benefits, pay, schedule. Also we included vendor management, etc. Check we didn't miss any: "Oversee virtual event setups using Zoom and Microsoft Teams" included in responsibilities. "Build and maintain run-of-show documents, production schedules, event timelines, and day-of briefings" included. "Coordinate event spaces, materials, and equipment across LabCentral's Cambridge sites" included. "Serve as the primary on-site point of contact for logistics, A/V, setup, vendor coordination, and breakdown" included. "Serve as the operational point of contact for resident companies, sponsors, and external guests during events" included. "Support groups hosting events by setting clear expectations of process" included. "Build and maintain the team's operational playbooks, checklists, templates