Sr. Application Engineer, Database ETL Programmer
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content.
From posting:
- Overview About PowerSchool (company description) maybe not needed as heading? Could be "About the role"? Actually "Overview About PowerSchool" is company overview, not role. The instruction: do NOT repeat the job title as a heading. Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content.
We have:
- Responsibilities: there is a "Responsibilities Description" and "Your Day-to-day Responsibilities Will Include" list. So we can have Responsibilities
with - items.
- Qualifications: there is "Minimum Qualifications" and "Preferred Qualifications". So we can have
Qualifications
with maybe sublists? Could separate Minimum and Preferred as items.
- Skills: maybe not explicit separate section; but we could infer from qualifications. However instruction: include a section ONLY when posting has real specific content for it. There's no explicit "Skills" heading; but we could treat qualifications as skills. Safer to not create Skills section if not explicit.
- Benefits: there is "Compensation & Benefits" with list of benefits. So we can have Benefits
with .
- Pay: there is "A reasonable estimate of the base compensation range for this position is $75,100 - $120,600 USD." So we can have Pay
with containing that sentence.
- Schedule: not mentioned. So omit.
- About the role: there is "Overview About PowerSchool" and "Team Overview". Could be considered "About the role". We have description of team and role. So we can include
About the role
with paragraphs.
- Requirements: maybe overlapping with Qualifications. But we have "Minimum Qualifications" and "Preferred Qualifications". Could treat as Requirements. But we already have Qualifications section. To avoid duplication, we could combine. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says use those headings; but we should only include when posting has real content. We have content for About the role, Responsibilities, Qualifications, Benefits, Pay. Possibly also Requirements (maybe same as Qualifications). But we can decide to include Requirements as separate if there is distinct content: there is "Minimum Qualifications" list; that could be considered Requirements. However we already have Qualifications. To be safe, we could include both Requirements and Qualifications, but that may duplicate content. Better to follow typical pattern: Requirements = minimum qualifications; Qualifications = preferred qualifications? But the instruction list includes both Requirements and Qualifications as possible headings. We could split: Requirements = Minimum Qualifications; Qualifications = Preferred Qualifications. That would avoid duplication and use both headings.
Thus:
- About the role
: combine Overview About PowerSchool and Team Overview paragraphs.
- Responsibilities
: include the description paragraph and the list of day-to-day responsibilities.
- Requirements
: Minimum Qualifications list.
- Qualifications
: Preferred Qualifications list.
- Benefits
: list of benefits.
- Pay
: compensation range sentence.
We must not include Schedule.
We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip the EEO Commitment section. Also remove any duplicated lines (like "Compensation & Benefits" appears twice? Actually appears as heading then list; we keep only once). Also remove "Overview About PowerSchool" maybe duplicate? We'll keep content.
We need to output only HTML fragment, no /, no markdown.
Let's extract content.
About the role:
From text:
"Overview About PowerSchool At PowerSchool, we power education for students around the world. As the global leader in cloud-based K-12 software, we support the full education ecosystem—from the central office to the classroom to the home. Joining PowerSchool means being part of a mission-driven team that is transforming K-12 education by helping schools operate more effectively and deliver better outcomes for educators, students, and families.
Team Overview The Services team works closely together to set PowerSchool customers up for ongoing success through post-implementation support, troubleshooting, consultation on system setup options, and training on features and functionality. The team offers cross-portfolio support, all while meeting organizational objectives for revenue, utilization, and customer satisfaction."
We can combine into a paragraph or two paragraphs. Use for prose.
Responsibilities:
Paragraph: "The Talent/Professional Learning Services Team partners with K-12 school districts to implement, customize, integrate, and optimize Human Resource applications within the PowerSchool Talent portfolio. This role combines technical consulting, database development, SQL programming, and data integration to help customers solve complex business challenges. The ideal candidate will work directly with clients to gather requirements, develop custom solutions, build data integrations, and support the movement of workforce and payroll data between PowerSchool applications and third-party systems. The role requires strong database, SQL, ETL, and scripting experience, along with the ability to translate customer requirements into scalable technical solutions."
Then list: "Your Day-to-day Responsibilities Will Include" followed by bullet points:
- Meet with customers to define and document business requirements
- Create custom data integration solutions between Talent HR applications and third-party payroll, HRIS, and ERP systems
- Design, develop, and support ETL processes for customer payroll and workforce data integrations
- Develop custom SQL and scripting solutions to support customer requirements and integrations
- Work collaboratively with clients, team members, Product Development, Engineering, Sales, Technical Support, and the Project Management Organization
- Serve as a technical advisor for database, integration, and data migration solutions
- Troubleshoot and support customer database solutions, integrations, and data migrations
We'll output as
- ... etc.
Requirements (Minimum Qualifications):
List:
- Minimum of 8+ years of relevant and related work experience
- Bachelor’s degree or equivalent, or equivalent years of relevant work experience
- Database experience supporting customer solutions
- Programming experience developing custom scripts and integrations
- ETL experience supporting payroll data integrations
- SQL programming experience supporting customer database integrations
We'll output as
.
Qualifications (Preferred Qualifications):
List:
- SQL/MySQL scripting experience
- Ability to lead requirements-gathering sessions and present solutions
- Ability to program/analyze scripts (Python, Java, Batch, and PowerShell)
- Pentaho ETL experience
- Customer-facing / consulting experience
- Experience supporting HRIS, ERP, or payroll system integrations
- Strong organizational skills
- Effective written communication skills
- Salesforce knowledge
We'll output as .
Benefits:
List from "Compensation & Benefits PowerSchool Offers The Following Benefits":
- Comprehensive Insurance Coverage (including Medical, Dental, Vision, Pharmacy benefits, Life Insurance and AD&D)
- Flexible Spending Accounts and Health Savings Accounts
- Short-Term Disability and Long-Term Disability
- Comprehensive 401(k) plan
- Generous Parental Leave
- Unrestricted paid time off (known as Discretionary Time Off - DTO)
- Wellness Program, including ClassPass & Employee Assistance Program
- Tuition Reimbursement
- Optional Benefits: Pet Insurance, Identity Theft Protection, Student Debt Repayment Program and Prepaid Legal coverage
We'll output as .
Pay:
Paragraph: "A reasonable estimate of the base compensation range for this position is $75,100 - $120,600 USD. This compensation range is specific to the United States and it incorporates many factors including but not limited to an applicant's skills and prior relevant experience and training; licensures, degrees, and certifications; internal equity; internal pay ranges; and market data/range parameters."
We'll output as .
We must not include any other sections like Schedule.
Now ensure we didn't include any boilerplate like EEO Commitment. Remove that.
Also remove duplicated lines: The heading "Compensation & Benefits" appears twice? Actually appears as "Compensation & Benefits" then list, then later "Compensation & Benefits PowerSchool Offers The Following Benefits". We'll keep only one Benefits section.
Now produce HTML fragment.
We'll need to wrap each section in appropriate tags:
About the role
then ... maybe multiple
paragraphs.
We'll output:
About the role
At PowerSchool, we power education for students around the world. As the global leader in cloud-based K-12 software, we support the full education ecosystem—from the central office to the classroom to the home. Joining PowerSchool means being part of a mission-driven team that is transforming K-12 education by helping schools operate more effectively and deliver better outcomes for educators, students, and families.
The Services team works closely together to set PowerSchool customers up for ongoing success through post-implementation support, troubleshooting, consultation on system setup options, and training on features and functionality. The team offers cross-portfolio support, all while meeting organizational objectives for revenue, utilization, and customer satisfaction.
Then Responsibilities:
Responsibilities
The Talent/Professional Learning Services Team partners with K-12 school districts to implement, customize, integrate, and optimize Human Resource applications within the PowerSchool Talent portfolio. This role combines technical consulting, database development, SQL programming, and data integration to help customers solve complex business challenges. The ideal candidate will work directly with clients to gather requirements, develop custom solutions, build data integrations, and support the movement of workforce and payroll data between PowerSchool applications and third-party systems. The role requires strong database, SQL, ETL, and scripting experience, along with the ability to translate customer requirements into scalable technical solutions.
- Meet with customers to define and document business requirements
- Create custom data integration solutions between Talent HR applications and third-party payroll, HRIS, and ERP systems
- Design, develop, and support ETL processes for customer payroll and workforce data integrations
- Develop custom SQL and scripting solutions to support customer requirements and integrations
- Work collaboratively with clients, team members, Product Development, Engineering, Sales, Technical Support, and the Project Management Organization
- Serve as a technical advisor for database, integration, and data migration solutions
- Troubleshoot and support customer database solutions, integrations, and data migrations
Then Requirements:
Requirements
- Minimum of 8+ years of relevant and related work experience
- Bachelor’s degree or equivalent, or equivalent years of relevant work experience
- Database experience supporting customer solutions
- Programming experience developing custom scripts and integrations
- ETL experience supporting payroll data integrations
- SQL programming experience supporting customer database integrations
Then Qualifications:
Qualifications
- SQL/MySQL scripting experience
- Ability to lead requirements-gathering sessions and present solutions
- Ability to program/analyze scripts (Python, Java, Batch, and PowerShell)
- Pentaho ETL experience
- Customer-facing / consulting experience
Qualifications
with maybe sublists? Could separate Minimum and Preferred as- items.
- Skills: maybe not explicit separate section; but we could infer from qualifications. However instruction: include a section ONLY when posting has real specific content for it. There's no explicit "Skills" heading; but we could treat qualifications as skills. Safer to not create Skills section if not explicit.
- Benefits: there is "Compensation & Benefits" with list of benefits. So we can have
- ... etc.
Requirements (Minimum Qualifications):
List:
- Minimum of 8+ years of relevant and related work experience
- Bachelor’s degree or equivalent, or equivalent years of relevant work experience
- Database experience supporting customer solutions
- Programming experience developing custom scripts and integrations
- ETL experience supporting payroll data integrations
- SQL programming experience supporting customer database integrations
We'll output as
- .
Qualifications (Preferred Qualifications):
List:
- SQL/MySQL scripting experience
- Ability to lead requirements-gathering sessions and present solutions
- Ability to program/analyze scripts (Python, Java, Batch, and PowerShell)
- Pentaho ETL experience
- Customer-facing / consulting experience
- Experience supporting HRIS, ERP, or payroll system integrations
- Strong organizational skills
- Effective written communication skills
- Salesforce knowledge
We'll output as
- Meet with customers to define and document business requirements
- Create custom data integration solutions between Talent HR applications and third-party payroll, HRIS, and ERP systems
- Design, develop, and support ETL processes for customer payroll and workforce data integrations
- Develop custom SQL and scripting solutions to support customer requirements and integrations
- Work collaboratively with clients, team members, Product Development, Engineering, Sales, Technical Support, and the Project Management Organization
- Serve as a technical advisor for database, integration, and data migration solutions
- Troubleshoot and support customer database solutions, integrations, and data migrations
- Minimum of 8+ years of relevant and related work experience
- Bachelor’s degree or equivalent, or equivalent years of relevant work experience
- Database experience supporting customer solutions
- Programming experience developing custom scripts and integrations
- ETL experience supporting payroll data integrations
- SQL programming experience supporting customer database integrations
- SQL/MySQL scripting experience
- Ability to lead requirements-gathering sessions and present solutions
- Ability to program/analyze scripts (Python, Java, Batch, and PowerShell)
- Pentaho ETL experience
- Customer-facing / consulting experience
- .
Benefits:
List from "Compensation & Benefits PowerSchool Offers The Following Benefits":
- Comprehensive Insurance Coverage (including Medical, Dental, Vision, Pharmacy benefits, Life Insurance and AD&D)
- Flexible Spending Accounts and Health Savings Accounts
- Short-Term Disability and Long-Term Disability
- Comprehensive 401(k) plan
- Generous Parental Leave
- Unrestricted paid time off (known as Discretionary Time Off - DTO)
- Wellness Program, including ClassPass & Employee Assistance Program
- Tuition Reimbursement
- Optional Benefits: Pet Insurance, Identity Theft Protection, Student Debt Repayment Program and Prepaid Legal coverage
We'll output as
- .
Pay:
Paragraph: "A reasonable estimate of the base compensation range for this position is $75,100 - $120,600 USD. This compensation range is specific to the United States and it incorporates many factors including but not limited to an applicant's skills and prior relevant experience and training; licensures, degrees, and certifications; internal equity; internal pay ranges; and market data/range parameters."
We'll output as
. We must not include any other sections like Schedule. Now ensure we didn't include any boilerplate like EEO Commitment. Remove that. Also remove duplicated lines: The heading "Compensation & Benefits" appears twice? Actually appears as "Compensation & Benefits" then list, then later "Compensation & Benefits PowerSchool Offers The Following Benefits". We'll keep only one Benefits section. Now produce HTML fragment. We'll need to wrap each section in appropriate tags:
About the role
then... maybe multiple
paragraphs. We'll output:
About the role
At PowerSchool, we power education for students around the world. As the global leader in cloud-based K-12 software, we support the full education ecosystem—from the central office to the classroom to the home. Joining PowerSchool means being part of a mission-driven team that is transforming K-12 education by helping schools operate more effectively and deliver better outcomes for educators, students, and families.
The Services team works closely together to set PowerSchool customers up for ongoing success through post-implementation support, troubleshooting, consultation on system setup options, and training on features and functionality. The team offers cross-portfolio support, all while meeting organizational objectives for revenue, utilization, and customer satisfaction.
Then Responsibilities:Responsibilities
The Talent/Professional Learning Services Team partners with K-12 school districts to implement, customize, integrate, and optimize Human Resource applications within the PowerSchool Talent portfolio. This role combines technical consulting, database development, SQL programming, and data integration to help customers solve complex business challenges. The ideal candidate will work directly with clients to gather requirements, develop custom solutions, build data integrations, and support the movement of workforce and payroll data between PowerSchool applications and third-party systems. The role requires strong database, SQL, ETL, and scripting experience, along with the ability to translate customer requirements into scalable technical solutions.
Requirements
Qualifications
Benefits
with- .
- Pay: there is "A reasonable estimate of the base compensation range for this position is $75,100 - $120,600 USD." So we can have
Pay
withcontaining that sentence. - Schedule: not mentioned. So omit. - About the role: there is "Overview About PowerSchool" and "Team Overview". Could be considered "About the role". We have description of team and role. So we can include
About the role
with paragraphs. - Requirements: maybe overlapping with Qualifications. But we have "Minimum Qualifications" and "Preferred Qualifications". Could treat as Requirements. But we already have Qualifications section. To avoid duplication, we could combine. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says use those headings; but we should only include when posting has real content. We have content for About the role, Responsibilities, Qualifications, Benefits, Pay. Possibly also Requirements (maybe same as Qualifications). But we can decide to include Requirements as separate if there is distinct content: there is "Minimum Qualifications" list; that could be considered Requirements. However we already have Qualifications. To be safe, we could include both Requirements and Qualifications, but that may duplicate content. Better to follow typical pattern: Requirements = minimum qualifications; Qualifications = preferred qualifications? But the instruction list includes both Requirements and Qualifications as possible headings. We could split: Requirements = Minimum Qualifications; Qualifications = Preferred Qualifications. That would avoid duplication and use both headings. Thus: -About the role
: combine Overview About PowerSchool and Team Overview paragraphs. -Responsibilities
: include the description paragraph and the list of day-to-day responsibilities. -Requirements
: Minimum Qualifications list. -Qualifications
: Preferred Qualifications list. -Benefits
: list of benefits. -Pay
: compensation range sentence. We must not include Schedule. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip the EEO Commitment section. Also remove any duplicated lines (like "Compensation & Benefits" appears twice? Actually appears as heading then list; we keep only once). Also remove "Overview About PowerSchool" maybe duplicate? We'll keep content. We need to output only HTML fragment, no /, no markdown. Let's extract content. About the role: From text: "Overview About PowerSchool At PowerSchool, we power education for students around the world. As the global leader in cloud-based K-12 software, we support the full education ecosystem—from the central office to the classroom to the home. Joining PowerSchool means being part of a mission-driven team that is transforming K-12 education by helping schools operate more effectively and deliver better outcomes for educators, students, and families. Team Overview The Services team works closely together to set PowerSchool customers up for ongoing success through post-implementation support, troubleshooting, consultation on system setup options, and training on features and functionality. The team offers cross-portfolio support, all while meeting organizational objectives for revenue, utilization, and customer satisfaction." We can combine into a paragraph or two paragraphs. Usefor prose. Responsibilities: Paragraph: "The Talent/Professional Learning Services Team partners with K-12 school districts to implement, customize, integrate, and optimize Human Resource applications within the PowerSchool Talent portfolio. This role combines technical consulting, database development, SQL programming, and data integration to help customers solve complex business challenges. The ideal candidate will work directly with clients to gather requirements, develop custom solutions, build data integrations, and support the movement of workforce and payroll data between PowerSchool applications and third-party systems. The role requires strong database, SQL, ETL, and scripting experience, along with the ability to translate customer requirements into scalable technical solutions." Then list: "Your Day-to-day Responsibilities Will Include" followed by bullet points: - Meet with customers to define and document business requirements - Create custom data integration solutions between Talent HR applications and third-party payroll, HRIS, and ERP systems - Design, develop, and support ETL processes for customer payroll and workforce data integrations - Develop custom SQL and scripting solutions to support customer requirements and integrations - Work collaboratively with clients, team members, Product Development, Engineering, Sales, Technical Support, and the Project Management Organization - Serve as a technical advisor for database, integration, and data migration solutions - Troubleshoot and support customer database solutions, integrations, and data migrations We'll output as