Associate Counsel, Immigration

The user wants me to reformat a job posting into clean semantic HTML. Let me analyze the content and apply the rules. First, identify sections: - About the role / Job Summary: There's a "Job Summary" paragraph. - Responsibilities: There's a "Responsibilities" section with a list of duties. - Requirements / Qualifications: Not explicitly labeled but there are skills listed and maybe implied requirements. The posting mentions "Skills" list at the end: Litigation Management; Regulatory Compliance; Legal Analysis; Policy Development; Corporate Governance; Legal Research; Contract Negotiations. That could be a Skills section. - Benefits: There's a paragraph about base pay, commission/bonus, benefits. But the rules say: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does mention base pay, commission/bonus, benefits. However, it's generic: "Base pay is one part of the Total Rewards... Most sales positions... most non-sales positions... Additionally, Comcast provides best-in-class Benefits... Please visit the compensation and benefits summary on our careers site for more details." This is not specific to the role; it's boilerplate. The rules say: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them but in a generic way. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". This is generic filler. So I should not include a Benefits/Pay section. - Schedule: The posting says "Must be able to work nights and weekends, variable schedule(s) as necessary." That's a schedule detail. Could be included in a Schedule section? But the rule says never create Schedule section unless posting actually states them. It does state schedule requirements. However, it's a single line. Could be folded into Responsibilities or a separate Schedule section. The rule: "Prefer a few substantive sections over many thin ones." So maybe include schedule as a bullet under Responsibilities or a separate small section? The rule says use

for section headings like Schedule. But only if real specific content. The schedule requirement is specific: nights, weekends, variable schedule. That's real content. But it's just one line. Could be a

under a Schedule heading? But the rule says use

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

  for prose. Schedule is not a list. Could be a

  . But the heading Schedule would be thin. Might be better to include in Responsibilities as a bullet. - Skills: There's a "Skills" list. That's a list, so use

  • . - The posting also has a disclaimer and EEO boilerplate, which should be removed. - The "Employees at all levels are expected to:" list is a set of expectations, could be part of Responsibilities or a separate section like "Expectations" or "Core Values". But the rule says use headings like Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Not "Expectations". Could fold into Responsibilities. - The "Job Summary" is a paragraph. - The "Responsibilities" section has a list of bullet points (though in the text they are separated by line breaks). I'll convert to
    • . - The "Skills" list is comma-separated; I'll make each a
    • . - The "Base pay..." paragraph is generic boilerplate; remove. - The "Comcast is an equal opportunity workplace..." is EEO boilerplate; remove. - The "Disclaimer:" paragraph is boilerplate; remove. - The "Job Description" heading appears before the responsibilities list; but the section is "Responsibilities". I'll use

      Responsibilities

      . - The "Job Summary" heading: use

      About the role

      or

      Job Summary

      . The rule says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So I can use "About the role" for the summary. - There's no explicit Requirements/Qualifications section. The skills list might be considered qualifications. But the rule says include section only when real specific content. The skills list is specific. I'll create a Skills section. - The "Employees at all levels are expected to:" list: could be a separate section "Expectations" but not in the allowed headings. Could be part of Responsibilities or omitted. Since they are general company expectations, not specific to the role, maybe omit. But they are part of the job description. The rule: "Preserve ALL substantive information; do NOT invent or summarize away detail." So I should include them. Could create a section "Expectations" but not in the example headings. The rule says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., not exhaustive. But to be safe, I'll include them under Responsibilities as a sublist or separate list. However, the rule says use

      • for any list of duties/requirements/benefits. These are expectations, not duties. Could be a separate
        under a heading "Expectations". But the heading might not be standard. I'll include them as a list under a heading "Expectations" but maybe better to fold into Responsibilities as "General expectations:" and list. - The "Regular, consistent and punctual attendance. Must be able to work nights and weekends, variable schedule(s) as necessary." is a requirement. Could be under Requirements or Schedule. Since there's no Requirements section, maybe create a "Requirements" heading? The posting doesn't have a Requirements section explicitly. But there are requirements implied: the skills, the schedule, the attendance. The rule says include section only when real specific content. There is specific content: schedule, attendance, skills. Could create a "Requirements" section with those. But the skills are separate. The schedule and attendance are requirements. I'll create a "Requirements" section with those two bullets, and a separate "Skills" section. - The "Other duties and responsibilities as assigned." is a generic line; could be omitted or included as a bullet. Let's structure:

        About the role

        Job Summary paragraph.

        Responsibilities

        • Providing in-depth legal counsel to specific business units, ensuring alignment with corporate strategies
        • Interpreting regulatory changes and advising on legal risks to preemptively protect business interests
        • Collaborating with senior executives to develop and implement legal policies and procedures
        • Leading complex legal research initiatives to inform organizational decision-making and strategy
        • Managing the selection and oversight of outside counsel for specialized legal matters
        • Formulating legal strategies and solutions that address unique business challenges
        • Exercising high-level discretion and judgment in sensitive and impactful legal cases
        • Contributing to strategic planning with legal expertise that influences company-wide objectives
        • Consistent exercise of independent judgment and discretion in matters of significance
        • Regular, consistent and punctual attendance. Must be able to work nights and weekends, variable schedule(s) as necessary.
        • Other duties and responsibilities as assigned.

        Requirements

        • Regular, consistent and punctual attendance
        • Ability to work nights and weekends, variable schedule(s) as necessary
        But the attendance and schedule are already in responsibilities. Might duplicate. Better to have a "Schedule" section for the schedule requirement. The rule says use Schedule heading if posting states them. It does. So:

        Schedule

        Must be able to work nights and weekends, variable schedule(s) as necessary. Regular, consistent and punctual attendance required.

        But the rule says use
        • for any list of duties/requirements/benefits, and

          for prose. Schedule is not a list, so

          is fine. Now the "Employees at all levels are expected to:" list. That's a list of expectations. Could be a separate section "Expectations" or "Core expectations". I'll include as a list under a heading "Expectations". But the rule says use headings like those listed. Not mandatory. I'll include as a subsection under Responsibilities? Or separate. Since it's substantive, I'll create a heading "Expectations" and list.

          Expectations

          • Understand our Operating Principles; make them the guidelines for how you do your job.
          • Own the customer experience think and act in ways that put our customers first, give them seamless digital options at every touchpoint, and make them promoters of our products and services.
          • Know your stuff be enthusiastic learners, users and advocates of our game-changing technology, products and services, especially our digital tools and experiences.
          • Win as a team make big things happen by working together and being open to new ideas.
          • Be an active part of the Net Promoter System a way of working that brings more employee and customer feedback into the company by joining huddles, making call backs and helping us elevate opportunities to do better for our customers.
          • Drive results and growth.
          • Support a culture of inclusion in how you work and lead.
          • Do what's right for each other, our customers, investors and our communities.
          Now Skills:

          Skills

          • Litigation Management
          • Regulatory Compliance
          • Legal Analysis
          • Policy Development
          • Corporate Governance
          • Legal Research
          • Contract Negotiations
          Now, the posting also has a paragraph about Comcast at the beginning: "Comcast brings together the best in media and technology..." That's company description, not about the role. The rule says "Do NOT repeat the job title as a heading (the page already shows it)". The company description is not the job title. Should we include it? The rule says "Preserve ALL substantive information". But the company description is boilerplate. However, it's part of the posting. The user might want it. But the instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The company description is marketing boilerplate. I'd consider it boilerplate and remove. But it's at the top. The rule says "Preserve ALL substantive information". The company description is not substantive to the role. I'll omit it. Also, the "Job Description" heading appears before the responsibilities list. That's just a label. I'll ignore. Now, the "Disclaimer" and "Comcast is an equal opportunity workplace" are boilerplate, remove. The "Base pay..." paragraph is generic benefits boilerplate, remove. Now, output only HTML fragment, no markdown. Let's write the HTML. Note: The rule says "use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So I should use those exact headings where appropriate. I used "About the role", "Responsibilities", "Schedule", "Expectations", "Skills". "Expectations" is not in the list but it's okay. Could rename to "Qualifications"? But expectations are not qualifications. Could be "Requirements". But requirements usually are skills, education, experience. The expectations are behavioral. I'll keep "Expectations". Alternatively, fold expectations into Responsibilities as a sublist. But they are separate from duties