Business Systems Analyst II (Orange, CA - US)

We need to output HTML fragment only, with headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

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

  for prose. Do NOT repeat the job title as a heading. 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. We need to parse the posting. Key content: - Intro paragraph: "Interested in joining a growing company where you will work with talented colleagues, enhance a supportive and energetic culture, and be part of the climate solution? At Energy Solutions, we focus on the big impacts. And we believe that market-based programs can be a powerful force to deliver large-scale energy, carbon, and water-use savings. Since 1995, we've harnessed that power to offer proven, performance-based solutions for our utility, government, and institutional customers. ES is currently seeking a powerhouse Business Systems Analyst II to join our fast-paced Information Systems Team. You'll play a key role in delivering innovative solutions that help drive business success. Partnering with stakeholders, developers, and cross-functional teams, you'll translate business needs into clear requirements that shape platform enhancements and technology initiatives. In this role, you'll analyze business processes, define and refine requirements, and help ensure solutions align with strategic objectives. Your ability to simplify complex concepts, facilitate collaboration, and bridge the gap between business and technical teams will be critical to delivering successful outcomes. You'll work with a high degree of ownership while collaborating closely with others to support solution design, validate requirements, maintain project documentation, and contribute to Agile delivery practices. You'll also have opportunities to share your expertise, mentor fellow analysts, and help strengthen business analysis best practices across the organization. If you're a curious problem-solver who enjoys turning ideas into solutions and loves working with people and technology, this is an exciting opportunity to make a meaningful impact while growing your career. This is a hybrid work opportunity. ES has offices in Oakland, CA; Orange, CA; New York, NY; Portland, OR; Chicago, IL; and Boston, MA." - Then "Responsibilities include but are not limited to:" followed by bullet list. - Then "Minimum Qualifications: (Quantifiable Skills i.e Years of experience)" followed by bullet list. - Then "The salary range for this role is $106,000 - $123,000 with a target compensation of $106,000 - $115,000 based on experience and qualifications. Compensation is commensurate with experience and includes a generous retirement package." - Then "Energy Solutions provides an excellent benefits package including medical, dental and vision insurance, other pre-tax contribution plans and an Employee Stock Ownership Plan (ESOP)." - Then "AI Use ..." (boilerplate about AI use). This is likely legal/EEO boilerplate; we should remove. - Then "Equal Opportunity Employer ..." (EEO boilerplate) remove. - Then "Office Locations and a Remote Workforce ..." (some info about remote workforce, offices, states not accepting applications). This is maybe relevant? It's about office locations and remote workforce. Might be considered substantive? It includes details about offices and remote workforce, and states not accepting applications. This is not boilerplate? It's location info. Might be considered relevant. However, we already have offices listed earlier. This repeats some info. We need to preserve all substantive info, but we can combine. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The "Office Locations and a Remote Workforce" paragraph includes some info about remote workforce and offices, but also includes states not accepting applications. That might be considered application instruction? It's about where they accept applications from. Might be considered relevant to applicants. However, it's somewhat boilerplate? Not sure. The instruction says to remove duplicated lines. The earlier paragraph already listed offices. This paragraph adds remote workforce details and states not accepting applications. That is substantive (states not accepting applications). Should we keep? It's not EEO or legal; it's about eligibility. Might be considered relevant. However, the instruction says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The states not accepting applications could be considered application instructions (where they accept from). Might be considered application instruction. Safer to remove? But we need to preserve ALL substantive information. The states not accepting applications is substantive for applicants. However, it's also a kind of restriction. The instruction says to remove application instructions. That likely refers to "how to apply" instructions like "please submit your resume", etc. Not necessarily eligibility restrictions. But the phrase "At this time, we are not accepting applications from candidates residing in the following states: Delaware, Kentucky, Mississippi, Montana, Nebraska, and North Dakota." is a restriction. Might be considered part of the job posting. I'd keep it as part of Office Locations/Remote Workforce section. Then "Background Check Information ..." (legal/boilerplate) remove. Then "Reasonable Accommodations ..." (EEO/legal) remove. Then "Privacy Notice for Job Applicants" remove. Thus we need sections: About the role (intro), Responsibilities, Requirements (maybe Minimum Qualifications), Qualifications? Actually Minimum Qualifications is qualifications. Could also have Skills (maybe from qualifications). Benefits (benefits package). Pay (salary range). Schedule (hybrid work opportunity). Offices maybe part of About the role or separate? Could be part of About the role. We need to avoid filler like "Compensation is commensurate with experience" (that's filler). The instruction says 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. For Pay we have actual numbers, so we can include Pay section. For Benefits we have actual benefits listed, so we can include Benefits section. For Schedule we have "This is a hybrid work opportunity." That's specific enough? It's not filler like "varies". It's a statement. So we can include Schedule section. We need to avoid duplication. We'll combine similar info. Let's extract: About the role: The introductory paragraphs describing company, role, hybrid work, offices. We can include offices list there. Responsibilities: bullet list as given. Requirements/Qualifications: Minimum Qualifications bullet list. Skills: maybe we can extract from qualifications: strong technical analysis skills, communication skills, proficiency in writing user stories, working knowledge of SQL/BI tools, strong organizational skills. Could be a Skills section. But we already have qualifications; we could combine. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section called "Requirements" or "Qualifications". But we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to include only those with real content. We could have Requirements (including minimum qualifications) and Skills (maybe derived). But to avoid thin sections, maybe we just have Requirements (including qualifications and skills). However, the instruction says use headings for those categories if we have content. We could have Requirements (minimum qualifications) and Skills (specific skills). But we need to see if we have enough content for Skills separate. The qualifications bullet list includes many skill-like items: Bachelor's degree, five years experience, experience within Agile, experience conducting UAT, strong technical analysis skills, strong communication skills, proficiency in writing user stories, working knowledge of SQL/BI tools, strong organizational skills. That's a mix of qualifications and skills. Could split: Requirements (education, experience) and Skills (technical analysis, communication, etc.). But we need to avoid thin sections. Might be okay to have both. Benefits: medical, dental, vision insurance, other pre-tax contribution plans, ESOP. Pay: salary range $106,000 - $123,000 with target compensation $106,000 - $115,000 based on experience and qualifications. Also mentions generous retirement package. We should include that. Schedule: hybrid work opportunity. We also have office locations list; we can include in About the role. We need to remove filler like "Compensation is commensurate with experience" (that's filler). So in Pay section we should not include that phrase. We'll just include the salary range and retirement package. We need to ensure we don't include any boilerplate like AI Use, Equal Opportunity Employer, Office Locations and a Remote Workforce (maybe we keep part). But we already have offices in About the role. The Office Locations and a Remote Workforce paragraph includes remote workforce details and states not accepting applications. The states not accepting applications is substantive; we could include that in About the role or maybe a separate section like "Eligibility". But we don't have a heading for eligibility. Could we incorporate into About the role? It's about office locations and remote workforce, plus states not accepting applications. We could add a sentence: "Employees who reside within 40 miles of an office (except New York) will be assigned to that location, though in-office attendance requirements may vary by team. At this time, we are not accepting applications from candidates residing in the following states: Delaware, Kentucky, Mississippi, Montana, Nebraska, and North Dakota." That's not boilerplate; it's specific. We'll keep it in About the role. Now we need to format. We'll produce:

  About the role

  ... intro paragraph with company description, role description, hybrid work, office locations, remote workforce details, states not accepting applications.

  Then

  Responsibilities

  • ... each bullet.
  Then

  Requirements

  • ... minimum qualifications bullet list (education, years experience, Agile experience, UAT experience).
  Then

  Skills

  • ... strong technical analysis skills, ability to translate/document business needs, strong communication skills, proficiency in writing/user stories/epics/acceptance criteria using Jira or similar, working knowledge of SQL or BI tools, strong organizational skills and attention to detail, ability to manage multiple priorities.
  Then

  Benefits

  • medical, dental and vision insurance
  • other pre-tax contribution plans
  • Employee Stock Ownership Plan (ESOP)
  • generous retirement package
  Then

  Pay

  The salary range for this role is $106,000 - $123,000 with a target compensation of $106,000 - $115,000 based on experience and qualifications.

  Then

  Schedule

  This is a hybrid work opportunity.

  We need to ensure we didn't miss any substantive info: The intro also mentions "You'll play a key role in delivering innovative solutions that help drive business success." etc. That's covered