Data Analyst - IT

We need to output HTML fragment with sections: About the role? Actually they want headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting. Key content: - Intro paragraph: "Amity Foundation, an internationally acclaimed Teaching, and Therapeutic Community is seeking compassionate and enthusiastic individuals with a desire to teach, learn and join our community as a Data Analyst (IT). This groundbreaking opportunity will allow you to work with our prison and re-entry programs helping the community and will also enhance your training and experience in the field." - About Amity: description. - Remembrance, Resolution, Reconciliation, Restoration, Renewal (maybe values). Not sure if needed. - Job Summary About the Position: "As a Data Analyst, you will be responsible for the efficient extraction, transformation, and loading (ETL) of data from various sources, creating and maintaining documentation of all data sources, and developing insightful data visualizations using business intelligence tools such as Power Bi. Your role is essential in ensuring that data is accurate, accessible, and actionable for informed decision-making for all key stakeholders." - About The Position Essential Duties: bullet list of duties (ETL, Data Visualizations, Data Governance, Documentation and Training, Continuous Learning and Innovation). Each bullet has subpoints. - Required Education and Experience: list of requirements. - Preferred Programming skills, etc. - Certifications Or Licenses Required: None Preferred: None - ADA Information Physical Requirements: list. - Mental Demands: list. - Work Conditions: list. - Environmental Conditions: list. - Travel: list. - Pay: "$65,000 - $75,000 a year" - Schedule: "Please note that this position requires you to work on-site in the office three days per week." - Additional note about job description etc (boilerplate) to remove. We need to decide which sections to include. We have substantive content for: - About the role (maybe "About the role" heading). Could combine intro and about Amity? The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. - About the role: could include intro paragraph and description of Amity, mission, values. - Responsibilities: list of duties (ETL, Data Visualizations, Data Governance, Documentation and Training, Continuous Learning and Innovation). Use

  • . - Requirements: maybe required education and experience. - Qualifications: maybe preferred qualifications? Or we could combine required and preferred under Requirements? But they have separate headings: Requirements, Qualifications, Skills. We need to decide based on content. We have "Required Education and Experience:" list. That's requirements. We have "Preferred Programming skills, including knowledge of scripting languages (e.g., Python, PowerShell) for automation. Expertise in API development and management, with knowledge of RESTful API design principles. Demonstrated experience with one or more of the following modern data management concepts - data lakes, nonrelational databases (NoSQL), cloud hosting (AWS), serverless storage or automated database recovery Project management." That's preferred qualifications. We also have "Certifications Or Licenses Required: None Preferred: None" - not substantive. We have ADA Physical Requirements, Mental Demands, Work Conditions, Environmental Conditions, Travel. Those could go under maybe "Skills"? Not exactly. Could be under "Requirements"? But they are more about work conditions. The instruction says include a section ONLY when posting has real, specific content for it. We have content for Physical Requirements etc. Could we put them under a "Work Conditions" section? Not in the list of allowed headings. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to fit those details into those sections. Physical requirements etc could go under "Skills"? Not really. Could go under "Requirements"? Possibly as part of job requirements (physical ability). But the instruction says "Use
    • for any list of duties/requirements/benefits". So we could treat physical requirements as part of Requirements. Similarly mental demands, work conditions, environmental conditions, travel could be part of Requirements or maybe Skills? But they are not skills. Probably better to include them under Requirements as additional requirements. But we need to avoid too many thin sections. We could combine all requirement-like items into a single Requirements section with sublists? But we need to use
      • for any list. We could have multiple
        inside the section. Alternatively, we could create separate sections for Requirements, Qualifications, Skills. Then we can put: - Requirements: Required Education and Experience (list), plus Physical Requirements, Mental Demands, Work Conditions, Environmental Conditions, Travel (maybe as separate sublists). But that may be many lists. - Qualifications: Preferred Programming skills etc. - Skills: maybe list of skills like problem-solving, communication, etc. Those are in Required Education and Experience list: "Strong problem-solving skills and attention to detail. Excellent communication and collaboration skills to work with cross-functional teams and stakeholders. Ability to adapt to evolving data technologies and industry best practices." Those could go under Skills. Thus we can separate: - About the role: intro + About Amity + values. - Responsibilities: duties list (ETL, Data Visualizations, Data Governance, Documentation and Training, Continuous Learning and Innovation). - Requirements: Required Education and Experience (list), plus Physical Requirements, Mental Demands, Work Conditions, Environmental Conditions, Travel (maybe as separate sublists but still under Requirements). Could also separate into subheadings? Not allowed; only h3 headings. So we can just have multiple
        inside the Requirements section. - Qualifications: Preferred Programming skills etc (list). - Skills: problem-solving, communication, adaptability (list). - Benefits: none mentioned? Not in posting. So we should not create Benefits section. - Pay: "$65,000 - $75,000 a year" -> create Pay section with

        . - Schedule: "Please note that this position requires you to work on-site in the office three days per week." -> create Schedule section with

        . We must not include boilerplate like "Note: This job description is intended..." etc. Remove that. Also remove duplicated lines. Now produce HTML fragment. Structure:

        About the role

        ... intro + about Amity + values ...

        Responsibilities

        • ETL (Extract, Transform, Load): ...
        ...
        But the duties have subpoints inside each bullet. We could keep them as part of the
        • text, maybe using
          or just plain text. The instruction: Use
          • for any list of duties/requirements/benefits. It doesn't forbid additional formatting inside
          • . We can keep the detailed sentences. Thus each
          • can contain the duty heading and its subpoints separated by semicolons or line breaks. We'll keep as plain text. Similarly for Requirements: we need multiple lists. Could do:

            Requirements

            Required Education and Experience:

            • 2-5 years experience or related work and/or Bachelor’s degree in a technical or other applicable discipline.
            • Proven experience as a Data Analyst or similar role, with a track record of successfully delivering data-driven insights.
            • Proven experience in data visualization tools such as Tableau, Power BI, or similar (non-Excel) software.
            • Proven experience in ETL development, including proficiency with ETL tools (e.g., Apache NiFi, Python)
            • Understanding of data governance principles, data security, and compliance regulations.
            • Strong problem-solving skills and attention to detail.
            • Excellent communication and collaboration skills to work with cross-functional teams and stakeholders.
            • Ability to adapt to evolving data technologies and industry best practices.
            But we already used problem-solving etc under Skills. Might duplicate. Better to separate: Required Education and Experience list includes the first 5 items (education/experience, proven experience as data analyst, proven experience in visualization tools, proven experience in ETL, understanding of data governance). Then we can put problem-solving etc under Skills. Thus Requirements section will have two lists: Required Education and Experience, Physical Requirements, Mental Demands, Work Conditions, Environmental Conditions, Travel. But we need to avoid too many thin sections; but it's okay to have multiple lists under same heading. We'll do:

            Requirements

            Required Education and Experience:

            ...

            Physical Requirements:

            ...

            Mental Demands:

            ...

            Work Conditions:

            ...

            Environmental Conditions:

            ...

            Travel:

            ...
            But that is many

            and

            . Might be okay. Alternatively, we could combine all into one big list with headings inside
            • but that deviates from instruction? The instruction says use
              • for any list of duties/requirements/benefits. It doesn't forbid using

                for headings inside the section. So above is fine. Now Qualifications: Preferred Programming skills etc. We'll do:

                Qualifications

                Preferred qualifications:

                • Preferred Programming skills, including knowledge of scripting languages (e.g., Python, PowerShell) for automation.
                • Expertise in API development and management, with knowledge of RESTful API design principles.
                • Demonstrated experience with one or more of the following modern data management concepts - data lakes, nonrelational databases (NoSQL), cloud hosting (AWS), serverless storage or automated database recovery.
                • Project management.
                Skills: problem-solving, communication, adaptability.

                Skills

                • Strong problem-solving skills and attention to detail.
                • Excellent communication and collaboration skills to work with cross-functional teams and stakeholders.
                • Ability to adapt to evolving data technologies and industry best practices.
                Pay:

                Pay

                $65,000 - $75,000 a year

                Schedule:

                Schedule

                Please note that this position requires you to work on-site in the office three days per week.

                Now About the role content: We need to include intro paragraph and About Amity description and values. Intro: "Amity Foundation, an internationally acclaimed Teaching, and Therapeutic Community is seeking compassionate and enthusiastic individuals with a desire to