Chief Brand Officer, Sports Academy - $400,000/year USD

We need to output HTML fragment with sections: About the role? The posting includes description. We need to use

for section headings: 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: "You are not here to polish posts..." etc. That's description of role. Could be "About the role" section. - Then "What You Will Be Doing" list bullet points. - Then "What You Won’t Be Doing" list. - Then "Chief Brand Officer" (title) but we shouldn't repeat title as heading. - Then "Key Responsibilities" bullet. - Then "Basic Requirements" list. - Then "Nice-to-have Requirements" list. - Then "About Sports Academy" description. - Then "Working with us": full-time, compensation, etc. That gives Pay and Schedule. We need sections: About the role (intro narrative), Responsibilities (What You Will Be Doing + Key Responsibilities maybe combined), Requirements (Basic Requirements), Qualifications? Could combine Basic Requirements and Nice-to-have as Requirements? But we have separate sections: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to include based on content. We have: - Responsibilities: What You Will Be Doing, What You Won’t Be Doing, Key Responsibilities. - Requirements: Basic Requirements (7+ years experience etc). Also Nice-to-have Requirements (background etc). Could be Qualifications. - Skills: maybe "Hands-on ability to use AI-enabled content production tools", "Ability to build brand narrative architecture", "Strong skill in audience code-switching", "Proven on-camera and on-stage presence". Could be Skills. - Benefits: Not explicitly mentioned besides compensation? There's no benefits like health etc. So we should not create Benefits section unless posting actually states them. It does not mention benefits besides pay. So skip Benefits. - Pay: Yes, compensation $200/hour, $400k/year, weekly payment. - Schedule: Full-time 40 hours per week, long-term position, immediately available. Thus we include sections: About the role, Responsibilities, Requirements, Skills, Pay, Schedule. Possibly Qualifications separate from Requirements? But we have both Basic and Nice-to-have; could treat Basic as Requirements, Nice-to-have as Qualifications. Or combine. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine Requirements and Qualifications into one "Requirements" section, and Skills separate. But we have headings list; we can include only those with real content. Let's decide: - About the role: intro paragraph. - Responsibilities: combine What You Will Be Doing, What You Won’t Be Doing, Key Responsibilities. - Requirements: Basic Requirements (7+ years etc). Could also include Nice-to-have as part of Requirements? Might be better to have Qualifications for Nice-to-have. But we can keep both as separate if they have substantive content. They do. So we could have Requirements (basic) and Qualifications (nice-to-have). That's two sections. - Skills: maybe we can incorporate into Requirements/Qualifications; but we have specific skill items: "Hands-on ability to use AI-enabled content production tools to create or direct high-quality content", "Ability to build brand narrative architecture and audience messaging from scratch", "Strong skill in audience code-switching across families, athletes, coaches, media, and public stakeholders", "Proven on-camera and on-stage presence". Those are skills. Could be a Skills section. - Pay: compensation details. - Schedule: full-time 40 hrs/week. Thus we have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay, Schedule. Check each for real content. About the role: The initial paragraphs describing mission, building narrative, etc. That's substantive. Responsibilities: bullet list from "What You Will Be Doing", "What You Won’t Be Doing", "Key Responsibilities". Need to ensure we don't repeat. We'll combine. Requirements: Basic Requirements list. Qualifications: Nice-to-have Requirements list. Skills: maybe we can extract skill items from Basic Requirements? Actually Basic Requirements includes: "7+ years of experience in persuasive public-facing roles", "Experience owning the narrative and public voice of a startup...", "Proven on-camera and on-stage presence as a speaker, host, founder, journalist, creator, or public representative", "Ability to build brand narrative architecture and audience messaging from scratch", "Strong skill in audience code-switching across families, athletes, coaches, media, and public stakeholders", "Hands-on ability to use AI-enabled content production tools to create or direct high-quality content", "Passion for sports and student athletics", "Austin-based or willing to relocate to Austin, TX for on-site work", "Authorized to work in the U.S." Some of those are skills/experience. But we already have Requirements and Qualifications; we could keep Skills separate for the explicit skill items. However to avoid duplication, we might incorporate skill items into Requirements/Qualifications. But the instruction: Use sections only when posting has real specific content for it. It does have skill content. So we can create Skills section with those skill items. But we must ensure we don't duplicate content across sections. We need to preserve ALL substantive information; not invent or summarize away detail. So we need to include each piece somewhere. If we put skill items in Skills section, we should not also put them in Requirements/Qualifications unless they are also listed there. But Basic Requirements includes those skill items as part of the list. If we move them to Skills, we would be removing them from Requirements, losing that detail. So we need to keep them somewhere. We could keep them in Requirements (as part of basic) and also have Skills section maybe redundant. Better to not create Skills if the content is already covered in Requirements/Qualifications. The instruction: Prefer a few substantive sections over many thin ones. So we can combine skill items into Requirements/Qualifications. So we may not need a separate Skills section. Thus we can have sections: About the role, Responsibilities, Requirements (including basic and nice-to-have), Pay, Schedule. But we have headings list: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could use Requirements for basic, Qualifications for nice-to-have. That's two sections. That's okay. Thus we will have About the role, Responsibilities, Requirements, Qualifications, Pay, Schedule. Check each for real content: - About the role: yes. - Responsibilities: yes. - Requirements: basic requirements list. - Qualifications: nice-to-have list. - Pay: compensation details. - Schedule: full-time details. We must not include Benefits as none. Now we need to format. Use

for each section heading. Inside each section, use

for prose,

• for lists. We must not repeat job title as heading. The title "Chief Brand Officer" appears but we should not make it a heading. We'll just include it maybe in About the role? Actually it's in the posting as a line "Chief Brand Officer". That's like a subheading but we should not repeat as heading. We can treat it as part of About the role paragraph or maybe as a

  with bold? But we cannot add markdown; we can just include it as plain text in a

  . It's okay. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes "Hit the Apply button if you found this interesting..." that's application instruction; we should remove that. Also "We look forward to meeting you!" maybe also application instruction; remove. Also "Working with us" includes details about contractor etc; that's not boilerplate, it's substantive about employment terms, we keep. Also "Crossover Job Code: ..." is metadata; we should drop it or fold into short

  or drop. According to instructions: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can either drop it or include in a short

  maybe under About the role? Better to drop it as it's minor. Also "Texas Sports Academy is Where Future Champions Excel in Academics and Athletics" is part of About Sports Academy; we keep. Now let's extract content. About the role: The initial paragraph(s) before "What You Will Be Doing". Let's capture: "You are not here to polish posts, chase impressions, or manage a content calendar. You are here to make families believe. Texas Sports Academy is building a $25k+/year AI-powered sports-education model for students who want both serious academics and serious athletic growth. The story is still being formed. That is the point. This work is for someone who can stand on stage, sit in front of a camera, speak to parents, athletes, coaches, media, and civic leaders, and make one clear idea land: this is a new category of school. You will turn student outcomes, athlete stories, and leadership vision into a narrative that every person inside the organization can repeat with force and accuracy. Then you will build the engine that proves it through profiles, video, editorial, data stories, earned media, and public events. The arc is big. At first, you will build from a blank page: message, proof, voice, content, press, and trust. As the brand grows, you will shape the creative team and set the bar for how TSA shows up in public. If you want a visible founding seat where the work creates demand before families ever reach enrollment, apply now." We should remove the "apply now" sentence as it's application instruction. So cut that last sentence. Keep rest. Thus About the role paragraph ends before "If you want a visible founding seat..." Actually that sentence is also encouraging to apply; we should remove it. So we stop before that. Thus About the role content: "You are not here to polish posts, chase impressions, or manage a content calendar. You are here to make families believe. Texas Sports Academy is building a $25k+/year AI-powered sports-education model for students who want both serious academics and serious athletic growth. The story is still being formed. That is the point. This work is for someone who can stand on stage, sit in front of a camera, speak to parents, athletes, coaches, media, and civic leaders, and make one clear idea land: this is a new category of school. You will turn student outcomes, athlete stories, and leadership vision into a narrative that every person inside the organization can repeat with force and accuracy. Then you will build the engine that proves it through profiles, video, editorial, data stories, earned media, and public events. The arc is big. At first, you will build from a blank page: message, proof, voice, content, press, and trust. As the brand grows, you will shape the creative team and set the bar for how TSA shows up in public." Now Responsibilities: combine What You Will Be Doing, What You Won’t Be Doing, Key Responsibilities. What You Will Be Doing bullet list: - Build the master narrative and audience-specific messaging for families, athletes, coaches, media, and policymakers - Produce proof-based student and athlete profiles, outcome-data stories, video, and editorial content - Pitch earned media, develop thought leadership, and manage communications during high-stakes moments - Represent TSA on camera, on stage, at events, in podcasts, and with the press - Set the creative quality bar and help the team speak with one clear, credible voice What You Won’t Be Doing bullet list: - Paid digital ads, ad buying, cold lead generation, and performance marketing campaigns are not part of this role - Managing backend enrollment operations, CRM administration, or admissions workflows - Chasing vanity metrics such as content volume, impressions, or softened engagement numbers - Hiding behind decks, committees, or internal brand reviews instead