City Launcher (Dallas)

We need to output HTML fragment with sections: h3 for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections where posting has real specific content. We have: - About the role: we have "Company Overview" and "Role Overview". Could combine into About the role. Use h3 About the role then paragraphs. - Responsibilities: we have "Core Responsibilities" with bullet points. Use h3 Responsibilities then ul li. - Requirements: we have "Requirements" list. Use h3 Requirements then ul li. - Nice to Have: could be Qualifications or Skills? The instruction: use headings like Qualifications, Skills. We have "Nice to Have" list. Could treat as Qualifications or Skills. Probably Skills. But we need to decide: The posting includes "Nice to Have" items: experience running a run, etc. Those are qualifications/skills. We'll put under Skills. - Benefits: we have "WHY JOIN BRODIE LEAGUE" bullet list: Highly competitive pay and uncapped commission, Growth & mentorship opportunities, Professional development budget, Play Brodie League for free, Opportunity to work for an organization at the intersection of sports, fashion, & tech. Also compensation range given later: Compensation Range: $70K - $80K. Also Salary: $70,000 - $80,000 USD base + uncapped commission (~$500 per team signed). So we have Pay and Benefits. Pay section: we can include Pay with the salary range and commission. Benefits: list the why join items. - Schedule: we have "Availability on evenings and weekends. Game nights run roughly 7pm to midnight." Also "Type: Full-time Location: Based in your launch market (Dallas) in-market presence required, including evenings and weekends". So we have schedule info: evenings and weekends, game nights 7pm-midnight. So we can include Schedule section. We must not repeat job title as heading. No Job ID. Remove boilerplate: AI disclosure, position status, application process, commitment to inclusion, etc. Also remove duplicated lines. We must preserve all substantive information. Ensure we include all details: Territory: Dallas, TX. Reports To: Sr. Director of Growth. Type: Full-time. Location: Based in your launch market (Dallas) in-market presence required, including evenings and weekends. Also mention neighbourhood requirement. We need to include that info somewhere. Could be in About the role paragraph or maybe a separate meta? But we should not create headings for minor metadata; fold into short p. So we can include a paragraph after About the role that includes Type, Location, Territory, Reports To. Let's craft:

About the role

Full-time position based in your launch market (Dallas) requiring in‑market presence, including evenings and weekends. Territory: Dallas, TX. Reports to the Sr. Director of Growth. Brodie League is a fast‑growing adult recreational basketball brand with 50,000 athletes across 30+ locations, aiming to make every league night the best night of the week for athletes.

Then Responsibilities h3 with ul. Then Requirements h3 with ul. Then Skills h3 (Nice to Have) with ul. Then Benefits h3 with ul (why join list). Then Pay h3 with p: Base salary $70,000‑$80,000 USD plus uncapped commission (~$500 per team signed). Then Schedule h3 with p: Evenings and weekends required; game nights run roughly 7 pm to midnight. Make sure not to include filler like "commensurate with experience". Not present. Check we didn't miss any substantive info: The "Before you apply, know what we are going to ask you" paragraph includes specific questions: neighbourhood, five gyms, first ten captains, connect us with three people. That's substantive; should be included. Where to put? Could be part of About the role or Responsibilities? It's more like prerequisites. Could be part of About the role as a note. We'll add a paragraph under About the role: "Before applying, be prepared to answer: which neighbourhood you are from, the five gyms you would walk into in week one and who runs the door, your first ten captains by name, and connecting us with three people in your market within a week." Also include "Core Responsibilities Bring Your Network — Community Recruit..." etc. We need to ensure we don't duplicate. Let's extract responsibilities list: - Bring Your Network — Community Recruit a minimum of 24 founding captains per league, starting with the people you could name today. Walk into the gyms/courts you already know (open runs, rec leagues, training sessions, tournaments), and bring Brodie into rooms where you are already a familiar face. Build and keep relationships with the people who move players: coaches, trainers, gym staff, run organizers, barbers, group-chat admins, local business owners. Drive the referral program so captains and players become your largest recruiting channel, and be visible in your neighbourhood weekly; not as outreach, as your normal life. - Secure the Venue and Close the Business — Sales Identify and evaluate gyms in your neighbourhood, then negotiate and lock in the right venue. Run our sequence in order: soft close the venue, prove the demand, then sign. We do not carry a lease on an unproven market. Own the number and track it in CRM (teams signed, fill rate, revenue) so the market is forecastable, not lucky. Know where you stand weekly and escalate early when you are behind. - Make Brodie the Thing People Are Talking About — Growth Marketing Own the local demand story from zero: nobody in your neighbourhood has heard of us, and eight weeks later the gym is full. Run your location’s social page in the lead-up to launch — building the following, the anticipation, and the local waitlist before night one. Host open runs and live events that convert curiosity into signed, paid teams on the night. Borrow local distribution — trainers with client lists, shops, barbershops, run pages, the photographer everyone follows — and build the trade so it is worth their while. - Own the Season, Then the Territory Attend game nights and build genuine relationships with captains, players, families and spectators so game night becomes a community rather than a booking. Monitor the health of your league in season (retention, team count, waitlist, feedback) and partner with Operations on game-night execution while retaining ownership of growth, revenue, and community. Help build the repeatable launch playbook every future Brodie city will run on, then earn the right to expand into adjacent cities as your territory grows. We'll turn each bullet into li. Requirements list: - You live in the neighbourhood we are launching in, or one directly beside it. Not the metro area. - An existing network in the local basketball community, today. Coaches, trainers, gym staff, run organizers, tournament organizers, group-chat admins. - You are currently in the game. Playing in a rec league now or last season, in a gym weekly. Not a fan of the culture; a participant in it. Standing in your scene. When you recommend something, people move. This is reputation, not follower count. - The confidence to name your first ten captains and the credibility to get them on the phone. - Comfort building demand from zero (events, social, partnerships, word of mouth) with little or no budget. - The ability to close. You can ask a facility owner for a Tuesday night and a captain for a deposit without flinching, and manage the conversation from first touch through to signature. - Comfort owning a number, working in a CRM, and adopting new tools quickly. Tech fuels our growth; strong tech acumen or curiosity is expected. - Availability on evenings and weekends. Game nights run roughly 7pm to midnight. - Willingness to travel across your territory as it expands. Nice to Have list: - Experience running a run, a league, a tournament, a training group, or a community program of your own. - Experience running social media for a local brand, venue, team, or community. - Background in sports, events, hospitality, fitness, lifestyle, or entertainment industries. - Experience selling partnerships, sponsorships, memberships, or experiential products and services. - 3+ years in sales, partnerships, community management, or growth. Useful, but not a filter — we care more about who you know and who listens to you than about your title history. Benefits (WHY JOIN BRODIE LEAGUE): - Highly competitive pay and uncapped commission - Growth & mentorship opportunities - Professional development budget - Play Brodie League for free - Opportunity to work for an organization at the intersection of sports, fashion, & tech Pay: we have base salary range and commission. Schedule: Already covered in requirements but we still need a Schedule section if posting actually states them. It does state availability on evenings and weekends, game nights 7pm-midnight. So we can include Schedule section. We must not repeat same info in multiple sections? It's okay if overlapping but we should avoid duplication. However schedule appears also in Requirements; we could keep it only in Schedule and remove from Requirements to avoid duplication. But the requirement list includes "Availability on evenings and weekends. Game nights run roughly 7pm to midnight." That is a requirement. If we move it to Schedule, we should still keep it as a requirement? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't forbid duplication, but better to avoid redundancy. However the requirement list includes many items; we could keep the schedule item in Requirements and also have a Schedule section that maybe just says "Evenings and weekends required; game nights run roughly 7 pm to midnight." That's duplication but maybe acceptable. To be safe, we could keep schedule only in Requirements and not create a separate Schedule section, because the posting does state schedule info, but we can embed it in Requirements. However the instruction says we should use headings for Pay, Schedule, Benefits if posting actually states them. Since schedule is stated, we should include a Schedule section. We'll include it and maybe remove the schedule line from Requirements to avoid duplication. But the requirement list also includes "Availability on evenings and weekends. Game nights run roughly 7pm to midnight." If we remove it, we might lose a requirement nuance. However the requirement is about availability; we could keep it in Requirements but rephrase to not duplicate exact sentence? Could keep but it's okay. I'd rather keep both; it's not harmful. Let's produce HTML. We need to ensure no markdown fences, just raw HTML. Let's craft:

About the role

Full-time position based in your launch market (Dallas) requiring in‑market presence, including evenings and weekends. Territory: Dallas, TX. Reports to the Sr. Director of Growth. Brodie League is a fast‑growing adult recreational basketball brand with 50,000 athletes across 30+ locations, aiming to make every league night the best night of the week for athletes.

Before applying, be prepared to answer: which neighbourhood you are from, the five gyms you would walk into in week one and who runs the door, your first ten captains by name, and connecting us with three people in your market within a week.

Responsibilities

• Bring Your Network — Community Recruit a minimum of 24 founding captains per league, starting with the people you could name today. Walk into the gyms/courts you already know (open runs, rec leagues, training sessions, tournaments), and bring Brodie into rooms where you are already a familiar face. Build and keep relationships with the people who move players: coaches, trainers, gym staff, run organizers, barbers, group-chat admins, local business owners. Drive the referral program so captains and players become your largest recruiting channel, and be visible in your neighbourhood weekly; not as outreach, as