Senior Business Analyst - Power BI & Data Analytics

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Also remove application instructions. Must not include placeholder like "commensurate with experience". Must not create Pay/Schedule/Benefits sections unless posting actually states them. Benefits: posting says "Benefits For information and details on employment benefits offered with this position, please visit here." That's not specific benefits; it's a placeholder. So we should NOT include Benefits section because no specific benefits listed. Pay: posting gives Min Hourly Rate $55.00 Max Hourly Rate $60.00. That's pay info. So we can include a Pay section with that info. Schedule: posting gives Work Model: Hybrid, 3 days onsite and 2 days remote per week. That's schedule info. So we can include Schedule section. Also we have Job Description etc. We need sections: About the role (maybe Job Overview), Responsibilities, Requirements (maybe Must Have Skills/Attributes), Qualifications (Education, certifications), Skills (maybe combine desired skills). We need to decide headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We'll include About the role (Job Overview), Responsibilities, Requirements (Must Have Skills/Attributes), Qualifications (Education, certifications), Skills (Desired Skills, Experience, & Abilities maybe plus Required Skills?). But we need to avoid duplication. The posting has "Required Skills, Experience, & Abilities" and "Desired Skills, Experience, & Abilities". Could combine into Skills section. But we also have Requirements maybe as Must Have Skills/Attributes. However the instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We'll create:

About the role

with Job Overview paragraph.

Responsibilities

with

• list of responsibilities.

  Requirements

  with Must Have Skills/Attributes list.

  Qualifications

  with Required Minimum Education and Desired Certifications.

  Skills

  with Desired Skills, Experience, & Abilities list (maybe also include Required Skills? but we already put them in Requirements). Could also include Required Skills as part of Requirements; but we might duplicate. Let's put Required Skills in Requirements, Desired Skills in Skills.

  Pay

  with paragraph showing min/max hourly rate.

  Schedule

  with paragraph about hybrid model. We must not include Benefits section because no specific benefits. We must not include any boilerplate like EEO, etc. We must preserve all substantive info: ensure we include all details from sections we keep. Let's extract content. Job Overview paragraph: "This team enables trusted, enterprise-scale operational insights and automation by transforming fragmented data into actionable intelligence. As the reporting ecosystem is modernized, the team is leading a strategic migration from legacy business intelligence platforms to Microsoft Power BI and Microsoft Fabric to establish a governed and scalable foundation for enterprise analytics. The Senior Data Analyst / Business Analyst will be a key contributor to the Power BI and Fabric transformation, partnering with business stakeholders, data engineers, product owners, and leadership teams to analyze reporting needs, rationalize existing dashboard portfolios, design compelling visualizations, and drive adoption of modern analytics solutions. The role requires strong analytical skills, visualization expertise, and business acumen, with the ability to translate complex operational data into intuitive, actionable insights that support executive decision-making and operational excellence. Success includes becoming a trusted advisor to business and operational stakeholders, driving measurable progress in the Power BI and Fabric migration, delivering highly adopted dashboards that replace legacy reporting solutions, championing governance and consistency, and helping establish Power BI as the preferred enterprise reporting platform within ProCODE’s supported domains." We'll put that in

  . Responsibilities list: bullet points from "Responsibilities" section. Let's extract each bullet: - Partner with business and operational stakeholders to capture reporting requirements, define success metrics, and identify opportunities for analytics modernization. - Conduct discovery sessions, process reviews, and dashboard assessments to understand current-state reporting and future-state needs. - Translate business questions into analytical requirements, user stories, and reporting specifications while serving as the bridge between technical delivery teams and business partners. - Lead analysis activities supporting the migration of reporting assets from legacy platforms into Power BI and Microsoft Fabric. - Evaluate existing dashboards based on usage, relevance, business value, and migration complexity, and recommend consolidation, retirement, enhancement, or migration strategies. - Support migration planning by documenting requirements, dependencies, and stakeholder expectations. - Design intuitive, impactful, and executive-ready Power BI dashboards. - Establish visualization standards and best practices that improve usability, consistency, and adoption. - Develop KPI frameworks, scorecards, operational dashboards, and executive reporting solutions that effectively communicate trends, risks, opportunities, and operational performance. - Support reporting governance standards, dataset ownership models, and certification processes. - Help establish trusted reporting practices that improve data quality, consistency, and confidence in business decisions. - Promote adoption of standardized semantic models and certified datasets. - Partner with data engineering teams to ensure reporting solutions align with enterprise data governance standards. - Identify opportunities to improve reporting experiences through automation, standardization, and self-service analytics. - Monitor adoption and stakeholder feedback to improve reporting effectiveness. - Contribute to the evolution of operational insights, reporting strategy, and the analytics operating model. We'll put each as

• . Requirements (Must Have Skills/Attributes): list: - Banking/Financial - Data Visualization - Modeling - PowerBI - SQL - Stakeholders But also there is "Experience Desired:" which includes specific years. However that might be considered Requirements as well. The instruction: Use Requirements heading for any list of duties/requirements/benefits. The Must Have Skills/Attributes is a list. Also Experience Desired includes years of experience; could be considered Requirements as well. But we might put those under Requirements as well. However we already have a Skills section for desired skills. Let's decide: Requirements heading will contain the Must Have Skills/Attributes list (maybe also include the experience years? but those are more like qualifications). The Experience Desired includes years of experience in specific areas; could be considered Qualifications. But we have Qualifications heading for education and certifications. Might be better to put experience years under Qualifications as well. However the instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - Must Have Skills/Attributes (list of skill areas) - Experience Desired (years of experience in specific areas) - Required Minimum Education - Desired Certifications - Required Skills, Experience, & Abilities (list of required skills) - Desired Skills, Experience, & Abilities (list of desired skills) We could treat: Requirements: Must Have Skills/Attributes (list) Qualifications: Education + Certifications + Experience Desired (years) Skills: Required Skills, Experience, & Abilities + Desired Skills, Experience, & Abilities (maybe combine) But we need to avoid duplication. Let's think: The posting already separates Required Skills, Experience, & Abilities (which is a list of required skills) and Desired Skills, Experience, & Abilities (list of desired). The Must Have Skills/Attributes is a short list of skill areas (Banking/Financial, Data Visualization, Modeling, PowerBI, SQL, Stakeholders). That seems like a subset of required skills. We could combine Must Have Skills/Attributes into Requirements as a brief list, and then put the longer Required Skills list under Skills? But the instruction says use Requirements heading for any list of duties/requirements/benefits. So we could put all requirement-like content under Requirements: Must Have Skills/Attributes, Experience Desired (years), Required Skills, Experience, & Abilities. That might be a long list but okay. Then Qualifications could be Education and Certifications. Skills could be Desired Skills, Experience, & Abilities. But we need to avoid filler like "commensurate with experience". Not present. Let's extract each piece. Experience Desired: "Power BI dashboard development and enterprise reporting experience (3+ yrs); Business analysis, requirements gathering, and stakeholder engagement experience (5+ yrs); SQL, data analysis, KPI development, and data visualization experience (5+ yrs)". We'll turn into list items. Required Skills, Experience, & Abilities list: - 5+ years of experience in business analysis, data analysis, business intelligence, or analytics consulting roles. - 3+ years of hands-on experience developing dashboards and reports in Microsoft Power BI. - Experience with Microsoft Fabric, Lakehouse architecture, Semantic Models, or modern cloud analytics platforms - Strong understanding of data visualization principles and user-centered dashboard design. - Experience gathering business requirements and translating them into reporting solutions. - Advanced proficiency with SQL and data analysis techniques. - Strong experience defining KPIs, metrics, scorecards, and operational reporting frameworks. - Excellent communication and stakeholder management skills with the ability to engage technical and non-technical audiences. - Ability to manage multiple initiatives in a fast-paced, evolving environment. - Analytical thinking, business process analysis, executive communication, and storytelling with data. - Dashboard and UX design, stakeholder influence, requirements elicitation, problem-solving, data governance awareness, and a continuous improvement mindset. Desired Skills, Experience, & Abilities list: - Experience supporting enterprise-scale reporting migrations. - Knowledge of data governance, metadata management, lineage, and reporting certification practices. - Familiarity with Agile delivery methodologies and product-driven development. - Experience working with operational, service management, program management, or enterprise reporting data. Now Qualifications: Required Minimum Education: Bachelor’s Degree. Also "Required Education Bachelor’s degree in Business Analytics, Information Systems, Data Analytics, Computer Science, Statistics, or a related field." Desired Certifications: Microsoft Power BI and/or Microsoft Fabric certifications. We'll put education and certifications under Qualifications. Now About the role: Job Overview paragraph. Now Responsibilities: as extracted. Now Requirements: combine Must Have Skills/Attributes list, Experience Desired list, Required Skills, Experience, & Abilities list. Might be long but okay. But we need to avoid duplication: Must Have Skills/Attributes includes Banking/Financial, Data Visualization, Modeling, PowerBI, SQL, Stakeholders. Those are also covered in Required Skills list (Power BI, SQL, data visualization, stakeholder management). It's okay to have some overlap but we should preserve all substantive info; duplication is not prohibited but we should avoid unnecessary repetition. However we could keep Must Have as a brief list and then Required Skills list includes more detail; duplication may be okay but we could omit Must Have to avoid redundancy. However the instruction says preserve ALL substantive information; not invent or summarize away detail. If we omit Must Have, we lose that specific list (though it's covered partially). But the Must Have list is a subset; if we include Required Skills list, we still have the substance (PowerBI, SQL, etc). However Banking/Financial, Modeling, Stakeholders are also covered? Banking/Financial maybe not explicitly in Required Skills list (though stakeholder management is there). Modeling maybe not explicit. So we might lose some nuance. Safer to include Must Have list as part of Requirements. Thus Requirements will have three sub-lists: Must Have Skills/Attributes, Experience Desired, Required Skills, Experience, & Abilities. We'll format each as
  • under the Requirements heading, maybe with a preceding

    introducing each subcategory? But we can just have multiple

    sections; each list is fine. Now Schedule: Work Model: Hybrid Work Model Details: 3 days onsite and 2 days remote per week. Shift: Standard Working Hours. We'll put that in a <