Energy Attorney

Here's a thinking process: 1. **Analyze the Request:** - User wants me to reformat a job posting into clean, well-structured semantic HTML. - Rules specified: - Use `

` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use `

• ` for any list of duties/requirements/benefits - Use `

  ` for prose - Do NOT repeat the job title as a heading (page already shows it) - Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short `

  ` or drop it - Preserve ALL substantive information; do NOT invent or summarize away detail - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions - IMPORTANT: 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") and never create Pay/Schedule/Benefits sections unless the posting actually states them - Prefer a few substantive sections over many thin ones - Output ONLY the HTML fragment — no /, no markdown code fences 2. **Analyze the Input Text:** The input is a job posting for an Energy Attorney at a law firm. Let me extract and structure the content: - Firm description: "Our client is a law firm committed to excellence in serving business, government, and individual clients regarding energy matters, business transactions, corporate matters and real estate transactions, employment counseling and litigation, civil litigation, bankruptcy, administrative law, elder law, and estate planning. Our core values focus on dignity, community, honor, civility, teamwork, and passion expressed in a balanced life." - Job title/role: Energy Attorney (but I shouldn't create a heading for it, as per rules: "Do NOT repeat the job title as a heading (the page already shows it)") - Requirements/Qualifications section: "Our client is seeking an Energy Attorney to join our Energy and Telecommunications Law Team in our Shockoe Slip, Richmond, VA office. The ideal candidate will have 5-10 years of litigation or regulatory experience and an interest in joining our Energy team. This position offers an experienced litigator or regulatory attorney an opportunity to apply existing skills in a new and sophisticated regulatory environment in one of the law's most collegial workspaces. It will also involve working with clients, legislators and regulators in developing and advocating for energy-related laws, rules and regulations. The ideal candidate will have experience with pleadings, discovery, motions, hearings, and legal briefing, along with the judgment, writing ability, and analytical skills necessary to navigate complex regulatory matters. Prior energy-sector or public utility experience is helpful but not required. We are willing to invest in the right candidate and provide the opportunity to develop deep subject-matter expertise. The successful candidate will possess excellent organizational, communication, and time management skills, along with exceptional attention to detail. This position requires sound judgment, discretion, confidentiality, and the ability to work both independently and collaboratively as part of a team. Candidates should be adaptable and willing to assist wherever needed to support the firm's attorneys, clients, and staff. This is a full-time, non-exempt, and in-office position." - Benefits/Salary: "Benifits Salary Range: $125,000-$175,000 annually, commensurate with qualifications and experience. Employer paid medical insurance for employees Employee funded medical flex spending and dependent care flex spending accounts (FSA) Dental and vision insurance Employer paid life and disability insurance 401k plan with employer contributions Generous paid leave benefits- including PTO, ten paid holidays, and paid parental leave Paid parking Provides equal employment and advancement opportunities to all colleagues and applicants for employment without regard to race, color, ethnicity, religion, gender, pregnancy/ [seems cut off, but I should include what's there, but remove EEO boilerplate per rules: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate"]" Let me re-read the input carefully. It ends with "Provides equal employment and advancement opportunities to all colleagues and applicants for employment without regard to race, color, ethnicity, religion, gender, pregnancy/" - this is EEO boilerplate, which I must remove per rules: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Also, "Benifits Salary Range: $125,000-$175,000 annually, commensurate with qualifications and experience." - Note: "Benifits" is a typo, should be "Benefits". I should preserve the content but maybe fix the typo? The rules say "Preserve ALL substantive information; do NOT invent or summarize away detail." I'll keep it as is, or maybe just clean it. I'll keep the text as provided but clean up obvious typos only if they don't change meaning. Actually, I should be careful: "Preserve ALL substantive information" - I shouldn't alter the text, just structure it. But "commensurate with qualifications and experience" is a phrase I should avoid leaving as filler if it's part of a section I'm creating. Wait, the rule says: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". So if I create a Pay section, I must not have "commensurate with experience" as the content. But the posting actually says "$125,000-$175,000 annually, commensurate with qualifications and experience." I can include the salary range, and maybe mention "commensurate with qualifications and experience" as part of the description, but I need to make sure the section has real content. Actually, the salary range is specific: $125,000-$175,000. I'll include that. The "commensurate with..." part is descriptive, I can include it in the

  or

• . Let's list out the sections I can identify: - About the firm/role (description, core values, location) - Responsibilities/Requirements (the ideal candidate criteria) - Qualifications (skills, experience) - Benefits/Salary (but careful: rules say never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state salary range and benefits. So I can create a Benefits section, but I need to include specific benefits, not generic placeholders.) - The posting has "Benifits Salary Range: $125,000-$175,000 annually, commensurate with qualifications and experience." then lists benefits. I should probably put the salary and benefits together or separate. The rules say use

  for section headings including Benefits, Pay, Schedule. But I should only create them if there's real content. There is real content. Let's parse the benefits listed: - Employer paid medical insurance for employees - Employee funded medical flex spending and dependent care flex spending accounts (FSA) - Dental and vision insurance - Employer paid life and disability insurance - 401k plan with employer contributions - Generous paid leave benefits- including PTO, ten paid holidays, and paid parental leave - Paid parking - (EEO statement at the end, which I remove) Salary: $125,000-$175,000 annually, commensurate with qualifications and experience. Now, section headings I should use:

  for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But I need to map the content appropriately and avoid repeating job title. Also, "Do NOT repeat the job title as a heading (the page already shows it)" - so I won't have an or for the title. I'll start with relevant sections. Rules: "Prefer a few substantive sections over many thin ones." "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text..." Let's decide on sections: - About the firm/role: The firm description and core values, plus location. - Responsibilities/Requirements: The candidate requirements, experience, skills. - Benefits & Compensation: Salary range and specific benefits. But I need to be careful with "Requirements" vs "Qualifications" vs "Skills". The posting mixes them. I can combine into one section or split. Let's see: "Requirements:" is actually at the start but seems to be a section label that's part of the text? The input says: "Requirements:Our client is seeking an Energy Attorney..." So "Requirements:" might be a heading that was in the original, but per rules, I shouldn't repeat job title, but "Requirements" is a section heading I'm allowed to use if there's content. However, the instruction says: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So I can use those. But I need to avoid creating thin sections. Let's map: Content analysis: - Firm description & core values: "Our client is a law firm committed to excellence... core values focus on dignity, community, honor, civility, teamwork, and passion expressed in a balanced life." - Location: Shockoe Slip, Richmond, VA office (mentioned in "join our Energy and Telecommunications Law Team in our Shockoe Slip, Richmond, VA office") - Role level/ experience: 5-10 years of litigation or regulatory experience - What the role involves: opportunity to apply skills in new regulatory environment, working with clients, legislators, regulators, developing/advocating energy-related laws, pleadings, discovery, motions, hearings, legal briefing, complex regulatory matters - Preferred but not required: prior energy-sector or public utility experience - Firm investment: willing to invest in right candidate, develop deep subject-matter expertise - Skills: excellent organizational, communication, time management, exceptional attention to detail - Personal attributes: sound judgment, discretion, confidentiality, ability to work independently and collaboratively, adaptable, willing to assist wherever needed - Employment type: full-time, non-exempt, in-office - Salary: $125,000-$175,000 annually, commensurate with qualifications and experience - Benefits: employer paid medical insurance, employee funded FSA (medical and dependent care), dental and vision insurance, employer paid life and disability insurance, 401k with employer contributions, generous paid leave (PTO, 10 paid holidays, paid parental leave), paid parking - EEO statement: remove Now, how to structure with

  sections. I'll choose these sections (only if they have specific content): 1. About the Role (or firm description/location) - but "About the role" might be vague. I could use "About the Firm" or just integrate. The rule says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). I'll map: -

  About the Firm

  or

  About the Role

  . The posting starts with firm description, so maybe "About the Firm" but the example says "About the role". I'll use

  About the Role

  and put the firm description there, or