Events Specialist

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, legal, etc. Keep substantive info. We need to parse the posting. Content: Company description: "The Company Versaterm is a PE-backed, high-growth SaaS company building a fully integrated platform across the entire public safety ecosystem — dispatch, law enforcement, forensics, courts, and beyond. We've grown through strategic acquisitions and deep product investment. What connects all of it is a single purpose: give public safety agencies the tools and insights to make better decisions in high-stakes moments. When a 911 call is answered, a detective investigates a case, or a forensic lab processes evidence, there's a good chance our software is working behind the scenes. That's been true for over four decades. AI is central to where we're going. Not as a feature but as core infrastructure. We're embedding intelligence directly into the workflows our customers rely on every day, and we're doing it alongside them. Our customers tell us what the mission demands. We build what answers it. This work attracts a specific kind of person — someone who wants to be pushed by great people, build things that outlast a sprint cycle, and go home knowing the work connected back to something real." That's about the company, could be "About the role"? Actually "About the role" is more about the role description. The posting includes "The Role" heading then description of role. So we can put that under

About the role

maybe. Or we could treat "About the role" as the role description. The company description could be considered "About the company" but we don't have that heading. We could include it under About the role? Might be okay. But we need to preserve all substantive info. We could include a

with company description before the role heading? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. Let's extract: - About the role: The description of the role (The Events Specialist plays a key role...). That's under "The Role". So we can put that as About the role. - Responsibilities: The bullet list under "What You Do": Event Planning & Execution, Industry Engagement, Workshops & Symposiums, Versaterm Team Meetings & Conferences, Vendor Management, Registration & Evaluation, Reporting & Analysis, Additional Duties. Those are responsibilities. - Requirements: The bullet list under "What You Bring": Bachelor's degree..., minimum 2-3 years experience..., Strong organizational skills..., Excellent communication..., Proficiency in Microsoft Office..., Ability to travel occasionally..., Note about CJIS compliance etc. That's requirements/qualifications. We could separate Qualifications vs Skills. The posting lumps education, experience, skills. We could put Requirements for education/experience, Skills for abilities. But we can also combine. The instruction: Prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements (including education, experience, skills, CJIS note). Benefits, Pay, Schedule: we need to see if any content. Benefits: The posting mentions "Versaterm is committed to fair and equitable compensation that is competitive, consistent, and aligned with the value each role contributes to our organization. The starting salary for this position will be dependent upon many factors, such as the successful candidate's skills, experience, education, training as well as internal equity, market data, and business needs. In addition to base salary and our comprehensive benefits offering, some roles may also be eligible for variable compensation such as incentive plans or discretionary performance bonuses." That's about compensation and benefits. It mentions "comprehensive benefits offering" but does not list specifics. It's vague. According to instruction: Do NOT create Benefits section unless posting actually states them. It says "comprehensive benefits offering" but no specifics. Is that enough? It says "some roles may also be eligible for variable compensation such as incentive plans or discretionary performance bonuses." That's still vague. The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Here they mention "comprehensive benefits offering" but not details. That could be considered filler. Safer to omit Benefits section. Pay: They mention starting salary dependent upon many factors, base salary, comprehensive benefits offering, variable compensation. No specific numbers. That's filler. So we should not create Pay section. Schedule: Not mentioned. So omit. Thus we will have sections: About the role, Responsibilities, Requirements (maybe combine qualifications and skills). Could also split into Requirements and Skills but we prefer few sections. We need to use

• for any list of duties/requirements/benefits. So for Responsibilities we need a list. For Requirements we need a list (education, experience, skills, CJIS note). Use

  for prose. We must not repeat job title as heading. The job title is "Events Specialist". Not used as heading. We must not include Job ID etc. We must remove boilerplate: EEO, equal opportunity, legal, etc. Also remove "Versaterm is committed to fair and equitable compensation..."? That's compensation but we decided to omit Benefits/Pay. However that paragraph also mentions "comprehensive benefits offering" and variable compensation. Since we are omitting Benefits/Pay, we might still need to include that info? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we omit the Benefits/Pay section, we are losing that substantive info (mention of benefits and variable compensation). But we could include it as a

  under About the role or Responsibilities? It's not really a responsibility. Could be a separate section "Compensation and Benefits" but we don't have that heading allowed. The allowed headings are limited to those list. We could put it under About the role as a paragraph? But About the role is supposed to be about the role, not compensation. However we could still include a

  about compensation within About the role if we want to preserve info. The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could create a Benefits section only if there is real specific content. The posting says "comprehensive benefits offering" but not specific. That's vague; could be considered filler. However the instruction says never create Benefits section unless posting actually states them. It does state "comprehensive benefits offering". That is a statement, albeit not specific. Is that enough? The examples of filler include "commensurate with experience", "not specified", "N/A", "varies", "TBD". "comprehensive benefits offering" is not exactly those, but still vague. I'd lean to omit Benefits section to avoid filler. But we must preserve ALL substantive information. If we omit that sentence, we lose info about benefits and variable compensation. However maybe that's considered boilerplate? It's generic statement about compensation. Might be considered boilerplate. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This compensation statement is not exactly those categories, but could be considered generic boilerplate. However it's part of the posting. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it. Where to put? Could add a

  after Responsibilities or Requirements, maybe under a heading "Compensation" but not allowed. Could we treat it as part of About the role? It's not about the role but could be placed there as a paragraph. The instruction didn't forbid adding extra paragraphs outside headings. It just says use

  for section headings (list). So we can have

  elements anywhere. So we can keep the compensation paragraph as a

  without a heading, or maybe under a heading "About the role"? That would be weird but acceptable. Better: Keep it as a

  after the Responsibilities section, before Requirements, with no heading. That preserves info. Similarly, the CJIS note is a requirement; we can include in Requirements list. Now let's craft HTML. Structure:

  About the role

  ... company description + role description? Actually About the role should focus on role. We'll put the role description paragraph(s) from "The Role" section. We have: "The Events Specialist plays a key role in planning and executing a variety of live and virtual events, including industry conferences, workshops, symposiums, and internal meetings. This role supports the full lifecycle of event management—from pre-event planning and logistics to post-event evaluation and reporting." That's the prose. We'll put that in

  . Then Responsibilities:

  Responsibilities

  • Event Planning & Execution: Assist with all aspects of planning and coordinating live and virtual events, including venue selection, scheduling, logistics, and on-site/online support.
  • Industry Engagement: Support the organization's presence at external industry events, including registration, booth coordination, and materials preparation.
  • Workshops & Symposiums: Coordinate internal and external educational events, ensuring smooth execution and alignment with strategic goals.
  • Versaterm Team Meetings & Conferences: Manage logistics for company-wide meetings and conferences, including agenda development, speaker coordination, and technical setup.
  • Vendor Management: Research vendors, maintain contracts, and liaise with external partners to ensure timely and quality service delivery.
  • Registration & Evaluation: Oversee attendee registration processes and compile post-event evaluations to assess success and identify areas for improvement.
  • Reporting & Analysis: Prepare summaries of event costs, attendee demographics, and feedback to inform future planning.
  • Additional Duties: Performs other related duties as assigned to support team objectives, departmental needs, and overall organizational priorities.
  Then Requirements (including qualifications, skills, CJIS note):

  Requirements

  • Bachelor's degree or diploma in Event Management, Communications, Marketing, or a related field, or equivalent combination of education and experience.
  • A minimum 2-3 years of experience in event coordination or administrative support, ideally in a corporate or client-facing environment.
  • Strong organizational skills and attention to detail.
  • Excellent communication and interpersonal abilities.
  • Proficiency in Microsoft Office Suite; experience with event management software is a plus.
  • Ability to travel occasionally and work flexible hours during events.
  • Due to the nature of our work with public safety agencies, this position requires compliance with the FBI's Criminal Justice Information Services (CJIS) Security Policy. Candidates must successfully pass a comprehensive, fingerprint-based background check. Please note that specific customer contracts may impose additional security verification requirements. Obtaining and maintaining all required security clearances is a condition of employment.
  Now we need to include the compensation paragraph somewhere. Let's put after Requirements as a

  without heading.

  Versaterm is committed to fair and equitable compensation that is competitive, consistent, and aligned with the value each role contributes to our organization. The starting salary for this position will be dependent upon many factors, such as the successful candidate's skills, experience, education, training as well as internal equity, market data