Managing Director, Audio Visual

We need to output HTML fragment with sections: About the role? Actually we have sections: WHO WE ARE, OUR CORE VALUES, ACCOUNTABILITIES, WHAT YOU'LL BE DOING, WHAT YOU SHOULD HAVE, WHAT WE BRING TO THE TABLE, COMPENSATION AND BENEFITS, DISCLOSURES (but we must remove boilerplate like EEO, legal, etc). Also we must not repeat job title as heading. Use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). However we can adapt headings to match content: maybe "About the Company", "Core Values", "Accountabilities", "Responsibilities", "Requirements", "What We Offer", "Compensation and Benefits". Must only include sections when posting has real specific content. Avoid filler like "commensurate with experience". We have compensation range given, so we can include Pay section. Benefits given, so Benefits section. Schedule? Not given (travel up to 40% but not schedule). So no Schedule section. We must use

• for any list of duties/requirements/benefits. Use

  for prose. 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. Also remove DISCLOSURES that are legal boilerplate. The DISCLOSURES includes notices about physical demands, reasonable accommodations, not an employment agreement, drug-free workplace, EEO. Those are boilerplate; we should drop them. Also "Physical Requirements" is part of WHAT YOU SHOULD HAVE? Actually it's under WHAT YOU SHOULD HAVE section. That's substantive (physical requirements). Keep that. We need to decide headings: The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map our content to those headings where appropriate. For example: - About the role: could be WHO WE ARE? Or maybe "About the Company". But they gave example headings; we can use "About the role" for description of role? However we have sections like ACCOUNTABILITIES, WHAT YOU'LL BE DOING (responsibilities), WHAT YOU SHOULD HAVE (requirements/qualifications/skills), WHAT WE BRING TO THE TABLE (benefits?), COMPENSATION AND BENEFITS (pay and benefits). We need to avoid duplicate sections. We could structure:

  About the role

  (maybe combine WHO WE ARE and OUR CORE VALUES? Actually "About the role" could be a brief description of the role; but we have WHO WE ARE (company description) and OUR CORE VALUES (values). Might be better to have separate sections: "About the Company" and "Core Values". But the instruction says use those example headings; but not strictly limited? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when appropriate. It doesn't forbid other headings, but to be safe we should stick to those headings. However we need to represent all content. We can map: - About the role: could include WHO WE ARE and OUR CORE VALUES? Might be too much but okay. - Responsibilities: WHAT YOU'LL BE DOING (list of duties). - Requirements: WHAT YOU SHOULD HAVE (experience, skills, etc.) plus maybe physical requirements. - Qualifications: maybe same as Requirements? Could combine. - Skills: maybe part of Requirements. - Benefits: WHAT WE BRING TO THE TABLE (benefits like facility, EOS, meetings, community service, social hours, ability to use talents) plus COMPENSATION AND BENEFITS (medical, dental, etc). Actually Benefits section should list benefits. - Pay: COMPENSATION AND BENEFITS includes base salary range plus bonus. We need to avoid duplication: we have both WHAT WE BRING TO THE TABLE and COMPENSATION AND BENEFITS. We could combine them into Benefits and Pay sections. Let's extract substantive content: WHO WE ARE: "Through our offering of furniture, walls, and audio-visual solutions, Continua Interiors is on a mission to transform the way people work, learn and heal across the Midwest. Continua places great importance on fostering a supportive work environment that values culture, community, and connection with both team members and clients. We are not just a company but a movement reshaping the dealer landscape across the Midwest." OUR CORE VALUES: "Strive To Be Great | Do Hard Things | Stronger Together | Own It" ACCOUNTABILITIES: "Lead, Manage, and Hold Accountable (LMA) the Audio Visual Sales Team Audio Visual Revenue Growth Sales Talent Development Strategic Client Relationships" WHAT YOU'LL BE DOING: List of duties (many bullet-like sentences). We need to turn into

  • . WHAT YOU SHOULD HAVE: List of requirements (10+ years, 5+ years leading, proven ability, demonstrated success, strong executive presence, experience leading strategic account planning, ability to balance strategic thinking, strong business and financial acumen, exceptional communication skills, experience collaborating across..., ability to travel up to 40% throughout the Midwest, Physical Requirements: ...). We'll need to keep physical requirements as part of requirements. WHAT WE BRING TO THE TABLE: "A State-of-the-Art Facility with incredible technology throughout and a multitude of workspaces at your disposal Use the EOS (Entrepreneurial Operating System) methodology to provide tools to help individuals and teams achieve goals, growth, and improvement. Quarterly All Company Meetings Community Service opportunities Company social hours Ability to use your talents and strengths to make a positive impact" COMPENSATION AND BENEFITS: "The hiring compensation range for this position is a base salary of $150,000-$200,000 plus bonus. Actual compensation will be determined based on various factors, including, but not limited to, the candidate's experience, skills, qualifications, and location, as well as internal equity and market considerations. Benefits available in this position include: Medical, Dental, and Vision insurance Company paid Short Term and Long Term Disability insurance Critical Illness and Accident Insurance HSA, DCA and FSA options available Paid time off and holidays Paid Parental Leave 401k Match (50% of every 1% up to 4%)" DISCLOSURES: drop. Now we need to produce HTML with

    headings for sections we include. We need to decide which headings to use: - About the role: could contain WHO WE ARE and OUR CORE VALUES? Might be okay. - Responsibilities: WHAT YOU'LL BE DOING. - Requirements: WHAT YOU SHOULD HAVE (including physical requirements). - Qualifications: maybe we could split Requirements into Requirements and Qualifications but we have similar content; better to just have one section for requirements/qualifications. But instruction says we can use those headings; we can include both if we have content. However we risk duplication. Perhaps we can use "Requirements" for the experience/skills, and "Qualifications" for the physical requirements? But physical requirements are part of qualifications. Might be okay to have both. - Skills: maybe we can extract skills from WHAT YOU SHOULD HAVE (communication, strategic thinking, etc.) but that overlaps. - Benefits: WHAT WE BRING TO THE TABLE (non-insurance benefits) plus maybe also include benefits from COMPENSATION AND BENEFITS? Actually benefits include insurance etc. So we could have Benefits section covering all benefits (including insurance, time off, etc.) and Pay section covering salary range. Thus:

    About the role

    (company description + core values)

    Responsibilities

    (WHAT YOU'LL BE DOING)

    Requirements

    (WHAT YOU SHOULD HAVE: experience, leadership, etc.)

    Qualifications

    (Physical Requirements) maybe.

    Benefits

    (WHAT WE BRING TO THE TABLE + insurance benefits etc.)

    Pay

    (base salary range plus bonus) We must not include Schedule. We must not repeat job title as heading. We must not include boilerplate. Now we need to format lists. For Responsibilities: we have many sentences. We'll turn each into
  • . For Requirements: we have bullet-like items (10+ years..., 5+ years..., Proven ability..., Demonstrated success..., Strong executive presence..., Experience leading..., Ability to balance..., Strong business and financial acumen..., Exceptional communication skills..., Experience collaborating..., Ability to travel up to 40%..., Physical Requirements: ...). We'll turn each into
  • . For physical requirements we need to keep the sentence. For Benefits: we have WHAT WE BRING TO THE TABLE items (facility, EOS, quarterly meetings, community service, social hours, ability to use talents) plus insurance benefits list (medical, dental, vision; company paid STD/LTD; critical illness and accident; HSA/DCA/FSA; paid time off and holidays; paid parental leave; 401k match). We'll combine into one
    • list. For Pay: we have a sentence about base salary range plus bonus. Could be

      . Now we need to ensure we preserve all substantive information. Let's extract exact phrasing. WHO WE ARE: "Through our offering of furniture, walls, and audio-visual solutions, Continua Interiors is on a mission to transform the way people work, learn and heal across the Midwest. Continua places great importance on fostering a supportive work environment that values culture, community, and connection with both team members and clients. We are not just a company but a movement reshaping the dealer landscape across the Midwest." OUR CORE VALUES: "Strive To Be Great | Do Hard Things | Stronger Together | Own It" We could present core values as a list or as a sentence. Probably as a

      • each value. ACCOUNTABILITIES: Actually we have ACCOUNTABILITIES section with four items. Should we include that? The instruction says we should include sections only when posting has real specific content. ACCOUNTABILITIES is a heading with four items. It's substantive. Should we include it? The example headings didn't include Accountabilities, but we could still use

        for it? The instruction says use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we could incorporate ACCOUNTABILITIES into Responsibilities or Requirements? However it's a distinct set of accountability areas. Might be better to include as a separate section with heading "Accountabilities". But the instruction didn't list that as example; but it didn't say we cannot use other headings. It says use

        for section headings (e.g. ...). The e.g. suggests those are examples, not exclusive. So we can use other headings as needed, as long as they are

        . However the instruction also says "Prefer a few substantive sections over many thin ones." So we should avoid too many sections. We could merge Accountabilities into Responsibilities (since they are about what you'll be doing). Actually ACCOUNTABILITIES list: Lead, Manage, and Hold Accountable (LMA) the Audio Visual Sales Team; Audio Visual Revenue Growth; Sales Talent Development; Strategic Client Relationships. Those are high-level accountability areas. The WHAT