Sr Business Analyst - Finance (Hybrid)
for section headings (e.g. 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 (the page already shows it) and 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.
We need to decide which sections to include. The posting includes:
- Who We Are (company description) – could be "About the role"? Actually "Who We Are" is about company, not role. But we can treat as "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map:
- About the role: maybe combine "Who We Are" and "Primary Purpose"? But "Who We Are" is about company; still could be considered about the role context. We'll include an
About the role
with prose summarizing who they are and primary purpose.
- Responsibilities: list of duties (Primary Duties). Could also include Primary Purpose tasks. We'll create a list.
- Requirements: Minimum Qualifications (maybe also Preferred Qualifications). Could separate into Requirements (minimum) and Preferred Qualifications (maybe as Skills?). But instruction says prefer few substantive sections over many thin ones. Could combine Minimum and Preferred into one "Qualifications" section with sublists? But they said use headings like Qualifications. Could have Qualifications
with two sub-sections? Not allowed to create extra headings beyond those listed? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have those headings. We can decide to have Requirements (minimum) and Qualifications (preferred) maybe both. But that's two sections; still okay. However we should avoid thin sections. Minimum Qualifications is fairly detailed; Preferred Qualifications also detailed. Could combine them into one Qualifications section with two lists: Minimum and Preferred. But the instruction says use headings like Qualifications (singular). Could still have one Qualifications section containing both minimum and preferred, maybe using
to differentiate. But we need to preserve all substantive information; we can include both as separate
inside the section.
- Benefits: there is a Benefits section with details. So include Benefits
with .
- Pay: there is salary range and bonus. So include Pay
with prose (maybe also bonus). Should not include placeholder like "varies". It says actual numbers: $80,000.00/Yr. – $110,000.00/Yr. Annual Bonus for eligible positions: 15%. That's specific, so include.
- Schedule: not mentioned explicitly except "May require working extended hours and/or shift work". That's schedule info but not explicit schedule like "Full-time". Could we create Schedule section? The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does mention extended hours/shift work, which is schedule-related. So we could include Schedule section with that info. However we need to see if it's substantive enough. It says "May require working extended hours and/or shift work to support business operations." That's schedule info. So we can include Schedule.
- Skills: not explicitly listed; we could infer from qualifications but better not to invent. So omit Skills.
- About the role: we need to include company description and primary purpose. We'll put that in About the role.
Now we need to remove boilerplate: "Who We Are" section includes some fluff but we keep substantive info: Exelon leading energy transformation, Fortune 200, 20k colleagues, serving 10.7M customers, list of utilities, commitment, employee experience tenets, etc. That's substantive.
Primary Purpose: "Perform detailed analysis and prepare comprehensive reports to support business operations..." etc. We'll incorporate into About the role or Responsibilities? Probably About the role includes primary purpose. But we also have Responsibilities separate.
We need to avoid duplication: The Primary Duties list repeats many of the Primary Purpose tasks. We'll keep Responsibilities as the list of duties (Primary Duties). The Primary Purpose can be short prose in About the role.
Now we need to format.
We'll output something like:
About the role
Exelon is a Fortune 200 energy company with 20,000 colleagues serving over 10.7 million customers across six utilities (Atlantic City Electric, Baltimore Gas and Electric, Commonwealth Edison, Delmarva Power & Light, PECO, and Potomac Electric Power Company). The company is committed to a cleaner, brighter future and fosters an inclusive, innovative, safe, and community‑focused workplace grounded in purposeful careers, growth opportunities, community impact, and support to thrive. The role involves performing detailed analysis, preparing comprehensive reports, conducting complex modeling, forecasting, variance analysis, business case development, and monitoring operational performance to support business operations.
Responsibilities
- Develop and conduct short‑term and long‑range business planning.
- Conduct complex modeling, forecasting, trending, variance analysis, business case development, and other financial and operational analysis (e.g., operational effectiveness, budget, resource, workload, workforce and capacity utilization, competitor, etc.).
- Provide statistical information to ensure effective utilization of personnel, equipment and/or materials.
- Monitor and coordinate activities to manage operational performance (e.g., safety, reliability, service level, productivity, etc.) and make recommendations for improvement.
- Track, maintain, analyze and provide current information on the operation's business scorecard or key performance indicators (KPIs).
- Perform analysis of the operation's cost elements to ensure effective and efficient operations.
- Prepare and analyze comprehensive and detailed reports.
- Develop, organize and present detailed performance reports for internal and external use.
- May develop, implement, evaluate or lead projects or initiatives (e.g., business plan or process improvement initiatives).
- Provide broad analytical and operational support to the business unit.
Qualifications
Minimum Qualifications
- Bachelor's degree in Business or Engineering AND 4‑7 years of related business experience, or in lieu of degree, 6‑9 years of relevant business experience.
- Comprehensive understanding of applicable standards, methods, processes and practices, business fundamentals, and performance metrics in the specific functional area supported (e.g., asset management, electric or gas operations, customer service, transmission and substation, distribution system operations, regulatory and external affairs, transmission operations and planning).
- Advanced proficiency in standard software applications (Microsoft Word, Excel, Access, PowerPoint, Project), specialized business technologies and applications (workforce management, project management, PassPort, Brio, CIS, EPS, Business Objects, SAP planning, business modeling, forecasting, voice response unit, automatic call distributors, work management, outage management) to retrieve and analyze data.
- Ability to provide in‑depth analysis and apply managerial accounting concepts, customer intelligence gathering, forecasting, staff planning, scheduling, analytical and statistical problem solving, financial, accounting, business and budget analysis.
- Demonstrated strong analytical skills for project evaluation including analysis of complex projects with economic, financial, risk and decision analysis; proficient in business case development and ability to effectively present business cases to business unit leadership.
- Customer‑driven with good oral and written communication skills and strong analytical, problem‑solving and project‑management skills.
- Comprehensive knowledge of performance analysis practices (trending, root cause and gap analysis), benchmarking and audit compliance.
- Ability to analyze organizational data and complex problems, interpret and recommend alternative courses of action, and implement intervention strategies to attain performance targets.
Preferred Qualifications
- MBA or relevant advanced degree.
- Experience with Financial Reporting including monthly forecasting, monthly financial book close (accruals and correcting journal entries), long‑range budgeting.
- Proficiency in Microsoft Office suite (proficiency in MS Excel is required).
Benefits
- Annual salary range: $80,000.00/Yr. – $110,000.00/Yr.
- Annual bonus for eligible positions: 15%.
- 401(k) match and annual company contribution.
- Medical, dental and vision insurance.
- Life and disability insurance.
- Generous paid time off options (vacation, sick time, floating and fixed holidays, maternity leave, bonding/primary caregiver leave or parental leave).
- Employee Assistance Program and resources for mental and emotional support.
- Wellbeing programs such as tuition reimbursement, adoption and surrogacy assistance, fitness reimbursement.
- Referral bonus program.
- And much more (programs may vary based on length of service, job grade, classification or represented status).
Pay
Annual salary will vary based on a candidate’s skills, qualifications, experience, and other factors: $80,000.00/Yr. – $110,000.00/Yr. Annual Bonus for eligible positions: 15%.
Schedule
May require working extended hours and/or shift work to support business operations, including coverage during storms or other energy delivery emergencies.
We need to ensure we didn't repeat info unnecessarily. The Pay section duplicates salary range already in Benefits list; but we could keep both? The instruction says preserve ALL substantive information; not to invent or summarize away detail. If we put salary range in Benefits list, we still need to include it somewhere; we could keep it only in Benefits and not repeat in Pay. But Pay section is supposed to be for pay details; we could keep Pay section with the salary and bonus, and Benefits section could exclude salary range to avoid duplication. However the Benefits section originally includes salary range as first bullet; we could keep it there and not have a separate Pay section. But the instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The posting does have specific pay info, so we should have a Pay section. It's okay to have some overlap as long as we preserve all info; duplication is not prohibited but might be considered redundant. However better to avoid duplication: we can put salary range
for prose. 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. 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. We need to decide which sections to include. The posting includes: - Who We Are (company description) – could be "About the role"? Actually "Who We Are" is about company, not role. But we can treat as "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map: - About the role: maybe combine "Who We Are" and "Primary Purpose"? But "Who We Are" is about company; still could be considered about the role context. We'll include an
About the role
with prose summarizing who they are and primary purpose. - Responsibilities: list of duties (Primary Duties). Could also include Primary Purpose tasks. We'll create a- list.
- Requirements: Minimum Qualifications (maybe also Preferred Qualifications). Could separate into Requirements (minimum) and Preferred Qualifications (maybe as Skills?). But instruction says prefer few substantive sections over many thin ones. Could combine Minimum and Preferred into one "Qualifications" section with sublists? But they said use headings like Qualifications. Could have
- Develop and conduct short‑term and long‑range business planning.
- Conduct complex modeling, forecasting, trending, variance analysis, business case development, and other financial and operational analysis (e.g., operational effectiveness, budget, resource, workload, workforce and capacity utilization, competitor, etc.).
- Provide statistical information to ensure effective utilization of personnel, equipment and/or materials.
- Monitor and coordinate activities to manage operational performance (e.g., safety, reliability, service level, productivity, etc.) and make recommendations for improvement.
- Track, maintain, analyze and provide current information on the operation's business scorecard or key performance indicators (KPIs).
- Perform analysis of the operation's cost elements to ensure effective and efficient operations.
- Prepare and analyze comprehensive and detailed reports.
- Develop, organize and present detailed performance reports for internal and external use.
- May develop, implement, evaluate or lead projects or initiatives (e.g., business plan or process improvement initiatives).
- Provide broad analytical and operational support to the business unit.
- Bachelor's degree in Business or Engineering AND 4‑7 years of related business experience, or in lieu of degree, 6‑9 years of relevant business experience.
- Comprehensive understanding of applicable standards, methods, processes and practices, business fundamentals, and performance metrics in the specific functional area supported (e.g., asset management, electric or gas operations, customer service, transmission and substation, distribution system operations, regulatory and external affairs, transmission operations and planning).
- Advanced proficiency in standard software applications (Microsoft Word, Excel, Access, PowerPoint, Project), specialized business technologies and applications (workforce management, project management, PassPort, Brio, CIS, EPS, Business Objects, SAP planning, business modeling, forecasting, voice response unit, automatic call distributors, work management, outage management) to retrieve and analyze data.
- Ability to provide in‑depth analysis and apply managerial accounting concepts, customer intelligence gathering, forecasting, staff planning, scheduling, analytical and statistical problem solving, financial, accounting, business and budget analysis.
- Demonstrated strong analytical skills for project evaluation including analysis of complex projects with economic, financial, risk and decision analysis; proficient in business case development and ability to effectively present business cases to business unit leadership.
- Customer‑driven with good oral and written communication skills and strong analytical, problem‑solving and project‑management skills.
- Comprehensive knowledge of performance analysis practices (trending, root cause and gap analysis), benchmarking and audit compliance.
- Ability to analyze organizational data and complex problems, interpret and recommend alternative courses of action, and implement intervention strategies to attain performance targets.
- MBA or relevant advanced degree.
- Experience with Financial Reporting including monthly forecasting, monthly financial book close (accruals and correcting journal entries), long‑range budgeting.
- Proficiency in Microsoft Office suite (proficiency in MS Excel is required).
- Annual salary range: $80,000.00/Yr. – $110,000.00/Yr.
- Annual bonus for eligible positions: 15%.
- 401(k) match and annual company contribution.
- Medical, dental and vision insurance.
- Life and disability insurance.
- Generous paid time off options (vacation, sick time, floating and fixed holidays, maternity leave, bonding/primary caregiver leave or parental leave).
- Employee Assistance Program and resources for mental and emotional support.
- Wellbeing programs such as tuition reimbursement, adoption and surrogacy assistance, fitness reimbursement.
- Referral bonus program.
- And much more (programs may vary based on length of service, job grade, classification or represented status).
Qualifications
with two sub-sections? Not allowed to create extra headings beyond those listed? It says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have those headings. We can decide to have Requirements (minimum) and Qualifications (preferred) maybe both. But that's two sections; still okay. However we should avoid thin sections. Minimum Qualifications is fairly detailed; Preferred Qualifications also detailed. Could combine them into one Qualifications section with two lists: Minimum and Preferred. But the instruction says use headings like Qualifications (singular). Could still have one Qualifications section containing both minimum and preferred, maybe using
to differentiate. But we need to preserve all substantive information; we can include both as separate
- inside the section.
- Benefits: there is a Benefits section with details. So include
Benefits
with- .
- Pay: there is salary range and bonus. So include
Pay
with prose (maybe also bonus). Should not include placeholder like "varies". It says actual numbers: $80,000.00/Yr. – $110,000.00/Yr. Annual Bonus for eligible positions: 15%. That's specific, so include. - Schedule: not mentioned explicitly except "May require working extended hours and/or shift work". That's schedule info but not explicit schedule like "Full-time". Could we create Schedule section? The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does mention extended hours/shift work, which is schedule-related. So we could include Schedule section with that info. However we need to see if it's substantive enough. It says "May require working extended hours and/or shift work to support business operations." That's schedule info. So we can include Schedule. - Skills: not explicitly listed; we could infer from qualifications but better not to invent. So omit Skills. - About the role: we need to include company description and primary purpose. We'll put that in About the role. Now we need to remove boilerplate: "Who We Are" section includes some fluff but we keep substantive info: Exelon leading energy transformation, Fortune 200, 20k colleagues, serving 10.7M customers, list of utilities, commitment, employee experience tenets, etc. That's substantive. Primary Purpose: "Perform detailed analysis and prepare comprehensive reports to support business operations..." etc. We'll incorporate into About the role or Responsibilities? Probably About the role includes primary purpose. But we also have Responsibilities separate. We need to avoid duplication: The Primary Duties list repeats many of the Primary Purpose tasks. We'll keep Responsibilities as the list of duties (Primary Duties). The Primary Purpose can be short prose in About the role. Now we need to format. We'll output something like:About the role
Exelon is a Fortune 200 energy company with 20,000 colleagues serving over 10.7 million customers across six utilities (Atlantic City Electric, Baltimore Gas and Electric, Commonwealth Edison, Delmarva Power & Light, PECO, and Potomac Electric Power Company). The company is committed to a cleaner, brighter future and fosters an inclusive, innovative, safe, and community‑focused workplace grounded in purposeful careers, growth opportunities, community impact, and support to thrive. The role involves performing detailed analysis, preparing comprehensive reports, conducting complex modeling, forecasting, variance analysis, business case development, and monitoring operational performance to support business operations.
Responsibilities
Qualifications
Minimum Qualifications
Preferred Qualifications
Benefits
Pay
Annual salary will vary based on a candidate’s skills, qualifications, experience, and other factors: $80,000.00/Yr. – $110,000.00/Yr. Annual Bonus for eligible positions: 15%.
Schedule
May require working extended hours and/or shift work to support business operations, including coverage during storms or other energy delivery emergencies.
We need to ensure we didn't repeat info unnecessarily. The Pay section duplicates salary range already in Benefits list; but we could keep both? The instruction says preserve ALL substantive information; not to invent or summarize away detail. If we put salary range in Benefits list, we still need to include it somewhere; we could keep it only in Benefits and not repeat in Pay. But Pay section is supposed to be for pay details; we could keep Pay section with the salary and bonus, and Benefits section could exclude salary range to avoid duplication. However the Benefits section originally includes salary range as first bullet; we could keep it there and not have a separate Pay section. But the instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The posting does have specific pay info, so we should have a Pay section. It's okay to have some overlap as long as we preserve all info; duplication is not prohibited but might be considered redundant. However better to avoid duplication: we can put salary range