Brand Alliances - Senior Manager, Partnership Marketing

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading. Use

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

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Remove boilerplate (EEO, application instructions, etc). Preserve all substantive info. Include a section only when posting has real specific content for it; never emit heading with filler placeholder. So we need to parse the posting. The posting includes: - Title: Senior Manager, Partnership Marketing (we ignore as heading) - Department: Brand Alliances - Reports To: Senior Director, Partnership Marketing - FLSA: Full-Time; Salaried; Exempt - "What Sets You Apart" paragraph describing role. - "Essential Duties And Responsibilities" long list of duties (bullet-like sentences). - "Qualifications" section with bullet list of qualifications. - "Additional Role-specific Requirements": Ability to travel as required. - "About Orlando City SC & Orlando Pride" description of company (maybe not needed? It's substantive but not about role; but we might include as "About the company"? Not in allowed headings. Allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these. We have "What Sets You Apart" could be About the role. So we can put that under

  About the role

  with

  . Responsibilities: the Essential Duties And Responsibilities list. Use

  • . Requirements: maybe combine Qualifications and Additional Role-specific Requirements? Actually Qualifications is separate heading allowed. Requirements could be for things like "Ability to travel as required." Also maybe "Must successfully complete a background check." etc. Those are in Qualifications section? Actually they appear under Qualifications: "Must successfully complete a background check." and "Ability to attain and maintain SafeSport certification." Also "Ability to work a flexible schedule..." etc. Those could be Requirements or Qualifications. But we have both Qualifications and Requirements headings allowed. We need to decide what goes where. The posting has a "Qualifications" section with bullet list. It also has "Additional Role-specific Requirements". So we can put Qualifications under

    Qualifications

    (list). And Requirements under

    Requirements

    (list) for things like travel, background check, SafeSport, flexible schedule, etc. However some of those are also in Qualifications bullet list. But we should not duplicate content. We need to preserve all substantive info, but we can split them logically. Let's extract: From "What Sets You Apart": paragraph(s). We'll capture as prose. From "Essential Duties And Responsibilities": many sentences each starting with a verb. We'll treat each as list item. From "Qualifications": bullet list: - Bachelor’s degree in sport management, business, marketing, or a related field required. - Four to five years of partnership marketing and activation experience, with demonstrated success in media, sports sponsorship, or entertainment; sales experience preferred. - Understanding of sponsorship analytics and experience interpreting third-party data to strengthen partner execution. - Strategic thinker and strong communicator who thrives on meeting and exceeding partner objectives. - Demonstrated success in senior-level account management while managing multiple accounts and priorities. - Demonstrated success in upselling and renewing partnerships. - Polished written and verbal presentation skills, with experience creating and delivering recap and sales presentations. - Experience in the Florida marketplace preferred but not required. - Supervisory experience preferred but not required. - Collaborative team player with a strong work ethic, self-initiative, and the ability to work independently. - Strong organizational and time-management skills, with the ability to manage multiple priorities, meet tight deadlines, and work well under pressure. - Strong interpersonal, communication, presentation, decision-making, and problem-solving skills. - Ability to work a flexible schedule, including evenings, weekends, holidays, and home matches, as business needs require. - Must successfully complete a background check. - Ability to attain and maintain SafeSport certification. Then "Additional Role-specific Requirements": Ability to travel as required. Also earlier: Department, Reports To, FLSA: Full-Time; Salaried; Exempt. This is metadata; we could fold into a short

    maybe under About the role or separate? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. So we can include a short paragraph with Department, Reports To, FLSA. Also "About Orlando City SC & Orlando Pride" is company description; not in allowed headings. Could we include under About the role? Probably not; but we could include as a separate

    maybe not under a heading? The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. It didn't forbid extra paragraphs without heading. But they said use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

      for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus we can include paragraphs for metadata and company description as

      without heading, as they are substantive. However they said "Prefer a few substantive sections over many thin ones." But we can still include them as paragraphs. We must not include EEO boilerplate etc. The posting includes EEO statement at end; we must remove that. Also remove application instructions: "In order to be considered for this role, after clicking "Apply Now" above and being redirected, you must fully complete the application process on the follow-up screen." Remove. Also remove duplicated lines? Not seeing duplicates. Now decide sections: - About the role: could include the "What Sets You Apart" paragraph plus maybe metadata (department, reports to, FLSA) as a short p. - Responsibilities: list of duties. - Requirements: maybe include travel requirement, background check, SafeSport, flexible schedule? But those are also in Qualifications. However we could treat Qualifications as separate section for education/experience/skills, and Requirements for mandatory items like travel, background check, SafeSport, flexible schedule. But flexible schedule is also in Qualifications. Might duplicate. Better to follow the posting: they have Qualifications section (including education, experience, skills, etc.) and Additional Role-specific Requirements (travel). So we can put Qualifications as

      Qualifications

      with list. And Requirements as

      Requirements

      with list containing: Ability to travel as required. Also maybe we could include "Must successfully complete a background check." and "Ability to attain and maintain SafeSport certification." but those are already in Qualifications; but we could keep them only in Qualifications to avoid duplication. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep them somewhere. If we put them only in Qualifications, that's fine. Requirements then only has travel. That's okay. But we also have "Ability to work a flexible schedule..." which is in Qualifications; we keep there. Thus: - Qualifications: list all bullet points from Qualifications section. - Requirements: list containing Ability to travel as required. - Skills: maybe we could extract skills from Qualifications but we already have Qualifications; Skills heading optional if we have content. Could we create Skills section from some of the qualifications like "Strong interpersonal, communication, presentation, decision-making, and problem-solving skills." etc. But we already have Qualifications covering those. The instruction: Prefer a few substantive sections over many thin ones. So maybe we skip Skills section if we already have Qualifications covering skills. But we need to decide if we should include Skills heading only if there is real specific content for it. We could treat the skills bullet as part of Qualifications; we don't need separate Skills. - Benefits, Pay, Schedule: we have no info about benefits, pay, schedule (except schedule mentioned in Qualifications as flexible schedule). But schedule is not a separate section; we could include schedule info under Requirements? But we already have flexible schedule in Qualifications. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does not state benefits, pay, or schedule explicitly (except flexible schedule). So we should not create Benefits, Pay, Schedule sections. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications. We need to ensure we use

      for each heading. Now craft HTML. First, a short paragraph for metadata: Department: Brand Alliances; Reports To: Senior Director, Partnership Marketing; FLSA: Full-Time; Salaried; Exempt. We can put that as a

      before About the role or after. Probably before About the role as intro. Then About the role:

      About the role

      ... (the "What Sets You Apart" paragraph). The paragraph: "The Senior Manager, Partnership Marketing oversees partner-related activities, including renewal strategy, activation, execution, and comprehensive recaps of partnership elements. The role creates value for corporate partners by ensuring successful sponsorship activation across in-stadium experiences, digital and social media, branding, and community engagement initiatives. This sales- and partnership-minded leader builds strong relationships with partner contacts at the mid- and executive levels, develops a deep understanding of their business objectives, and identifies opportunities that support successful execution, renewal, and upsell. The position provides strategic direction for assigned corporate partnership accounts, leads select department initiatives, and collaborates with internal stakeholders to continually strengthen the service and support provided by the Brand Alliances department." We need to preserve all info; that's fine. Then Responsibilities:

      Responsibilities

      • ... each duty. We need to split the long list into items. Each sentence ends with a period. We'll make each sentence a
      • . Let's extract duties from "Essential Duties And Responsibilities": List: 1. Maintain a high level of service and build strong relationships with partner contacts at all levels of the organization. 2. Manage the successful delivery of all assets for assigned partner accounts, ensuring alignment with each partner’s business objectives. 3. Develop a deep understanding of each partner’s business and identify mutually beneficial opportunities to collaborate. 4. Advance organizational marketing objectives through partner activations, including ticket offers, expanded reach through partner inventory, retail activations, in-stadium promotions, special events, and community outreach. 5. Identify upsell opportunities and present partners with new ideas that align with their business objectives. 6. Manage the overall renewal process with the goal of growing each relationship. 7. Collaborate with Brand Alliances leadership to develop an effective approach and strategy at all levels of the organization. 8. Partner with Legal and Brand Alliances leadership to execute new agreements as part of the renewal process. 9. Manage the budget for each partner account to meet financial and partner objectives. 10. Submit invoices regularly, provide quarterly expense-management updates, and develop initial budgets for future years. 11. Lead an annual planning session for each Brand Alliance partner account to develop strategies and ideas aligned with business objectives. 12. Engage members of the broader Orlando City and Orlando Pride teams, provide an annual recap, and partner with Business Intelligence to develop meaningful insights and recommendations. 13. Collaborate across Creative, Ticketing, Marketing, Social and Digital, Information Technology, Community Impact, and People and Culture to ensure alignment and support for partner programs. 14. Maintain accurate benchmarks and documentation in the Brand Alliances OneDrive, Partnership Asset Tracker, KORE CRM, and inventory-management systems