Jobs · Sales

Senior PowerBI Consultant

Datavail · United States · 1 mo ago
RemoteRemoteSalesFull-time
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 that have real specific content. The posting includes many details: responsibilities, requirements, qualifications, skills, etc. No explicit Benefits, Pay, Schedule mentioned. So we should not include those sections. We need to preserve all substantive info, but we can group similar items. Use
  • for any list of duties/requirements/benefits. Use

    for prose. We must not repeat job title as heading. No Job ID etc. We need to extract sections: About the role (maybe a brief description), Responsibilities, Requirements (maybe education/experience), Qualifications (maybe certifications), Skills (technical). The posting includes many bullet-like lists. We need to decide structure: maybe sections: About the role (short paragraph summarizing role), Responsibilities (list), Requirements (education + experience), Qualifications (certifications), Skills (technical competencies). Ensure we don't create sections with filler. Let's parse content. Job Description text includes: "5+ years of hands-on experience developing enterprise Power BI solutions 3+ years working with Power BI Service, Semantic Models, and enterprise deployment practices Experience building reports using PBIP (Power BI Project) format and source-controlled development methodologies Experience developing complex DAX measures, KPIs, calculated tables, and advanced calculations Experience working with certified/shared semantic models using Live Connection and DirectQuery approaches Experience migrating and modernizing legacy BI platforms (SSRS, Cognos, Business Objects, Tableau, or legacy Power BI reports) Experience working in Agile delivery teams and collaborating with Data Architects, Data Engineers, and Business Analysts. Experience with Git-based version control and deployment processes Experience supporting large-scale reporting programs from pilot through enterprise rollout" Then "Required Bachelor's degree in Computer Science, Information Systems, Data Analytics, Engineering, or related field 5+ years of Power BI development experience Strong understanding of Semantic Modeling concepts Advanced DAX development skills Experience with Power BI Service and Workspace administration Experience developing reports using PBIP / Power BI Projects Consuming Enterprise Semantic Models using Live Connections Strong SQL skills for validation and reconciliation activities Experience with Git repositories and source control workflows Microsoft Power BI Data Analyst Associate (PL-300) Experience with TMDL (Tabular Model Definition Language). Experience with XMLA endpoints and Tabular Editor Experience with SSRS/Paginated Reports (RDL) Experience with Fabric Semantic Models and Databricks Experience supporting Finance, ERP, or Enterprise Data Warehouse reporting solutions Experience working with Azure DevOps" Then a list of technologies: "Power BI Development Power BI Desktop Power BI Service PBIP (Power BI Projects) Power Query (M) Report Optimization Dashboard Design Drill-through Reporting Bookmarks Tooltips Dynamic Visualizations Semantic Modeling Semantic Models Certified Datasets Shared Datasets Live Connections Composite Models Star Schema Concepts Relationship Management Calculation Groups TMDL XMLA Endpoints DAX & Analytics Advanced DAX Measures Filter Context Row Context Time Intelligence KPI Design Calculation Validation Data Reconciliation Reporting & Modernization Legacy Report Conversion Report Parity Validation Financial Reporting Operational Reporting Report Standardization Self-Service Analytics DevOps & Collaboration Git Azure DevOps Source Control Release Management Agile/Scrum Stakeholder Management" Then responsibilities section: "This role will work closely with DataArchitects, Data Engineers, Business Analysts, and business stakeholders throughout the lifecycle of a large-scale analytics modernization initiative The developer will build report deliverables on top of certified semantic models, support measure development, perform report reconciliation activities, and help deliver reporting capabilities across multiple business domains Key Responsibilities Report Development Design and develop Power BI reports and dashboards using PBIP project format Build interactive visualizations, drill-through functionality, bookmarks, and navigation experiences Deliver reporting solutions aligned with business requirements and enterprise standards Recreate and modernize legacy reports while preserving business logic and formatting consistency Semantic Model Consumption Consume shared and certified semantic models using Live Connections Collaborate with semantic model architects to identify reporting requirements Assist in creation and maintenance of measures under senior technical guidance Validate model usability and performance for reporting workload DAX Development Develop and optimize complex DAX calculations and KPIs Create reusable calculations and reporting standards Troubleshoot DAX performance issues Ensure accurate implementation of business calculation logic Validation & Reconciliation Perform detailed reconciliation between legacy reports and new Power BI deliverables Validate measures, calculations, totals, subtotals, and KPIs Work with business users to resolve discrepancies Support UAT and business signoff activities Follow version control, branching, and deployment standards Document development processes and report design decisions Support release management activities Collaboration Work closely with architects, engineers, QA analysts, and business stakeholders Participate in sprint planning, design reviews, and project governance meetings Provide technical guidance for reporting best practices and standards Success Metrics Delivery of high-quality Power BI reports on schedule 100% reconciliation accuracy against legacy reporting systems Reduced report maintenance through reusable measures and standardized design Adherence to governance, source-control, and deployment standards Successful rollout of domain reporting packages from pilot through enterprise deployment" Then About Us and About The Team (company description). Probably we can include an "About the Company" section? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It didn't mention About Us. But we could include "About the Company" maybe not required. The instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., so we can use those headings; we could also add others if needed but better to stick to those. The About Us could be considered "About the role"? Not exactly. Might be better to omit About Us as not required. The instruction: "Prefer a few substantive sections over many thin ones." So we can combine company info into a brief paragraph under maybe "About the role" or separate "About the Company" but not in list. Safer to include a short paragraph under "About the role" describing role and maybe company? But we must not invent. We could include a short paragraph about the role from the description: "This role will work closely with DataArchitects, Data Engineers, Business Analysts, and business stakeholders throughout the lifecycle of a large-scale analytics modernization initiative..." That's already in responsibilities. So maybe we don't need separate About the role. We need to include sections only when posting has real specific content. So we can have:

    Responsibilities

    with ul list.

    Requirements

    with ul list (education + experience).

    Qualifications

    with ul list (certifications, specific experiences).

    Skills

    with ul list (technical competencies). We must not repeat job title. We need to preserve all substantive information. So we need to capture each bullet from the posting. Let's extract responsibilities bullets: - Design and develop Power BI reports and dashboards using PBIP project format - Build interactive visualizations, drill-through functionality, bookmarks, and navigation experiences - Deliver reporting solutions aligned with business requirements and enterprise standards - Recreate and modernize legacy reports while preserving business logic and formatting consistency - Consume shared and certified semantic models using Live Connections - Collaborate with semantic model architects to identify reporting requirements - Assist in creation and maintenance of measures under senior technical guidance - Validate model usability and performance for reporting workload - Develop and optimize complex DAX calculations and KPIs - Create reusable calculations and reporting standards - Troubleshoot DAX performance issues - Ensure accurate implementation of business calculation logic - Perform detailed reconciliation between legacy reports and new Power BI deliverables - Validate measures, calculations, totals, subtotals, and KPIs - Work with business users to resolve discrepancies - Support UAT and business signoff activities - Follow version control, branching, and deployment standards - Document development processes and report design decisions - Support release management activities - Work closely with architects, engineers, QA analysts, and business stakeholders - Participate in sprint planning, design reviews, and project governance meetings - Provide technical guidance for reporting best practices and standards Also earlier bullet: "This role will work closely with DataArchitects, Data Engineers, Business Analysts, and business stakeholders throughout the lifecycle of a large-scale analytics modernization initiative" and "The developer will build report deliverables on top of certified semantic models, support measure development, perform report reconciliation activities, and help deliver reporting capabilities across multiple business domains". Those could be part of responsibilities too. Success metrics maybe could be part of responsibilities or separate but we don't have a heading for success metrics; we could include under Responsibilities as additional bullets. Now Requirements: education + experience: - Bachelor's degree in Computer Science, Information Systems, Data Analytics, Engineering, or related field - 5+ years of Power BI development experience - Strong understanding of Semantic Modeling concepts - Advanced DAX development skills - Experience with Power BI Service and Workspace administration - Experience developing reports using PBIP / Power BI Projects - Consuming Enterprise Semantic Models using Live Connections - Strong SQL skills for validation and reconciliation activities - Experience with Git repositories and source control workflows Also earlier: "5+ years of hands-on experience developing enterprise Power BI solutions", "3+ years working with Power BI Service, Semantic Models, and enterprise deployment practices", etc. Those could be part of Requirements as well. Let's gather all experience bullets from first block: - 5+ years of hands-on experience developing enterprise Power BI solutions - 3+ years working with Power BI Service, Semantic Models, and enterprise deployment practices - Experience building reports using PBIP (Power BI Project) format and source-controlled development methodologies - Experience developing complex DAX measures, KPIs, calculated tables, and advanced calculations - Experience working with certified/shared semantic models using Live Connection and DirectQuery approaches - Experience migrating and modernizing legacy BI platforms (SSRS, Cognos, Business Objects, Tableau, or legacy Power BI reports) - Experience working in Agile delivery teams and collaborating with Data Architects, Data Engineers, and Business Analysts. Experience with Git-based version control and deployment processes - Experience supporting large-scale reporting programs from pilot through enterprise rollout These are similar to later requirements but we can combine. Qualifications: certifications and specific experiences: - Microsoft Power BI Data Analyst Associate (PL-300) - Experience with TMDL (Tabular Model Definition Language) - Experience with XMLA endpoints and Tabular Editor - Experience with SSRS/Paginated Reports (RDL) - Experience with Fabric Semantic Models and Databricks - Experience supporting Finance, ERP, or Enterprise Data Warehouse reporting solutions - Experience working with Azure DevOps Also maybe "Experience with certified/shared semantic models using Live Connection and DirectQuery approaches" already in requirements. Skills: list of technologies and concepts: - Power BI Desktop - Power BI Service - PBIP (Power BI Projects) - Power Query (M) - Report Optimization - Dashboard Design - Drill-through Reporting - Bookmarks - Tooltips - Dynamic Visualizations - Semantic Modeling - Semantic Models - Certified Datasets - Shared Datasets - Live Connections - Composite Models - Star Schema Concepts - Relationship Management - Calculation Groups - TMDL - XMLA Endpoints - DAX & Analytics - Advanced DAX Measures - Filter Context - Row Context - Time Intelligence - KPI Design - Calculation Validation - Data Reconciliation - Reporting & Modernization - Legacy Report Conversion - Report Parity Validation - Financial Reporting - Operational Reporting - Report Standardization - Self-Service Analytics - DevOps & Collaboration - Git - Azure DevOps - Source Control - Release Management - Agile/Scrum - Stakeholder Management

Similar jobs