Managing Director, Data & Systems
Breakthrough Public Schools · Cleveland, OH · 4 wk ago
HybridFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes description about organization and opportunity. We need to use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invented or summarized away detail. Remove boilerplate: EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Also remove cookie/navigation/legal.
We need to parse the posting: It starts with "BREAKTHROUGH PUBLIC SCHOOLSBreakthrough Public Schools is a nationally recognized Charter Management Organization (CMO) network in Ohio..." That's about the organization. Then "OPPORTUNITY Breakthrough Public Schools seeks an experienced and visionary leader to serve as Managing Director of Data & Systems. Reporting to the Chief of Staff and serving on the network’s Extended Leadership Team, the MD will drive the organization’s data strategy, systems infrastructure, and analytics to advance Breakthrough’s mission and goals. The MD, Data & Systems will oversee all aspects of data collection, analysis, reporting, and systems management, ensuring accurate, actionable information is used to inform decision-making, improve academic outcomes, and ensure organizational accountability. This leader will also own the design and implementation of scalable systems and tools that enable operational excellence across the network. Ideal candidates will bring a creative, solutions-oriented mindset, expertise in building robust data systems and infrastructure, and a deep belief that every child deserves a joyful, rigorous, and equitable education."
Then "ROLES & RESPONSIBILITIES" with subheadings: Strategic Planning, Data Analytics, Systems Management, Team Oversight. Under each bullet points.
Then "QUALIFICATIONS" with subheadings: Strategic Leadership, Organizational & Technical Effectiveness, Personal Effectiveness & Mission Alignment.
Then "EDUCATION AND EXPERIENCE" with bullet points.
Then "Breakthrough Public Schools is an equal opportunity employer..." which is boilerplate to remove.
Also there is a line about falsification etc, also boilerplate.
We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have content for About the role (organization description and opportunity). Responsibilities (the ROLES & RESPONSIBILITIES). Requirements maybe combine QUALIFICATIONS and EDUCATION AND EXPERIENCE? The spec says we can have Requirements and Qualifications separate. But we need to only include sections when posting has real specific content. We have qualifications content (Strategic Leadership etc). Also education and experience content. Could combine into Qualifications section (including education & experience). Or we could have Requirements (maybe education & experience) and Qualifications (the leadership etc). But we need to avoid thin sections. Let's decide: Use About the role, Responsibilities, Qualifications. Possibly Skills? The posting mentions specific skills: SQL, Stata, data automation, data modeling, cloud-based warehousing, SIS, EMIS, data governance, etc. Those are part of qualifications. Could put them under Skills section. But we already have Qualifications covering them. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which to include. We need to preserve all substantive info. If we put everything under Qualifications, we might lose distinction but still preserve. However we might want to separate Skills to avoid thin sections? But we can include Skills if we have specific skill list. The posting includes: Expertise in SQL, Stata, data automation (e.g., Apache Airflow), data modeling (e.g., dbt), and cloud-based data warehousing (e.g., Azure). Skilled in integrating multiple data sources, maintaining Student Information Systems (SIS), and managing Ohio EMIS reporting to ensure compliance and accuracy. Strong knowledge of data governance, privacy regulations, and performance optimization best practices. Proficiency with data automation tools (e.g., Apache Airflow) and data modeling tools (e.g., dbt); highly skilled in writing and maintaining complex SQL queries. Experience with student information systems (SIS) and familiarity with Ohio Department of Education data systems (including EMIS) strongly preferred.
Thus we can have a Skills section listing those. Qualifications could contain leadership, organizational effectiveness, personal effectiveness, education & experience. But we need to avoid duplication. Let's structure:
- About the role: includes organization description and opportunity paragraph.
- Responsibilities: includes the four categories with bullet points.
- Skills: list of technical skills (SQL, Stata, Apache Airflow, dbt, Azure, SIS, EMIS, data governance, etc.)
- Qualifications: includes Strategic Leadership, Organizational & Technical Effectiveness, Personal Effectiveness & Mission Alignment, Education and Experience (7+ years, DEI commitment, interpersonal skills, etc.)
We must not include Benefits, Pay, Schedule as they are not present.
We must not include Requirements if we don't have separate content; but we could treat Qualifications as Requirements. However we already have Qualifications. The spec says we can include Requirements heading if we have content. We could treat the education and experience as Requirements, and the leadership etc as Qualifications. But that may split content thinly. Let's see if we have enough for each: Education and Experience bullet points: 7+ years experience, DEI commitment, interpersonal skills, proficiency with data automation/tools, experience with SIS, familiarity with Ohio EMIS. That's a decent chunk. Could be Requirements. Then Qualifications could be the leadership/organizational/personal effectiveness. That seems reasonable.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills.
Check if any content left out: The opportunity paragraph includes ideal candidates creative solutions-oriented mindset etc. That could be part of About the role or Qualifications. We'll keep it in About the role.
Now we need to format: Use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invented or summarized away detail. Remove boilerplate: EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Also remove cookie/navigation/legal.
We need to parse the posting: It starts with "BREAKTHROUGH PUBLIC SCHOOLSBreakthrough Public Schools is a nationally recognized Charter Management Organization (CMO) network in Ohio..." That's about the organization. Then "OPPORTUNITY Breakthrough Public Schools seeks an experienced and visionary leader to serve as Managing Director of Data & Systems. Reporting to the Chief of Staff and serving on the network’s Extended Leadership Team, the MD will drive the organization’s data strategy, systems infrastructure, and analytics to advance Breakthrough’s mission and goals. The MD, Data & Systems will oversee all aspects of data collection, analysis, reporting, and systems management, ensuring accurate, actionable information is used to inform decision-making, improve academic outcomes, and ensure organizational accountability. This leader will also own the design and implementation of scalable systems and tools that enable operational excellence across the network. Ideal candidates will bring a creative, solutions-oriented mindset, expertise in building robust data systems and infrastructure, and a deep belief that every child deserves a joyful, rigorous, and equitable education."
Then "ROLES & RESPONSIBILITIES" with subheadings: Strategic Planning, Data Analytics, Systems Management, Team Oversight. Under each bullet points.
Then "QUALIFICATIONS" with subheadings: Strategic Leadership, Organizational & Technical Effectiveness, Personal Effectiveness & Mission Alignment.
Then "EDUCATION AND EXPERIENCE" with bullet points.
Then "Breakthrough Public Schools is an equal opportunity employer..." which is boilerplate to remove.
Also there is a line about falsification etc, also boilerplate.
We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have content for About the role (organization description and opportunity). Responsibilities (the ROLES & RESPONSIBILITIES). Requirements maybe combine QUALIFICATIONS and EDUCATION AND EXPERIENCE? The spec says we can have Requirements and Qualifications separate. But we need to only include sections when posting has real specific content. We have qualifications content (Strategic Leadership etc). Also education and experience content. Could combine into Qualifications section (including education & experience). Or we could have Requirements (maybe education & experience) and Qualifications (the leadership etc). But we need to avoid thin sections. Let's decide: Use About the role, Responsibilities, Qualifications. Possibly Skills? The posting mentions specific skills: SQL, Stata, data automation, data modeling, cloud-based warehousing, SIS, EMIS, data governance, etc. Those are part of qualifications. Could put them under Skills section. But we already have Qualifications covering them. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which to include. We need to preserve all substantive info. If we put everything under Qualifications, we might lose distinction but still preserve. However we might want to separate Skills to avoid thin sections? But we can include Skills if we have specific skill list. The posting includes: Expertise in SQL, Stata, data automation (e.g., Apache Airflow), data modeling (e.g., dbt), and cloud-based data warehousing (e.g., Azure). Skilled in integrating multiple data sources, maintaining Student Information Systems (SIS), and managing Ohio EMIS reporting to ensure compliance and accuracy. Strong knowledge of data governance, privacy regulations, and performance optimization best practices. Proficiency with data automation tools (e.g., Apache Airflow) and data modeling tools (e.g., dbt); highly skilled in writing and maintaining complex SQL queries. Experience with student information systems (SIS) and familiarity with Ohio Department of Education data systems (including EMIS) strongly preferred.
Thus we can have a Skills section listing those. Qualifications could contain leadership, organizational effectiveness, personal effectiveness, education & experience. But we need to avoid duplication. Let's structure:
- About the role: includes organization description and opportunity paragraph.
- Responsibilities: includes the four categories with bullet points.
- Skills: list of technical skills (SQL, Stata, Apache Airflow, dbt, Azure, SIS, EMIS, data governance, etc.)
- Qualifications: includes Strategic Leadership, Organizational & Technical Effectiveness, Personal Effectiveness & Mission Alignment, Education and Experience (7+ years, DEI commitment, interpersonal skills, etc.)
We must not include Benefits, Pay, Schedule as they are not present.
We must not include Requirements if we don't have separate content; but we could treat Qualifications as Requirements. However we already have Qualifications. The spec says we can include Requirements heading if we have content. We could treat the education and experience as Requirements, and the leadership etc as Qualifications. But that may split content thinly. Let's see if we have enough for each: Education and Experience bullet points: 7+ years experience, DEI commitment, interpersonal skills, proficiency with data automation/tools, experience with SIS, familiarity with Ohio EMIS. That's a decent chunk. Could be Requirements. Then Qualifications could be the leadership/organizational/personal effectiveness. That seems reasonable.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills.
Check if any content left out: The opportunity paragraph includes ideal candidates creative solutions-oriented mindset etc. That could be part of About the role or Qualifications. We'll keep it in About the role.
Now we need to format: Use for each section heading. Under each heading, use
for prose,
- for lists.
We must preserve all substantive information, not invent or summarize away detail. So we need to keep the exact phrasing? We should preserve the meaning but not necessarily exact wording? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the details, but we can rephrase slightly as long as we don't lose detail. Safer to keep original sentences.
We'll need to break into paragraphs and lists.
Let's extract content.
About the role:
- First paragraph: "Breakthrough Public Schools is a nationally recognized Charter Management Organization (CMO) network in Ohio. Our mission is to provide Cleveland area scholars with an education that empowers them to lead lives full of impact and opportunity. Our network of schools centers joy, curiosity, and individual growth, uniquely positioning Breakthrough Public Schools to cultivate a learning community where all students thrive. At Breakthrough, we are committed to providing scholars with the academic, social, and emotional skills necessary to excel at learning and citizenship from kindergarten through eighth-grade promotion. We are committed to the success of every child.The CMO network manages core administrative responsibilities, including human resources, finance, information technology, facilities, student recruitment, and marketing for our schools. We serve 3,000 K-8 grade scholars across ten schools and employ over 450 staff members."
- Opportunity paragraph: "Breakthrough Public Schools seeks an experienced and visionary leader to serve as Managing Director of Data & Systems. Reporting to the Chief of Staff and serving on the network’s Extended Leadership Team, the MD will drive the organization’s data strategy, systems infrastructure, and analytics to advance Breakthrough’s mission and goals. The MD, Data & Systems will oversee all aspects of data collection, analysis, reporting, and systems management, ensuring accurate, actionable information is used to inform decision-making, improve academic outcomes, and ensure organizational accountability. This leader will also own the design and implementation of scalable systems and tools that enable operational excellence across the network. Ideal candidates will bring a creative, solutions-oriented mindset, expertise in building robust data systems and infrastructure, and a deep belief that every child deserves a joyful, rigorous, and equitable education."
We can combine into one or two
elements. Responsibilities: Under heading
Responsibilities
. Then we have subheadings: Strategic Planning, Data Analytics, Systems Management, Team Oversight. Should we treat those as subheadings? The spec only mentions usingfor section headings (About the role, Responsibilities, etc). It doesn't forbid other headings, but we should follow spec: only use those headings. However we can still include the subheadings as or
maybe. But to preserve structure, we could make each responsibility area as a
- with a preceding
- ... etc. We need to preserve all bullet points. Let's list them: Strategic Planning: - Set the vision and direction for Breakthrough’s data strategy, ensuring alignment with organizational goals and growth as a network of learning organizations. - Partner with senior leadership to define key metrics, reporting priorities, and long-term strategies for data systems and analytics. - Foster a data-driven, continuous improvement culture across the network, promoting transparency and evidence-based decision-making. - Communicate data insights clearly and effectively to a range of internal and external stakeholders, including executive leadership, school teams, and the Board. Data Analytics: - Lead the design, implementation, and maintenance of dashboards and reporting systems that provide timely, accurate, and actionable data to schools, network leaders, and external partners. - Oversee the analysis of student achievement, enrollment, demographic, and operational data to support academic and organizational improvement. - Design and execute internal studies, surveys, and progress-monitoring tools to assess program effectiveness. - Provide high-quality data visualization and reporting products to empower stakeholders to make informed decisions. Systems Management: - Serve as the primary owner of the Student Information System (SIS) and ensure accurate and timely EMIS reporting to the Ohio Department of Education. - Oversee the architecture, integration, and optimization of data systems, including a centralized data warehouse and other operational platforms. - Develop and enforce data governance policies to ensure data integrity, accuracy, security, and compliance with FERPA and other privacy standards. - Identify opportunities for process improvement, recommend system modifications, and lead cross-functional initiatives to strengthen data systems and workflows. - Troubleshoot data-related issues and provide technical leadership for migration, transformation, and reporting projects. Team Oversight: - Manage and develop a team of data strategists, providing clear priorities, coaching, and professional growth opportunities. - Establish team structures and routines to deliver exceptional customer service to schools and departments. - Prioritize and allocate team resources effectively to meet organizational deadlines and data needs. - Build strong partnerships with school and network teams, ensuring consistent support for assessments, compliance, and data-informed decision-making. Now Requirements (education and experience): From "EDUCATION AND EXPERIENCE": - 7+ years of experience in data analysis, reporting, and developing actionable insights to drive organizational improvement. - Demonstrated commitment to diversity, equity, and inclusion (DEI) and experience integrating these principles into organizational practices. - Strong interpersonal, communication, and leadership skills, with a track record of building relationships and influencing across teams. - Proficiency with data automation tools (e.g., Apache Airflow) and data modeling tools (e.g., dbt); highly skilled in writing and maintaining complex SQL queries. - Experience with student information systems (SIS) and familiarity with Ohio Department of Education data systems (including EMIS) strongly preferred. We could also include the earlier line about "To perform this job successfully, an individual must be able to perform each essential duty and work strategically across teams in the network. The requirements below represent the required knowledge, skill, and/or ability. Reason
bold? The spec didn't forbid other tags, just said use
for section headings. So we can use
or for subheadings. Safer to use
Strategic Planning
then