Director, PR, Communications & Influencers

We need to output HTML fragment with sections for About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule etc. Only include sections that have real specific content. The posting includes About Lovesac, About Our Culture, About The Role, What You’ll Do (list of duties), Qualifications (with subparts: Who you Are: Core Values..., Table-Stake Values..., Core Competencies:..., Requirements...), Full Time Benefits* (list). No explicit Pay or Schedule info. So we should not create Pay or Schedule sections. Also we should not repeat job title as heading. We need headings: About the role (maybe "About The Role" but heading text should be like "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings? It says e.g., so we can use those headings. We'll include sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. Possibly Skills? Not present. We'll not include Skills if no specific content. We'll embed the content from posting. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At end there is EEO statement and background check info; we should remove that. Also remove "Full Time Benefits*" maybe keep benefits but remove footnote. Also remove "Associate pay will vary based on factors..." that's about pay but not specific numbers; we should not create Pay section because no specific pay. However that sentence is about pay variability; we could maybe include it in Benefits? But it's not a benefit. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits (Full Time Benefits*). So we include Benefits section. The pay variability sentence is not a specific pay figure; we should not create Pay section. We could maybe include that sentence in Benefits? But it's about pay, not a benefit. Safer to omit it as it's not a benefit and not required. However we must preserve ALL substantive information; removing that sentence might be losing substantive info about pay variability. But the instruction says do not create Pay section unless posting actually states them. It does state that pay will vary based on factors... That is a statement about pay, but not a specific number. Should we include it? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about pay (variability). So we could include a Pay section with that statement. However they also said "Prefer a few substantive sections over many thin ones." Might be okay to include Pay section with that line. But we need to decide. Similarly, Schedule: no mention. So omit Schedule. We also need to include "About the role" section: that likely corresponds to the paragraph under "About The Role". We'll put that prose. Responsibilities: the "What You’ll Do" bullet list (actually paragraphs with bold headings). We need to convert to

• . Each duty is a paragraph with a bold heading (like "Public Relations & Earned Media") then sentences. We could treat each bold heading as a list item containing the heading and its description. Or we could split into multiple list items per duty. Probably each duty as a list item. Requirements: The "Requirements" section includes bullet points after "Who you Are: Core Values..." etc. Actually the section "Qualifications" includes "Who you Are: Core Values...", "Table-Stake Values...", "Core Competencies:...", then "Requirements" bullet list. The instruction says use headings: Requirements, Qualifications, Skills. So we need separate Requirements and Qualifications sections. The posting lumps them together under "Qualifications". We need to split: Requirements bullet list (the list after "Requirements") and Qualifications (the preceding parts: Core Values, Table-Stake Values, Core Competencies). We'll treat those as Qualifications section content. We must preserve all substantive info: include Core Values list, Table-Stake Values list, Core Competencies list, and Requirements list. We also need to include Benefits section: the bullet list under "Full Time Benefits*". We'll format as
  • . We must not include boilerplate: EEO statement, background check, etc. Also remove duplicated lines. Now produce HTML fragment. Structure:

    About the role

    ... (the paragraph under About The Role)

    Responsibilities

    • Public Relations & Earned Media ...
    • Influencer & Creator Marketing ...
    • Brand & Product Storytelling ...
    • Corporate & Executive Communications ...
    • Omnichannel & Experiential Communications ...
    • Reputation & Issues Management ...
    • Measurement & Business Impact ...
    • Cross-Functional Leadership ...

    Requirements

    • Bachelor’s degree in Communications, Public Relations, Marketing, Journalism, or a related field required.
    • 8+ years of progressive experience in public relations, corporate communications, influencer marketing, brand communications, or an integrated communications role.
    • Experience in retail, furniture, home furnishings, lifestyle, consumer products, fashion, beauty, hospitality, or another consumer-focused industry strongly preferred.
    • Demonstrated success developing and executing integrated PR and communications strategies.
    • Strong relationships with relevant media, influencers, creators, and industry contacts.
    • Demonstrated experience developing and scaling influencer and creator programs.
    • Strong understanding of the evolving media, social, creator, and digital landscape.
    • Exceptional storytelling, writing, presentation, and communication skills.
    • Strong business and commercial acumen with the ability to connect communications strategies to business objectives.
    • Experience managing agencies, budgets, and cross-functional teams.
    • Strong strategic thinking and ability to operate effectively in a fast-paced, highly collaborative environment.
    • Excellent judgment and discretion, particularly when managing sensitive or reputation-related matters.
    • Exemplify each of our Lovesac values, at all times, be results driven and utilize knowledge to meet or exceed key performance indicators (KPIs), goals and deadlines.
    • Must be able to travel using various forms of transportation, as required by the Company in its sole discretion, for mandatory meetings and conferences held either at our offices or offsite (i.e. quarterly team connection weeks, companywide meetings and events, vendor visits).
    • Must be able to travel up to 25% of the time to support company events, media opportunities, influencer activations, business meetings, and other communications initiatives as needed.
    • Must comply with all policies and procedures outlined in the Lovesac Employee Handbook and work collaboratively with fellow employees, treating all clients, both internal and external with dignity and respect at all times.

    Qualifications

    We need to include Core Values, Table-Stake Values, Core Competencies. Could format as

    or

    . Since they are lists, we can use
    • . We'll separate maybe three subheadings? But we only have h3 for section headings; we could embed headings inside

      or

    • . Simpler: make a

      with the three categories each as a sentence? But we need preserve list detail. Could do:

      Qualifications

      Core Values: Top Ambition, We All Win Together, Conscious Operations, Do Less and Do Best, Love Matters

      Table-Stake Values: Willing to Sweep Floors, Grit, Positive, Self-Aware, Self-Starting, Insatiable Learners, Transparency, Customer-Centric

      Core Competencies: Builds Customer Centricity, Drives Remark-able Results, Collaborates Effectively, Makes Good Decisions, Demonstrates Self-Awareness

      That preserves info. Now Benefits:

      Benefits

      • Financial Benefits: Annual Bonus Program, Annual Long Term Incentive Program, Inaugural Grant Equity Award, 401K Matching Contribution, Financial Wellness Tools.
      • Health and Wellness Benefits: Medical, Dental, Vision, Health Savings and Flexible Spending Accounts, Paid Parental Leave, Life/AD&D, Short Term and Long-Term Disability, Critical Illness and Accident Insurance, Employee Assistance Program.
      • Paid Time Off: Up to 160 hours of paid time off within our fiscal calendar year, prorated from date of hire, 8 paid company recognized holidays.
      • Pet Insurance and generous Associate Discounts.
      We should not include "Eligibility and terms for all benefits listed are as outlined in Lovesac’s policy and plan documents." That's boilerplate? It's still substantive but maybe considered generic. Might keep? It's not a benefit detail but a statement. Could include as a

      . But to be safe, we could include it as a

      after list. However instruction: preserve ALL substantive information. That sentence is substantive about eligibility. I'd include it as a

      . Now Pay: we have statement about pay variability. Should we include Pay section? The posting says: "Associate pay will vary based on factors such as qualifications, experience, skill level and competencies." That's a statement about pay. So we could add:

      Pay

      Associate pay will vary based on factors such as qualifications, experience, skill level and competencies.

      But we must not create Pay section unless posting actually states them. It does state that, so okay. We must not include Schedule. Now ensure we removed duplicated lines, boilerplate. Also remove "About Lovesac", "About Our Culture" sections as not required headings (they are not in list). We should not include them because they are not requested headings. The instruction: use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should only include those sections when posting has real specific content for it. The "About Lovesac" and "About Our Culture" are not in the list of suggested headings, but they are substantive. However the instruction says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections; other headings maybe not needed. It also says "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." It doesn't forbid other headings like About Lovesac. But the instruction to "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 include About Lovesac and About Our Culture as sections with appropriate headings, but they are not in the examples. However the examples are just examples; we could still use them. But the instruction says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should limit to those headings. Safer to follow the examples and only include