Director, Battery Asset Management
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists,
for prose
- Do NOT repeat job title as heading (page already shows it)
- Do NOT put Job ID/requisition numbers as headings
- Preserve ALL substantive information
- Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions
- Include section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Prefer few substantive sections over many thin ones
- Output ONLY HTML fragment — no /, no markdown code fences
Now, let's map the content:
1. "About Us" - company description, but the rule says "About the role" as heading. However, the posting has "About Us" and "About You". The rule says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So I should use appropriate headings. "About Us" is company info, but maybe "About the Role" or "About the Company"? The rule says "About the role" as example. But the posting has "About Us" and "About You". I think I should keep the substantive content but use appropriate headings. Since the rule says "About the role" as example, but the posting has "About Us" describing the company and the role context. I'll use "About the Role" for the "About Us" section? Actually, "About Us" is about the company, not the role. But the rule says "About the role" as example heading. However, the posting has "About Us" and "About You". I think I should create sections based on content: maybe "About the Company" and "About You"? But the rule says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those. I'll use headings that match the content: "About the Company" for "About Us", "About You" for "About You", "Responsibilities" for "Key Responsibilities", "Requirements" for "What You Bring", "Benefits" for "Benefits", "Pay" for salary, and maybe "How We Work" for culture but that includes EEO boilerplate which should be removed. The "How We Work" section has company culture description and then EEO statement. I should keep the culture description but remove EEO boilerplate. However, the rule says remove EEO/equal-opportunity boilerplate. So I'll keep the culture paragraph but not the EEO line.
Also, the rule: "Do NOT repeat the job title as a heading (the page already shows it)". The job title is "Director of Battery Asset Management". Not in the content as heading, but the posting starts with "About Us Madison Energy Infrastructure is hiring a Director of Battery Asset Management...". That's fine.
Now, structure:
- About the Company (from "About Us")
- About You (from "About You")
- Responsibilities (from "Key Responsibilities")
- Requirements (from "What You Bring")
- Benefits (from "Benefits")
- Pay (from salary line)
- Maybe "How We Work" for culture but it's somewhat boilerplate. The rule says prefer few substantive sections over many thin ones. The culture paragraph is somewhat generic but specific to the company. I'll include it as "Culture" or "How We Work"? The rule says use headings like "Schedule" but not "Culture". However, the rule says "include a section ONLY when the posting has real, specific content for it". The "How We Work" section has specific content about the company's portfolio, team, environment. It's not just filler. I'll include it as "How We Work" but remove the EEO line.
Now, for each section, use
for prose,
- for lists.
Let's parse each section:
**About Us**:
"Madison Energy Infrastructure is hiring a Director of Battery Asset Management to build and run the operating platform behind our national, distributed, battery fleet. We have 80 MW of batteries operating today across 30 sites and 5 states, expect that fleet to triple next year and double the following year, with $2 billion of battery deployment ahead of us. The goal is simple: get the operating system right now, while the fleet is still manageable, so that it works when at scale."
This is prose, so
.
**About You**:
"You've spent years elbow-deep in battery systems — you can read a three-line diagram without help, and you know an OEM's manual well enough to push back on their own engineers. You've managed contracts and you've managed people, and you're just as comfortable owning a preventative maintenance program as you are picking up the phone when a site goes down. You'd rather build something from scratch than inherit someone else's system, and you want to own the numbers that come with that."
Prose,
.
**Key Responsibilities**:
"In year one, expect to be a player-coach: you'll manage the Battery Asset Manager, but you'll also be hands-on yourself — on the phone with OEMs, troubleshooting failures remotely, reviewing alarms, negotiating O&M agreements, visiting sites, escalating warranty claims, and making sure batteries dispatch when they're supposed to. That hands-on work is also how you'll build the operating system this role exists to create — you will own:"
Then a list:
- Fleet Performance - Own fleet performance against target (97%+ monthly availability,
- for each bullet. The introductory paragraph is prose, then list.
**What You Bring**:
"The right person will probably have:"
Then a list:
- 5+ years of technical experience with distributed generation battery systems
- Meaningful hands on troubleshooting experience
- Distributed generation battery experience specifically. Utility scale only experience is not a match for this role
- 4+ years of battery market or commercial operations experience, including exposure to market participation, capacity obligations, settlement, or battery value stacks
- Experience negotiating or administering O&M agreements or LTSAs
- Experience reviewing preventative and corrective maintenance reports and challenging contractor conclusions
- Strong familiarity with OEM manuals, specifications, warranties, and operating requirements
- Management experience with at least one direct report
- Budget ownership experience
- Working knowledge of battery fire safety and applicable codes
- Experience with operational reporting tools such as Power BI
- The ability to read and understand electrical drawings, including three line diagrams
- Battery and inverter manufacturer certifications are a plus.
- Entrepreneurial experience is also a plus. We value people who have had to build something, own a metric, fix problems without a playbook, and operate with urgency.
This is a list of requirements. Use
- . The introductory sentence "The right person will probably have:" can be a
before the list.
**Benefits**:
List:
- PTO and company holidays
- Medical, dental, vision
- Employer-paid short-term disability, long-term disability, life insurance
- 401(k) and company match
- Professional development stipend
- Strong culture of collaboration, performance, and personal growth
Use
- .
**Pay**:
"$175,000 - $200,000 a year The actual salary offered may vary depending on job-related factors including, but not limited to knowledge, skills, experience and location."
This is pay information. Use
for the range and the note.
**How We Work**:
"At Madison Energy Infrastructure, we believe in the power of clean energy infrastructure to drive real impact—for our customers, our partners, and the communities we serve. We’ve quickly emerged as a preeminent developer, investor, and operator of distributed generation, helping organizations across sectors meet their energy goals with certainty, speed, and trust. Our robust portfolio consists of over half a gigawatt of clean energy infrastructure projects across more than 25 states. We’re building a team that thrives on ownership and ambition. As we expand into direct, end-to-end services for Fortune 500 companies, public entities, and nonprofits alike, we rely on collaborative thinkers who bring structure to complexity, energy to execution, and curiosity to every challenge. Our environment is fast-paced and outcome-oriented—but grounded in the belief that how we work together matters as much as what we deliver. If you’re excited to shape the future of clean energy and be part of a high-performance, high-integrity team, we’d love to meet you."
Then EEO statement: "Madison Energy Infrastructure is an equal opportunity employer. All applicants will be considered for employment without attention to race, color, religion, sex, sexual orientation, gender identity, national origin, veteran, or disability status." This is boilerplate, remove.
So keep the culture paragraph as
under "How We Work" or "Culture". The rule says use headings like "Schedule" but not "Culture". However, the rule says "include a section ONLY when the posting has real, specific content for it". This is specific content about the company. I'll use "How We Work" as heading.
Now, ensure no duplicate lines, no application instructions (none present), no cookie/navigation/legal/EEO/scam-warning.
Now, output HTML fragment with
headings and appropriate tags.
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. For "About Us", maybe "About the Role
for prose - Do NOT repeat job title as heading (page already shows it) - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions - Include section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment — no /, no markdown code fences Now, let's map the content: 1. "About Us" - company description, but the rule says "About the role" as heading. However, the posting has "About Us" and "About You". The rule says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So I should use appropriate headings. "About Us" is company info, but maybe "About the Role" or "About the Company"? The rule says "About the role" as example. But the posting has "About Us" and "About You". I think I should keep the substantive content but use appropriate headings. Since the rule says "About the role" as example, but the posting has "About Us" describing the company and the role context. I'll use "About the Role" for the "About Us" section? Actually, "About Us" is about the company, not the role. But the rule says "About the role" as example heading. However, the posting has "About Us" and "About You". I think I should create sections based on content: maybe "About the Company" and "About You"? But the rule says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those. I'll use headings that match the content: "About the Company" for "About Us", "About You" for "About You", "Responsibilities" for "Key Responsibilities", "Requirements" for "What You Bring", "Benefits" for "Benefits", "Pay" for salary, and maybe "How We Work" for culture but that includes EEO boilerplate which should be removed. The "How We Work" section has company culture description and then EEO statement. I should keep the culture description but remove EEO boilerplate. However, the rule says remove EEO/equal-opportunity boilerplate. So I'll keep the culture paragraph but not the EEO line.
Also, the rule: "Do NOT repeat the job title as a heading (the page already shows it)". The job title is "Director of Battery Asset Management". Not in the content as heading, but the posting starts with "About Us Madison Energy Infrastructure is hiring a Director of Battery Asset Management...". That's fine.
Now, structure:
- About the Company (from "About Us")
- About You (from "About You")
- Responsibilities (from "Key Responsibilities")
- Requirements (from "What You Bring")
- Benefits (from "Benefits")
- Pay (from salary line)
- Maybe "How We Work" for culture but it's somewhat boilerplate. The rule says prefer few substantive sections over many thin ones. The culture paragraph is somewhat generic but specific to the company. I'll include it as "Culture" or "How We Work"? The rule says use headings like "Schedule" but not "Culture". However, the rule says "include a section ONLY when the posting has real, specific content for it". The "How We Work" section has specific content about the company's portfolio, team, environment. It's not just filler. I'll include it as "How We Work" but remove the EEO line.
Now, for each section, use
for prose,
- for lists.
Let's parse each section:
**About Us**:
"Madison Energy Infrastructure is hiring a Director of Battery Asset Management to build and run the operating platform behind our national, distributed, battery fleet. We have 80 MW of batteries operating today across 30 sites and 5 states, expect that fleet to triple next year and double the following year, with $2 billion of battery deployment ahead of us. The goal is simple: get the operating system right now, while the fleet is still manageable, so that it works when at scale."
This is prose, so
. **About You**: "You've spent years elbow-deep in battery systems — you can read a three-line diagram without help, and you know an OEM's manual well enough to push back on their own engineers. You've managed contracts and you've managed people, and you're just as comfortable owning a preventative maintenance program as you are picking up the phone when a site goes down. You'd rather build something from scratch than inherit someone else's system, and you want to own the numbers that come with that." Prose,
. **Key Responsibilities**: "In year one, expect to be a player-coach: you'll manage the Battery Asset Manager, but you'll also be hands-on yourself — on the phone with OEMs, troubleshooting failures remotely, reviewing alarms, negotiating O&M agreements, visiting sites, escalating warranty claims, and making sure batteries dispatch when they're supposed to. That hands-on work is also how you'll build the operating system this role exists to create — you will own:" Then a list: - Fleet Performance - Own fleet performance against target (97%+ monthly availability,
- for each bullet. The introductory paragraph is prose, then list.
**What You Bring**:
"The right person will probably have:"
Then a list:
- 5+ years of technical experience with distributed generation battery systems
- Meaningful hands on troubleshooting experience
- Distributed generation battery experience specifically. Utility scale only experience is not a match for this role
- 4+ years of battery market or commercial operations experience, including exposure to market participation, capacity obligations, settlement, or battery value stacks
- Experience negotiating or administering O&M agreements or LTSAs
- Experience reviewing preventative and corrective maintenance reports and challenging contractor conclusions
- Strong familiarity with OEM manuals, specifications, warranties, and operating requirements
- Management experience with at least one direct report
- Budget ownership experience
- Working knowledge of battery fire safety and applicable codes
- Experience with operational reporting tools such as Power BI
- The ability to read and understand electrical drawings, including three line diagrams
- Battery and inverter manufacturer certifications are a plus.
- Entrepreneurial experience is also a plus. We value people who have had to build something, own a metric, fix problems without a playbook, and operate with urgency.
This is a list of requirements. Use
- . The introductory sentence "The right person will probably have:" can be a
before the list. **Benefits**: List: - PTO and company holidays - Medical, dental, vision - Employer-paid short-term disability, long-term disability, life insurance - 401(k) and company match - Professional development stipend - Strong culture of collaboration, performance, and personal growth Use
- .
**Pay**:
"$175,000 - $200,000 a year The actual salary offered may vary depending on job-related factors including, but not limited to knowledge, skills, experience and location."
This is pay information. Use
for the range and the note. **How We Work**: "At Madison Energy Infrastructure, we believe in the power of clean energy infrastructure to drive real impact—for our customers, our partners, and the communities we serve. We’ve quickly emerged as a preeminent developer, investor, and operator of distributed generation, helping organizations across sectors meet their energy goals with certainty, speed, and trust. Our robust portfolio consists of over half a gigawatt of clean energy infrastructure projects across more than 25 states. We’re building a team that thrives on ownership and ambition. As we expand into direct, end-to-end services for Fortune 500 companies, public entities, and nonprofits alike, we rely on collaborative thinkers who bring structure to complexity, energy to execution, and curiosity to every challenge. Our environment is fast-paced and outcome-oriented—but grounded in the belief that how we work together matters as much as what we deliver. If you’re excited to shape the future of clean energy and be part of a high-performance, high-integrity team, we’d love to meet you." Then EEO statement: "Madison Energy Infrastructure is an equal opportunity employer. All applicants will be considered for employment without attention to race, color, religion, sex, sexual orientation, gender identity, national origin, veteran, or disability status." This is boilerplate, remove. So keep the culture paragraph as
under "How We Work" or "Culture". The rule says use headings like "Schedule" but not "Culture". However, the rule says "include a section ONLY when the posting has real, specific content for it". This is specific content about the company. I'll use "How We Work" as heading. Now, ensure no duplicate lines, no application instructions (none present), no cookie/navigation/legal/EEO/scam-warning. Now, output HTML fragment with
headings and appropriate tags. 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. For "About Us", maybe "About the Role
- .
**Pay**:
"$175,000 - $200,000 a year The actual salary offered may vary depending on job-related factors including, but not limited to knowledge, skills, experience and location."
This is pay information. Use
- . The introductory sentence "The right person will probably have:" can be a