Freelance In Person Event Host - St. Louis, MO
Visit.org · St Louis, MO · 3 wk ago
On-siteOTHRContract
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. Must preserve all substantive info.
We need to parse the posting.
Content:
- Intro: "Visit.org is looking for a passionate and ambitious Freelance In-Person Event Host in St. Louis, MO to join our Events team on a contract basis. The Event Host will facilitate interactive social impact experiences for our corporate partner on location for in-person event(s). This is an opportunity for an individual with stage experience who finds comfort in front of a crowd and wants to contribute their skills to positively impact local communities. The right candidate will be based in St. Louis, MO, and have corporate event experience, an entrepreneurial spirit, extreme passion for our mission, and the energy and discipline to come in and be a builder in a start-up tech environment."
- "What Motivates Us" paragraph: "There is room for everyone! We empower each other to innovate and create processes that use technology to generate meaningful, lasting change. We enjoy the challenge of finding solutions to problems that are not a way around it but through it. We're driven by the opportunity to help enterprises and their employees around the world to contribute to their communities."
- "When You Join the Team": "You'll join a movement from the ground floor and a team of purpose-driven people with a strong sense of responsibility, ownership, and pride that we're building this thing togetherYou'll combine passion, purpose, and a paycheck—Visit.org team members get out of bed every day knowing their work is meaningful and has a tangible impact on individuals and communities around the world"
- "About Visit.org": description.
- "Role & Responsibilities:" then bullet list? Actually it's a paragraph: "Host impactful, engaging, team-building, social impact events that support a great causeWelcome, engage, and inspire participants while supporting nonprofits in facilitating in-person eventsPresent events in partnership with a nonprofit organization or lead the event in fullBe skilled at storytelling and getting volunteers to really understand and feel the impact of their timeBe able to deliver clear instructions to lead volunteers through impactful, engaging activities Be available for 1-4 prep meetings prior to an event (depending on event complexities)"
- Then "Requirements Qualifications:" then list: "Fluent in English Based in St. Louis, MOAvailability to work on a contract per event basis, including prep timeStrong experience in event Hosting, Facilitation, and emceeing is requiredComfortable interacting with both large groups of people and small groups or one-on-one, keeping the events flowing and the participants engagedEasy conversationalists with lots of energy, a charismatic personality, and a sense of funExperience with group facilitation and managing group dynamicsStoryteller, High energy, and a positive attitudeQuick thinker—sometimes during events, things go wrong; you can problem-solve on the flyExtremely comfortable with and enjoys public speakingExcellent customer service and presentation skills"
- Then "Benefits": "This is an on-location, in-person, per-event contract role in St. Louis, MO. This role is open only to candidates already based in St. Louis, MO. Compensation is paid per event, depending on experience."
We need to separate sections: About the role (maybe intro), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide what content goes where.
The posting includes "Role & Responsibilities:" which we can map to Responsibilities.
"Requirements Qualifications:" seems combined; we can split into Requirements and Qualifications maybe.
Skills: maybe list of skills like storytelling, high energy, etc.
Benefits: we have benefits description.
Pay: compensation per event depending on experience.
Schedule: maybe not specified; we have "Availability to work on a contract per event basis, including prep time" but not schedule specifics. Should we include Schedule? Only if posting actually states them. It mentions availability to work per event basis, but not specific schedule like part-time/full-time. Might be considered schedule info? The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state compensation per event depending on experience => Pay section can be included. Benefits section: they gave benefits description (on-location, in-person, per-event contract role, only St. Louis based). That's more like job details but could be considered Benefits. We'll include Benefits.
Schedule: Not explicitly stated like "full-time", "part-time", "flexible hours". There's "Availability to work on a contract per event basis, including prep time" which is about availability but not schedule. Might be considered schedule? Safer to omit Schedule section if not explicit.
Now About the role: we can include introductory paragraphs about role motivation, mission, About Visit.org maybe as About the role? Actually "About Visit.org" is separate. Could be About the role? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content.
We have content for:
- About the role: maybe the initial description of role and motivations. Could combine "What Motivates Us", "When You Join the Team", "About Visit.org". That seems like about the role/company.
- Responsibilities: the bullet list under Role & Responsibilities.
- Requirements: maybe the basic requirements: Fluent in English, Based in St. Louis, MO, Availability to work on a contract per event basis, Strong experience in event Hosting, Facilitation, and emceeing is required.
- Qualifications: maybe the list of skills/experience: Comfortable interacting with groups, Easy conversationalists, Experience with group facilitation, Storyteller, High energy, Positive attitude, Quick thinker, Extremely comfortable with public speaking, Excellent customer service and presentation skills.
- Skills: maybe overlapping with Qualifications; but we could treat Qualifications as skills. However we need to avoid duplication. Perhaps we combine Requirements and Qualifications into one section? But instruction says we can have both if content distinct. Let's try to split.
Requirements: mandatory baseline: Fluent in English, Based in St. Louis, MO, Availability to work on a contract per event basis, Strong experience in event Hosting, Facilitation, and emceeing is required.
Qualifications: desired attributes: Comfortable interacting with both large groups and small groups/one-on-one, Easy conversationalists with lots of energy, charismatic personality, sense of fun, Experience with group facilitation and managing group dynamics, Storyteller, High energy, positive attitude, Quick thinker—problem solve on the fly, Extremely comfortable with and enjoys public speaking, Excellent customer service and presentation skills.
Skills: maybe we could list specific skills like storytelling, public speaking, facilitation, customer service, etc. But that overlaps with Qualifications. Could combine Qualifications and Skills into one. But we need to follow instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one "Requirements" section, and have Skills separate? Or combine Qualifications and Skills.
Let's think: The posting lumps "Requirements Qualifications:" then a list. So it's basically combined. So we could have a single section "Requirements" containing all those items. Then we could have a "Skills" section maybe not needed. But we need to include sections only when posting has real specific content. If we put Skills but it's just same as Requirements, might be thin. Better to have just Requirements.
Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay.
We need to ensure we don't create sections with filler like "commensurate with experience". Pay section: "Compensation is paid per event, depending on experience." That's specific enough.
Benefits: "This is an on-location, in-person, per-event contract role in St. Louis, MO. This role is open only to candidates already based in St. Louis, MO." That's benefits? It's more job details but we can treat as Benefits.
Now we need to format using
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. Must preserve all substantive info.
We need to parse the posting.
Content:
- Intro: "Visit.org is looking for a passionate and ambitious Freelance In-Person Event Host in St. Louis, MO to join our Events team on a contract basis. The Event Host will facilitate interactive social impact experiences for our corporate partner on location for in-person event(s). This is an opportunity for an individual with stage experience who finds comfort in front of a crowd and wants to contribute their skills to positively impact local communities. The right candidate will be based in St. Louis, MO, and have corporate event experience, an entrepreneurial spirit, extreme passion for our mission, and the energy and discipline to come in and be a builder in a start-up tech environment."
- "What Motivates Us" paragraph: "There is room for everyone! We empower each other to innovate and create processes that use technology to generate meaningful, lasting change. We enjoy the challenge of finding solutions to problems that are not a way around it but through it. We're driven by the opportunity to help enterprises and their employees around the world to contribute to their communities."
- "When You Join the Team": "You'll join a movement from the ground floor and a team of purpose-driven people with a strong sense of responsibility, ownership, and pride that we're building this thing togetherYou'll combine passion, purpose, and a paycheck—Visit.org team members get out of bed every day knowing their work is meaningful and has a tangible impact on individuals and communities around the world"
- "About Visit.org": description.
- "Role & Responsibilities:" then bullet list? Actually it's a paragraph: "Host impactful, engaging, team-building, social impact events that support a great causeWelcome, engage, and inspire participants while supporting nonprofits in facilitating in-person eventsPresent events in partnership with a nonprofit organization or lead the event in fullBe skilled at storytelling and getting volunteers to really understand and feel the impact of their timeBe able to deliver clear instructions to lead volunteers through impactful, engaging activities Be available for 1-4 prep meetings prior to an event (depending on event complexities)"
- Then "Requirements Qualifications:" then list: "Fluent in English Based in St. Louis, MOAvailability to work on a contract per event basis, including prep timeStrong experience in event Hosting, Facilitation, and emceeing is requiredComfortable interacting with both large groups of people and small groups or one-on-one, keeping the events flowing and the participants engagedEasy conversationalists with lots of energy, a charismatic personality, and a sense of funExperience with group facilitation and managing group dynamicsStoryteller, High energy, and a positive attitudeQuick thinker—sometimes during events, things go wrong; you can problem-solve on the flyExtremely comfortable with and enjoys public speakingExcellent customer service and presentation skills"
- Then "Benefits": "This is an on-location, in-person, per-event contract role in St. Louis, MO. This role is open only to candidates already based in St. Louis, MO. Compensation is paid per event, depending on experience."
We need to separate sections: About the role (maybe intro), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide what content goes where.
The posting includes "Role & Responsibilities:" which we can map to Responsibilities.
"Requirements Qualifications:" seems combined; we can split into Requirements and Qualifications maybe.
Skills: maybe list of skills like storytelling, high energy, etc.
Benefits: we have benefits description.
Pay: compensation per event depending on experience.
Schedule: maybe not specified; we have "Availability to work on a contract per event basis, including prep time" but not schedule specifics. Should we include Schedule? Only if posting actually states them. It mentions availability to work per event basis, but not specific schedule like part-time/full-time. Might be considered schedule info? The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state compensation per event depending on experience => Pay section can be included. Benefits section: they gave benefits description (on-location, in-person, per-event contract role, only St. Louis based). That's more like job details but could be considered Benefits. We'll include Benefits.
Schedule: Not explicitly stated like "full-time", "part-time", "flexible hours". There's "Availability to work on a contract per event basis, including prep time" which is about availability but not schedule. Might be considered schedule? Safer to omit Schedule section if not explicit.
Now About the role: we can include introductory paragraphs about role motivation, mission, About Visit.org maybe as About the role? Actually "About Visit.org" is separate. Could be About the role? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content.
We have content for:
- About the role: maybe the initial description of role and motivations. Could combine "What Motivates Us", "When You Join the Team", "About Visit.org". That seems like about the role/company.
- Responsibilities: the bullet list under Role & Responsibilities.
- Requirements: maybe the basic requirements: Fluent in English, Based in St. Louis, MO, Availability to work on a contract per event basis, Strong experience in event Hosting, Facilitation, and emceeing is required.
- Qualifications: maybe the list of skills/experience: Comfortable interacting with groups, Easy conversationalists, Experience with group facilitation, Storyteller, High energy, Positive attitude, Quick thinker, Extremely comfortable with public speaking, Excellent customer service and presentation skills.
- Skills: maybe overlapping with Qualifications; but we could treat Qualifications as skills. However we need to avoid duplication. Perhaps we combine Requirements and Qualifications into one section? But instruction says we can have both if content distinct. Let's try to split.
Requirements: mandatory baseline: Fluent in English, Based in St. Louis, MO, Availability to work on a contract per event basis, Strong experience in event Hosting, Facilitation, and emceeing is required.
Qualifications: desired attributes: Comfortable interacting with both large groups and small groups/one-on-one, Easy conversationalists with lots of energy, charismatic personality, sense of fun, Experience with group facilitation and managing group dynamics, Storyteller, High energy, positive attitude, Quick thinker—problem solve on the fly, Extremely comfortable with and enjoys public speaking, Excellent customer service and presentation skills.
Skills: maybe we could list specific skills like storytelling, public speaking, facilitation, customer service, etc. But that overlaps with Qualifications. Could combine Qualifications and Skills into one. But we need to follow instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one "Requirements" section, and have Skills separate? Or combine Qualifications and Skills.
Let's think: The posting lumps "Requirements Qualifications:" then a list. So it's basically combined. So we could have a single section "Requirements" containing all those items. Then we could have a "Skills" section maybe not needed. But we need to include sections only when posting has real specific content. If we put Skills but it's just same as Requirements, might be thin. Better to have just Requirements.
Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay.
We need to ensure we don't create sections with filler like "commensurate with experience". Pay section: "Compensation is paid per event, depending on experience." That's specific enough.
Benefits: "This is an on-location, in-person, per-event contract role in St. Louis, MO. This role is open only to candidates already based in St. Louis, MO." That's benefits? It's more job details but we can treat as Benefits.
Now we need to format using for each section heading, then content:
for prose,
- for lists.
We need to preserve all substantive information; do not invent or summarize away detail.
Let's extract each piece.
About the role content:
We need to combine:
- Intro: "Visit.org is looking for a passionate and ambitious Freelance In-Person Event Host in St. Louis, MO to join our Events team on a contract basis. The Event Host will facilitate interactive social impact experiences for our corporate partner on location for in-person event(s). This is an opportunity for an individual with stage experience who finds comfort in front of a crowd and wants to contribute their skills to positively impact local communities. The right candidate will be based in St. Louis, MO, and have corporate event experience, an entrepreneurial spirit, extreme passion for our mission, and the energy and discipline to come in and be a builder in a start-up tech environment."
- What Motivates Us: "There is room for everyone! We empower each other to innovate and create processes that use technology to generate meaningful, lasting change. We enjoy the challenge of finding solutions to problems that are not a way around it but through it. We're driven by the opportunity to help enterprises and their employees around the world to contribute to their communities."
- When You Join the Team: "You'll join a movement from the ground floor and a team of purpose-driven people with a strong sense of responsibility, ownership, and pride that we're building this thing togetherYou'll combine passion, purpose, and a paycheck—Visit.org team members get out of bed every day knowing their work is meaningful and has a tangible impact on individuals and communities around the world"
Note there is a missing space between "togetherYou'll". We'll keep as is but maybe add a space for readability? Must preserve all substantive information; we can fix spacing? Probably okay to keep as is but we could add a space to improve readability without altering meaning. Safer to keep exactly? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Adding a space is not inventing info, just formatting. Might be okay. We'll keep as is but maybe add a space to avoid run-on. I'd add a space.
- About Visit.org: "Visit.org is a women-led Certified B Corporation that designs and delivers full-scale volunteering programs for global companies, with volunteering experiences built with vetted nonprofit partners and rooted in real community needs in 100+ countries and 40+ languages. Trusted by teams at companies like Amazon, Colgate, Paramount, and Cisco, Visit.org acts as an extension of lean CSR teams to run global volunteering that employees love and nonprofits trust."
We'll combine these into About the role section as prose paragraphs.
Now Responsibilities:
The text: "Host impactful, engaging, team-building, social impact events that support a great causeWelcome, engage, and inspire participants while supporting nonprofits in facilitating in-person eventsPresent events in partnership with a nonprofit organization or lead the event in fullBe skilled at storytelling and getting volunteers to really understand and feel the impact of their timeBe able to deliver clear instructions to lead volunteers through impactful, engaging activities Be available for 1-4 prep meetings prior to an event (depending on event complexities)"
We need to split into list items. Each sentence seems separated by missing spaces. Let's parse:
- Host impactful, engaging, team-building, social impact events that support a great cause
- Welcome, engage, and inspire participants while supporting nonprofits in facilitating in-person events
- Present events in partnership with a nonprofit organization or lead the event in full
- Be skilled at storytelling and getting volunteers to really understand and feel the impact of their time
- Be able to deliver clear instructions to lead volunteers through impactful, engaging activities
- Be available for 1-4 prep meetings prior to an event (depending on event complexities)
We'll make
- for each. Now Requirements: From "Requirements Qualifications:" list: - Fl