Jobs · Analyst · Wisconsin

Data Analytics and Business Intelligence Manager

University of Wisconsin-Milwaukee · Milwaukee, WI · 1 mo ago
Analyst$85k–$97k/yrFull-time
We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. First, we have "Current Employees: ..." internal note – that's boilerplate? It's about internal application process; we should remove application instructions, navigation, legal, EEO, etc. So we drop that line. Position Title: Data Analytics and Business Intelligence Manager – we should not repeat as heading. Job Category, Employment Type, Job Profile – minor metadata; we can fold into a short

or drop. Probably we can include a short paragraph with that info. Then "School/College/Division Description: ..." That's about the role? It's description of CASL. Could be part of About the role. Then "Job Summary ..." That's also about role. Then "Key Job Responsibilities" with bullet points – that's Responsibilities. Then "Data Strategy, Reporting, and Analytics" etc – those are subpoints under responsibilities. Then "Data Integration and Architecture" etc. Then "Database and SQL Server Management" etc. Then "School: School of Continuing Education Unit: Center for Advancing Student Learning (CASL)" – maybe part of About the role. Then "Target Salary Range: $85,000 - $97,000/annually. Salary will be determined by finalist's experience, training, education, and equity-based factors." That's Pay info. Then "Required Qualifications" list – that's Requirements/Qualifications. Then "Preferred Qualifications" list – could be part of Qualifications or separate? We can combine under Qualifications. Then "Application Instructions" – remove. Then "Contact Information" – maybe minor metadata; could be a short p. Then "Reasonable Accommodations" – boilerplate EEO etc; remove. Then "Confidentiality of Applicant Materials" – remove. Then "CBC and Reference Check Policy" – remove. Then "Annual Security and Fire Safety Report (Clery Act)" – remove. Then "Employment Authorization" – remove. Then "UW is an Equal Opportunity Employer" – remove. Thus we need sections: - About the role: could combine School/College/Division Description, Job Summary, School/Unit info. - Responsibilities: list of duties (the bullet points under Key Job Responsibilities and subpoints). We need to preserve all substantive info. - Requirements/Qualifications: Required Qualifications and Preferred Qualifications. - Pay: Target Salary Range. - Benefits: Not mentioned; do not include. - Schedule: Not mentioned; do not include. - Skills: Not explicitly separate; maybe we could include under Qualifications? But we have no separate Skills section; we can omit. We need to use

for each section heading. We need to use
  • for any list of duties/requirements/benefits, and

    for prose. We must not repeat job title as heading. We must not put Job ID/requisition numbers as headings. We need to preserve ALL substantive information; do not invent or summarize away detail. We need to remove boilerplate. Let's extract substantive content. First, About the role: - School/College/Division Description: The Center for Advancing Student Learning (CASL) at the University of Wisconsin–Milwaukee is the unified hub for lifelong learning and instructional excellence, dedicated to making a high-quality UWM education available to anyone, anywhere, at any time. We champion flexible, student-centered approaches that allow learners to move seamlessly across educational experiences—from youth programming and degree-seeking pathways to professional upskilling in continuing education. By partnering with instructors to design inclusive, technology-driven learning environments, CASL ensures that innovative learning extends beyond the traditional classroom. Join us in our mission to support educators and empower learners at every stage of their journey, providing the resources necessary to thrive in an increasingly digital and global landscape. Through strong community and employer partnerships, responsive support, and a commitment to continuous improvement, CASL works to cultivate a teaching and learning environment where all students can thrive. - Job Summary: The Data Analytics and Business Intelligence Manager leads the design, development, and maintenance of CASL data systems in support of unit and institutional decision‑making. This role is responsible for integrating and managing data across platforms; and delivering high‑quality reports, dashboards, and analyses that enable stakeholders to engage with and share actionable insights. The position also oversees database and SQL server administration to ensure data security, integrity, and performance. - School: School of Continuing Education Unit: Center for Advancing Student Learning (CASL) We can combine these into a few paragraphs. Now Responsibilities: Key Job Responsibilities bullet points: - Data Strategy, Reporting, and Analytics - Analyze, plan, and produce data sets, reports, and dashboards to support unit, program, and institutional planning. - Design, develop, and implement business intelligence and reporting solutions using tools such as Power BI and SQL‑based environments. - Generate recurring and ad hoc reports, including annual reports on identified key outcomes. - Provide accurate, timely, and actionable data to leadership to support strategic decision‑making. - Serve as a point of contact for CASL database systems, reporting platforms, and data‑related projects. - Develop user documentation and facilitate training to support effective use of databases, reports, and dashboards by unit staff and partners. - Ensure responsible handling of confidential and sensitive data. - Data Integration and Architecture - Partner with academic and administrative units across campus to integrate data from multiple systems in support of a unified, institution‑wide view. - Prepare data sets for analysis, including data cleaning, quality assurance, transformation, restructuring, and integration of multiple data sources. - Organize data preparation and analysis into reproducible, automated pipelines optimized for performance and scalability. - Database and SQL Server Management - Design, develop, build, and maintain one or more database systems and SQL server environments to ensure data availability, integrity, and security. - Implement and maintain security measures in accordance with institutional policies and data governance standards. - Identify and resolve routine data and database issues while upholding database‑use guidelines. We need to output these as a list (

    • ) possibly with nested lists? The instruction: Use
      • for any list of duties/requirements/benefits. It doesn't forbid nested lists, but we can flatten: each bullet as
      • . However we have sub-bullets; we could keep them as separate
      • items, maybe with a leading dash? Better to keep hierarchy: we could have
        • Data Strategy, Reporting, and Analytics
          • ... etc
        • etc. That's still using
          • . That's fine. Now Requirements/Qualifications: Required Qualifications: - Bachelor’s degree in data analytics, information systems, computer science, statistics, or a related field. - Three (3) or more years of professional experience in data analysis, business intelligence, database management, or a closely related role. - Demonstrated experience extracting, integrating, and analyzing data from multiple systems to support programmatic or institutional decision‑making. - Proficiency in SQL, including writing complex queries, views, and stored procedures. - Experience developing reports and interactive dashboards using Power BI or comparable business intelligence tools. - Strong organizational skills and the ability to manage multiple projects, priorities, and deadlines simultaneously. Preferred Qualifications: - Master’s degree in data science, analytics, information systems, computer science, higher education administration, or a related field. - Experience working with data systems commonly used in higher education (e.g., student information systems, learning management systems, Modern Campus Lifelong Learning Extended Education, CRM, or finance). - Familiarity with cloud‑based data environments or enterprise reporting infrastructures. - Experience supporting leadership decision‑making through dashboards, key performance indicators, and strategic reporting. We can combine Required and Preferred under a Qualifications section, maybe with two subheadings? But we only have

            for section headings; we could have a single Qualifications section and inside we can have

            for intro and then

            • for required and another
              • for preferred, maybe with a heading inside? But we cannot add extra headings besides

                . We could separate into two sections: Requirements and Qualifications? The instruction list includes both Requirements and Qualifications as possible headings. We could use Requirements for required qualifications and Qualifications for preferred qualifications. That seems appropriate. Thus: -

                Requirements

                with
                • list of required qualifications. -

                  Qualifications

                  with
                  • list of preferred qualifications. Alternatively we could combine but better to follow instruction. Now Pay: - Target Salary Range: $85,000 - $97,000/annually. Salary will be determined by finalist's experience, training, education, and equity-based factors. We need a Pay section with that info as

                    . Now Benefits: Not mentioned; skip. Schedule: Not mentioned; skip. Skills: Not mentioned; skip. About the role: we need a section heading

                    About the role

                    with prose

                    maybe multiple paragraphs. We also have minor metadata like Job Category, Employment Type, Job Profile, School/Unit, Contact Information. We can fold into a short

                    maybe after About the role or separate? The instruction: "fold minor metadata into a short

                    or drop it." So we can include a short paragraph after About the role that includes Job Category: Academic Staff; Employment Type: Regular; Job Profile: Database Report Writer II; School: School of Continuing Education; Unit: Center for Advancing Student Learning (CASL); Contact: Adam Garcia - HR Coordinator garci289@uwm.edu. That's minor metadata. We should not include internal note about Current Employees. Now ensure we don't include any boilerplate like "Reasonable Accommodations", etc. Now produce HTML fragment. Let's craft:

                    About the role

                    The Center for Advancing Student Learning (CASL) at the University of Wisconsin–Milwaukee is the unified hub for lifelong learning and instructional excellence, dedicated to making a high-quality UWM education available to anyone, anywhere, at any time. We champion flexible, student-centered approaches that allow learners to move seamlessly across educational experiences—from youth programming and degree-seeking pathways to professional upskilling in continuing education. By partnering with instructors to design inclusive, technology-driven learning environments, CASL ensures that innovative learning extends beyond the traditional classroom. Join us in our mission to support educators and empower learners at every stage of their journey, providing the resources necessary to thrive in an increasingly digital and global landscape. Through strong community and employer partnerships, responsive support, and a commitment to continuous improvement, CASL works to cultivate a teaching and learning environment where all students can thrive.

                    The Data Analytics and Business Intelligence Manager leads the design, development, and maintenance of CASL data systems in support of unit and institutional decision‑making. This role is responsible for integrating and managing data across platforms; and delivering high‑quality reports, dashboards, and analyses that enable stakeholders to engage with and share actionable insights. The position also oversees database and SQL server administration to ensure data security, integrity, and performance.

                    Job Category: Academic Staff • Employment Type: Regular • Job Profile: Database Report Writer II • School: School of Continuing Education • Unit: Center for Advancing Student Learning (CASL) • Contact: Adam Garcia - HR Coordinator (garci289@uwm.edu)

                    Then Responsibilities:

                    Responsibilities

                    • Data Strategy, Reporting, and Analytics
                      • Analyze, plan, and produce data sets, reports, and dashboards to support unit, program, and institutional planning.
                      • Design, develop, and implement business intelligence and reporting solutions using tools such as Power BI and SQL‑based environments.
                      • Generate recurring and ad hoc reports, including annual reports on identified key outcomes.

Similar jobs