Business Intelligence (B.I.) Specialist
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must include sections only when posting has real specific content. Benefits: they mention "We offer competitive pay, excellent benefits and the opportunity for professional growth". That's generic but includes benefits mention. Should we create Benefits section? It says "competitive pay, excellent benefits". Not specific details. The rule: 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. Here they state "competitive pay, excellent benefits". That's somewhat vague but still states benefits exist. Might be acceptable to include Benefits section with that sentence. However they also say "We offer competitive pay, excellent benefits and the opportunity for professional growth". That's a statement about benefits. Could include Benefits section with that sentence.
Pay: they mention competitive pay but no specifics. According to rule, we should not create Pay section unless posting actually states them. It states "competitive pay" but no numbers. Might be considered filler? The rule says avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "competitive pay" is vague but still a statement. Might be okay but safer to not create Pay section, as it's not specific. Benefits we could include because they said "excellent benefits". Still vague. Might be better to omit Benefits and Pay sections, as they are not specific. The instruction: "Prefer a few substantive sections over many thin ones." So we could omit Benefits and Pay.
Schedule: they mention hybrid on-site position located at headquarters in Oak Creek, WI. That's schedule info (hybrid). Could create Schedule section with that sentence. It's specific: hybrid on-site. So include Schedule.
We need to include location and reporting line maybe in About the role or a short p.
We must not include boilerplate like EEO etc. Remove that.
We need to preserve all substantive information.
Let's extract sections:
- About the role: maybe a brief summary: "We are seeking a highly skilled, detail-oriented, and collaborative Business Intelligence Specialist to join our Business Intelligence & Data Science team." Could be in About the role.
But we already have "What You Will Do" which is essentially responsibilities. Could treat that as Responsibilities section.
We have "How You Will Do It" which breaks down into subcategories: BI Intake, Requirements & Human-Centered Design; Data Readiness & Governance; Dashboard Design & Development; AI-Assisted & Agentic Workflow Enablement; Monitoring, Maintenance & Continuous Improvement. Those are duties/responsibilities. Could be under Responsibilities as subheadings? But rule: use
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So only those headings allowed? It says use for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we can use those headings, but not required to limit to those exactly; but likely they expect those headings. We should use those headings where appropriate.
Thus we could have:
About the role
with a paragraph summarizing.
Responsibilities
with a - list of duties (maybe combine the detailed bullet points). Could break into sub-items but still
- .
Requirements
with - for required qualifications.
Preferred Qualifications
maybe use Skills>?? Actually they have Preferred Knowledge etc. Could use Skills> or Preferred Qualifications>. The list includes Skills, Benefits, Pay, Schedule. They didn't list Preferred Qualifications but we could use Skills> for preferred? Might be better to use Skills> for both required and preferred? But we already have Requirements. Could use Skills> for preferred qualifications. Or we could use Qualifications> for required and Skills> for preferred. The instruction list includes Qualifications and Skills as possible headings. So we can use Qualifications> for required, Skills> for preferred.
Thus:
About the role
...
Responsibilities
- ... each duty as li.
We need to capture all duties from "What You Will Do" and "How You Will Do It". The "What You Will Do" is a paragraph summarizing role. The "How You Will Do It" enumerates categories with bullet-like sentences. We'll extract each sentence as li.
Let's list duties:
From "What You Will Do":
- designing, developing, validating, deploying, and maintaining business intelligence dashboards and reporting solutions that help stakeholders make better decisions.
- act as a bridge between business needs, governed data products, dashboard design, and technical implementation to ensure BI products are accurate, useful, usable, actionable, and aligned to measurable business outcomes.
- support the full BI dashboard lifecycle, including intake, requirements discovery, development, quality assurance, deployment, maintenance, and continuous improvement.
- actively leverage human-centered design methods and approved AI-assisted or agentic development tools to assist in the BI lifecycle, while ensuring human review, data protection, and governance compliance.
From "How You Will Do It" sections:
BI Intake, Requirements & Human-Centered Design:
- Partner with business stakeholders to define dashboard requests, business objectives, scope, intended decisions, expected outcomes, success measures, and stakeholder needs.
- Apply human-centered design methods, including stakeholder interviews, needfinding, task analysis, design alternatives, prototyping, evaluation, and iteration, to ensure BI products are useful, usable, and actionable.
- Translate business needs and user tasks into clear BI requirements, dashboard concepts, metrics, visualizations, and acceptance criteria.
Data Readiness & Governance:
- Identify required datasets, metric definitions, dimensional context, ownership, refresh requirements, data quality expectations, lineage needs, and access considerations.
- Coordinate with Data Owners, Data Stewards, Business Owners, and Data Engineering to clarify responsibilities, validate data readiness, and support governed data use.
- Route complex transformations to governed upstream data sources where appropriate and avoid embedding complex transformation logic in the dashboard layer.
Dashboard Design & Development:
- Design and develop Power BI dashboards, semantic models, and reporting solutions that are aligned to documented user tasks, business objectives, and measurable outcomes.
- Develop and validate SQL, DAX, Power Query, Python, R, or other analytics logic as needed to support accurate and maintainable BI deliverables.
- Ensure each visualization supports a documented user task, decision, or business action.
AI-Assisted & Agentic Workflow Enablement:
- Use approved AI-assisted and agentic development tools, such as Codex, Gemini CLI, Claude Code, or similar platforms, to support BI development, SQL/DAX/Python generation, documentation, testing, refactoring, workflow automation, and repeatable BI lifecycle activities.
- Apply human review, validation, and governance controls to all AI-assisted outputs, including code, metrics, documentation, QA evidence, and release materials.
- Develop reusable instructions, prompts, runbooks, or automation patterns that improve BI team productivity, consistency, and maintainability.
Monitoring, Maintenance & Continuous Improvement:
- Monitor dashboard adoption, usage telemetry, refresh performance, stakeholder feedback, and ongoing business value to support maintenance, enhancement, optimization, and decommissioning decisions.
- Identify opportunities to automate recurring BI lifecycle activities, improve documentation quality, reduce manual effort, and increase dashboard reliability.
- Communicate findings, risks, requirements, and recommendations clearly to technical and non-technical audiences while contributing to data literacy and team process improvement.
Now Required qualifications:
- Minimum of a Bachelor's Degree in Computer Science, Data Science, Mathematics, Finance, Business Administration, Engineering, or another related field from an accredited institution.
- 3–5 years of related professional experience in business intelligence, analytics, reporting, data analysis, or dashboard development.
- Proficiency with Power BI, including Power Query, DAX, data modeling, report/dashboard interface development, and dashboard publishing.
- Experience using SQL for data querying, validation, and analysis.
- Experience with data manipulation or analysis using Python and/or R.
- Demonstrated ability to responsibly use AI-assisted productivity, coding, or analytics tools in a professional environment.
- Ability to apply human-centered design practices, such as need finding, task analysis, prototyping, evaluation, or iteration, to business intelligence or analytics work.
- Strong analytical skills with the ability to interpret data, identify trends, validate assumptions, and communicate insights.
- Understanding of data governance concepts, including data quality, data ownership, data stewardship, metadata, lineage, access control, and refresh expectations.
- Ability to gather requirements from stakeholders and translate business needs into actionable BI deliverables.
- Strong written and verbal communication skills.
- Highly motivated and capable of working independently as well as collaboratively with business and technical teams.
- U.S. Citizen or U.S. Permanent Resident.
Preferred qualifications (list):
- Knowledge of data visualization best practices and dashboard usability principles.
- Experience applying structured human-centered design methods, user research, prototyping, or usability evaluation in dashboard, application, or analytics projects.
- Understanding of software engineering principles such as version control, testing, CI/CD, reusable design patterns, and controlled release processes.
- Familiarity with containerization tools such as Docker or Docker Compose.
- Experience working with data warehouses, governed datasets, semantic models, or enterprise data platforms.
- Experience documenting business requirements, data definitions, QA evidence, release criteria, or support models.
- Experience using AI-assisted or agentic development tools, such as Codex, Gemini CLI, Claude Code, or similar platforms, to improve analytics, BI engineering, documentation, testing, or process automation workflows.
- Experience developing reusable instructions, prompts, or automation patterns for AI-assisted software or analytics workflows.
- Knowledge of operations research, statistics, experimental design, or process improvement methods.
- Experience monitoring dashboard adoption, usage telemetry, or business value metrics.
Who We Are (company description) could be placed under About the role or maybe a separate section like "About the company". But headings list includes About the role only. Could incorporate into About the role paragraph.
Also location/hybrid: "This hybrid on-site position is located at our headquarters in Oak Creek, WI. You will report directly to the Senior Manager, Business Intelligence & Data Science." Could be in About the role or Schedule. Since Schedule heading is allowed, we can put schedule info there.
Thus sections:
About the role
We are seeking a highly skilled, detail-oriented, and collaborative Business Intelligence Specialist to join our Business Intelligence & Data Science team. In this role, you will be responsible for designing, developing, validating, deploying, and maintaining business intelligence dashboards and reporting solutions that help stakeholders make better decisions. You will act as a bridge between business needs, governed data products, dashboard design, and technical implementation to ensure BI products are accurate, useful, usable, actionable, and aligned to measurable business outcomes. This role supports the full BI dashboard lifecycle, including intake, requirements discovery, development, quality assurance, deployment, maintenance, and continuous improvement. The Business Intelligence Specialist is expected to actively leverage human-centered design methods and approved AI-assisted or agentic development tools to assist in the BI lifecycle, while ensuring human review, data protection, and governance compliance. This hybrid on-site position is located at our headquarters in Oak Creek, WI. You will report directly to the Senior Manager, Business Intelligence & Data Science.
for prose. We must include sections only when posting has real specific content. Benefits: they mention "We offer competitive pay, excellent benefits and the opportunity for professional growth". That's generic but includes benefits mention. Should we create Benefits section? It says "competitive pay, excellent benefits". Not specific details. The rule: 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. Here they state "competitive pay, excellent benefits". That's somewhat vague but still states benefits exist. Might be acceptable to include Benefits section with that sentence. However they also say "We offer competitive pay, excellent benefits and the opportunity for professional growth". That's a statement about benefits. Could include Benefits section with that sentence. Pay: they mention competitive pay but no specifics. According to rule, we should not create Pay section unless posting actually states them. It states "competitive pay" but no numbers. Might be considered filler? The rule says avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "competitive pay" is vague but still a statement. Might be okay but safer to not create Pay section, as it's not specific. Benefits we could include because they said "excellent benefits". Still vague. Might be better to omit Benefits and Pay sections, as they are not specific. The instruction: "Prefer a few substantive sections over many thin ones." So we could omit Benefits and Pay. Schedule: they mention hybrid on-site position located at headquarters in Oak Creek, WI. That's schedule info (hybrid). Could create Schedule section with that sentence. It's specific: hybrid on-site. So include Schedule. We need to include location and reporting line maybe in About the role or a short p. We must not include boilerplate like EEO etc. Remove that. We need to preserve all substantive information. Let's extract sections: - About the role: maybe a brief summary: "We are seeking a highly skilled, detail-oriented, and collaborative Business Intelligence Specialist to join our Business Intelligence & Data Science team." Could be in About the role. But we already have "What You Will Do" which is essentially responsibilities. Could treat that as Responsibilities section. We have "How You Will Do It" which breaks down into subcategories: BI Intake, Requirements & Human-Centered Design; Data Readiness & Governance; Dashboard Design & Development; AI-Assisted & Agentic Workflow Enablement; Monitoring, Maintenance & Continuous Improvement. Those are duties/responsibilities. Could be under Responsibilities as subheadings? But rule: use
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So only those headings allowed? It says use for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we can use those headings, but not required to limit to those exactly; but likely they expect those headings. We should use those headings where appropriate.
Thus we could have:
About the role
with a paragraph summarizing.
Responsibilities
with a - list of duties (maybe combine the detailed bullet points). Could break into sub-items but still
- .
Requirements
with - for required qualifications.
Preferred Qualifications
maybe use Skills>?? Actually they have Preferred Knowledge etc. Could use Skills> or Preferred Qualifications>. The list includes Skills, Benefits, Pay, Schedule. They didn't list Preferred Qualifications but we could use Skills> for preferred? Might be better to use Skills> for both required and preferred? But we already have Requirements. Could use Skills> for preferred qualifications. Or we could use Qualifications> for required and Skills> for preferred. The instruction list includes Qualifications and Skills as possible headings. So we can use Qualifications> for required, Skills> for preferred.
Thus:
About the role
...
Responsibilities
- ... each duty as li.
We need to capture all duties from "What You Will Do" and "How You Will Do It". The "What You Will Do" is a paragraph summarizing role. The "How You Will Do It" enumerates categories with bullet-like sentences. We'll extract each sentence as li.
Let's list duties:
From "What You Will Do":
- designing, developing, validating, deploying, and maintaining business intelligence dashboards and reporting solutions that help stakeholders make better decisions.
- act as a bridge between business needs, governed data products, dashboard design, and technical implementation to ensure BI products are accurate, useful, usable, actionable, and aligned to measurable business outcomes.
- support the full BI dashboard lifecycle, including intake, requirements discovery, development, quality assurance, deployment, maintenance, and continuous improvement.
- actively leverage human-centered design methods and approved AI-assisted or agentic development tools to assist in the BI lifecycle, while ensuring human review, data protection, and governance compliance.
From "How You Will Do It" sections:
BI Intake, Requirements & Human-Centered Design:
- Partner with business stakeholders to define dashboard requests, business objectives, scope, intended decisions, expected outcomes, success measures, and stakeholder needs.
- Apply human-centered design methods, including stakeholder interviews, needfinding, task analysis, design alternatives, prototyping, evaluation, and iteration, to ensure BI products are useful, usable, and actionable.
- Translate business needs and user tasks into clear BI requirements, dashboard concepts, metrics, visualizations, and acceptance criteria.
Data Readiness & Governance:
- Identify required datasets, metric definitions, dimensional context, ownership, refresh requirements, data quality expectations, lineage needs, and access considerations.
- Coordinate with Data Owners, Data Stewards, Business Owners, and Data Engineering to clarify responsibilities, validate data readiness, and support governed data use.
- Route complex transformations to governed upstream data sources where appropriate and avoid embedding complex transformation logic in the dashboard layer.
Dashboard Design & Development:
- Design and develop Power BI dashboards, semantic models, and reporting solutions that are aligned to documented user tasks, business objectives, and measurable outcomes.
- Develop and validate SQL, DAX, Power Query, Python, R, or other analytics logic as needed to support accurate and maintainable BI deliverables.
- Ensure each visualization supports a documented user task, decision, or business action.
AI-Assisted & Agentic Workflow Enablement:
- Use approved AI-assisted and agentic development tools, such as Codex, Gemini CLI, Claude Code, or similar platforms, to support BI development, SQL/DAX/Python generation, documentation, testing, refactoring, workflow automation, and repeatable BI lifecycle activities.
- Apply human review, validation, and governance controls to all AI-assisted outputs, including code, metrics, documentation, QA evidence, and release materials.
- Develop reusable instructions, prompts, runbooks, or automation patterns that improve BI team productivity, consistency, and maintainability.
Monitoring, Maintenance & Continuous Improvement:
- Monitor dashboard adoption, usage telemetry, refresh performance, stakeholder feedback, and ongoing business value to support maintenance, enhancement, optimization, and decommissioning decisions.
- Identify opportunities to automate recurring BI lifecycle activities, improve documentation quality, reduce manual effort, and increase dashboard reliability.
- Communicate findings, risks, requirements, and recommendations clearly to technical and non-technical audiences while contributing to data literacy and team process improvement.
Now Required qualifications:
- Minimum of a Bachelor's Degree in Computer Science, Data Science, Mathematics, Finance, Business Administration, Engineering, or another related field from an accredited institution.
- 3–5 years of related professional experience in business intelligence, analytics, reporting, data analysis, or dashboard development.
- Proficiency with Power BI, including Power Query, DAX, data modeling, report/dashboard interface development, and dashboard publishing.
- Experience using SQL for data querying, validation, and analysis.
- Experience with data manipulation or analysis using Python and/or R.
- Demonstrated ability to responsibly use AI-assisted productivity, coding, or analytics tools in a professional environment.
- Ability to apply human-centered design practices, such as need finding, task analysis, prototyping, evaluation, or iteration, to business intelligence or analytics work.
- Strong analytical skills with the ability to interpret data, identify trends, validate assumptions, and communicate insights.
- Understanding of data governance concepts, including data quality, data ownership, data stewardship, metadata, lineage, access control, and refresh expectations.
- Ability to gather requirements from stakeholders and translate business needs into actionable BI deliverables.
- Strong written and verbal communication skills.
- Highly motivated and capable of working independently as well as collaboratively with business and technical teams.
- U.S. Citizen or U.S. Permanent Resident.
Preferred qualifications (list):
- Knowledge of data visualization best practices and dashboard usability principles.
- Experience applying structured human-centered design methods, user research, prototyping, or usability evaluation in dashboard, application, or analytics projects.
- Understanding of software engineering principles such as version control, testing, CI/CD, reusable design patterns, and controlled release processes.
- Familiarity with containerization tools such as Docker or Docker Compose.
- Experience working with data warehouses, governed datasets, semantic models, or enterprise data platforms.
- Experience documenting business requirements, data definitions, QA evidence, release criteria, or support models.
- Experience using AI-assisted or agentic development tools, such as Codex, Gemini CLI, Claude Code, or similar platforms, to improve analytics, BI engineering, documentation, testing, or process automation workflows.
- Experience developing reusable instructions, prompts, or automation patterns for AI-assisted software or analytics workflows.
- Knowledge of operations research, statistics, experimental design, or process improvement methods.
- Experience monitoring dashboard adoption, usage telemetry, or business value metrics.
Who We Are (company description) could be placed under About the role or maybe a separate section like "About the company". But headings list includes About the role only. Could incorporate into About the role paragraph.
Also location/hybrid: "This hybrid on-site position is located at our headquarters in Oak Creek, WI. You will report directly to the Senior Manager, Business Intelligence & Data Science." Could be in About the role or Schedule. Since Schedule heading is allowed, we can put schedule info there.
Thus sections:
About the role
We are seeking a highly skilled, detail-oriented, and collaborative Business Intelligence Specialist to join our Business Intelligence & Data Science team. In this role, you will be responsible for designing, developing, validating, deploying, and maintaining business intelligence dashboards and reporting solutions that help stakeholders make better decisions. You will act as a bridge between business needs, governed data products, dashboard design, and technical implementation to ensure BI products are accurate, useful, usable, actionable, and aligned to measurable business outcomes. This role supports the full BI dashboard lifecycle, including intake, requirements discovery, development, quality assurance, deployment, maintenance, and continuous improvement. The Business Intelligence Specialist is expected to actively leverage human-centered design methods and approved AI-assisted or agentic development tools to assist in the BI lifecycle, while ensuring human review, data protection, and governance compliance. This hybrid on-site position is located at our headquarters in Oak Creek, WI. You will report directly to the Senior Manager, Business Intelligence & Data Science.
About the role
with a paragraph summarizing.Responsibilities
with a- list of duties (maybe combine the detailed bullet points). Could break into sub-items but still
- .
Requirements
with- for required qualifications.
Preferred Qualifications
maybe useSkills>?? Actually they have Preferred Knowledge etc. Could use
Skills> or
Preferred Qualifications>. The list includes Skills, Benefits, Pay, Schedule. They didn't list Preferred Qualifications but we could use
Skills> for preferred? Might be better to use
Skills> for both required and preferred? But we already have Requirements. Could use
Skills> for preferred qualifications. Or we could use
Qualifications> for required and
Skills> for preferred. The instruction list includes Qualifications and Skills as possible headings. So we can use
Qualifications> for required,
Skills> for preferred. Thus:
About the role
...
Responsibilities
- ... each duty as li.
We need to capture all duties from "What You Will Do" and "How You Will Do It". The "What You Will Do" is a paragraph summarizing role. The "How You Will Do It" enumerates categories with bullet-like sentences. We'll extract each sentence as li.
Let's list duties:
From "What You Will Do":
- designing, developing, validating, deploying, and maintaining business intelligence dashboards and reporting solutions that help stakeholders make better decisions.
- act as a bridge between business needs, governed data products, dashboard design, and technical implementation to ensure BI products are accurate, useful, usable, actionable, and aligned to measurable business outcomes.
- support the full BI dashboard lifecycle, including intake, requirements discovery, development, quality assurance, deployment, maintenance, and continuous improvement.
- actively leverage human-centered design methods and approved AI-assisted or agentic development tools to assist in the BI lifecycle, while ensuring human review, data protection, and governance compliance.
From "How You Will Do It" sections:
BI Intake, Requirements & Human-Centered Design:
- Partner with business stakeholders to define dashboard requests, business objectives, scope, intended decisions, expected outcomes, success measures, and stakeholder needs.
- Apply human-centered design methods, including stakeholder interviews, needfinding, task analysis, design alternatives, prototyping, evaluation, and iteration, to ensure BI products are useful, usable, and actionable.
- Translate business needs and user tasks into clear BI requirements, dashboard concepts, metrics, visualizations, and acceptance criteria.
Data Readiness & Governance:
- Identify required datasets, metric definitions, dimensional context, ownership, refresh requirements, data quality expectations, lineage needs, and access considerations.
- Coordinate with Data Owners, Data Stewards, Business Owners, and Data Engineering to clarify responsibilities, validate data readiness, and support governed data use.
- Route complex transformations to governed upstream data sources where appropriate and avoid embedding complex transformation logic in the dashboard layer.
Dashboard Design & Development:
- Design and develop Power BI dashboards, semantic models, and reporting solutions that are aligned to documented user tasks, business objectives, and measurable outcomes.
- Develop and validate SQL, DAX, Power Query, Python, R, or other analytics logic as needed to support accurate and maintainable BI deliverables.
- Ensure each visualization supports a documented user task, decision, or business action.
AI-Assisted & Agentic Workflow Enablement:
- Use approved AI-assisted and agentic development tools, such as Codex, Gemini CLI, Claude Code, or similar platforms, to support BI development, SQL/DAX/Python generation, documentation, testing, refactoring, workflow automation, and repeatable BI lifecycle activities.
- Apply human review, validation, and governance controls to all AI-assisted outputs, including code, metrics, documentation, QA evidence, and release materials.
- Develop reusable instructions, prompts, runbooks, or automation patterns that improve BI team productivity, consistency, and maintainability.
Monitoring, Maintenance & Continuous Improvement:
- Monitor dashboard adoption, usage telemetry, refresh performance, stakeholder feedback, and ongoing business value to support maintenance, enhancement, optimization, and decommissioning decisions.
- Identify opportunities to automate recurring BI lifecycle activities, improve documentation quality, reduce manual effort, and increase dashboard reliability.
- Communicate findings, risks, requirements, and recommendations clearly to technical and non-technical audiences while contributing to data literacy and team process improvement.
Now Required qualifications:
- Minimum of a Bachelor's Degree in Computer Science, Data Science, Mathematics, Finance, Business Administration, Engineering, or another related field from an accredited institution.
- 3–5 years of related professional experience in business intelligence, analytics, reporting, data analysis, or dashboard development.
- Proficiency with Power BI, including Power Query, DAX, data modeling, report/dashboard interface development, and dashboard publishing.
- Experience using SQL for data querying, validation, and analysis.
- Experience with data manipulation or analysis using Python and/or R.
- Demonstrated ability to responsibly use AI-assisted productivity, coding, or analytics tools in a professional environment.
- Ability to apply human-centered design practices, such as need finding, task analysis, prototyping, evaluation, or iteration, to business intelligence or analytics work.
- Strong analytical skills with the ability to interpret data, identify trends, validate assumptions, and communicate insights.
- Understanding of data governance concepts, including data quality, data ownership, data stewardship, metadata, lineage, access control, and refresh expectations.
- Ability to gather requirements from stakeholders and translate business needs into actionable BI deliverables.
- Strong written and verbal communication skills.
- Highly motivated and capable of working independently as well as collaboratively with business and technical teams.
- U.S. Citizen or U.S. Permanent Resident.
Preferred qualifications (list):
- Knowledge of data visualization best practices and dashboard usability principles.
- Experience applying structured human-centered design methods, user research, prototyping, or usability evaluation in dashboard, application, or analytics projects.
- Understanding of software engineering principles such as version control, testing, CI/CD, reusable design patterns, and controlled release processes.
- Familiarity with containerization tools such as Docker or Docker Compose.
- Experience working with data warehouses, governed datasets, semantic models, or enterprise data platforms.
- Experience documenting business requirements, data definitions, QA evidence, release criteria, or support models.
- Experience using AI-assisted or agentic development tools, such as Codex, Gemini CLI, Claude Code, or similar platforms, to improve analytics, BI engineering, documentation, testing, or process automation workflows.
- Experience developing reusable instructions, prompts, or automation patterns for AI-assisted software or analytics workflows.
- Knowledge of operations research, statistics, experimental design, or process improvement methods.
- Experience monitoring dashboard adoption, usage telemetry, or business value metrics.
Who We Are (company description) could be placed under About the role or maybe a separate section like "About the company". But headings list includes About the role only. Could incorporate into About the role paragraph.
Also location/hybrid: "This hybrid on-site position is located at our headquarters in Oak Creek, WI. You will report directly to the Senior Manager, Business Intelligence & Data Science." Could be in About the role or Schedule. Since Schedule heading is allowed, we can put schedule info there.
Thus sections:
About the role
We are seeking a highly skilled, detail-oriented, and collaborative Business Intelligence Specialist to join our Business Intelligence & Data Science team. In this role, you will be responsible for designing, developing, validating, deploying, and maintaining business intelligence dashboards and reporting solutions that help stakeholders make better decisions. You will act as a bridge between business needs, governed data products, dashboard design, and technical implementation to ensure BI products are accurate, useful, usable, actionable, and aligned to measurable business outcomes. This role supports the full BI dashboard lifecycle, including intake, requirements discovery, development, quality assurance, deployment, maintenance, and continuous improvement. The Business Intelligence Specialist is expected to actively leverage human-centered design methods and approved AI-assisted or agentic development tools to assist in the BI lifecycle, while ensuring human review, data protection, and governance compliance. This hybrid on-site position is located at our headquarters in Oak Creek, WI. You will report directly to the Senior Manager, Business Intelligence & Data Science.
- ... each duty as li.
We need to capture all duties from "What You Will Do" and "How You Will Do It". The "What You Will Do" is a paragraph summarizing role. The "How You Will Do It" enumerates categories with bullet-like sentences. We'll extract each sentence as li.
Let's list duties:
From "What You Will Do":
- designing, developing, validating, deploying, and maintaining business intelligence dashboards and reporting solutions that help stakeholders make better decisions.
- act as a bridge between business needs, governed data products, dashboard design, and technical implementation to ensure BI products are accurate, useful, usable, actionable, and aligned to measurable business outcomes.
- support the full BI dashboard lifecycle, including intake, requirements discovery, development, quality assurance, deployment, maintenance, and continuous improvement.
- actively leverage human-centered design methods and approved AI-assisted or agentic development tools to assist in the BI lifecycle, while ensuring human review, data protection, and governance compliance.
From "How You Will Do It" sections:
BI Intake, Requirements & Human-Centered Design:
- Partner with business stakeholders to define dashboard requests, business objectives, scope, intended decisions, expected outcomes, success measures, and stakeholder needs.
- Apply human-centered design methods, including stakeholder interviews, needfinding, task analysis, design alternatives, prototyping, evaluation, and iteration, to ensure BI products are useful, usable, and actionable.
- Translate business needs and user tasks into clear BI requirements, dashboard concepts, metrics, visualizations, and acceptance criteria.
Data Readiness & Governance:
- Identify required datasets, metric definitions, dimensional context, ownership, refresh requirements, data quality expectations, lineage needs, and access considerations.
- Coordinate with Data Owners, Data Stewards, Business Owners, and Data Engineering to clarify responsibilities, validate data readiness, and support governed data use.
- Route complex transformations to governed upstream data sources where appropriate and avoid embedding complex transformation logic in the dashboard layer.
Dashboard Design & Development:
- Design and develop Power BI dashboards, semantic models, and reporting solutions that are aligned to documented user tasks, business objectives, and measurable outcomes.
- Develop and validate SQL, DAX, Power Query, Python, R, or other analytics logic as needed to support accurate and maintainable BI deliverables.
- Ensure each visualization supports a documented user task, decision, or business action.
AI-Assisted & Agentic Workflow Enablement:
- Use approved AI-assisted and agentic development tools, such as Codex, Gemini CLI, Claude Code, or similar platforms, to support BI development, SQL/DAX/Python generation, documentation, testing, refactoring, workflow automation, and repeatable BI lifecycle activities.
- Apply human review, validation, and governance controls to all AI-assisted outputs, including code, metrics, documentation, QA evidence, and release materials.
- Develop reusable instructions, prompts, runbooks, or automation patterns that improve BI team productivity, consistency, and maintainability.
Monitoring, Maintenance & Continuous Improvement:
- Monitor dashboard adoption, usage telemetry, refresh performance, stakeholder feedback, and ongoing business value to support maintenance, enhancement, optimization, and decommissioning decisions.
- Identify opportunities to automate recurring BI lifecycle activities, improve documentation quality, reduce manual effort, and increase dashboard reliability.
- Communicate findings, risks, requirements, and recommendations clearly to technical and non-technical audiences while contributing to data literacy and team process improvement.
Now Required qualifications:
- Minimum of a Bachelor's Degree in Computer Science, Data Science, Mathematics, Finance, Business Administration, Engineering, or another related field from an accredited institution.
- 3–5 years of related professional experience in business intelligence, analytics, reporting, data analysis, or dashboard development.
- Proficiency with Power BI, including Power Query, DAX, data modeling, report/dashboard interface development, and dashboard publishing.
- Experience using SQL for data querying, validation, and analysis.
- Experience with data manipulation or analysis using Python and/or R.
- Demonstrated ability to responsibly use AI-assisted productivity, coding, or analytics tools in a professional environment.
- Ability to apply human-centered design practices, such as need finding, task analysis, prototyping, evaluation, or iteration, to business intelligence or analytics work.
- Strong analytical skills with the ability to interpret data, identify trends, validate assumptions, and communicate insights.
- Understanding of data governance concepts, including data quality, data ownership, data stewardship, metadata, lineage, access control, and refresh expectations.
- Ability to gather requirements from stakeholders and translate business needs into actionable BI deliverables.
- Strong written and verbal communication skills.
- Highly motivated and capable of working independently as well as collaboratively with business and technical teams.
- U.S. Citizen or U.S. Permanent Resident.
Preferred qualifications (list):
- Knowledge of data visualization best practices and dashboard usability principles.
- Experience applying structured human-centered design methods, user research, prototyping, or usability evaluation in dashboard, application, or analytics projects.
- Understanding of software engineering principles such as version control, testing, CI/CD, reusable design patterns, and controlled release processes.
- Familiarity with containerization tools such as Docker or Docker Compose.
- Experience working with data warehouses, governed datasets, semantic models, or enterprise data platforms.
- Experience documenting business requirements, data definitions, QA evidence, release criteria, or support models.
- Experience using AI-assisted or agentic development tools, such as Codex, Gemini CLI, Claude Code, or similar platforms, to improve analytics, BI engineering, documentation, testing, or process automation workflows.
- Experience developing reusable instructions, prompts, or automation patterns for AI-assisted software or analytics workflows.
- Knowledge of operations research, statistics, experimental design, or process improvement methods.
- Experience monitoring dashboard adoption, usage telemetry, or business value metrics.
Who We Are (company description) could be placed under About the role or maybe a separate section like "About the company". But headings list includes About the role only. Could incorporate into About the role paragraph.
Also location/hybrid: "This hybrid on-site position is located at our headquarters in Oak Creek, WI. You will report directly to the Senior Manager, Business Intelligence & Data Science." Could be in About the role or Schedule. Since Schedule heading is allowed, we can put schedule info there.
Thus sections:
- for required qualifications.