Client Lead

We need to output HTML fragment with sections for 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. Must not include Job ID etc. Must remove boilerplate. Must preserve all substantive info. We need to parse the posting. Key info: - Salary: Up to USD 110,000 salary, depending on experience, on a full time, permanent employment contract. So Pay: Up to USD 110,000, depending on experience. Also mention full time permanent. - Fully remote anywhere in US. So Schedule? Not exactly schedule but location. Working Hours: must align closely with US Eastern Time across weekdays (regardless of location). So schedule: Must align with US Eastern Time weekdays. - 33 Days Paid Leave and Benefits. So Benefits: 33 days paid leave, plus benefits (unspecified). Could list "33 days paid leave" as benefit. - Opportunity to work close to major basketball and sports clients... etc. That's more about role context. - Modern tooling environment where we expect thoughtful use of AI to improve speed, quality, repeatability, and team performance. - About us: description of Storyteller. - The Role: description of leading team, etc. - Sports Context: basketball knowledge useful. - What You Will Own: list of responsibilities. - What Good Looks Like: more expectations. - What We Are Looking For: list of traits/skills. - Helpful Experience: list of experience. - What This Role Is Not: list of what it's not. - Recruitment Process: description of process (but we should remove application instructions? The instruction says remove application instructions. Recruitment process might be considered application instructions? It says "remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Recruitment process could be considered application instructions; but it's part of the selection process. Might be considered application instructions. Safer to omit it. We need to produce sections: About the role (maybe corresponds to "The Role" description). Responsibilities (from "What You Will Own"). Requirements (maybe from "What We Are Looking For" and "Helpful Experience"? Actually "Requirements" could be the qualifications needed. Qualifications maybe similar. Skills maybe from "What We Are Looking For". Benefits from "33 Days Paid Leave and Benefits". Pay from salary. Schedule from working hours. We must not create sections with filler. So we need to ensure each section has substantive content. Let's extract: About the role: The description under "The Role" (starting "This role leads the team and operating system behind one of our largest and most important client relationships...") plus maybe "Sports Context". Could combine. Responsibilities: The bullet list under "What You Will Own". Also maybe "What Good Looks Like" could be responsibilities but it's more expectations. We'll treat "What You Will Own" as responsibilities. Requirements: Could be "What We Are Looking For" (traits). Also "Helpful Experience" maybe qualifications. But we need to avoid duplication. We could have Requirements = "What We Are Looking For" (traits). Qualifications = "Helpful Experience". Skills = maybe "Practical AI fluency" etc but could be part of requirements. However we need to avoid thin sections. Perhaps combine Requirements and Qualifications into one? But we need to follow instruction: use headings for those categories if they have content. We could have Requirements (traits), Qualifications (experience), Skills (maybe AI fluency etc). But we need to ensure each has substantive content. Let's extract each: What We Are Looking For (traits): - High agency: you create forward motion without waiting for perfect instructions. - Strong judgement: you can decide what matters now, what stops, what waits, what needs more evidence and what needs escalation. - Direct people leadership: you have set standards, allocated work, coached people, handled performance problems and remained accountable for the team's output. - Operational grip: you can run several different workstreams at once without losing the detail or drowning the team in process. - Numeracy and analytical ability: you can interrogate imperfect data, find the signal and turn it into a decision. - Clear communication: you can explain complex work simply to team members, specialists and senior client stakeholders. - Cross-functional range: you are comfortable working across content, design, analytics, projects, product, engineering and service delivery. - Systems thinking: you improve the mechanism behind the work rather than relying on repeated manual effort or individual heroics. - Practical AI fluency: you use AI and agents to improve real operating loops, validate the output and drive adoption. - Pace and resilience: you can stay calm, make decisions and reorganise the work when priorities change quickly. - Attention to detail: you notice the small errors, weak handoffs and missing ownership that become larger problems later. - Genuine interest in basketball and sport: you understand how live games, tentpoles, player news and the shape of a season change operational priorities. That's a good list for Requirements. Helpful Experience: - Relevant experience may come from client operations, delivery leadership, content or publishing operations, programme management, product operations, support operations, media, sport or another high-volume environment. - We care more about what you have actually led, decided and improved than a particular job title. - Strong candidates will be able to show: - Responsibility for direct reports and difficult people decisions; - Ownership of several simultaneous workstreams across different disciplines; - A consequential decision made from incomplete evidence; - A process, system or operating model they materially improved; - An example of helping specialists or functional leaders deliver better; - A capability gap they closed through clearer ownership, process change or hiring; - Practical AI use that improved a measurable outcome. That's qualifications. What This Role Is Not: list of what it's not. Could be included under Requirements? Might be considered extra but could be a section "What the role is not". However instruction says only include sections when posting has real specific content. This is specific content. Could be a section "What the role is not". But we don't have a heading for that in the allowed list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we cannot add custom headings. So we must fit content into those. Thus "What This Role Is Not" could be placed under Requirements or Qualifications as a clarification. But maybe better to omit as it's not required. However we must preserve ALL substantive information; we cannot invent or summarize away detail. So we need to include that info somewhere. Could incorporate into Requirements as bullet points under "What the role is not". But that might deviate from heading semantics. However instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we should use those headings. It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should only use those headings. So we need to map all content to those headings. Thus we need to place "What This Role Is Not" under maybe Requirements or Qualifications. Could add a bullet list under Requirements titled "What the role is not". But that would be a subheading not allowed. Could just include as bullet points under Requirements with a note. That's okay. Similarly "Recruitment Process" is application instructions, should be removed. Now we need to extract Pay: Up to USD 110,000 salary, depending on experience, on a full time, permanent employment contract. Thus Pay: Up to USD 110,000, depending on experience. Full-time permanent. Schedule: Working Hours: this role must align closely with US Eastern Time across weekdays (regardless of your location). So schedule: Must align with US Eastern Time weekdays. Benefits: 33 Days Paid Leave and Benefits. Could list "33 days paid leave" plus unspecified benefits. We'll just state "33 days paid leave" as benefit. Now About the role: combine "The Role" description and maybe "Sports Context". Let's extract: The Role: "This role leads the team and operating system behind one of our largest and most important client relationships: a globally recognised organisation in major US sport.The work is high-volume and unusually broad. It spans content and publishing operations, design delivery, analytics and analysis, client projects, product and engineering coordination, releases, integrations, live-event readiness and a growing set of AI-enabled services. We need one strong operational generalist who can see that whole picture, lead the people doing the work and make sure priorities become completed outcomes. You will give the team clarity, pace and high standards; help specialists do their best work; and stop important work from depending on senior leaders chasing it. This is an operational and people-leadership role. It is not primarily a product-management, sales or account-director position." Sports Context: "The client is in major US sport, where a playoff run, Draft, trade, injury, live-game issue or major campaign can change the shape of the week immediately. Basketball knowledge is useful because it helps you anticipate those moments, understand their importance and organise the team accordingly. You do not need to be a basketball analyst. You do need to be interested enough to understand the season, the audience and why timing matters." We can combine. Now Responsibilities: "What You Will Own" bullet list: - Lead and develop the multidisciplinary team delivering work for the account. - Maintain one clear operating picture across priorities, owners, deadlines, dependencies, risks and decisions. - Set the team's workload and standards, inspect delivery and intervene early when quality, pace or performance slips. - Run a high volume of work across content, publishing, design, analytics, client projects, releases, integrations and AI-enabled services. - Turn unclear requests into a practical plan: the outcome, scope, owner, next action, dependency, deadline and decision required. - Use operating, audience and delivery data to diagnose problems and make decisions, not simply report activity. - Work closely with design, content, product, engineering, support and client leaders without pretending to replace their specialist judgement. - Help functional leaders manage priorities and handoffs, provide operational cover when they are unavailable and prevent one account from consuming all of their capacity. - Lead large, ambiguous operational projects, including audits and migrations, while keeping live delivery moving. - Improve the operating system itself. This includes simplifying fragmented tracking, moving appropriate work from Airtable into Linear and building useful review rhythms, automations and controls. - Recognise when a growing area needs clearer ownership, a different process or a specialist hire; define the need, help hire the right person and make the resulting capability work. - Prepare concise, accurate client updates and lead day-to-day delivery conversations, including incidents and difficult news. - Make sensible day-to-day decisions independently and escalate only the decisions that genuinely need senior or specialist input. That's responsibilities. Now Requirements: traits list from "What We Are Looking For". We'll put as

• . Qualifications: helpful experience list. Skills: maybe we can extract specific skills like "Practical AI fluency", "Numeracy and analytical ability", "Clear communication", etc. But those are already in Requirements. Could treat Skills as subset like "Practical AI fluency, Numeracy, Analytical ability, Clear communication, Cross-functional range, Systems thinking, Attention to detail, Pace and resilience, Direct people leadership, Operational grip, Strong judgement, High agency, Genuine interest in basketball and sport." But that duplicates. Perhaps better to treat Skills as "Practical AI fluency, Numeracy and analytical ability, Clear communication, Cross-functional range, Systems thinking, Attention to detail, Pace and resilience, Direct people leadership, Operational grip, Strong judgement, High agency, Genuine interest in basketball and sport." But that's essentially same as Requirements. However we need to avoid thin sections; but we have content for each