Development Business Analyst
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. Must include sections only when posting has real specific content. We need to parse the job details.
The posting includes:
- Overview (description) about role: we can put under About the role
with paragraphs.
- REPORTS TO: Business Intelligence Data Architect, IIT – maybe include as a short paragraph under About the role or separate? It's metadata; we can fold into a short
. - Essential Responsibilities: list of duties. Use
Responsibilities
with- each.
- Requirements: list of requirements. Use
Requirements
with- . Also includes "Bachelor’s degree preferred or equivalent work experience." etc.
- There's also "Ada Requirements" (Americans with Disabilities Act) which is about physical requirements. Could be considered under Requirements or maybe a separate section? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Ada Requirements could be part of Requirements (physical). We'll include under Requirements.
- There's no explicit Benefits, Pay, Schedule mentioned. So we should not create those sections.
- There's no Qualifications separate from Requirements; but we could treat Requirements as qualifications. We'll just have Requirements.
- Skills: maybe we could extract skills from requirements (SQL, Power BI, etc.) but we already have them in Requirements. The instruction says prefer a few substantive sections over many thin ones. So we can combine skills into Requirements or maybe have a Skills section. But we have to avoid thin sections. Since we already have Requirements covering skills, we can omit separate Skills.
- No Benefits, Pay, Schedule.
Thus output:
About the role
Overview text...
REPORTS TO: Business Intelligence Data Architect, IIT
Responsibilities
- ... ...
Requirements
- ... ...
. Then REPORTS TO line: "REPORTS TO: Business Intelligence Data Architect, IIT". We'll put as a short
. Now responsibilities list: The bullet points after "Essential Responsibilities". Let's capture each sentence separated by periods? The text: "Essential Responsibilities Designs, builds, maintains, and enhances reports, dashboards, and self-service analytics for Advancement and other museum departments using CRM, data warehouse, and related enterprise data sources.Translates business questions into analytical requirements, measures, data definitions, and technical solutions; develops ad-hoc queries and analyses to answer complex operational and strategic questions.Develops, validates, and maintains predictive analytics and machine learning models for use cases such as donor propensity, segmentation, retention, upgrades, campaign response, forecasting, and other museum priorities.Builds projections, forecasts, and scenario analyses using historical and current data, and partners with Advancement leaders and analytics staff to ensure outputs are understood and usable for planning and decision-making.Develops working knowledge and assists with integration between Development and Finance systems to ensure records are reconciled accurately.Performs quality assurance on analytical products, investigates anomalies and data issues, and maintains documentation for business logic, calculations, data definitions, model assumptions, and reporting processes.Collaborates with IIT, the Data team, and museum departments to incorporate data from CRM, finance, web, marketing, retail, and other platforms into integrated reporting and analytics solutions.Serves as an active member of the Data and CRM governance teams, helping establish and maintain shared definitions, data standards, documentation, access practices, and policies that support trusted museum-wide reporting.Partners with CRM stakeholders to improve data capture and business processes that affect reporting and analytics, and provides technical guidance and training on the effective use of analytical tools.Maintains strong working relationships with colleagues in advancement and other stakeholders, prioritizes analytical requests in coordination with the Data team, and communicates technical findings, limitations, and recommendations clearly to technical and non-technical audiences." We need to split into list items. Each sentence seems separated by a period but sometimes no space after period. We'll split accordingly. Let's create list items: - Designs, builds, maintains, and enhances reports, dashboards, and self-service analytics for Advancement and other museum departments using CRM, data warehouse, and related enterprise data sources. - Translates business questions into analytical requirements, measures, data definitions, and technical solutions; develops ad-hoc queries and analyses to answer complex operational and strategic questions. - Develops, validates, and maintains predictive analytics and machine learning models for use cases such as donor propensity, segmentation, retention, upgrades, campaign response, forecasting, and other museum priorities. - Builds projections, forecasts, and scenario analyses using historical and current data, and partners with Advancement leaders and analytics staff to ensure outputs are understood and usable for planning and decision-making. - Develops working knowledge and assists with integration between Development and Finance systems to ensure records are reconciled accurately. - Performs quality assurance on analytical products, investigates anomalies and data issues, and maintains documentation for business logic, calculations, data definitions, model assumptions, and reporting processes. - Collaborates with IIT, the Data team, and museum departments to incorporate data from CRM, finance, web, marketing, retail, and other platforms into integrated reporting and analytics solutions. - Serves as an active member of the Data and CRM governance teams, helping establish and maintain shared definitions, data standards, documentation, access practices, and policies that support trusted museum-wide reporting. - Partners with CRM stakeholders to improve data capture and business processes that affect reporting and analytics, and provides technical guidance and training on the effective use of analytical tools. - Maintains strong working relationships with colleagues in advancement and other stakeholders, prioritizes analytical requests in coordination with the Data team, and communicates technical findings, limitations, and recommendations clearly to technical and non-technical audiences. Now Requirements section: The text after "Requirements". Let's capture: "Bachelor’s degree preferred or equivalent work experience. Three (3) years of experience in business intelligence, reporting, data analysis, analytics, or a related field. Experience with nonprofit fundraising or membership data is preferred. Strong SQL skills and experience working with relational databases; experience with data warehouses and integrated enterprise data is preferred. Demonstrated experience designing and building dashboards and reports using Power BI, Tableau, or similar tools, including data modeling, metric definition, visualization, and quality assurance. Experience with Python, R, or similar analytical tools and practical experience building, validating, or maintaining predictive analytics or machine learning models. Experience with CRM systems and a working knowledge of fundraising, membership, marketing, or constituent data. Experience with Tessitura or another nonprofit-specific CRM is preferred. Strong analytical and problem-solving skills, with the ability to translate business questions into technical requirements and explain results, assumptions, and limitations to non-technical audiences. Demonstrated ability to use generative AI and large language model (LLM) tools effectively and responsibly to support analytics, coding, research, documentation, and other work processes, with appropriate attention to data privacy, accuracy, validation, and organizational policies. Proven commitment to data quality, documentation, governance, privacy, and responsible handling of highly sensitive confidential information. Ability to work collaboratively with diverse individuals across the museum and community, manage multiple priorities, and work independently while knowing when to seek additional information or guidance. Strong proficiency with Excel and standard Microsoft Office applications; experience with version control, APIs, ETL/data integration, or other modern data tools is a plus." Then Ada Requirements: "Ada Requirements Must be able to perform work in indoor environment, review detailed documents, and view computer monitor. Must be able to communicate extensively via telephone, one-on-one conversations and public presentations in planning and execution of work. Must be able to handle heavy keyboard and calculator use, and process large volumes of paperwork. Requires the ability to sit or to stand for extended periods of time, lift up to 30 lbs; and tolerate dust in the environment and negotiate local and regional travel." We can incorporate Ada Requirements into Requirements as additional list items, maybe under a subheading? But we only have headings for sections; we could just add them as list items under Requirements. Thus Requirements list items: - Bachelor’s degree preferred or equivalent work experience. - Three (3) years of experience in business intelligence, reporting, data analysis, analytics, or a related field. Experience with nonprofit fundraising or membership data is preferred. - Strong SQL skills and experience working with relational databases; experience with data warehouses and integrated enterprise data is preferred. - Demonstrated experience designing and building dashboards and reports using Power BI, Tableau, or similar tools, including data modeling, metric definition, visualization, and quality assurance. - Experience with Python, R, or similar analytical tools and practical experience building, validating, or maintaining predictive analytics or machine learning models. - Experience with CRM systems and a working knowledge of fundraising, membership, marketing, or constituent data. Experience with Tessitura or another nonprofit-specific CRM is preferred. - Strong analytical and problem-solving skills, with the ability to translate business questions into technical requirements and explain results, assumptions, and limitations to non-technical audiences. - Demonstrated ability to use generative AI and large language model (LLM) tools effectively and responsibly to support analytics, coding, research, documentation, and other work processes, with appropriate attention to data privacy, accuracy, validation, and organizational policies. - Proven commitment to data quality, documentation, governance, privacy, and responsible handling of highly sensitive confidential information. - Ability to work collaboratively with diverse individuals across the museum and community, manage multiple priorities, and work independently while knowing when to seek additional information or guidance. - Strong proficiency with Excel and standard Microsoft Office applications; experience with version control, APIs, ETL/data integration, or other modern data tools is a plus. - Must be able to perform work in indoor environment, review detailed documents, and view computer monitor. - Must be able to communicate extensively via telephone, one-on-one conversations and public presentations in planning and execution of work. - Must be able to handle heavy keyboard and calculator use, and process large volumes of paperwork. - Requires the ability to sit or to stand for extended periods of time, lift up to 30 lbs; and tolerate dust in the environment and negotiate local and regional travel. We should ensure no duplication. The Ada Requirements lines start with "Must be able to..." etc. We'll keep them. Now we need to output only HTML fragment. No extra text. Let's craft:
About the role
Overview paragraph...
REPORTS TO: Business Intelligence Data Architect, IIT
Responsibilities
- ...
Requirements
- . Also includes "Bachelor’s degree preferred or equivalent work experience." etc.
- There's also "Ada Requirements" (Americans with Disabilities Act) which is about physical requirements. Could be considered under Requirements or maybe a separate section? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Ada Requirements could be part of Requirements (physical). We'll include under Requirements.
- There's no explicit Benefits, Pay, Schedule mentioned. So we should not create those sections.
- There's no Qualifications separate from Requirements; but we could treat Requirements as qualifications. We'll just have Requirements.
- Skills: maybe we could extract skills from requirements (SQL, Power BI, etc.) but we already have them in Requirements. The instruction says prefer a few substantive sections over many thin ones. So we can combine skills into Requirements or maybe have a Skills section. But we have to avoid thin sections. Since we already have Requirements covering skills, we can omit separate Skills.
- No Benefits, Pay, Schedule.
Thus output: