Senior Business Intelligence Analyst

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 must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (EEO, disclaimer, etc). Must not invent or summarize away detail. Must not create sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting does not mention pay, schedule, benefits explicitly. There's no mention of benefits, pay, schedule. So we should not include those sections. We need sections: About the role (maybe from "About Rogue Credit Union"? Actually "About the role" heading is for role description. The posting includes "About Rogue Credit Union" (company description) and "Role: The Senior Business Intelligence Analyst leads...". So we can put company description under About the role? Or maybe separate "About the company"? But headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use About the role for company overview and role summary. Responsibilities for essential functions & responsibilities. Requirements for experience/education? Qualifications maybe for education/certifications? Skills for knowledge & skills. We need to decide mapping. We must not invent headings without content. So we need to see if we have content for each. We have: - About Rogue Credit Union: description of company, mission, culture. That's substantive. - Role description: "The Senior Business Intelligence Analyst leads the delivery..." That's also role summary. We could combine both under About the role. - Essential Functions & Responsibilities: detailed bullet points with percentages. That's Responsibilities. - Knowledge & Skills: includes Experience, Education, Interpersonal Skills, Other Skills. That's a mix of requirements, qualifications, skills. We need to split into Requirements, Qualifications, Skills as per allowed headings. We have: Experience: Five years to eight years of similar or related experience. Experience evaluating business needs and user requirements in a related position. Three to Five years of experience in a financial services environment with an awareness of accounting principles and financial statements preferred. Education: (1) A master's degree, or (2) a bachelor's degree plus professional certification (e.g., CPA). Interpersonal Skills: Work involves extensive personal contact... etc. Other Skills: Demonstrates high general competency... etc. Thus we can have: - Requirements: maybe the experience and education? Or Requirements could be experience and education. Qualifications could be interpersonal skills? But the heading list includes Qualifications separate from Skills. Usually Qualifications could be education/certifications, Requirements could be experience. Skills could be technical and other skills. We need to ensure we don't create sections with filler. All content must be preserved. Thus we can create:

About the role

Rogue Credit Union is a member-owned, not-for-profit financial cooperative headquartered in the Rogue Valley located in beautiful southern Oregon. Providing services to our members in select Oregon, Idaho and California counties. We strive to make an impact in the communities we serve by living, giving, and supporting local. Our mission is to provide exceptional member experiences that build mutually beneficial relationships to create the most loyal members in the nation. Here at Rogue, we believe in having a culture of happy team members who feel supported, have the chance to grow their careers, and LOVE where they work! The Senior Business Intelligence Analyst leads the delivery of advanced analytics and serves as a strategic partner to business leaders across the organization. This role translates complex business needs into scalable, enterprise-level analytics solutions and provides clear requirements to technical and analytics partners to support the development of underlying data models and structures. Through leadership in data quality, governance, and analytics practices, the position advances organizational analytics maturity while mentoring team members. Collaboration across technical and business teams ensures analytics solutions align with organizational strategy, optimize analytics workflows, and effectively support business outcomes. Success in this role is defined by leadership impact, strategic influence, and the ability to elevate analytics maturity, and drive meaningful business results.

Then Responsibilities:

Responsibilities

• Leads advanced data analysis to identify complex trends, risks, and opportunities that drive decision-making and uncover opportunities across the organization (35%). Delivers advanced forecasting, scenario, and comparative analysis and applies expert analytical judgment to provide recommendations that influence long-term organizational objectives and member outcomes. Provides recommendations to management of how data can translate to tools that staff can utilize to deliver exceptional service and deepen member participation. Prepares and transforms data using tools such as KNIME and Microsoft Fabric, and programming languages such as Python ensuring data consistency, reliability, and quality through optimized SQL queries, data validation, and troubleshooting.
• Serves as a trusted analytics advisor to business leaders and cross-functional partners (25%). Leads complex requirement discussions, integrates data sources across domains, and ensures analytics outputs meet stakeholder needs while adhering to organizational standards and best practices. Establishes effective communication frameworks and supports alignment across initiatives. Partners with business and BI leadership to inform prioritization decisions by framing tradeoffs, risks, and expected business impact. Provides data-driven recommendations that support decision-making and ensure analytics efforts align with organizational goals and established priorities.
• Leads advanced requirements definition and gap analysis for complex and enterprise-level data sets (15%). May oversee or assist with the evaluation and validation of new data sources to ensure scalability, quality, and reuse. Partners closely with Data Engineers and Data Scientists to define requirements and provide input into data aggregation, transformation, and modeling approaches, ensuring solutions effectively support analytics and business needs. Drives improvements in data quality, governance, and data lifecycle management practices, ensuring data assets are reliable, well-documented, and aligned with business needs.
• Champions self-service analytics by identifying systemic gaps and driving improvements in data accessibility, usability, and adoption (10%). Provides training and ongoing support to power users, mentors BI Analysts at all levels, and promotes best practices across the team. Assists in troubleshooting complex issues and collaborates across teams to remove impediments and improve delivery. Contributes to building a strong culture of data literacy and effective use of analytics tools.
• Translates complex business requirements into technical specifications and provides strategic recommendations to management on how data can be operationalized through tools and solutions that improve service delivery and member engagement (10%). Identifies and implements opportunities for process improvement within the BI program and supports adoption of analytics solutions. Partners with BI leadership to ensure analytics initiatives enhance the user experience and align with organizational priorities. Stays current with industry trends and emerging technologies to continuously improve analytics capabilities.
• Proactively performs other duties as assigned (5%).

Now Requirements: maybe experience and education. We have experience and education details. We'll put them under Requirements.

Requirements

• Five to eight years of similar or related experience.
• Experience evaluating business needs and user requirements in a related position.
• Three to five years of experience in a financial services environment with an awareness of accounting principles and financial statements preferred.
• A master's degree, or a bachelor's degree plus professional certification (e.g., CPA).

Qualifications: maybe interpersonal skills? But the heading Qualifications could be for interpersonal skills? However the list includes Qualifications separate from Skills. We could put Interpersonal Skills under Qualifications.

Qualifications

• Work involves extensive personal contact with others and is of a personal or sensitive nature.
• Motivating, influencing, and/or training others is key at this level.
• Outside contacts become important and fostering sound relationships with other entities (companies and/or individuals) becomes necessary and often requires the ability to influence and/or sell ideas or services to others.

Skills: Other Skills (technical and general). We'll put under Skills.

Skills

• Demonstrates high general competency with the ability to quickly learn and apply new concepts.
• Self-starter who is highly motivated, organized, and results-oriented, with a strong focus on quality and attention to detail.
• Effectively manages time and priorities, demonstrating flexibility and adaptability in response to changing direction and competing demands.
• Collaborates effectively as a team player, working across business and technical teams.
• Comfortable interacting with senior management and communicates clearly and effectively with stakeholders at all levels.
• Possesses strong technical proficiency, including extensive experience with SQL and relational database systems (e.g., DB2, Oracle, SQL Server) and data warehouse environments.
• Demonstrates knowledge of logical and physical data modeling concepts.
• Experience with programming languages such as R and/or Python for data analysis.
• Familiarity with ETL and BI tools, as well as data visualization platforms (e.g., Tableau, Power BI, Sisense).
• Working knowledge of programming/scripting concepts and the software development life cycle.

We must not include Benefits, Pay, Schedule sections because not present. We must ensure we didn't include any boilerplate like EEO, disclaimer, etc. We removed them. Check that we preserved all substantive info: company description, role summary, responsibilities with percentages, experience, education, interpersonal skills, other skills. Did we miss any? The "Physical Requirements" and "Work Environment" sections were present but we omitted them. Are they considered substantive? The instruction says to preserve ALL substantive information. Physical Requirements and Work Environment are substantive. However we are limited to headings list; we could include them under a generic heading? Not allowed headings beyond those listed. We could possibly incorporate them into Responsibilities or Skills? But they are not responsibilities or skills. The instruction says: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the allowed headings. It does not say we cannot use other headings, but the examples imply those are the expected ones. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It may be interpreted as we should use those headings for sections, but we could also use other headings if needed? However later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid other headings. But to be safe, we should stick to the allowed headings. However we would be omitting Physical Requirements and Work Environment, which is substantive. That would violate "Preserve ALL substantive information". So we need to incorporate that info somewhere within allowed sections. Could we put Physical Requirements under Skills? Not really. Could we put Work Environment under Responsibilities? Not ideal but maybe we can add a bullet under Responsibilities about work environment? But that would misrepresent. Perhaps we can create a section "Requirements" to include physical requirements? But Requirements already used for experience/education. Could we add another subsection? We could add a

Requirements

and include both experience/education and physical requirements/work environment as list items. That would preserve all. However the instruction says "Prefer a few substantive sections over many thin ones." So we could combine. Thus we can have:

Requirements

• Five to eight years of similar or related experience.
• Experience evaluating business needs and user requirements in a related position.
• Three to five years of experience in a financial services environment with an awareness of accounting principles and financial statements preferred.
• A master's degree