Data Analyst II-Business Analyst Focus
Tech Jobs for Good · Madison, WI · 1 mo ago
AnalystFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills?, Benefits?, Pay?, Schedule? Only include sections if posting has real specific content.
We need to parse the posting.
Content:
- Intro about role: "EA is seeking a Data Analyst II (Business Analyst Focus) to join our team. In this role, you’ll connect partner and user needs to data, analytics, and technical solutions. You’ll work to understand the questions education leaders are trying to answer, translate those needs into clear data definitions and analytic requirements, and help ensure that reports, dashboards, and data products provide meaningful and useful information. You’ll work closely with education partners, analysts, engineers, and other technical teams throughout the analytic process. Depending on project needs, you may conduct partner discovery, define and document analytic requirements, map source data to reporting concepts, investigate data quality, develop technical specifications, mock up reports or dashboards, and help guide projects from initial problem definition through delivery. This is a newer role type at EA that builds on our existing technical analytics work with greater emphasis on user needs, data definitions, analytic requirements, and the connection between data systems and how information is ultimately used. People in this role will have opportunities to help shape how this work develops at EA. EA will consider candidates with a range of experience and qualifications for placement at the Data Analyst I, Data Analyst II, or Senior Data Analyst level. The level and responsibilities will be determined based on the candidate’s experience, skills, and demonstrated capabilities. This position is based on-site at EA’s downtown Madison, WI office. Remote work may be considered for candidates with substantial relevant experience."
That's about the role.
Then "Candidates may come from a variety of professional backgrounds. We encourage applicants with experience as Business Analysts, Data Analysts, BI Analysts, BI Developers, Data Scientists, education data specialists, or in similar roles that combine technical data work with understanding and translating user needs to apply."
Then "Requirements" list bullet points.
Then "Qualifications" list bullet points.
We need to extract sections: About the role (maybe heading "About the role"), Responsibilities (maybe we can treat the description of duties as responsibilities), Requirements, Qualifications, Skills? The posting includes skills within requirements (SQL, etc). Could combine into Requirements or Skills. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include only those with real content.
We have content for About the role (intro). Responsibilities: we have duties like "conduct partner discovery, define and document analytic requirements, map source data to reporting concepts, investigate data quality, develop technical specifications, mock up reports or dashboards, and help guide projects from initial problem definition through delivery." Also earlier tasks: "connect partner and user needs to data, analytics, and technical solutions. You’ll work to understand the questions education leaders are trying to answer, translate those needs into clear data definitions and analytic requirements, and help ensure that reports, dashboards, and data products provide meaningful and useful information. You’ll work closely with education partners, analysts, engineers, and other technical teams throughout the analytic process." So we can put responsibilities.
Requirements: list bullet points: "Experience turning broad or ambiguous requests into clear questions, data definitions, analytic requirements, and technical specifications, and communicating those needs across technical and non-technical audiences. Experience investigating complex data sources, assessing data quality, and determining how data should be mapped, combined, transformed, and interpreted for reporting and analytics. Working proficiency with SQL, including the ability to write, interpret, and debug complex queries in a cloud data warehouse environment, such as Snowflake. Familiarity with education data standards such as Ed-Fi, or demonstrated ability to learn and apply complex data standards, definitions, and reporting rules. Experience working with business intelligence, reporting, or data visualization tools and engaging in the mockup phase, with Apache Superset and Figma experience preferred. Experience using a statistical programming language to investigate, process, or validate data, with R or Python preferred. Experience using Git and GitHub for version control and collaborative development. Comfort working in an evolving technical environment and adopting new tools, including AI-assisted technologies, to improve the efficiency and quality of analytical work. Strong organizational and time-management skills, with the ability to prioritize multiple responsibilities in a fast-paced environment with limited direction."
Qualifications: bullet points: "Minimum bachelor’s degree or equivalent relevant experience in Statistics, Economics, Computer Science, Mathematics, Data Science, Information Systems, Public Policy, Education, or a related field. At least one year of relevant professional experience, including progressively independent work with data, analytics, technical requirements, or data products. Familiarity with K–12 education data, state or district reporting, or education data standards is helpful but not required."
Also there is mention of location and remote work: "This position is based on-site at EA’s downtown Madison, WI office. Remote work may be considered for candidates with substantial relevant experience." That could be part of About the role or maybe a separate section like "Location" but not in allowed headings. Could embed in About the role paragraph.
We should not include Benefits, Pay, Schedule as not present.
We need to output HTML fragment only, no /. Use for headings. Use
for headings. Use - for lists. Use
for prose.
We must not repeat job title as heading. So no heading for "Data Analyst II". Good.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep all details.
We need to avoid boilerplate like EEO etc. Not present.
We need to remove duplicated lines.
Let's craft sections:
About the role
EA is seeking a Data Analyst II (Business Analyst Focus) to join our team. In this role, you’ll connect partner and user needs to data, analytics, and technical solutions. You’ll work to understand the questions education leaders are trying to answer, translate those needs into clear data definitions and analytic requirements, and help ensure that reports, dashboards, and data products provide meaningful and useful information. You’ll work closely with education partners, analysts, engineers, and other technical teams throughout the analytic process. Depending on project needs, you may conduct partner discovery, define and document analytic requirements, map source data to reporting concepts, investigate data quality, develop technical specifications, mock up reports or dashboards, and help guide projects from initial problem definition through delivery. This is a newer role type at EA that builds on our existing technical analytics work with greater emphasis on user needs, data definitions, analytic requirements, and the connection between data systems and how information is ultimately used. People in this role will have opportunities to help shape how this work develops at EA. EA will consider candidates with a range of experience and qualifications for placement at the Data Analyst I, Data Analyst II, or Senior Data Analyst level. The level and responsibilities will be determined based on the candidate’s experience, skills, and demonstrated capabilities. This position is based on-site at EA’s downtown Madison, WI office. Remote work may be considered for candidates with substantial relevant experience.
Then maybe a paragraph about encouraged backgrounds: "Candidates may come from a variety of professional backgrounds. We encourage applicants with experience as Business Analysts, Data Analysts, BI Analysts, BI Developers, Data Scientists, education data specialists, or in similar roles that combine technical data work with understanding and translating user needs to apply." Could be part of About the role or separate? Could be part of About the role as well. Probably include in About the role.
Thus combine.
Then Responsibilities: we can list bullet points of duties.
But we already included many duties in About the role. To avoid duplication, we could separate: About the role includes general description; Responsibilities includes specific duties list.
Let's extract responsibilities list:
- Connect partner and user needs to data, analytics, and technical solutions.
- Understand the questions education leaders are trying to answer.
- Translate those needs into clear data definitions and analytic requirements.
- Help ensure that reports, dashboards, and data products provide meaningful and useful information.
- Work closely with education partners, analysts, engineers, and other technical teams throughout the analytic process.
- Conduct partner discovery.
- Define and document analytic requirements.
- Map source data to reporting concepts.
- Investigate data quality.
- Develop technical specifications.
- Mock up reports or dashboards.
- Help guide projects from initial problem definition through delivery.
We can put these as - .
Then Requirements: list bullet points as given.
Then Qualifications: list bullet points.
We need to ensure we don't repeat content. The About the role paragraph already includes some of those responsibilities; but we can keep them both? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we duplicate, that's okay as long as we preserve. But better to avoid duplication? Not required but could be okay. However duplication might be considered redundant but not invented. It's okay to repeat? Might be considered unnecessary but not violating. Safer to not duplicate: we can keep About the role as high-level overview, and Responsibilities as detailed list. Ensure we don't omit any detail.
Let's craft About the role paragraph that includes high-level but not the detailed list; we can keep the earlier sentences up to "Depending on project needs, you may conduct partner discovery, define and document analytic requirements, map source data to reporting concepts, investigate data quality, develop technical specifications, mock up reports or dashboards, and help guide projects from initial problem definition through delivery." That's actually the detailed list. If we move that to Responsibilities, we should remove from About the role. So About the role will be more generic: connecting partner/user needs, understanding questions, translating needs, ensuring reports useful, working closely with teams, role newer, opportunities to shape, level determination, location/remote.
Let's craft About the role paragraph:
"EA is seeking a Data Analyst II (Business Analyst Focus) to join our team. In this role, you’ll connect partner and user needs to data, analytics, and technical solutions. You’ll work to understand the questions education leaders are trying to answer, translate those needs into clear data definitions and analytic requirements, and help ensure that reports, dashboards, and data products provide meaningful and useful information. You’ll work closely with education partners, analysts, engineers, and other technical teams throughout the analytic process. This is a newer role type at EA that builds on our existing technical analytics work with greater emphasis on user needs, data definitions, analytic requirements, and the connection between data systems and how information is ultimately used. People in this role will have opportunities to help shape how this work develops at EA. EA will consider candidates with a range of experience and qualifications for placement at the Data Analyst I, Data Analyst II, or Senior Data Analyst level. The level and responsibilities will be determined based on the candidate’s experience, skills, and demonstrated capabilities. This position is based on-site at EA’s downtown Madison, WI office. Remote work may be considered for candidates with substantial relevant experience. Candidates may come from a variety of professional backgrounds. We encourage applicants with experience as Business Analysts, Data Analysts, BI Analysts, BI Developers, Data Scientists, education data specialists, or in similar roles that combine technical data work with understanding and translating user needs to apply."
That covers all generic.
Now Responsibilities list as bullet points (the detailed list). Ensure we include all items from the "Depending on project needs" sentence plus maybe also the earlier tasks? Already covered.
Let's list:
- Conduct partner discovery
- Define and document analytic requirements
- Map source data to reporting concepts
- Investigate data quality
- Develop technical specifications
- Mock up reports or dashboards
- Help guide projects from initial problem definition through delivery
Also maybe include "Connect partner and user needs to data, analytics, and technical solutions" etc but that's in About. We'll keep as is.
Now Requirements list bullet points as given.
Now Qualifications list bullet points.
Now output HTML.
Make sure to use
for each section heading.
We'll output:
About the role
...
Responsibilities
for prose. We must not repeat job title as heading. So no heading for "Data Analyst II". Good. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep all details. We need to avoid boilerplate like EEO etc. Not present. We need to remove duplicated lines. Let's craft sections:
About the role
EA is seeking a Data Analyst II (Business Analyst Focus) to join our team. In this role, you’ll connect partner and user needs to data, analytics, and technical solutions. You’ll work to understand the questions education leaders are trying to answer, translate those needs into clear data definitions and analytic requirements, and help ensure that reports, dashboards, and data products provide meaningful and useful information. You’ll work closely with education partners, analysts, engineers, and other technical teams throughout the analytic process. Depending on project needs, you may conduct partner discovery, define and document analytic requirements, map source data to reporting concepts, investigate data quality, develop technical specifications, mock up reports or dashboards, and help guide projects from initial problem definition through delivery. This is a newer role type at EA that builds on our existing technical analytics work with greater emphasis on user needs, data definitions, analytic requirements, and the connection between data systems and how information is ultimately used. People in this role will have opportunities to help shape how this work develops at EA. EA will consider candidates with a range of experience and qualifications for placement at the Data Analyst I, Data Analyst II, or Senior Data Analyst level. The level and responsibilities will be determined based on the candidate’s experience, skills, and demonstrated capabilities. This position is based on-site at EA’s downtown Madison, WI office. Remote work may be considered for candidates with substantial relevant experience.
Then maybe a paragraph about encouraged backgrounds: "Candidates may come from a variety of professional backgrounds. We encourage applicants with experience as Business Analysts, Data Analysts, BI Analysts, BI Developers, Data Scientists, education data specialists, or in similar roles that combine technical data work with understanding and translating user needs to apply." Could be part of About the role or separate? Could be part of About the role as well. Probably include in About the role. Thus combine. Then Responsibilities: we can list bullet points of duties. But we already included many duties in About the role. To avoid duplication, we could separate: About the role includes general description; Responsibilities includes specific duties list. Let's extract responsibilities list: - Connect partner and user needs to data, analytics, and technical solutions. - Understand the questions education leaders are trying to answer. - Translate those needs into clear data definitions and analytic requirements. - Help ensure that reports, dashboards, and data products provide meaningful and useful information. - Work closely with education partners, analysts, engineers, and other technical teams throughout the analytic process. - Conduct partner discovery. - Define and document analytic requirements. - Map source data to reporting concepts. - Investigate data quality. - Develop technical specifications. - Mock up reports or dashboards. - Help guide projects from initial problem definition through delivery. We can put these as- .
Then Requirements: list bullet points as given.
Then Qualifications: list bullet points.
We need to ensure we don't repeat content. The About the role paragraph already includes some of those responsibilities; but we can keep them both? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we duplicate, that's okay as long as we preserve. But better to avoid duplication? Not required but could be okay. However duplication might be considered redundant but not invented. It's okay to repeat? Might be considered unnecessary but not violating. Safer to not duplicate: we can keep About the role as high-level overview, and Responsibilities as detailed list. Ensure we don't omit any detail.
Let's craft About the role paragraph that includes high-level but not the detailed list; we can keep the earlier sentences up to "Depending on project needs, you may conduct partner discovery, define and document analytic requirements, map source data to reporting concepts, investigate data quality, develop technical specifications, mock up reports or dashboards, and help guide projects from initial problem definition through delivery." That's actually the detailed list. If we move that to Responsibilities, we should remove from About the role. So About the role will be more generic: connecting partner/user needs, understanding questions, translating needs, ensuring reports useful, working closely with teams, role newer, opportunities to shape, level determination, location/remote.
Let's craft About the role paragraph:
"EA is seeking a Data Analyst II (Business Analyst Focus) to join our team. In this role, you’ll connect partner and user needs to data, analytics, and technical solutions. You’ll work to understand the questions education leaders are trying to answer, translate those needs into clear data definitions and analytic requirements, and help ensure that reports, dashboards, and data products provide meaningful and useful information. You’ll work closely with education partners, analysts, engineers, and other technical teams throughout the analytic process. This is a newer role type at EA that builds on our existing technical analytics work with greater emphasis on user needs, data definitions, analytic requirements, and the connection between data systems and how information is ultimately used. People in this role will have opportunities to help shape how this work develops at EA. EA will consider candidates with a range of experience and qualifications for placement at the Data Analyst I, Data Analyst II, or Senior Data Analyst level. The level and responsibilities will be determined based on the candidate’s experience, skills, and demonstrated capabilities. This position is based on-site at EA’s downtown Madison, WI office. Remote work may be considered for candidates with substantial relevant experience. Candidates may come from a variety of professional backgrounds. We encourage applicants with experience as Business Analysts, Data Analysts, BI Analysts, BI Developers, Data Scientists, education data specialists, or in similar roles that combine technical data work with understanding and translating user needs to apply."
That covers all generic.
Now Responsibilities list as bullet points (the detailed list). Ensure we include all items from the "Depending on project needs" sentence plus maybe also the earlier tasks? Already covered.
Let's list:
- Conduct partner discovery
- Define and document analytic requirements
- Map source data to reporting concepts
- Investigate data quality
- Develop technical specifications
- Mock up reports or dashboards
- Help guide projects from initial problem definition through delivery
Also maybe include "Connect partner and user needs to data, analytics, and technical solutions" etc but that's in About. We'll keep as is.
Now Requirements list bullet points as given.
Now Qualifications list bullet points.
Now output HTML.
Make sure to use
for each section heading. We'll output:
About the role
...
Responsibilities