Consulting Manager - Senior Business Analyst, Energy & Utilities Consulting

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - About Cognizant Consulting (intro) maybe part of About the role? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include only those with content. We have content: About the role: The paragraph after "About The Role" includes description: "As a Consulting Manager - Senior Business Analyst, Energy & Utilities, you will make an impact by leading business analysis and transformation workstreams that improve utility operations, decision-making, and technology delivery. You will be a valued member of Cognizant Consulting's Energy & Utilities team and work collaboratively with utility business leaders, product owners, field operations, data and technology teams, vendors, delivery partners, and clients. The core requirements are strong business analysis capability and Energy & Utilities industry experience. Experience with Palantir Foundry and AIP or utility vegetation management will help you stand out. Candidates may bring strength in either specialized area and are not required to have both." Also "In This Role, You Will" bullet list. We can treat that as Responsibilities? Actually "In This Role, You Will" enumerates duties. So we can put that under Responsibilities. Requirements: "What you must have to be considered" list: 8-15 years experience, strong Energy & Utilities experience, proven experience leading end-to-end business analysis, experience leading client-facing workstreams and supporting Agile/Waterfall/hybrid delivery, strong analytical etc, bachelor's degree, ability to work onsite in Houston 3-4 days per week. Qualifications: maybe overlapping with Requirements? The instruction distinguishes Requirements and Qualifications. Usually Requirements are mandatory, Qualifications are preferred. Here "These will help you succeed" list is qualifications/preferred: Palantir Foundry and AIP experience, utility vegetation management experience, familiarity with various systems, experience connecting vegetation management data to outage prevention, experience delivering complex utility transformation programs, mentoring consultants, or holding relevant certifications. Skills: maybe we can extract skills like analytical, problem-solving, communication, facilitation, presentation, team leadership. Benefits: listed under "Compensation" then "Benefits" bullet list. Pay: The posting mentions "Compensation This position is eligible for Cognizant's discretionary annual incentive program, based on performance and subject to the terms of Cognizant's applicable plans." That's about pay/incentive. So we can include Pay section with that sentence. Schedule: "Work model ... hybrid position requiring 3-4 days a week in a client or Cognizant office in Houston, Texas." Also ability to work onsite in Houston 3-4 days per week. So schedule section. We must not include filler like "commensurate with experience". Not present. We must not include duplicated lines. We must not include application instructions, closing date, etc. The posting includes "Post closing date Applications will be accepted until 28th Oct, 2026". That's application instruction/boilerplate; we should drop it. Also "We're excited to meet people..." etc is fluff but maybe we keep as part of About the role? It's not boilerplate; it's encouraging to apply. Might be considered boilerplate? It's not EEO etc. It's okay to keep? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. That paragraph is not exactly those; it's motivational. Could keep but maybe it's fluff. Safer to keep as part of About the role? It doesn't add substantive info about role. Might be considered filler. I'd drop it. Also "About Cognizant Consulting" paragraph is introductory about company; could be part of About the role? Might be considered company overview; we could include under About the role or maybe not needed. The instruction: About the role heading; we can include description of role and maybe company overview. It's substantive? It's about Cognizant Consulting; not directly role but could be considered context. Might keep. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from the posting that are not boilerplate. Thus we need to include: - About Cognizant Consulting paragraph (global community 5,000+ experts, etc). That's substantive about company. - About The Role paragraph (first paragraph after About The Role) describing impact. - In This Role, You Will bullet list (duties). - Work model paragraph (hybrid, 3-4 days a week, wellbeing programs). This could go under Schedule. - What you must have to be considered (requirements) list. - These will help you succeed (preferred qualifications) list. - Benefits list. - Compensation paragraph about discretionary annual incentive. We need to map to headings. Let's decide:

About the role

: include About Cognizant Consulting paragraph + About The Role paragraph (first paragraph). Possibly also the "In This Role, You Will" could be under Responsibilities.

Responsibilities

: list of duties from "In This Role, You Will". Use

• .

  Requirements

  : mandatory requirements list from "What you must have to be considered". Use
  • .

    Qualifications

    : preferred qualifications list from "These will help you succeed". Use
    • .

      Skills

      : maybe we can extract skills from requirements: Strong analytical, problem-solving, communication, facilitation, presentation, and team leadership skills. Also maybe "strong business analysis capability". Could list them. But we already have them in Requirements; but we could still create Skills section if we want. However instruction: Prefer a few substantive sections over many thin ones. Might combine skills into Requirements or Qualifications. But we have separate headings allowed; we could include Skills if we have content. The skills are already mentioned in Requirements; we could still create a Skills section but that would duplicate content. Better to not duplicate; we can omit Skills section if we think it's thin. However we need to include all substantive info; if we omit Skills heading, we still have the skills mentioned in Requirements (they are there). That's fine.

      Benefits

      : list of benefits.

      Pay

      : paragraph about discretionary annual incentive.

      Schedule

      : work model hybrid 3-4 days a week, wellbeing programs, ability to work onsite. We must not include heading with empty content. Now we need to ensure we don't include any boilerplate like "Post closing date". Also remove duplicated lines. Let's extract exact text. About Cognizant Consulting: "Cognizant Consulting is more than Cognizant's consulting practice. We are a global community of 5,000+ experts dedicated to helping clients reimagine their business. Blending our deep industry and technology advisory capability, we create innovative business solutions for Fortune 500 clients. And now, we are looking for our next colleague who will join us in shaping the future of business. Could it be you?" We can keep that. About The Role paragraph: "As a Consulting Manager - Senior Business Analyst, Energy & Utilities, you will make an impact by leading business analysis and transformation workstreams that improve utility operations, decision-making, and technology delivery. You will be a valued member of Cognizant Consulting's Energy & Utilities team and work collaboratively with utility business leaders, product owners, field operations, data and technology teams, vendors, delivery partners, and clients. The core requirements are strong business analysis capability and Energy & Utilities industry experience. Experience with Palantir Foundry and AIP or utility vegetation management will help you stand out. Candidates may bring strength in either specialized area and are not required to have both." Now Responsibilities (In This Role, You Will): List: - Lead business analysis and transformation workstreams across electric, gas, water, renewable energy, transmission, distribution, customer, and field operations. - Elicit, analyze, validate, and document business and functional requirements, user stories, use cases, process flows, data and integration needs, reporting requirements, and acceptance criteria. - Connect utility business objectives to product, platform, data, analytics, and technology solutions, while supporting backlog refinement, testing, UAT, defect triage, release readiness, training, and adoption. - Manage client and stakeholder relationships, define KPIs and dashboards, lead cross-functional teams, and mentor analysts and consultants to deliver measurable business outcomes. We need to preserve all details. Now Requirements (What you must have to be considered): List: - 8-15 years of experience in utilities consulting, business analysis, product management, solution consulting, program delivery, or technology-enabled transformation. - Strong Energy & Utilities experience and knowledge of utility processes such as Meter-to-Cash, billing, customer operations, outage management, grid reliability, asset and work management, field operations, or customer analytics. - Proven experience leading end-to-end business analysis, including requirements elicitation, workshop facilitation, process analysis, functional documentation, user stories, acceptance criteria, and stakeholder validation. - Experience leading client-facing workstreams and supporting Agile, Waterfall, or hybrid delivery, including backlog management, testing, UAT, issue resolution, release planning, and business adoption. - Strong analytical, problem-solving, communication, facilitation, presentation, and team leadership skills; a bachelor's degree in Business, Engineering, Information Systems, Computer Science, Operations Management, Data Science, or a related discipline; and the ability to work onsite in Houston 3-4 days per week. Note: The last bullet includes skills and degree and onsite ability. We'll keep as one bullet. Now Qualifications (These will help you succeed): List: - Palantir Foundry and AIP experience involving ontologies, object/link/action types, data products, pipelines, data quality, governance, lineage, Foundry applications, AI-enabled workflows, agents, automation, or GenAI. - Utility vegetation management experience involving cycle trimming, hazard trees, pre-inspection, work planning, permitting, customer notification, contractor scheduling, quality assurance, work verification, closeout, or regulatory reporting. - Familiarity with CIS, CRM, EAM, work management, mobile workforce, contractor portals, GIS, OMS, DMS, ADMS, SCADA, AMI, outage and restoration data, or field service platforms. - Experience connecting vegetation management, data, or operational analytics to outage prevention, feeder reliability, circuit prioritization, asset risk, storm readiness, wildfire or hazard mitigation, field productivity, and executive reporting. - Experience delivering complex utility transformation programs for a large utility or Fortune 500 organization, mentoring consultants, or holding relevant PMP, Agile/Scrum, ITIL, GIS, cloud, or utility vegetation management credentials. Now Benefits: List: - Medical, dental, vision, and life insurance - 401(k) plan and contributions - Employee stock purchase plan and employee assistance program - 10 paid holidays plus paid time off, paid parental leave, and fertility assistance - Learning and development certifications and programs Now Pay: Paragraph: "This position is eligible for Cognizant's discretionary annual incentive program, based on performance and subject to the terms of Cognizant's applicable plans." Now Schedule: Paragraph: "We believe hybrid work is the way forward as we strive to provide flexibility wherever possible. Based on this role's business requirements, this is a hybrid position requiring 3-4 days a week in a client or Cognizant