Meeting Coordinator, Speaker Bureau

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Need to parse the posting. Let's extract content: - About Us: not needed as heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should not include About Us as a heading; maybe we can include as

if needed? But they said do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. They didn't forbid About Us heading, but they gave examples of headings to use. Probably we should only include sections that have content: About The Role, Responsibilities (You’re Good At...), Requirements/Qualifications/Skills (You Might Also Have...), Benefits (The Perks...), Pay (salary range), Schedule (travel requirements? maybe schedule? They mention flexible working, time zones, travel less than 25%). Schedule maybe not explicit; they have flexible working and time zones. Could treat as Schedule? Might be okay. We must not include sections with filler like "commensurate with experience". Not present. We need to preserve all substantive information; do not invent or summarize away detail. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We need to output only HTML fragment, no /, no markdown fences. Let's structure:

  About the role

  Love keeping moving pieces organized and making great events happen? As a Meeting Coordinator, you’ll support Life Sciences programs in a fast-paced, highly regulated environment where precision, communication, and follow-through really matter. You’ll partner closely with Customer Success Managers to bring educational programs to life, from early planning through final execution, while helping ensure compliance every step of the way. This is a great fit for someone who enjoys client-facing work, thrives on details, and likes turning complex logistics into seamless experiences.

  Then Responsibilities: list bullet points from "You’re Good At". Those are duties.

  Responsibilities

  • Managing program logistics from kickoff to execution, including registration, travel coordination, venue support, speaker communication, and meeting materials
  • Staying organized in a structured, deadline-driven environment where documentation, accuracy, and compliance are essential
  • Working directly with clients, vendors, and internal teams to answer questions, solve problems, and keep programs moving forward
  • Maintaining clean, accurate data across project management systems, reports, and program records
  • Juggling multiple priorities while delivering high-touch service and clear communication in a professional setting
  Then Requirements/Qualifications/Skills: The posting has "You Might Also Have" list and "A BS/BA degree". Also maybe "You Should Know" about virtual and time zones. Could treat as Requirements. We need to decide sections: Could combine Requirements and Qualifications and Skills into one? But instruction says prefer few substantive sections over many thin ones. Could have a single section "Requirements" covering experience, education, skills, etc. Or separate Qualifications and Skills if content distinct. Let's extract: You Might Also Have: - 1–5 years of experience supporting meetings, events, or program coordination - A background in marketing, sales support, or program management - Comfort working with Excel, Word, and data management tools to track logistics and reporting - Familiarity with Life Sciences, medical, or HCP-focused programs in a compliance-focused environment - A BS/BA degree You Should Know: - This role is virtual and operates within the Central/Eastern time zones. Also maybe "Travel requirements for this role are as follows: Less than 25%". That could be Schedule or maybe Benefits? It's travel requirement. We could have a section "Schedule" covering virtual, time zones, travel
• for list of benefits. The text: "Flexible Working ...", "Room to Grow ...", "Everyone has a voice ...", "Make your move ...", "We’ve got you covered ...", "We’re positive. You’ll love it. It starts from the top....", "Travel requirements for this role are as follows: Less than 25%". Actually travel requirement appears also in benefits? It appears after "We’ve got you covered". Might be separate. We need to preserve all substantive information; we should not duplicate. Let's parse benefits paragraphs: - Flexible Working: We believe that a flexible working environment is key to getting the best out of our teams. We will support you to work where you need to and when you need to, depending on how you work best. - Room to Grow: Our line of work and business structure challenge our people in a way that inspires growth, with learning and development built into every role. We give individuals ownership over the direction and speed in which they grow. - Everyone has a voice: We thrive on conversations that spark curiosity and empathy. No matter how big or how small, every voice is heard, considered and respected. - Make your move: The diversity of roles across BCD M&E’s global locations means that our people often find new adventures during their time with us. Join us as a meeting planner role in the UK, stay for a global marketing career — there’s always room to move. - We’ve got you covered: Our extensive benefits include comprehensive healthcare, retirement plans, continued education support, diverse work locations, travel and hotel discounts, volunteer and sustainability opportunities and a successful employee recognition program. - We’re positive. You’ll love it. It starts from the top. Our leaders lead with positivity, believe in our people and trust us to do the right thing. There will always be support along your journey, in little and big ways. - Travel requirements for this role are as follows: Less than 25% We could combine some but better to keep each as list item. Pay: The salary range: between $53,000 - $58,000. Also note about actual pay depends on skills etc. We'll include that. Schedule: Could include virtual, time zones, travel About the role

...

Responsibilities

...

Requirements

...

(list items for experience, background, tools familiarity, Life Sciences familiarity, BS/BA degree, virtual/time zones? Actually time zones maybe schedule.) But we might separate Qualifications and Skills. However we have limited distinct categories: experience/background/education (qualifications) and skills (Excel, Word, data management). Could split. Let's do:

Qualifications

• 1–5 years of experience supporting meetings, events, or program coordination
• A background in marketing, sales support, or program management
• A BS/BA degree

Skills

• Comfort working with Excel, Word, and data management tools to track logistics and reporting
• Familiarity with Life Sciences, medical, or HCP-focused programs in a compliance-focused environment

Then maybe a short

for "You Should Know: This role is virtual and operates within the Central/Eastern time zones." Could go under Schedule. Now Schedule:

Schedule

This role is virtual and operates within the Central/Eastern time zones. Travel requirements for this role are as follows: Less than 25%.

Benefits:

Benefits

• Flexible Working: We believe that a flexible working environment is key to getting the best out of our teams. We will support you to work where you need to and when you need to, depending on how you work best.
• Room to Grow: Our line of work and business structure challenge our people in a way that inspires growth, with learning and development built into every role. We give individuals ownership over the direction and speed in which they grow.
• Everyone has a voice: We thrive on conversations that spark curiosity and empathy. No matter how big or how small, every voice is heard, considered and respected.
• Make your move: The diversity of roles across BCD M&E’s global locations means that our people often find new adventures during their time with us. Join us as a meeting planner role in the UK, stay for a global marketing career — there’s always room to move.
• We’ve got you covered: Our extensive benefits include comprehensive healthcare, retirement plans, continued education support, diverse work locations, travel and hotel discounts, volunteer and sustainability opportunities and a successful employee recognition program.
• We’re positive. You’ll love it. It starts from the top. Our leaders lead with positivity, believe in our people and trust us to do the right thing. There will always be support along your journey, in little and big ways.

Pay:

Pay

The salary range for candidates in applicable jurisdictions in the US for the position of Meeting Coordinator, Speaker Bureau is between $53,000 - $58,000. The actual pay depends on your skills, qualifications, experience, geographical location, and project budget.

Check we didn't miss any substantive info: The "About Us" paragraph at start: we omitted. Is that considered substantive? It's about company overview. The instruction: use headings for sections like About the role etc. They didn't say to include About Us. Could we include as a

before sections? They said do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. About Us is not minor metadata; it's substantive. Should we include it? The instruction: "Prefer a few substantive sections over many thin ones." Could include About Us as a

without heading? They didn't forbid. But they gave examples of headings to use; not required to use only those. Could add a

about the company. However they said "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings for sections. It doesn't forbid other headings, but we should follow the pattern. The About Us could be a

without heading.