Lead Counsel, Youth

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. First, job title: Product Counsel (youth-focused). Not to repeat as heading. We need sections: - About the role: likely the first paragraph describing role: "Meta's Legal team is seeking an experienced Product Counsel to support our youth-focused products...". That's about the role. - Responsibilities: list of duties: "Advise on compliance with children's and teens' privacy laws...", "Identify and assess legal risks...", "Partner with policy...", "Monitor and analyze emerging legislative...", "Collaborate with cross-functional partners...", "Engage with regulatory inquiries...", "Contribute to team-level goals...". Those are responsibilities. - Requirements: Minimum Qualifications list. - Qualifications: Preferred Qualifications list. - Skills: maybe combine some skills from requirements? But we have separate sections for Skills. The posting includes skills like "Effective communication, legal writing, and interpersonal skills", "Demonstrated business judgment, client counseling, and strategic thinking skills", etc. Those could go under Skills. - Benefits: posting mentions "$170,000/year to $237,000/year + bonus + equity + benefits". Also "In addition to base compensation, Meta offers benefits. Learn more about benefits at Meta." So we have Pay and Benefits. Pay: salary range. Benefits: mention benefits but not details. Since we should only include Benefits if posting actually states them. It says "Meta offers benefits." That's vague but still states benefits exist. Might be considered real content? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits exist, though not detailed. I'd include Benefits section with a short paragraph: "Meta offers benefits (details available at Meta)." However we should avoid filler like "not specified". This is okay. - Pay: include salary range. - Schedule: not mentioned, so omit. We also need to include minor metadata like Job ID etc? Not present. We need to remove boilerplate: EEO, accommodations, etc. Remove those paragraphs. We need to use

for section headings. Use

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

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to output only HTML fragment, no /, no markdown fences. Let's craft. First, About the role: combine first two sentences? Actually first paragraph: "Meta's Legal team is seeking an experienced Product Counsel to support our youth-focused products and experiences across Meta's family of apps. In this role, you will serve as a trusted legal partner to product, policy, engineering, and operations teams building features and safeguards for younger users. You will navigate a complex and rapidly evolving legal and regulatory landscape — including youth privacy/data protection laws, age-appropriate design requirements, and online safety frameworks — to help Meta build products that are safe, responsible, and compliant for teens and families." That's prose. Second paragraph: "Meta’s Product Counsel organization provides strategic legal advice and risk mitigation to product, engineering, and business teams across Meta’s family of products and services. The organization partners cross-functionally to address complex, novel legal issues in a fast-paced, innovative environment, and influences product and business decisions at scale." This also about the role/organization. Could be part of About the role. We'll put that in About the role

  . Now Responsibilities: list items from "Lead Counsel, Youth Responsibilities:" bullet points. We need to capture each bullet as

• . List: - Advise on compliance with children's and teens' privacy laws and regulations, including youth privacy/data protection laws, age-appropriate design requirements, and online safety laws - Identify and assess legal risks associated with new product launches and feature changes affecting younger users, and develop practical mitigation strategies - Partner with policy, trust and safety, and operations teams to shape internal standards and external commitments related to youth safety and online wellbeing - Monitor and analyze emerging legislative and regulatory developments impacting youth online safety and privacy, and translate their implications into actionable guidance for product and business stakeholders - Collaborate with cross-functional partners to develop and maintain compliance frameworks, product review processes, and documentation supporting youth-related legal obligations - Engage with regulatory inquiries, government investigations, and external stakeholders on matters related to youth products and safety - Contribute to team-level goals by identifying legal trends, sharing insights across the broader legal organization, and helping shape Meta's approach to youth-related legal strategy Now Requirements (Minimum Qualifications): list items. List: - Juris Doctor (JD) or equivalent law degree from an accredited institution - Active and in good standing bar license in at least one U.S. state or equivalent foreign bar license. Where the jurisdiction of licensure differs from the location in which the role is based, the ability to promptly obtain permission to practice law for Meta in that location - 5+ years of legal experience as a practicing attorney, including at a law firm, in-house, or in government - Experience advising on children's or teens' privacy and online safety laws and regulations (e.g., COPPA, UK AADC, UK OSA, EU DSA, AU SMMA) - Experience working directly with product and engineering teams to assess legal risk and implement compliance requirements in a fast-paced environment - Experience managing regulatory inquiries or government-facing matters related to consumer, privacy, or platform safety issues - Demonstrated experience providing legal advice on technology, internet, or media products and services - Effective communication, legal writing, and interpersonal skills - Demonstrated business judgment, client counseling, and strategic thinking skills - Proven track record of delivering results with large-scale, cross-functional projects in a fast-paced environment - Experience making decisions in the face of ambiguity and evolving priorities Note: Some of these are skills; but they are in Minimum Qualifications. We'll keep them under Requirements. Now Preferred Qualifications: list. - Experience adhering to and implementing responsible, ethical AI practices (e.g., risk assessment, bias mitigation, quality and accuracy reviews) - Demonstrated ongoing AI skill development (e.g., prompt/context engineering, agent orchestration) and staying current with emerging AI technologies - Familiarity with age-appropriate design frameworks, parental consent mechanisms, and minor-specific data handling requirements across multiple jurisdictions - In-house legal experience at a consumer technology or social media company with youth-facing products - Demonstrated ability to integrate AI tools to optimize/redesign workflows and drive measurable impact (e.g., efficiency gains, quality improvements) Now Skills: maybe we can extract skills not already covered? But we already have communication etc in Requirements. Could still have a Skills section for things like "Effective communication, legal writing, and interpersonal skills", "Demonstrated business judgment, client counseling, and strategic thinking skills". However those are already in Requirements. To avoid duplication, we could still include Skills section but risk duplication. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication but better to avoid redundancy. However we need a Skills section only if posting has real specific content for it. The posting does mention skills explicitly: "Effective communication, legal writing, and interpersonal skills", "Demonstrated business judgment, client counseling, and strategic thinking skills". Those are indeed skills. We could put them under Skills. But they also appear in Minimum Qualifications. To avoid duplication, we could move them to Skills and remove from Requirements? But that would lose some info from Requirements. Better to keep them in Requirements and not create a Skills section unless there are additional skills not covered. The posting does not have a separate "Skills" heading; it's embedded. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can have a Skills section if there is content. Since the posting does mention skills, we could create a Skills section with those skill items. However we must not lose the other qualifications. We could keep Requirements as the minimum qualifications (including education, experience, bar license) and put the skill-based items under Skills. Let's parse: Minimum Qualifications list includes both experience/education and skills. We could split: Requirements: education, experience, bar license, years, specific experience areas (privacy, product, regulatory inquiries, tech advice). Skills: communication, business judgment, track record, decision-making, etc. But the instruction says "Preserve ALL substantive information". Splitting is okay as long as we keep all. Let's decide: Requirements (Minimum Qualifications) will contain: - Juris Doctor (JD) or equivalent law degree from an accredited institution - Active and in good standing bar license in at least one U.S. state or equivalent foreign bar license. Where the jurisdiction of licensure differs from the location in which the role is based, the ability to promptly obtain permission to practice law for Meta in that location - 5+ years of legal experience as a practicing attorney, including at a law firm, in-house, or in government - Experience advising on children's or teens' privacy and online safety laws and regulations (e.g., COPPA, UK AADC, UK OSA, EU DSA, AU SMMA) - Experience working directly with product and engineering teams to assess legal risk and implement compliance requirements in a fast-paced environment - Experience managing regulatory inquiries or government-facing matters related to consumer, privacy, or platform safety issues - Demonstrated experience providing legal advice on technology, internet, or media products and services Skills section will contain: - Effective communication, legal writing, and interpersonal skills - Demonstrated business judgment, client counseling, and strategic thinking skills - Proven track record of delivering results with large-scale, cross-functional projects in a fast-paced environment - Experience making decisions in the face of ambiguity and evolving priorities That seems reasonable. Now Qualifications (Preferred Qualifications) as above. Now Benefits: we have "Meta offers benefits. Learn more about benefits at Meta." Also compensation line includes "+ bonus + equity + benefits". We'll create Benefits section with a short paragraph: "Meta offers benefits (details available at Meta)." That's not too vague but still states benefits exist. Pay: salary range: "$170,000/year to $237,000/year + bonus + equity". We'll put that in Pay section. Schedule: none. Now we need to output HTML fragment. Structure:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Skills

  • ...
  ...

  Qualifications

  • ...
  ...

  Benefits

  Meta offers benefits (details available at Meta).

  Pay

  $170,000/year to $237,000/year + bonus + equity

  We should not include Schedule. Check for any leftover boilerplate: EEO, accommodations, etc. Remove. Now ensure we didn't miss any substantive info: The paragraph about "Meta builds technologies that help people connect..." is under "About Meta". That's also substantive. Should we include that? It's under "About Meta". Could be part of About the role or a separate section? The instruction only lists certain headings; "About Meta" is not in the list. But we could incorporate that into About the role? It's about the company, not the role. The instruction says to use those headings; we could still include a paragraph about Meta under About the role? Might be okay. However the instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications,