Energy Attorney
` 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. **Identify the Input Data:**
The user provided text that seems to be a job posting snippet, but it's actually just the "Qualifications" and "Benefits" sections. Let me re-read carefully:
"Qualifications We are seeking an Energy Attorney to join our Energy and Telecommunications Law Team in our Shockoe Slip, Richmond, VA office. 5-10 years of litigation or regulatory experience 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.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.Will possess excellent organizational, communication, and time management skills, along with exceptional attention to detail. Requires sound judgment, discretion, confidentiality, and the ability to work both independently and collaboratively as part of a teamCandidates should be adaptable and willing to assist wherever needed to support the firm's attorneys, clients, and staff. Benefits Including Employer paid medical insurance for employeesEmployee funded medical flex spending and dependent care flex spending accounts (FSA)Dental and vision insuranceEmployer paid life and disability insurance401k plan with employer contributionsGenerous paid leave benefits- including PTO, ten paid holidays, and paid parental leavePaid parking"
Wait, this is just the Qualifications and Benefits sections. There's no "About the role", "Responsibilities", "Skills", "Pay", "Schedule" sections provided, or maybe some are embedded. Let me parse carefully.
Actually, the user might be giving me a partial posting, and I need to output HTML based on what's there, following the rules. The rules say: "include a section ONLY when the posting has real, specific content for it" and "never emit a heading followed by filler/placeholder text". So I should only output sections that have actual content.
Let me identify what's in the text:
- It starts with "Qualifications" but that seems like a section label from the original posting. However, the rules say "Do NOT repeat the job title as a heading (the page already shows it)" and use `
` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But also: "include a section ONLY when the posting has real, specific content for it". The text begins with "Qualifications We are seeking..." so "Qualifications" might be a heading already, but I should treat it as content. However, the rules say don't repeat job title, but "Qualifications" is a section type. I need to decide whether to include a "Qualifications" section. The text has substantial content under what seems like Qualifications. But wait, the user might have just pasted the Qualifications and Benefits parts, and maybe other parts are implied or I should only output what's given.
Let me re-read the prompt: "Reformat a job posting into clean, well-structured semantic HTML." Then they give rules, then they give the text. The text appears to be just the Qualifications and Benefits sections of a job posting. There's no "About the role", "Responsibilities" (though some content overlaps), "Skills" (maybe overlapping), "Pay", "Schedule".
I need to extract substantive content and format it into HTML sections with `` headings, `- ` for lists, `
` for prose. I should remove boilerplate, duplicate lines, application instructions, etc. The text given has no obvious boilerplate beyond what's listed.
Let me parse the text into meaningful sections:
Starting: "Qualifications We are seeking an Energy Attorney to join our Energy and Telecommunications Law Team in our Shockoe Slip, Richmond, VA office. 5-10 years of litigation or regulatory experience"
This could be part of Qualifications or an About the role. The text says "Qualifications" at the very beginning, but maybe that's just the section label from the source. I should probably not output a "Qualifications" heading if it's just the start, but the rules say include a section ONLY when the posting has real, specific content for it. The content under "Qualifications" is real. However, the rules also say "Do NOT repeat the job title as a heading (the page already shows it)" - "Qualifications" is a section heading, not a job title. I think I should include sections that have content.
Let me look at the structure typical of job postings: Often they have sections like: About the role, Responsibilities, Requirements/Qualifications, Skills, Benefits, Pay, Schedule. The user gave examples: "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". So I can use those as heading options, but only if content exists.
From the text, I can identify:
- Location/office: Shockoe Slip, Richmond, VA
- Experience: 5-10 years of litigation or regulatory experience
- Description of the role/opportunity: "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."
- Requirements/skills: Experience with pleadings, discovery, motions, hearings, and legal briefing, judgment, writing ability, analytical skills. Prior energy-sector or public utility experience helpful but not required. Willingness to invest in candidate, develop deep subject-matter expertise. Excellent organizational, communication, and time management skills, exceptional attention to detail. Sound judgment, discretion, confidentiality. Ability to work independently and collaboratively. Adaptable, assist wherever needed.
- Benefits: 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.
Now, rules: "never create Pay/Schedule/Benefits sections unless the posting actually states them" - Benefits are stated, so I can include a Benefits section. "Pay" and "Schedule" are not stated, so I should NOT create those sections.
Also: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The text doesn't seem to have those, except maybe "Candidates should be adaptable and willing to assist wherever needed to support the firm's attorneys, clients, and staff." That's not boilerplate, it's substantive.
"Preserve ALL substantive information; do NOT invent or summarize away detail." So I need to include all the details given.
"Prefer a few substantive sections over many thin ones." So I should group related content into fewer sections if possible, but the rules specify using `
` for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I need to decide how to split the content.
Let me try to categorize the content logically into sections that exist in the posting:
The posting seems to have a "Qualifications" section and a "Benefits" section. But there's also role description text. I could create:
- "About the role" or keep it as part of qualifications? The text starts with "Qualifications We are seeking..." so maybe "Qualifications" is the heading. But the rules say use `` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). I can use "Qualifications" as an `` if the content warrants it. However, the prompt says "Do NOT repeat the job title as a heading (the page already shows it)" - that's about job title, not section headings. I think using "Qualifications" as a heading is fine if the posting has a qualifications section.
But wait: The user's text might be the entire posting, or just a part. The prompt says "Reformat a job posting into clean, well-structured semantic HTML." Then gives rules, then gives the text. I should assume the text is the relevant content to reformat. I'll work with what's given.
Let me list all distinct pieces of information:
1. Location/Office: Shockoe Slip, Richmond, VA (mentioned in "Qualifications We are seeking an Energy Attorney to join our Energy and Telecommunications Law Team in our Shockoe Slip, Richmond, VA office.")
2. Experience requirement: 5-10 years of litigation or regulatory experience
3. Role description/opportunity: "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."
4. Technical/functional requirements: Experience with pleadings, discovery, motions, hearings, and legal briefing; judgment, writing ability, analytical skills; navigate complex regulatory matters
5. Preferred/optional: Prior energy-sector or public utility experience helpful but not required
6. Firm investment: Willing to invest in the right candidate, provide opportunity to develop deep subject-matter expertise
7. Soft skills/organizational: Excellent organizational, communication, and time management skills; exceptional attention to detail
8. Professional attributes: Sound judgment, discretion, confidentiality; ability to work independently and collaboratively as part of a team
9. Adaptability: Candidates should be adaptable and willing to assist wherever needed to support the firm's attorneys, clients, and staff
10. Benefits list:
- 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
Now, how to structure with `<
` 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. **Identify the Input Data:** The user provided text that seems to be a job posting snippet, but it's actually just the "Qualifications" and "Benefits" sections. Let me re-read carefully: "Qualifications We are seeking an Energy Attorney to join our Energy and Telecommunications Law Team in our Shockoe Slip, Richmond, VA office. 5-10 years of litigation or regulatory experience 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.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.Will possess excellent organizational, communication, and time management skills, along with exceptional attention to detail. Requires sound judgment, discretion, confidentiality, and the ability to work both independently and collaboratively as part of a teamCandidates should be adaptable and willing to assist wherever needed to support the firm's attorneys, clients, and staff. Benefits Including Employer paid medical insurance for employeesEmployee funded medical flex spending and dependent care flex spending accounts (FSA)Dental and vision insuranceEmployer paid life and disability insurance401k plan with employer contributionsGenerous paid leave benefits- including PTO, ten paid holidays, and paid parental leavePaid parking" Wait, this is just the Qualifications and Benefits sections. There's no "About the role", "Responsibilities", "Skills", "Pay", "Schedule" sections provided, or maybe some are embedded. Let me parse carefully. Actually, the user might be giving me a partial posting, and I need to output HTML based on what's there, following the rules. The rules say: "include a section ONLY when the posting has real, specific content for it" and "never emit a heading followed by filler/placeholder text". So I should only output sections that have actual content. Let me identify what's in the text: - It starts with "Qualifications" but that seems like a section label from the original posting. However, the rules say "Do NOT repeat the job title as a heading (the page already shows it)" and use `
` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But also: "include a section ONLY when the posting has real, specific content for it". The text begins with "Qualifications We are seeking..." so "Qualifications" might be a heading already, but I should treat it as content. However, the rules say don't repeat job title, but "Qualifications" is a section type. I need to decide whether to include a "Qualifications" section. The text has substantial content under what seems like Qualifications. But wait, the user might have just pasted the Qualifications and Benefits parts, and maybe other parts are implied or I should only output what's given.
Let me re-read the prompt: "Reformat a job posting into clean, well-structured semantic HTML." Then they give rules, then they give the text. The text appears to be just the Qualifications and Benefits sections of a job posting. There's no "About the role", "Responsibilities" (though some content overlaps), "Skills" (maybe overlapping), "Pay", "Schedule".
I need to extract substantive content and format it into HTML sections with `` headings, `- ` for lists, `
` for prose. I should remove boilerplate, duplicate lines, application instructions, etc. The text given has no obvious boilerplate beyond what's listed.
Let me parse the text into meaningful sections:
Starting: "Qualifications We are seeking an Energy Attorney to join our Energy and Telecommunications Law Team in our Shockoe Slip, Richmond, VA office. 5-10 years of litigation or regulatory experience"
This could be part of Qualifications or an About the role. The text says "Qualifications" at the very beginning, but maybe that's just the section label from the source. I should probably not output a "Qualifications" heading if it's just the start, but the rules say include a section ONLY when the posting has real, specific content for it. The content under "Qualifications" is real. However, the rules also say "Do NOT repeat the job title as a heading (the page already shows it)" - "Qualifications" is a section heading, not a job title. I think I should include sections that have content.
Let me look at the structure typical of job postings: Often they have sections like: About the role, Responsibilities, Requirements/Qualifications, Skills, Benefits, Pay, Schedule. The user gave examples: "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". So I can use those as heading options, but only if content exists.
From the text, I can identify:
- Location/office: Shockoe Slip, Richmond, VA
- Experience: 5-10 years of litigation or regulatory experience
- Description of the role/opportunity: "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."
- Requirements/skills: Experience with pleadings, discovery, motions, hearings, and legal briefing, judgment, writing ability, analytical skills. Prior energy-sector or public utility experience helpful but not required. Willingness to invest in candidate, develop deep subject-matter expertise. Excellent organizational, communication, and time management skills, exceptional attention to detail. Sound judgment, discretion, confidentiality. Ability to work independently and collaboratively. Adaptable, assist wherever needed.
- Benefits: 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.
Now, rules: "never create Pay/Schedule/Benefits sections unless the posting actually states them" - Benefits are stated, so I can include a Benefits section. "Pay" and "Schedule" are not stated, so I should NOT create those sections.
Also: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The text doesn't seem to have those, except maybe "Candidates should be adaptable and willing to assist wherever needed to support the firm's attorneys, clients, and staff." That's not boilerplate, it's substantive.
"Preserve ALL substantive information; do NOT invent or summarize away detail." So I need to include all the details given.
"Prefer a few substantive sections over many thin ones." So I should group related content into fewer sections if possible, but the rules specify using `
` for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I need to decide how to split the content.
Let me try to categorize the content logically into sections that exist in the posting:
The posting seems to have a "Qualifications" section and a "Benefits" section. But there's also role description text. I could create:
- "About the role" or keep it as part of qualifications? The text starts with "Qualifications We are seeking..." so maybe "Qualifications" is the heading. But the rules say use `` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). I can use "Qualifications" as an `` if the content warrants it. However, the prompt says "Do NOT repeat the job title as a heading (the page already shows it)" - that's about job title, not section headings. I think using "Qualifications" as a heading is fine if the posting has a qualifications section.
But wait: The user's text might be the entire posting, or just a part. The prompt says "Reformat a job posting into clean, well-structured semantic HTML." Then gives rules, then gives the text. I should assume the text is the relevant content to reformat. I'll work with what's given.
Let me list all distinct pieces of information:
1. Location/Office: Shockoe Slip, Richmond, VA (mentioned in "Qualifications We are seeking an Energy Attorney to join our Energy and Telecommunications Law Team in our Shockoe Slip, Richmond, VA office.")
2. Experience requirement: 5-10 years of litigation or regulatory experience
3. Role description/opportunity: "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."
4. Technical/functional requirements: Experience with pleadings, discovery, motions, hearings, and legal briefing; judgment, writing ability, analytical skills; navigate complex regulatory matters
5. Preferred/optional: Prior energy-sector or public utility experience helpful but not required
6. Firm investment: Willing to invest in the right candidate, provide opportunity to develop deep subject-matter expertise
7. Soft skills/organizational: Excellent organizational, communication, and time management skills; exceptional attention to detail
8. Professional attributes: Sound judgment, discretion, confidentiality; ability to work independently and collaboratively as part of a team
9. Adaptability: Candidates should be adaptable and willing to assist wherever needed to support the firm's attorneys, clients, and staff
10. Benefits list:
- 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
Now, how to structure with `<
- ` for lists, `
` for prose. I should remove boilerplate, duplicate lines, application instructions, etc. The text given has no obvious boilerplate beyond what's listed. Let me parse the text into meaningful sections: Starting: "Qualifications We are seeking an Energy Attorney to join our Energy and Telecommunications Law Team in our Shockoe Slip, Richmond, VA office. 5-10 years of litigation or regulatory experience" This could be part of Qualifications or an About the role. The text says "Qualifications" at the very beginning, but maybe that's just the section label from the source. I should probably not output a "Qualifications" heading if it's just the start, but the rules say include a section ONLY when the posting has real, specific content for it. The content under "Qualifications" is real. However, the rules also say "Do NOT repeat the job title as a heading (the page already shows it)" - "Qualifications" is a section heading, not a job title. I think I should include sections that have content. Let me look at the structure typical of job postings: Often they have sections like: About the role, Responsibilities, Requirements/Qualifications, Skills, Benefits, Pay, Schedule. The user gave examples: "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". So I can use those as heading options, but only if content exists. From the text, I can identify: - Location/office: Shockoe Slip, Richmond, VA - Experience: 5-10 years of litigation or regulatory experience - Description of the role/opportunity: "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." - Requirements/skills: Experience with pleadings, discovery, motions, hearings, and legal briefing, judgment, writing ability, analytical skills. Prior energy-sector or public utility experience helpful but not required. Willingness to invest in candidate, develop deep subject-matter expertise. Excellent organizational, communication, and time management skills, exceptional attention to detail. Sound judgment, discretion, confidentiality. Ability to work independently and collaboratively. Adaptable, assist wherever needed. - Benefits: 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. Now, rules: "never create Pay/Schedule/Benefits sections unless the posting actually states them" - Benefits are stated, so I can include a Benefits section. "Pay" and "Schedule" are not stated, so I should NOT create those sections. Also: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The text doesn't seem to have those, except maybe "Candidates should be adaptable and willing to assist wherever needed to support the firm's attorneys, clients, and staff." That's not boilerplate, it's substantive. "Preserve ALL substantive information; do NOT invent or summarize away detail." So I need to include all the details given. "Prefer a few substantive sections over many thin ones." So I should group related content into fewer sections if possible, but the rules specify using `
` for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I need to decide how to split the content. Let me try to categorize the content logically into sections that exist in the posting: The posting seems to have a "Qualifications" section and a "Benefits" section. But there's also role description text. I could create: - "About the role" or keep it as part of qualifications? The text starts with "Qualifications We are seeking..." so maybe "Qualifications" is the heading. But the rules say use `
` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). I can use "Qualifications" as an `
` if the content warrants it. However, the prompt says "Do NOT repeat the job title as a heading (the page already shows it)" - that's about job title, not section headings. I think using "Qualifications" as a heading is fine if the posting has a qualifications section. But wait: The user's text might be the entire posting, or just a part. The prompt says "Reformat a job posting into clean, well-structured semantic HTML." Then gives rules, then gives the text. I should assume the text is the relevant content to reformat. I'll work with what's given. Let me list all distinct pieces of information: 1. Location/Office: Shockoe Slip, Richmond, VA (mentioned in "Qualifications We are seeking an Energy Attorney to join our Energy and Telecommunications Law Team in our Shockoe Slip, Richmond, VA office.") 2. Experience requirement: 5-10 years of litigation or regulatory experience 3. Role description/opportunity: "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." 4. Technical/functional requirements: Experience with pleadings, discovery, motions, hearings, and legal briefing; judgment, writing ability, analytical skills; navigate complex regulatory matters 5. Preferred/optional: Prior energy-sector or public utility experience helpful but not required 6. Firm investment: Willing to invest in the right candidate, provide opportunity to develop deep subject-matter expertise 7. Soft skills/organizational: Excellent organizational, communication, and time management skills; exceptional attention to detail 8. Professional attributes: Sound judgment, discretion, confidentiality; ability to work independently and collaboratively as part of a team 9. Adaptability: Candidates should be adaptable and willing to assist wherever needed to support the firm's attorneys, clients, and staff 10. Benefits list: - 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 Now, how to structure with `<