Director, BESS Services
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only if posting has real specific content. The posting includes: About AESC (but not "About the role"? There's a description of role at top: "AESC is seeking a senior service leader..." That's about the role. Could treat as "About the role". There's "Key Responsibilities" section. There's "Qualifications" section. There's "Preferred Qualifications" maybe part of Qualifications? Could combine. There's "Performance Measures" maybe not needed. There's "What Success Looks Like" maybe not needed. There's "Level Calibration" maybe not needed. There's "Candidate Evidence Expected" maybe not needed. There's "What We Offer" which includes benefits. There's no explicit Pay or Schedule. So we should not create Pay or Schedule sections because not specified. Benefits: we have list of benefits: Comprehensive compensation packages including a competitive salary and a rewarding bonus program. An inclusive and diverse work environment... Highly automated... Medical, Dental and Vision Insurance HSA and Flexible Spending Accounts 401K with company match Life Insurance (Company paid and additional voluntary life available) Paid Vacation and 14 Paid Holidays Short term and long-term disability coverage (Company Paid) Tuition reimbursement. That's benefits. Also maybe "Skills" not explicit; we could skip Skills section. Requirements: maybe combine Qualifications and Preferred Qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which headings to include based on content. We have About the role (intro). Responsibilities (Key Responsibilities). Qualifications (Experience etc). Benefits (What We Offer). Possibly Skills not present; we skip. Requirements maybe same as Qualifications? Could treat Qualifications as Requirements? But they have both Qualifications and Preferred Qualifications. Could put Requirements heading for mandatory qualifications, and maybe Skills for preferred? But better to follow instruction: include a section ONLY when posting has real specific content. So we can have About the role, Responsibilities, Qualifications, Benefits. Possibly also Requirements if we separate mandatory vs preferred? But we have Qualifications section that includes both mandatory and preferred; we could split: Requirements (mandatory) and Skills (preferred). However the posting has "Qualifications" heading with subpoints, then "Preferred Qualifications". So we could map: Requirements = Qualifications (mandatory). Skills = Preferred Qualifications. That seems reasonable.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits.
We must not repeat job title as heading. No Job ID etc.
We need to preserve all substantive information; do not invent or summarize away detail. Must keep details but we can format as lists or paragraphs.
We need to use - for any list of duties/requirements/benefits, and
for prose.
Thus for each section, we need to decide what is list vs prose.
About the role: The introductory paragraph(s) describing role. Could be multiple paragraphs. We'll put as
elements.
Responsibilities: There's a list of responsibilities under "Key Responsibilities" with bullet-like sentences each starting with a bold heading? Actually the text: "Key Responsibilities Service strategy and organization. Define the U.S. service operating model, organization, regional coverage, make-versus-buy strategy, headcount plan, partner network, systems, procedures, and multi-year capability roadmap. Recruit, develop, and retain commissioning, field service, technical support, performance, and service-operations talent.Safety leadership. Own the service safety culture and field execution standards...." It's a series of sections each ending with a period. Could treat each as list item. We'll make
- for each responsibility block.
Requirements: The "Qualifications" section includes bullet-like sentences each starting with a bold label: "Experience.", "BESS lifecycle depth.", etc. We'll make list.
Skills: "Preferred Qualifications" similar.
Benefits: "What We Offer" includes sentences; we can make list.
We must not include boilerplate like EEO etc. The posting ends with application process etc; we should remove that. So stop before "Application Process". The text includes "Application Process Even if you don't meet every requirement..." etc. We'll exclude that.
Now craft HTML.
We need to ensure we don't include any markdown fences.
Let's extract content precisely.
About the role: The first paragraph: "AESC is seeking a senior service leader to build and operate the U.S. service organization for its growing battery energy storage system (BESS) business. This leader will own the installed-base customer experience and the safe, reliable, and profitable delivery of commissioning support, long-term service agreements (LTSAs), field service, warranty, remote support, spare parts, and lifecycle performance. The role spans the full post-sale lifecycle, from design-for-serviceability and commissioning readiness through commercial operation, planned and corrective maintenance, major incident response, upgrades, warranty closeout, and contract renewal. It requires a hands-on builder who can establish a geographically distributed team and partner network while serving as the senior escalation point for customers and internal executives. Core mandate: Build a safety-first, scalable U.S. BESS service platform that protects customers, maximizes fleet availability, fulfills contractual commitments, converts field learning into product improvement, and develops service into a durable source of revenue and margin."
We could split into two paragraphs but fine as one
.
About AESC: There's a section "About AESC". Should we include that? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). About AESC is not in that list, but could be considered part of About the role? Might be extra info about company. The instruction says include a section ONLY when posting has real specific content for it — never emit a heading followed by filler/placeholder text. It didn't forbid adding other headings not in the list, but the examples given are those. Safer to stick to those headings. So we could incorporate About AESC into About the role paragraph or maybe omit. But we should preserve all substantive information; omitting About AESC would lose info. However we could treat it as part of About the role (since it's about the company). The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." It didn't forbid adding other headings, but the list of headings is examples. I think we should include About AESC as a separate section maybe under "About the role" or we could add a heading "About AESC" but not in the list; risk of being considered not following instruction. Better to incorporate into About the role paragraph.
Thus About the role paragraph will include both the role description and About AESC.
Now Responsibilities: Need to capture each bullet.
Let's extract the responsibilities text after "Key Responsibilities". The text:
"Service strategy and organization. Define the U.S. service operating model, organization, regional coverage, make-versus-buy strategy, headcount plan, partner network, systems, procedures, and multi-year capability roadmap. Recruit, develop, and retain commissioning, field service, technical support, performance, and service-operations talent.Safety leadership. Own the service safety culture and field execution standards. Establish governance for LOTO, energized work, switching, arc-flash controls, permit-to-work, job hazard analysis, emergency response, stop-work authority, contractor safety, incident reporting, and lessons learned.Commissioning-to-service transition. Establish service-readiness gates, handover criteria, punch-list closure, documentation, training, asset registration, baseline performance, warranty activation, spare-parts readiness, and customer acceptance requirements before commercial operation.Field service and fleet reliability. Lead preventive, predictive, and corrective maintenance across utility-scale BESS assets. Plan outages, deploy resources, supervise service partners, standardize work execution, and continuously improve system availability, capacity, reliability, first-time fix rate, and mean time to repair.Technical escalation and incident management. Direct 24/7 escalation coverage for critical events. Lead structured troubleshooting, containment, root-cause analysis, corrective and preventive action (CAPA), management of change, recovery plans, executive communications, and closure of repeat-failure mechanisms.Remote operations and performance. Build remote monitoring, alarm triage, fleet analytics, condition-based maintenance, performance reporting, and case-management capabilities. Use BMS, PCS, EMS/SCADA, controls, communications, thermal management, and fire-system data to identify risk and improve lifecycle performance.Warranty, spares, and supplier recovery. Own warranty administration, claims, RMA/return processes, failure evidence, cost recovery, field campaigns, spare-parts forecasting, regional inventory, repair strategy, obsolescence planning, and supplier/OEM escalation.LTSA and commercial performance. Ensure compliance with SLAs, availability and capacity guarantees, response times, reporting obligations, maintenance scope, and liquidated-damages exposure. Own the regional service budget/cost center and, as assigned, service P&L, pricing inputs, lifecycle cost models, change orders, renewals, and service growth.Customer leadership. Serve as the executive service owner for strategic customers. Establish governance, performance reviews, escalation protocols, transparent communications, recovery plans, and a consistent experience that supports satisfaction, retention, references, and repeat business.Quality and product feedback. Partner with Engineering, Product, Quality, Project Delivery, Supply Chain, Software, Sales, Finance, and Legal to improve serviceability, reliability, documentation, training, warranty terms, contract assumptions, and future product design based on field evidence.Operating discipline. Implement CMMS and case-management workflows, asset hierarchy, work orders, controlled procedures, skills certification, service bulletins, audit routines, KPI dashboards, financial controls, data quality, and executive reporting."
We need to split into list items. Each sentence ends with a period before next capitalized heading. We'll make each heading plus its description as a list item.
Thus list items:
- Service strategy and organization. Define the U.S. service operating model, organization, regional coverage, make-versus-buy strategy, headcount plan, partner network, systems, procedures, and multi-year capability roadmap. Recruit, develop, and retain commissioning, field service, technical support, performance, and service-operations talent.
- Safety leadership. Own the service safety culture and field execution standards. Establish governance for LOTO, energized work, switching, arc-flash controls, permit-to-work, job hazard analysis, emergency response, stop-work authority, contractor safety, incident reporting, and lessons learned.
- Commissioning-to-service transition. Establish service-readiness gates, handover criteria, punch-list closure, documentation, training, asset registration, baseline performance, warranty activation, spare-parts readiness, and customer acceptance requirements before commercial operation.
- Field service and fleet reliability. Lead preventive, predictive, and corrective maintenance across utility-scale BESS assets. Plan outages, deploy resources, supervise service partners, standardize work execution, and continuously improve system availability, capacity, reliability, first-time fix rate, and mean time to repair.
- Technical escalation and incident management. Direct 24/7 escalation coverage for critical events. Lead structured troubleshooting, containment, root-cause analysis, corrective and preventive action (CAPA), management of change, recovery plans, executive communications, and closure of repeat-failure mechanisms.
- Remote operations and performance. Build remote monitoring, alarm triage, fleet analytics, condition-based maintenance, performance reporting, and case-management capabilities. Use BMS, PCS, EMS/SCADA, controls, communications, thermal management, and fire-system data to identify risk and improve lifecycle performance.
- Warranty, spares, and supplier recovery. Own warranty administration, claims, R
for prose. Thus for each section, we need to decide what is list vs prose. About the role: The introductory paragraph(s) describing role. Could be multiple paragraphs. We'll put as
elements. Responsibilities: There's a list of responsibilities under "Key Responsibilities" with bullet-like sentences each starting with a bold heading? Actually the text: "Key Responsibilities Service strategy and organization. Define the U.S. service operating model, organization, regional coverage, make-versus-buy strategy, headcount plan, partner network, systems, procedures, and multi-year capability roadmap. Recruit, develop, and retain commissioning, field service, technical support, performance, and service-operations talent.Safety leadership. Own the service safety culture and field execution standards...." It's a series of sections each ending with a period. Could treat each as list item. We'll make
- for each responsibility block.
Requirements: The "Qualifications" section includes bullet-like sentences each starting with a bold label: "Experience.", "BESS lifecycle depth.", etc. We'll make list.
Skills: "Preferred Qualifications" similar.
Benefits: "What We Offer" includes sentences; we can make list.
We must not include boilerplate like EEO etc. The posting ends with application process etc; we should remove that. So stop before "Application Process". The text includes "Application Process Even if you don't meet every requirement..." etc. We'll exclude that.
Now craft HTML.
We need to ensure we don't include any markdown fences.
Let's extract content precisely.
About the role: The first paragraph: "AESC is seeking a senior service leader to build and operate the U.S. service organization for its growing battery energy storage system (BESS) business. This leader will own the installed-base customer experience and the safe, reliable, and profitable delivery of commissioning support, long-term service agreements (LTSAs), field service, warranty, remote support, spare parts, and lifecycle performance. The role spans the full post-sale lifecycle, from design-for-serviceability and commissioning readiness through commercial operation, planned and corrective maintenance, major incident response, upgrades, warranty closeout, and contract renewal. It requires a hands-on builder who can establish a geographically distributed team and partner network while serving as the senior escalation point for customers and internal executives. Core mandate: Build a safety-first, scalable U.S. BESS service platform that protects customers, maximizes fleet availability, fulfills contractual commitments, converts field learning into product improvement, and develops service into a durable source of revenue and margin."
We could split into two paragraphs but fine as one
. About AESC: There's a section "About AESC". Should we include that? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). About AESC is not in that list, but could be considered part of About the role? Might be extra info about company. The instruction says include a section ONLY when posting has real specific content for it — never emit a heading followed by filler/placeholder text. It didn't forbid adding other headings not in the list, but the examples given are those. Safer to stick to those headings. So we could incorporate About AESC into About the role paragraph or maybe omit. But we should preserve all substantive information; omitting About AESC would lose info. However we could treat it as part of About the role (since it's about the company). The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." It didn't forbid adding other headings, but the list of headings is examples. I think we should include About AESC as a separate section maybe under "About the role" or we could add a heading "About AESC" but not in the list; risk of being considered not following instruction. Better to incorporate into About the role paragraph. Thus About the role paragraph will include both the role description and About AESC. Now Responsibilities: Need to capture each bullet. Let's extract the responsibilities text after "Key Responsibilities". The text: "Service strategy and organization. Define the U.S. service operating model, organization, regional coverage, make-versus-buy strategy, headcount plan, partner network, systems, procedures, and multi-year capability roadmap. Recruit, develop, and retain commissioning, field service, technical support, performance, and service-operations talent.Safety leadership. Own the service safety culture and field execution standards. Establish governance for LOTO, energized work, switching, arc-flash controls, permit-to-work, job hazard analysis, emergency response, stop-work authority, contractor safety, incident reporting, and lessons learned.Commissioning-to-service transition. Establish service-readiness gates, handover criteria, punch-list closure, documentation, training, asset registration, baseline performance, warranty activation, spare-parts readiness, and customer acceptance requirements before commercial operation.Field service and fleet reliability. Lead preventive, predictive, and corrective maintenance across utility-scale BESS assets. Plan outages, deploy resources, supervise service partners, standardize work execution, and continuously improve system availability, capacity, reliability, first-time fix rate, and mean time to repair.Technical escalation and incident management. Direct 24/7 escalation coverage for critical events. Lead structured troubleshooting, containment, root-cause analysis, corrective and preventive action (CAPA), management of change, recovery plans, executive communications, and closure of repeat-failure mechanisms.Remote operations and performance. Build remote monitoring, alarm triage, fleet analytics, condition-based maintenance, performance reporting, and case-management capabilities. Use BMS, PCS, EMS/SCADA, controls, communications, thermal management, and fire-system data to identify risk and improve lifecycle performance.Warranty, spares, and supplier recovery. Own warranty administration, claims, RMA/return processes, failure evidence, cost recovery, field campaigns, spare-parts forecasting, regional inventory, repair strategy, obsolescence planning, and supplier/OEM escalation.LTSA and commercial performance. Ensure compliance with SLAs, availability and capacity guarantees, response times, reporting obligations, maintenance scope, and liquidated-damages exposure. Own the regional service budget/cost center and, as assigned, service P&L, pricing inputs, lifecycle cost models, change orders, renewals, and service growth.Customer leadership. Serve as the executive service owner for strategic customers. Establish governance, performance reviews, escalation protocols, transparent communications, recovery plans, and a consistent experience that supports satisfaction, retention, references, and repeat business.Quality and product feedback. Partner with Engineering, Product, Quality, Project Delivery, Supply Chain, Software, Sales, Finance, and Legal to improve serviceability, reliability, documentation, training, warranty terms, contract assumptions, and future product design based on field evidence.Operating discipline. Implement CMMS and case-management workflows, asset hierarchy, work orders, controlled procedures, skills certification, service bulletins, audit routines, KPI dashboards, financial controls, data quality, and executive reporting." We need to split into list items. Each sentence ends with a period before next capitalized heading. We'll make each heading plus its description as a list item. Thus list items: - Service strategy and organization. Define the U.S. service operating model, organization, regional coverage, make-versus-buy strategy, headcount plan, partner network, systems, procedures, and multi-year capability roadmap. Recruit, develop, and retain commissioning, field service, technical support, performance, and service-operations talent. - Safety leadership. Own the service safety culture and field execution standards. Establish governance for LOTO, energized work, switching, arc-flash controls, permit-to-work, job hazard analysis, emergency response, stop-work authority, contractor safety, incident reporting, and lessons learned. - Commissioning-to-service transition. Establish service-readiness gates, handover criteria, punch-list closure, documentation, training, asset registration, baseline performance, warranty activation, spare-parts readiness, and customer acceptance requirements before commercial operation. - Field service and fleet reliability. Lead preventive, predictive, and corrective maintenance across utility-scale BESS assets. Plan outages, deploy resources, supervise service partners, standardize work execution, and continuously improve system availability, capacity, reliability, first-time fix rate, and mean time to repair. - Technical escalation and incident management. Direct 24/7 escalation coverage for critical events. Lead structured troubleshooting, containment, root-cause analysis, corrective and preventive action (CAPA), management of change, recovery plans, executive communications, and closure of repeat-failure mechanisms. - Remote operations and performance. Build remote monitoring, alarm triage, fleet analytics, condition-based maintenance, performance reporting, and case-management capabilities. Use BMS, PCS, EMS/SCADA, controls, communications, thermal management, and fire-system data to identify risk and improve lifecycle performance. - Warranty, spares, and supplier recovery. Own warranty administration, claims, R