Commercial Report Developer
for sections: About the role, Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit 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 posting actually states them. Prefer a few substantive sections over many thin ones.
We need to extract content: Overview (maybe not needed as heading). The posting includes "Overview", "Who We Are", "About The Role", "Responsibilities", "Qualifications", "What We Offer". Also includes "Our Commitment To Equal Opportunity And Veteran Inclusion" which is boilerplate EEO, should be removed.
We need to map sections: About the role (maybe combine Overview and Who We Are? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have headings: About the role, Responsibilities, Requirements (or Qualifications?), Skills, Benefits, Pay, Schedule. But we need to decide which sections to include based on content.
We have content for About the role: description under "About The Role". We have Responsibilities: list under "Responsibilities". We have Qualifications: includes Education, Experience, Skills/Competencies. Could split into Requirements (education/experience) and Skills (competencies). The instruction says we can have Requirements and Skills separate headings. We need to decide if we should split.
We have "What We Offer": includes compensation package details: Competitive Base salary, Discretionary bonus, Equity participation, Comprehensive health, dental, vision insurance, Flexible HSAs/FSAs, Generous paid time off, 401(k) with match, Employee wellness initiatives, mental health resources, EAP, Employee recognition programs, Commuter benefits or transportation stipends. This is benefits and pay. So we can have Benefits section (list of benefits) and Pay section (maybe base salary, bonus, equity). However the instruction says: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state compensation details, so we can include Pay and Benefits. But we need to avoid filler like "competitive pay" is vague but still specific? It says "Competitive Base salary" - that's still vague but it's stated. Should we include? The instruction says never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "Competitive Base salary" is somewhat vague but not exactly placeholder like "commensurate with experience". It's still a statement. I'd include Pay section with bullet points: Competitive Base salary, Discretionary bonus, Equity participation as approved by Board of Directors (4-year vesting schedule). Benefits section: Comprehensive health, dental, and vision insurance plans; Flexible Health Savings Accounts (HSAs) and/or Flexible Spending Accounts (FSAs); Generous paid time off (vacation, sick leave, holidays, and flexible time off that is available for Exempt employees); 401(k) retirement plan with company match; Employee wellness initiatives, mental health resources, and Employee Assistance Program (EAP); Employee recognition programs and awards; Commuter benefits or transportation stipends.
Schedule: Not mentioned. So we should not include Schedule heading.
Skills: We have Skills/Competencies list: Advanced proficiency in Microsoft Power BI..., Experience developing and managing Power BI Semantic Models..., Experience administering Power BI workspaces..., Experience integrating and analyzing data from Salesforce CRM..., Proficiency with PBIX files, Power Query, DAX, and SQL., Moderate to advanced proficiency in Salesforce.com report and dashboard development., Moderate to advanced proficiency in Microsoft Excel for reporting, data analysis, and process automation., Experience leveraging AI tools..., Strong analytical, problem-solving, and data interpretation skills., Ability to translate complex business requirements..., Experience collaborating with cross-functional stakeholders..., Experience with Python for data analysis... (preferred), Knowledge of business analysis methodologies... (preferred), Understanding of statistical concepts... (preferred), Experience with predictive analytics... (preferred). We could include these under Skills heading.
Requirements: Education and Experience. Could be under Requirements heading: Bachelor's degree in ... required; 4+ years of experience developing business intelligence..., 3+ years of experience developing and maintaining Microsoft Power BI reports...
We could also combine Requirements and Qualifications but instruction suggests separate headings possible. We'll do Requirements (education/experience) and Skills (competencies). Also we could have a separate "Qualifications" heading but they said we can use Requirements, Qualifications, Skills. Since we have both, we could use Requirements for education/experience, and Skills for competencies. Avoid duplication.
Now we need to strip boilerplate: Overview, Who We Are (maybe we can incorporate into About the role? But About the role heading expects description of role. The "Who We Are" is company description; could be considered part of About the role? But we might omit it as not required. The instruction: include a section ONLY when posting has real, specific content for it. The "Who We Are" is company overview; not required heading. We could omit it or incorporate into About the role? Probably better to omit as not needed.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the details from About The Role paragraph, Responsibilities list, Qualifications (education/experience), Skills list, What We Offer (compensation and benefits). We must not repeat job title as heading. No Job ID.
We need to output only HTML fragment, no /, no markdown fences.
Thus produce something like:
About the role
... (the paragraph from About The Role)
Responsibilities
- ...
...
Requirements
- Bachelor's degree in Business Analytics, Information Systems, Computer Science, Data Analytics, Finance, Statistics, Mathematics, or a related field required.
- 4+ years of experience developing business intelligence, reporting, and analytics solutions in a corporate environment.
- 3+ years of experience developing and maintaining Microsoft Power BI reports, dashboards, and data models.
Skills
- Advanced proficiency in Microsoft Power BI report development, maintenance, and dashboard design utilizing UI/UX best practices.
- Experience developing and managing Power BI Semantic Models within Microsoft Fabric.
- Experience administering Power BI workspaces, user access, and role-level security.
- Experience integrating and analyzing data from Salesforce CRM (SFDC), ERP systems, and Snowflake data platforms.
- Proficiency with PBIX files, Power Query, DAX, and SQL.
- Moderate to advanced proficiency in Salesforce.com report and dashboard development.
- Moderate to advanced proficiency in Microsoft Excel for reporting, data analysis, and process automation.
- Experience leveraging AI tools to improve business processes, reporting efficiency, and analytical capabilities.
- Strong analytical, problem-solving, and data interpretation skills.
- Ability to translate complex business requirements into meaningful reporting and visualization solutions.
- Experience collaborating with cross-functional stakeholders to develop reporting solutions that support business objectives.
- Experience with Python for data analysis, reporting automation, and business intelligence solutions (preferred).
- Knowledge of business analysis methodologies and requirements gathering (preferred).
- Understanding of statistical concepts and data analysis techniques (preferred).
- Experience with predictive analytics, trend analysis, or advanced reporting methodologies (preferred).
Benefits
- Comprehensive health, dental, and vision insurance plans
- Flexible Health Savings Accounts (HSAs) and/or Flexible Spending Accounts (FSAs)
- Generous paid time off (vacation, sick leave, holidays, and flexible time off that is available for Exempt employees)
- 401(k) retirement plan with company match
- Employee wellness initiatives, mental health resources, and Employee Assistance Program (EAP)
- Employee recognition programs and awards
- Commuter benefits or transportation stipends
Pay
- Competitive Base salary
- Discretionary bonus
- Equity participation as approved by Board of Directors (4-year vesting schedule)
We should not include Schedule.
Check for any duplicated lines: Ensure we didn't repeat any.
Check that we didn't include any boilerplate like "Our Commitment To Equal Opportunity And Veteran Inclusion". Good.
Check that we didn't include "Overview" or "Who We Are". Good.
Check that we preserved all substantive information: The About The Role paragraph: we need to include that exactly? Let's copy it:
"The Commercial Report Developer is responsible for designing, developing, maintaining, and optimizing reporting and analytics solutions that support commercial operations, sales effectiveness, customer engagement, and strategic decision-making. This role partners closely with Sales, Marketing, Finance, Customer Service, and Business Leaders to transform data into meaningful insights through intuitive dashboards, automated reporting solutions, and data visualization tools. The Commercial Report Developer leverages advanced expertise in Microsoft Power BI, Salesforce.com, Excel, and enterprise data platforms to deliver scalable reporting solutions that improve operational efficiency, data accessibility, and business performance. This individual serves as a trusted partner in identifying reporting needs, ensuring data integrity, and enabling data-driven decision making across the organization."
We need to preserve that exactly. We'll put inside .
Now Responsibilities list: we need to capture each bullet under "WHAT YOU'LL DO:" and the subsequent lines. Let's extract them:
- Develop, maintain, and enhance Power BI dashboards, reports, semantic models, and data visualizations that support commercial reporting initiatives.
- Collaborate with business stakeholders to gather requirements, understand reporting needs, and translate business objectives into effective analytics solutions.
- Design user-friendly dashboards and reporting experiences that promote adoption, accessibility, and actionable decision-making.
- Manage and maintain Power BI workspaces, security permissions, and role-level security to ensure appropriate access and governance.
- Integrate and model data from multiple enterprise systems, including Salesforce CRM, ERP platforms, Snowflake, and other business applications.
- Develop, optimize, and troubleshoot Power Query transformations, DAX measures, SQL queries, and data models to improve reporting performance and accuracy.
- Create and maintain Salesforce reports and dashboards that provide visibility into sales performance, pipeline management, customer engagement, and operational metrics.
- Utilize advanced Microsoft Excel capabilities, including data analysis, automation, and reporting tools, to support business reporting requirements.
- Partner with cross-functional teams to identify opportunities for process improvements, reporting automation, and enhanced business intelligence capabilities.
- Ensure the accuracy, consistency, and integrity of commercial reporting data through validation, testing, and quality assurance practices.
- Analyze business data and trends to provide insights and recommendations that support strategic planning and operational improvements.
- Leverage emerging technologies, including AI-powered tools, to streamline reporting processes, increase productivity, and improve analytical capabilities.
- Document reporting processes, data definitions, and technical specifications to support knowledge sharing and operational continuity.
- Provide training, guidance, and support to end users to maximize the effectiveness and adoption of reporting tools and dashboards.
- Stay current on industry trends, reporting technologies, and business intelligence best practices to continuously improve reporting capabilities.
-
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit 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 posting actually states them. Prefer a few substantive sections over many thin ones. We need to extract content: Overview (maybe not needed as heading). The posting includes "Overview", "Who We Are", "About The Role", "Responsibilities", "Qualifications", "What We Offer". Also includes "Our Commitment To Equal Opportunity And Veteran Inclusion" which is boilerplate EEO, should be removed. We need to map sections: About the role (maybe combine Overview and Who We Are? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have headings: About the role, Responsibilities, Requirements (or Qualifications?), Skills, Benefits, Pay, Schedule. But we need to decide which sections to include based on content.
We have content for About the role: description under "About The Role". We have Responsibilities: list under "Responsibilities". We have Qualifications: includes Education, Experience, Skills/Competencies. Could split into Requirements (education/experience) and Skills (competencies). The instruction says we can have Requirements and Skills separate headings. We need to decide if we should split.
We have "What We Offer": includes compensation package details: Competitive Base salary, Discretionary bonus, Equity participation, Comprehensive health, dental, vision insurance, Flexible HSAs/FSAs, Generous paid time off, 401(k) with match, Employee wellness initiatives, mental health resources, EAP, Employee recognition programs, Commuter benefits or transportation stipends. This is benefits and pay. So we can have Benefits section (list of benefits) and Pay section (maybe base salary, bonus, equity). However the instruction says: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state compensation details, so we can include Pay and Benefits. But we need to avoid filler like "competitive pay" is vague but still specific? It says "Competitive Base salary" - that's still vague but it's stated. Should we include? The instruction says never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "Competitive Base salary" is somewhat vague but not exactly placeholder like "commensurate with experience". It's still a statement. I'd include Pay section with bullet points: Competitive Base salary, Discretionary bonus, Equity participation as approved by Board of Directors (4-year vesting schedule). Benefits section: Comprehensive health, dental, and vision insurance plans; Flexible Health Savings Accounts (HSAs) and/or Flexible Spending Accounts (FSAs); Generous paid time off (vacation, sick leave, holidays, and flexible time off that is available for Exempt employees); 401(k) retirement plan with company match; Employee wellness initiatives, mental health resources, and Employee Assistance Program (EAP); Employee recognition programs and awards; Commuter benefits or transportation stipends.
Schedule: Not mentioned. So we should not include Schedule heading.
Skills: We have Skills/Competencies list: Advanced proficiency in Microsoft Power BI..., Experience developing and managing Power BI Semantic Models..., Experience administering Power BI workspaces..., Experience integrating and analyzing data from Salesforce CRM..., Proficiency with PBIX files, Power Query, DAX, and SQL., Moderate to advanced proficiency in Salesforce.com report and dashboard development., Moderate to advanced proficiency in Microsoft Excel for reporting, data analysis, and process automation., Experience leveraging AI tools..., Strong analytical, problem-solving, and data interpretation skills., Ability to translate complex business requirements..., Experience collaborating with cross-functional stakeholders..., Experience with Python for data analysis... (preferred), Knowledge of business analysis methodologies... (preferred), Understanding of statistical concepts... (preferred), Experience with predictive analytics... (preferred). We could include these under Skills heading.
Requirements: Education and Experience. Could be under Requirements heading: Bachelor's degree in ... required; 4+ years of experience developing business intelligence..., 3+ years of experience developing and maintaining Microsoft Power BI reports...
We could also combine Requirements and Qualifications but instruction suggests separate headings possible. We'll do Requirements (education/experience) and Skills (competencies). Also we could have a separate "Qualifications" heading but they said we can use Requirements, Qualifications, Skills. Since we have both, we could use Requirements for education/experience, and Skills for competencies. Avoid duplication.
Now we need to strip boilerplate: Overview, Who We Are (maybe we can incorporate into About the role? But About the role heading expects description of role. The "Who We Are" is company description; could be considered part of About the role? But we might omit it as not required. The instruction: include a section ONLY when posting has real, specific content for it. The "Who We Are" is company overview; not required heading. We could omit it or incorporate into About the role? Probably better to omit as not needed.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the details from About The Role paragraph, Responsibilities list, Qualifications (education/experience), Skills list, What We Offer (compensation and benefits). We must not repeat job title as heading. No Job ID.
We need to output only HTML fragment, no /, no markdown fences.
Thus produce something like:
About the role
... (the paragraph from About The Role)
Responsibilities
- ... ...
Requirements
- Bachelor's degree in Business Analytics, Information Systems, Computer Science, Data Analytics, Finance, Statistics, Mathematics, or a related field required.
- 4+ years of experience developing business intelligence, reporting, and analytics solutions in a corporate environment.
- 3+ years of experience developing and maintaining Microsoft Power BI reports, dashboards, and data models.
Skills
- Advanced proficiency in Microsoft Power BI report development, maintenance, and dashboard design utilizing UI/UX best practices.
- Experience developing and managing Power BI Semantic Models within Microsoft Fabric.
- Experience administering Power BI workspaces, user access, and role-level security.
- Experience integrating and analyzing data from Salesforce CRM (SFDC), ERP systems, and Snowflake data platforms.
- Proficiency with PBIX files, Power Query, DAX, and SQL.
- Moderate to advanced proficiency in Salesforce.com report and dashboard development.
- Moderate to advanced proficiency in Microsoft Excel for reporting, data analysis, and process automation.
- Experience leveraging AI tools to improve business processes, reporting efficiency, and analytical capabilities.
- Strong analytical, problem-solving, and data interpretation skills.
- Ability to translate complex business requirements into meaningful reporting and visualization solutions.
- Experience collaborating with cross-functional stakeholders to develop reporting solutions that support business objectives.
- Experience with Python for data analysis, reporting automation, and business intelligence solutions (preferred).
- Knowledge of business analysis methodologies and requirements gathering (preferred).
- Understanding of statistical concepts and data analysis techniques (preferred).
- Experience with predictive analytics, trend analysis, or advanced reporting methodologies (preferred).
Benefits
- Comprehensive health, dental, and vision insurance plans
- Flexible Health Savings Accounts (HSAs) and/or Flexible Spending Accounts (FSAs)
- Generous paid time off (vacation, sick leave, holidays, and flexible time off that is available for Exempt employees)
- 401(k) retirement plan with company match
- Employee wellness initiatives, mental health resources, and Employee Assistance Program (EAP)
- Employee recognition programs and awards
- Commuter benefits or transportation stipends
Pay
- Competitive Base salary
- Discretionary bonus
- Equity participation as approved by Board of Directors (4-year vesting schedule)
. Now Responsibilities list: we need to capture each bullet under "WHAT YOU'LL DO:" and the subsequent lines. Let's extract them: - Develop, maintain, and enhance Power BI dashboards, reports, semantic models, and data visualizations that support commercial reporting initiatives. - Collaborate with business stakeholders to gather requirements, understand reporting needs, and translate business objectives into effective analytics solutions. - Design user-friendly dashboards and reporting experiences that promote adoption, accessibility, and actionable decision-making. - Manage and maintain Power BI workspaces, security permissions, and role-level security to ensure appropriate access and governance. - Integrate and model data from multiple enterprise systems, including Salesforce CRM, ERP platforms, Snowflake, and other business applications. - Develop, optimize, and troubleshoot Power Query transformations, DAX measures, SQL queries, and data models to improve reporting performance and accuracy. - Create and maintain Salesforce reports and dashboards that provide visibility into sales performance, pipeline management, customer engagement, and operational metrics. - Utilize advanced Microsoft Excel capabilities, including data analysis, automation, and reporting tools, to support business reporting requirements. - Partner with cross-functional teams to identify opportunities for process improvements, reporting automation, and enhanced business intelligence capabilities. - Ensure the accuracy, consistency, and integrity of commercial reporting data through validation, testing, and quality assurance practices. - Analyze business data and trends to provide insights and recommendations that support strategic planning and operational improvements. - Leverage emerging technologies, including AI-powered tools, to streamline reporting processes, increase productivity, and improve analytical capabilities. - Document reporting processes, data definitions, and technical specifications to support knowledge sharing and operational continuity. - Provide training, guidance, and support to end users to maximize the effectiveness and adoption of reporting tools and dashboards. - Stay current on industry trends, reporting technologies, and business intelligence best practices to continuously improve reporting capabilities. -