Community Engagement Manager - 2 week Fashion Event [AQ-18503]

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We must not repeat job title. No Job ID etc. Remove boilerplate like EEO, etc. Must preserve all substantive info. So we need to parse the posting. Content: - Intro paragraph: "Aquent, in partnership with a leading consumer brand at the forefront of cultural moments, is seeking dynamic social media professionals to make an immediate and highly visible impact. This is your chance to directly influence brand perception, amplify positive sentiment, and foster genuine connections, creating a memorable experience for millions of fans worldwide during one of the year’s most anticipated events. Step into the vibrant world of real-time social engagement and make your mark on a major cultural event! We’re seeking passionate and quick-thinking community engagement specialists to join a dedicated team of professionals. For two high-energy weeks, you’ll be at the forefront of online conversations, shaping how this globally recognized brand interacts with its audience during one of its biggest moments of the year. If you thrive in fast-paced environments, love internet culture, and are eager to add a highly visible, culturally relevant campaign to your portfolio, this short-term, impactful assignment is for you! You will play a crucial role in shaping online conversations, amplifying positive sentiment, and fostering genuine connections with millions of fans, directly influencing brand perception during a major cultural event." That's basically description of role. Could be "About the role" section. Then "What You’ll Do" list: bullet points. Then "What You’ll Bring" with Must-Have Qualifications list and Nice-to-Have Qualifications list. Then "About Aquent Talent" paragraph about benefits etc. That's benefits section. Also mention "Available for scheduled 4–5 hour shifts every day, including weekends, throughout the two-week assignment. Example coverage windows may include approximately 9 AM–2 PM ET, 1 PM–6 PM ET, or 4 PM–9 PM ET, with later coverage potentially needed surrounding live event moments." That's schedule info. Pay not mentioned. So we should not create Pay section. Benefits: we have Aquent Talent benefits: subsidized health, vision, dental plans, paid sick leave, retirement plans with a match, free online training through Aquent Gymnasium. That's benefits. Thus sections: About the role (intro), Responsibilities (What You’ll Do), Requirements (maybe combine Must-Have Qualifications as Requirements), Qualifications (maybe Nice-to-Have?), Skills (maybe not separate), Benefits, Schedule. We need to decide which headings to use. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings if content exists. We must not create sections with filler. So we will include: -

About the role

with paragraph(s) summarizing the intro (but must preserve all substantive info; we can't summarize away detail; we need to preserve all substantive information. So we need to include the content verbatim? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That suggests we should not paraphrase or summarize; we should keep the original sentences. However we can break into paragraphs but keep the same content. So we can put the intro paragraphs as

under About the role. - Responsibilities: list of duties from "What You’ll Do". Use

• . - Requirements: Must-Have Qualifications list. - Qualifications: Nice-to-Have Qualifications list (maybe we could combine but they said prefer few substantive sections over many thin ones. Could combine Must-Have and Nice-to-Have under Requirements? But they have separate headings. We could put Must-Have under Requirements and Nice-to-Have under Qualifications. That seems fine. - Benefits: paragraph about Aquent Talent benefits. - Schedule: paragraph about shift availability. We must not include boilerplate like EEO, equal-opportunity, etc. Remove those lines. Also remove "About Aquent Talent" heading? We'll incorporate its content into Benefits section. We must not include navigation, cookie, legal, etc. We must not repeat job title. We must not put Job ID. We must not include application instructions. Now produce HTML fragment. Let's extract exact text. Intro paragraphs: "Aquent, in partnership with a leading consumer brand at the forefront of cultural moments, is seeking dynamic social media professionals to make an immediate and highly visible impact. This is your chance to directly influence brand perception, amplify positive sentiment, and foster genuine connections, creating a memorable experience for millions of fans worldwide during one of the year’s most anticipated events. Step into the vibrant world of real-time social engagement and make your mark on a major cultural event! We’re seeking passionate and quick-thinking community engagement specialists to join a dedicated team of professionals. For two high-energy weeks, you’ll be at the forefront of online conversations, shaping how this globally recognized brand interacts with its audience during one of its biggest moments of the year. If you thrive in fast-paced environments, love internet culture, and are eager to add a highly visible, culturally relevant campaign to your portfolio, this short-term, impactful assignment is for you! You will play a crucial role in shaping online conversations, amplifying positive sentiment, and fostering genuine connections with millions of fans, directly influencing brand perception during a major cultural event." That's one big paragraph but we can keep as is. Responsibilities list (What You’ll Do): - Provide active community coverage across social media platforms. - Engage proactively and reactively with customers, fans, creators, and talent. - Monitor owned social content as well as relevant user-generated content. - Respond to high-volume conversations surrounding the event in real time. - Identify trending conversations and cultural moments where the brand can authentically participate. - Engage with relevant creator and fan content to help build excitement and community connection. - Amplify positive sentiment, standout comments, creator moments, and noteworthy user-generated content. - Maintain a consistent brand voice while adapting communication appropriately for each social platform. - Monitor community sentiment and quickly identify emerging trends or issues. - Escalate sensitive, customer service-related, or high-priority conversations appropriately. - Surface viral posts, meaningful feedback, trends, and notable community moments to the broader social team. - Support basic engagement and performance reporting as needed. - Collaborate with the Social and Community teams to ensure seamless coverage throughout the event. Make sure to keep punctuation. Requirements (Must-Have Qualifications): - At least 1–2 years of professional social media community management, moderation, or engagement experience. - Experience engaging with audiences on behalf of a brand or agency. - Strong understanding of major social media platforms, including how audiences communicate differently across each platform. - Excellent written communication skills and strong attention to detail. - Ability to quickly learn and write within an established brand voice. - Comfortable managing fast-moving, high-volume social conversations. - Able to quickly assess tone, sentiment, and context and determine the right response. - Strong judgment around when to engage, escalate, or flag an emerging issue. - Proactive—you naturally look for conversations and opportunities rather than waiting for them to come to you. - Strong interest in pop culture, entertainment, and social media trends. - Available for scheduled 4–5 hour shifts every day, including weekends, throughout the two-week assignment. Example coverage windows may include approximately 9 AM–2 PM ET, 1 PM–6 PM ET, or 4 PM–9 PM ET, with later coverage potentially needed surrounding live event moments. Note: The availability schedule appears also in Must-Have Qualifications. But we also have a Schedule section. To avoid duplication, we could keep schedule info under Schedule section and not repeat in Requirements. However the Must-Have includes that line. The instruction: preserve ALL substantive information; do not invent or summarize away detail. If we remove that line from Requirements, we would be omitting substantive info. So we need to keep it somewhere. We could keep it in Requirements and also have Schedule section that maybe just repeats? That would be duplication. Better to move schedule info to Schedule section and remove from Requirements? But that would be removing content from Must-Have Qualifications, which is substantive. However we could keep the schedule info in Schedule section and not duplicate; but then the Must-Have Qualifications would be missing that sentence. The instruction says preserve ALL substantive information; we cannot omit any. So we need to keep that sentence somewhere. We could keep it in Requirements and also have Schedule section that maybe just says "See Requirements for schedule details" but that would be summarizing. Better to keep schedule info in Requirements and not have a separate Schedule section, unless we also include schedule info there but that would duplicate. Duplication is allowed? The instruction didn't forbid duplication, but said remove duplicated lines. It said "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should avoid duplicated lines. So we should not duplicate the schedule sentence. So we need to decide where to place it. The schedule info is part of Must-Have Qualifications (availability). It could also be considered schedule info. Since we have a Schedule heading, we could put schedule details there and remove from Must-Have Qualifications? But that would be removing from Must-Have Qualifications, which is part of the posting. However we could rephrase: The Must-Have Qualifications list includes "Available for scheduled 4–5 hour shifts every day, including weekends, throughout the two-week assignment. Example coverage windows may include approximately 9 AM–2 PM ET, 1 PM–6 PM ET, or 4 PM–9 PM ET, with later coverage potentially needed surrounding live event moments." If we move that to Schedule section, we are still preserving the info, just relocating it. The instruction says preserve ALL substantive information; it doesn't say we must keep it under the same heading. So moving it to Schedule section is okay as long as we keep the exact sentence. However we must not create a Schedule section unless the posting actually states them. The posting does state schedule info (availability). So we can create Schedule section with that sentence. Then we must remove that sentence from Must-Have Qualifications to avoid duplication. But then Must-Have Qualifications would be missing that sentence; but we could consider that the schedule info is not a qualification but a requirement? It's listed under Must-Have Qualifications, but we could still keep it there and also have Schedule section? That would duplicate. The instruction says remove duplicated lines. So we should avoid duplication. So we need to decide: either keep schedule under Must-Have Qualifications and not have a separate Schedule section, or move it to Schedule and remove from Must-Have. Which is better? The instruction says "Prefer a few substantive sections over many thin ones." Having both Requirements and Schedule might be more sections but still okay. However we already have Requirements, Qualifications, Benefits, etc. Adding Schedule makes another section. But we could keep schedule under Requirements and not have Schedule section. The instruction says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". The posting does have schedule info, so we could have a Schedule section. But we must not duplicate. So we need to decide where to place the schedule info. I think it's fine to put schedule info under Schedule section and remove from Must-Have Qualifications, because the schedule info is more about scheduling than qualification. However the Must-Have Qualifications list includes it; removing it changes the list. But we could keep the list without that sentence, and the schedule info appears elsewhere. That still preserves all substantive info (just relocated). The list would be missing that sentence, but the info is still present elsewhere. That should be acceptable as we are not omitting info, just moving it. The instruction didn't require preserving the exact grouping. So I'll do that. Thus Must-Have Qualifications list will exclude the availability sentence. Now Benefits: from About Aquent Talent: "Our eligible talent get access to amazing benefits like subsidized health, vision, and dental plans, paid sick leave, and retirement