Program Associate I - Integration Specialist, ESE Systems & Analytics

We need to output HTML fragment with sections for 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 details. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we need to extract relevant content: Position Summary, Essential Functions, Minimum Qualifications, Preferred qualifications (experience with PowerSchool etc), Benefits Eligible: Yes, Telecommuting Eligibility: Eligible for telecommuting up to 20% (one day per week). Salary range: $75,048 - $98,163. Reports to: Senior Director of ESE Systems & Analytics. Bargaining Unit: OSAS. Location: Fisher Building, 3011 W. Grand Blvd., Detroit, MI 48202. Also maybe "Security Clearance" etc but that's boilerplate? It's about internal/external applicants and security clearance; might be considered application instructions? Probably we should drop that as it's application instructions. Also "Method Of Application" etc drop. We need to decide sections: About the role (position summary). Responsibilities (Essential Functions). Requirements (Minimum Qualifications). Qualifications (maybe Preferred qualifications). Skills (maybe technical skills listed). Benefits (Benefits Eligible: Yes, Telecommuting Eligibility). Pay (Salary range). Schedule (maybe not given; we have telecommuting eligibility but not schedule like full-time/part-time; not explicit schedule. So we should not create Schedule section unless posting states it. It does not state schedule like full-time, hours. So omit Schedule. We must not include placeholder text like "commensurate with experience". Not present. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information. So we need to include location, reports to, bargaining unit, salary, benefits, telecommuting, etc. Where to put them? Could be in About the role section as prose. Or we could create a separate section like "Details" but not in allowed headings. Only allowed headings are those listed. So we must fit info into those sections. For location, reports to, bargaining unit maybe go under About the role as prose. Salary under Pay. Benefits under Benefits. Telecommuting maybe under Benefits or Schedule? Since Schedule not present, we could put telecommuting under Benefits as part of benefits. Or we could create a separate section but not allowed. So include in Benefits. We need to avoid duplication. Ensure we don't repeat same info multiple times. Let's extract: Position Summary paragraph: "The Program Associate I - Integration Specialist supports the ESE Systems & Analytics team within the Student Data & Accountability division by building and maintaining the data pipelines and system integrations that connect PowerSchool Special Programs (PSSP) to the district's broader data infrastructure. The team is responsible for the administration, integration, reporting, and end-user support of PSSP, which is the district's primary platform for special education data management, and serves as the data quality and systems bridge between the ESE division and the Student Information Services team. The Integration Specialist builds and maintains the connections between PSSP and other district systems, automates manual data movement, and develops PSSP-native operational reports. As the district works toward building MTSS infrastructure, this role will support the data connections needed to track pre-referral interventions alongside special education records. This role works in close coordination with the Program Supervisor and the Senior Director and operates as the team's primary technical resource for data extraction, pipeline development, and platform-to-platform integration. Success in this role requires strong technical skills in data integration, a demonstrated ability to work across systems with different architectures, and a willingness to develop working knowledge of special education data requirements on the job." That's prose. Essential Functions list: multiple bullet points. We'll convert each to

• . Minimum Qualifications list: bullet points. Preferred qualifications: list of items like "Experience with PowerSchool products...", "Familiarity with special education data workflows...", etc. We'll treat as Qualifications section (maybe "Preferred Qualifications"). Skills: maybe we can extract technical skills: proficiency in SQL, scripting language, ability to work with large-scale data systems, troubleshoot, analytical problem-solving, communication, etc. But those are already in Minimum Qualifications. Could still have a Skills section but might duplicate. Better to put technical skills under Requirements or Qualifications. Since we have Requirements (Minimum Qualifications) and Qualifications (Preferred). Skills maybe not needed. But we need to follow instruction: use headings only when posting has real specific content for it. We have content for About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Skills maybe not needed as separate; we could omit. Benefits: "Benefits Eligible: Yes" and "Telecommuting Eligibility: Eligible for telecommuting up to 20% (one day per week)". Also maybe Bargaining Unit? Not a benefit. We'll include those. Pay: Salary range. We need to ensure we don't include boilerplate like "Security Clearance", "Method Of Application", "DPSCD does not discriminate..." etc. Now craft HTML. Structure:

  About the role

  ... (position summary plus location, reports to, bargaining unit maybe)

  We could include location, reports to, bargaining unit in same paragraph. Let's compose: "The Program Associate I - Integration Specialist supports the ESE Systems & Analytics team within the Student Data & Accountability division by building and maintaining the data pipelines and system integrations that connect PowerSchool Special Programs (PSSP) to the district's broader data infrastructure. The team is responsible for the administration, integration, reporting, and end-user support of PSSP, which is the district's primary platform for special education data management, and serves as the data quality and systems bridge between the ESE division and the Student Information Services team. The Integration Specialist builds and maintains the connections between PSSP and other district systems, automates manual data movement, and develops PSSP-native operational reports. As the district works toward building MTSS infrastructure, this role will support the data connections needed to track pre-referral interventions alongside special education records. This role works in close coordination with the Program Supervisor and the Senior Director and operates as the team's primary technical resource for data extraction, pipeline development, and platform-to-platform integration. Success in this role requires strong technical skills in data integration, a demonstrated ability to work across systems with different architectures, and a willingness to develop working knowledge of special education data requirements on the job. Position is located at the Fisher Building, 3011 W. Grand Blvd., Detroit, MI 48202, reports to the Senior Director of ESE Systems & Analytics, and is part of the OSAS bargaining unit." That's fine. Next Responsibilities:

  Responsibilities

  • Build and maintain data pipelines between PSSP and other district systems, including the SIS, data warehouse, and ancillary platforms, using API-based, flat-file, or ETL-based approaches
  • Negotiate and implement scheduled data exports from PSSP to the district's data environment, ensuring that data flows reliably and on the cadence required for reporting and compliance monitoring
  • Develop and maintain automated data feeds that replace manual processes — including contractor onboarding data, service delivery records, and other recurring data exchanges between systems
  • Build and maintain data connections that support pre-referral intervention tracking alongside special education records — exploring approaches within PSSP and other existing systems as the district works toward a consistent MTSS framework
  • Coordinate with the Student Information Services team and other technical partners to ensure that changes on either side of a system integration are managed without breaking downstream data flows
  • Troubleshoot integration failures, data mismatches, and synchronization issues, documenting root causes and implementing fixes that prevent recurrence
  • Support the Program Supervisor on PSSP backend configuration tasks that require an understanding of the platform's data structure, particularly where configuration changes affect data extraction or reporting
  • Build and maintain operational reports inside PSSP, including single-level and multi-level reports, that surface data needed for compliance monitoring, count preparation, ESE partner team operations, and MTSS monitoring prior to determinations for special education eligibility
  • Validate reports against known cases and expected outputs before they are used for decision-making; document report logic and data definitions so that outputs can be interpreted accurately by non-technical users
  • Maintain technical documentation for all integrations, pipelines, and automated processes, including data dictionaries, source-to-target mappings, and process logs
  • Identify manual data processes that could be automated and propose integration solutions that reduce operational burden across ESE partner teams
  • Perform other duties as assigned by the Senior Director, ESE Systems & Analytics
  Note: we need to keep the special characters like ¿? In the original there is "¿" maybe a typo. We'll keep as is? Probably replace with appropriate punctuation. The original: "Develop and maintain automated data feeds that replace manual processes ¿ including contractor onboarding data, service delivery records, and other recurring data exchanges between systems". The "¿" seems like a stray character; we could replace with em dash or colon. But we must preserve substantive information; we can keep the dash. I'll replace with em dash "—". That's fine. Next Requirements (Minimum Qualifications):

  Requirements

  • Bachelor's degree from an accredited institution with a focus in computer science, information systems, data engineering, or a related technical field
  • Minimum of two to three (3) years of experience in data integration, systems administration, or a closely related technical role
  • Demonstrated experience building and maintaining data pipelines between systems, including API-based, flat-file, or ETL-based approaches
  • Proficiency in SQL and at least one scripting or development language (e.g., Python, JavaScript) for data extraction, transformation, and automation
  • Ability to work with large-scale data systems and troubleshoot integration failures, data mismatches, and synchronization issues
  • Strong analytical and problem-solving skills with the ability to diagnose technical root causes and propose effective solutions
  • Ability to communicate technical processes and findings clearly to non-technical partners
  Next Qualifications (Preferred):

  Qualifications

  • Experience with PowerSchool products: PowerSchool SIS, PowerSchool Special Programs, or equivalent student information or case management platforms (preferred)
  • Familiarity with special education data workflows, compliance timelines, or IEP-related processes (preferred)
  • Experience with report development inside a student information or case management platform (preferred)
  • Knowledge of Michigan state reporting requirements, including CEPI data submissions and pupil accounting processes (preferred)
  • Familiarity with data warehouse environments and dashboard tools such as Power BI (preferred)
  • Familiarity with MTSS frameworks and tiered intervention data systems (preferred)
  Next Benefits:

  Benefits

  • Benefits eligible: Yes
  • Telecommuting eligibility: Eligible for telecommuting up to 20% (one day per week)
  Next Pay:

  Pay

  Salary range: $75,048 - $98,163

  We should not include Schedule section. Check for any duplicated content: we have location, reports to, bargaining unit included in About the role. Good. We must ensure we didn't include any boilerplate