Data Analyst II
for section headings. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Remove boilerplate. Preserve all substantive info.
We need to parse the posting:
"EA is seeking a Data Analyst II to join our team. In this role, you’ll work with complex education data throughout the analytical process, from integrating and preparing data to applying statistical methods and developing data products. You’ll use data from school districts and state agencies to answer complex analytical, research, and policy questions, build reliable analytical workflows, and create tools and visualizations that support our partners. You’ll also have opportunities to collaborate across teams and directly with education partners, helping translate complex data, technical, and policy needs into clear and practical solutions. Depending on project needs, you may work with partners to clarify analytical questions, assess relevant data sources, explain technical considerations and findings, and help guide analytical work from initial exploration through delivery. 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 Data Analysts, Research Analysts, Data Scientists, Analytics Engineers, BI Analysts, education data specialists, or in similar roles involving technical data analysis and the development of analytical products to apply."
Then "Requirements" heading in posting: list bullet points.
Then "Qualifications" heading: bullet points.
We need to produce sections: About the role (maybe first paragraph summarizing role). Responsibilities (maybe the tasks described). Requirements (list). Qualifications (list). Skills (maybe combine requirements? but we could list technical skills as a separate section). However we must not create sections with filler. If we have overlapping content, we could put skills under Requirements or Qualifications. But we can create a Skills section if we have specific skill list: proficiency with statistical programming language (R/Python), SQL, statistical modeling, education data standards, BI tools (Apache Superset), Git/GitHub, dbt, Databricks, BigQuery, Looker, organizational/time-management, communication. Those are skills. The Requirements section already lists many of those. The Qualifications lists degree and experience. So we could have sections: About the role (prose), Responsibilities (maybe we can extract duties: integrate/prepare data, apply statistical methods, develop data products, answer analytical/research/policy questions, build workflows, create tools/visualizations, collaborate across teams, translate data/technical/policy needs, clarify analytical questions, assess data sources, explain considerations/findings, guide analytical work). That seems like responsibilities.
Then Requirements (list of technical proficiencies). Then Qualifications (list of education/experience). Then Skills (maybe we can combine but we could also omit if redundant). However instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Skills into one Requirements section? But they ask to use headings for Skills if we have content. Could we have Requirements (technical) and Qualifications (education/experience) and maybe Skills (soft skills). Let's see: The posting includes "Strong organizational and time-management skills..." and "Strong communication skills..." under Requirements? Actually those appear after the list of technical requirements, still under Requirements heading? In the posting, after the bullet list of technical requirements, there is a paragraph: "Strong organizational and time-management skills, with the ability to prioritize multiple responsibilities in a fast-paced environment with limited direction. Strong communication skills, including the ability to explain complex data, analytical methods, and technical concepts clearly to both technical and non-technical audiences." That is still part of Requirements? It appears after the bullet list but before Qualifications heading. So we could treat those as part of Requirements (soft skills). So we could have Requirements section containing both technical and soft skills as a list.
Qualifications section: degree and experience.
Thus we may not need a separate Skills section.
We need About the role: maybe first paragraph(s) describing role.
Responsibilities: maybe the bullet list of duties? But we already used bullet list for requirements. However we could treat the description of tasks as responsibilities.
Let's extract responsibilities from the description: "work with complex education data throughout the analytical process, from integrating and preparing data to applying statistical methods and developing data products." "use data from school districts and state agencies to answer complex analytical, research, and policy questions, build reliable analytical workflows, and create tools and visualizations that support our partners." "have opportunities to collaborate across teams and directly with education partners, helping translate complex data, technical, and policy needs into clear and practical solutions." "Depending on project needs, you may work with partners to clarify analytical questions, assess relevant data sources, explain technical considerations and findings, and help guide analytical work from initial exploration through delivery."
We can turn those into a
- list.
Now About the role: maybe a short paragraph summarizing the role: "EA is seeking a Data Analyst II to join our team. In this role, you’ll work with complex education data throughout the analytical process, from integrating and preparing data to applying statistical methods and developing data products. You’ll use data from school districts and state agencies to answer complex analytical, research, and policy questions, build reliable analytical workflows, and create tools and visualizations that support our partners. You’ll also have opportunities to collaborate across teams and directly with education partners, helping translate complex data, technical, and policy needs into clear and practical solutions." That's basically same as responsibilities. But we need to avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we can keep both About the role and Responsibilities, but they may overlap. However we could combine them: maybe About the role is a brief overview, Responsibilities is detailed list. That's okay.
We must not repeat the job title as heading. So we will not have
Data Analyst II
. We'll have headings: About the role, Responsibilities, Requirements, Qualifications.
We must not include Benefits, Pay, Schedule sections because not present.
Now we need to output only HTML fragment, no /, no markdown fences.
Let's craft:
About the role
EA is seeking a Data Analyst II to join our team. In this role, you’ll work with complex education data throughout the analytical process, from integrating and preparing data to applying statistical methods and developing data products. You’ll use data from school districts and state agencies to answer complex analytical, research, and policy questions, build reliable analytical workflows, and create tools and visualizations that support our partners. You’ll also have opportunities to collaborate across teams and directly with education partners, helping translate complex data, technical, and policy needs into clear and practical solutions.
Responsibilities
- Work with complex education data throughout the analytical process: integrate and prepare data, apply statistical methods, develop data products.
- Use data from school districts and state agencies to answer complex analytical, research, and policy questions.
- Build reliable analytical workflows and create tools and visualizations that support partners.
- Collaborate across teams and directly with education partners to translate complex data, technical, and policy needs into clear and practical solutions.
- Depending on project needs, work with partners to clarify analytical questions, assess relevant data sources, explain technical considerations and findings, and help guide analytical work from initial exploration through delivery.
Requirements
- Proficiency with a statistical programming language, such as R or Python, including functional programming, commonly used data‑processing packages, and development of clear, maintainable analytical code.
- Working proficiency with SQL, including the ability to write, interpret, and debug complex queries in a cloud data warehouse environment (e.g., Snowflake).
- Understanding of statistical modeling techniques such as linear regression, logistic regression, and machine learning is desired.
- Familiarity with education data standards such as Ed-Fi, or demonstrated ability to learn and apply complex data standards and business rules.
- Experience working with business intelligence tools, with Apache Superset preferred.
- Comfort working in an evolving technical environment and adopting new tools, including AI‑assisted technologies, to improve efficiency and quality of analytical work.
- Experience using Git and GitHub for version control and collaborative development.
- Experience with dbt is a plus.
- Experience with other modern data and analytics tools, such as Databricks, BigQuery, or Looker, is relevant and welcome.
- Strong organizational and time‑management skills, with the ability to prioritize multiple responsibilities in a fast‑paced environment with limited direction.
- Strong communication skills, including the ability to explain complex data, analytical methods, and technical concepts clearly to both technical and non‑technical audiences.
Qualifications
- Minimum bachelor’s degree or equivalent relevant experience in Statistics, Economics, Computer Science, Mathematics, Data Science, or a related field.
- At least one year of relevant professional experience in a Data Analyst or related role, including progressively independent analytical work.
We should ensure no extra whitespace issues. Output exactly as HTML fragment.
Check for any boilerplate removed: we removed remote work mention? Actually remote work mention is in the description: "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 substantive info about location/remote. Should we include? It's not in any of the sections we have. Could add a short paragraph under About the role or Responsibilities? It's about work location. Could be part of About the role. We could add a sentence: "This position is based on-site at EA’s downtown Madison, WI office, with remote work possible for candidates with substantial relevant experience." That is substantive. We should preserve it. Let's incorporate into About the role paragraph.
Also "Candidates may come from a variety of professional backgrounds. We encourage applicants with experience as Data Analysts, Research Analysts, Data Scientists, Analytics Engineers, BI Analysts, education data specialists, or in similar roles involving technical data analysis and the development of analytical products to apply." That's also substantive, maybe under About the role or Responsibilities. Could add to About the role.
We need to preserve all substantive info. So we should incorporate those details.
Let's rewrite About the role to include location, remote, encouragement.
About the role paragraph: "EA is seeking a Data Analyst II to join our team. In this role, you’ll work with complex education data throughout the analytical process, from integrating and preparing data to applying statistical methods and developing data products. You’ll use data from school districts and state agencies to answer complex analytical, research, and policy questions, build reliable analytical workflows, and create tools and visualizations that support our partners. You’ll also have opportunities to collaborate across teams and directly with education partners, helping translate complex data, technical, and policy needs into clear and practical solutions. Depending on project needs, you may work with partners to clarify analytical questions, assess relevant data sources, explain technical considerations and findings, and help guide analytical work from initial exploration through delivery. This position is
for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Remove boilerplate. Preserve all substantive info. We need to parse the posting: "EA is seeking a Data Analyst II to join our team. In this role, you’ll work with complex education data throughout the analytical process, from integrating and preparing data to applying statistical methods and developing data products. You’ll use data from school districts and state agencies to answer complex analytical, research, and policy questions, build reliable analytical workflows, and create tools and visualizations that support our partners. You’ll also have opportunities to collaborate across teams and directly with education partners, helping translate complex data, technical, and policy needs into clear and practical solutions. Depending on project needs, you may work with partners to clarify analytical questions, assess relevant data sources, explain technical considerations and findings, and help guide analytical work from initial exploration through delivery. 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 Data Analysts, Research Analysts, Data Scientists, Analytics Engineers, BI Analysts, education data specialists, or in similar roles involving technical data analysis and the development of analytical products to apply." Then "Requirements" heading in posting: list bullet points. Then "Qualifications" heading: bullet points. We need to produce sections: About the role (maybe first paragraph summarizing role). Responsibilities (maybe the tasks described). Requirements (list). Qualifications (list). Skills (maybe combine requirements? but we could list technical skills as a separate section). However we must not create sections with filler. If we have overlapping content, we could put skills under Requirements or Qualifications. But we can create a Skills section if we have specific skill list: proficiency with statistical programming language (R/Python), SQL, statistical modeling, education data standards, BI tools (Apache Superset), Git/GitHub, dbt, Databricks, BigQuery, Looker, organizational/time-management, communication. Those are skills. The Requirements section already lists many of those. The Qualifications lists degree and experience. So we could have sections: About the role (prose), Responsibilities (maybe we can extract duties: integrate/prepare data, apply statistical methods, develop data products, answer analytical/research/policy questions, build workflows, create tools/visualizations, collaborate across teams, translate data/technical/policy needs, clarify analytical questions, assess data sources, explain considerations/findings, guide analytical work). That seems like responsibilities. Then Requirements (list of technical proficiencies). Then Qualifications (list of education/experience). Then Skills (maybe we can combine but we could also omit if redundant). However instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Skills into one Requirements section? But they ask to use headings for Skills if we have content. Could we have Requirements (technical) and Qualifications (education/experience) and maybe Skills (soft skills). Let's see: The posting includes "Strong organizational and time-management skills..." and "Strong communication skills..." under Requirements? Actually those appear after the list of technical requirements, still under Requirements heading? In the posting, after the bullet list of technical requirements, there is a paragraph: "Strong organizational and time-management skills, with the ability to prioritize multiple responsibilities in a fast-paced environment with limited direction. Strong communication skills, including the ability to explain complex data, analytical methods, and technical concepts clearly to both technical and non-technical audiences." That is still part of Requirements? It appears after the bullet list but before Qualifications heading. So we could treat those as part of Requirements (soft skills). So we could have Requirements section containing both technical and soft skills as a list. Qualifications section: degree and experience. Thus we may not need a separate Skills section. We need About the role: maybe first paragraph(s) describing role. Responsibilities: maybe the bullet list of duties? But we already used bullet list for requirements. However we could treat the description of tasks as responsibilities. Let's extract responsibilities from the description: "work with complex education data throughout the analytical process, from integrating and preparing data to applying statistical methods and developing data products." "use data from school districts and state agencies to answer complex analytical, research, and policy questions, build reliable analytical workflows, and create tools and visualizations that support our partners." "have opportunities to collaborate across teams and directly with education partners, helping translate complex data, technical, and policy needs into clear and practical solutions." "Depending on project needs, you may work with partners to clarify analytical questions, assess relevant data sources, explain technical considerations and findings, and help guide analytical work from initial exploration through delivery." We can turn those into a
- list.
Now About the role: maybe a short paragraph summarizing the role: "EA is seeking a Data Analyst II to join our team. In this role, you’ll work with complex education data throughout the analytical process, from integrating and preparing data to applying statistical methods and developing data products. You’ll use data from school districts and state agencies to answer complex analytical, research, and policy questions, build reliable analytical workflows, and create tools and visualizations that support our partners. You’ll also have opportunities to collaborate across teams and directly with education partners, helping translate complex data, technical, and policy needs into clear and practical solutions." That's basically same as responsibilities. But we need to avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we can keep both About the role and Responsibilities, but they may overlap. However we could combine them: maybe About the role is a brief overview, Responsibilities is detailed list. That's okay.
We must not repeat the job title as heading. So we will not have
Data Analyst II
. We'll have headings: About the role, Responsibilities, Requirements, Qualifications. We must not include Benefits, Pay, Schedule sections because not present. Now we need to output only HTML fragment, no /, no markdown fences. Let's craft:About the role
EA is seeking a Data Analyst II to join our team. In this role, you’ll work with complex education data throughout the analytical process, from integrating and preparing data to applying statistical methods and developing data products. You’ll use data from school districts and state agencies to answer complex analytical, research, and policy questions, build reliable analytical workflows, and create tools and visualizations that support our partners. You’ll also have opportunities to collaborate across teams and directly with education partners, helping translate complex data, technical, and policy needs into clear and practical solutions.
Responsibilities
- Work with complex education data throughout the analytical process: integrate and prepare data, apply statistical methods, develop data products.
- Use data from school districts and state agencies to answer complex analytical, research, and policy questions.
- Build reliable analytical workflows and create tools and visualizations that support partners.
- Collaborate across teams and directly with education partners to translate complex data, technical, and policy needs into clear and practical solutions.
- Depending on project needs, work with partners to clarify analytical questions, assess relevant data sources, explain technical considerations and findings, and help guide analytical work from initial exploration through delivery.
Requirements
- Proficiency with a statistical programming language, such as R or Python, including functional programming, commonly used data‑processing packages, and development of clear, maintainable analytical code.
- Working proficiency with SQL, including the ability to write, interpret, and debug complex queries in a cloud data warehouse environment (e.g., Snowflake).
- Understanding of statistical modeling techniques such as linear regression, logistic regression, and machine learning is desired.
- Familiarity with education data standards such as Ed-Fi, or demonstrated ability to learn and apply complex data standards and business rules.
- Experience working with business intelligence tools, with Apache Superset preferred.
- Comfort working in an evolving technical environment and adopting new tools, including AI‑assisted technologies, to improve efficiency and quality of analytical work.
- Experience using Git and GitHub for version control and collaborative development.
- Experience with dbt is a plus.
- Experience with other modern data and analytics tools, such as Databricks, BigQuery, or Looker, is relevant and welcome.
- Strong organizational and time‑management skills, with the ability to prioritize multiple responsibilities in a fast‑paced environment with limited direction.
- Strong communication skills, including the ability to explain complex data, analytical methods, and technical concepts clearly to both technical and non‑technical audiences.
Qualifications
- Minimum bachelor’s degree or equivalent relevant experience in Statistics, Economics, Computer Science, Mathematics, Data Science, or a related field.
- At least one year of relevant professional experience in a Data Analyst or related role, including progressively independent analytical work.