Data Analyst

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, legal, etc. Must preserve all substantive info. We need to parse the posting. Content: Intro paragraph: "Join us at Sparksoft, where we're not just another tech company—we're a catalyst for change. Our mission isn't just to offer IT solutions; it's to revolutionize the way you work. Here, passion isn't just a buzzword; it's the fuel behind groundbreaking ideas and transformative technologies. We serve a wide range of government clients, delivering impact that's felt across the nation. Our true strength lies in our people. They're the problem-solvers and innovators consistently delivering extraordinary outcomes. With Sparksoft, you're not stepping into a routine job; you're joining a team committed to innovation and excellence. Our innovation extends beyond just delivering projects. Through our specialized Innovation Centers, we continuously refine our methods, ensuring we remain industry leaders. We are Sparksoft!" That's about the company, could be "About the role"? Actually "About the role" is for role description. But we have a generic company description. Could put under "About the role" or maybe not needed. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We need to extract: Responsibilities: The block after "ROLE AND RESPONSIBILITIES:" includes many bullet-like sentences. We'll list them as

• . Requirements: The "REQUIRED EXPERIENCE:" block. Preferred Experience: Could be under Qualifications or Skills? The instruction includes Qualifications and Skills sections. We could put education under Qualifications, and preferred experience under Skills? Or we could combine. We have "EDUCATION AND CERTIFICATIONS:" block. We have "WHAT WE OFFER:" block includes benefits: Competitive compensation and a 401(k) with employer contributions, Flexible paid time off and hybrid ways of working, Comprehensive health coverage..., A curated in-office experience..., Opportunities to give back..., Training and development programs..., A collaborative, transparent, and fun culture..., Accessibility and Accommodations..., Security Notice..., Artificial Intelligence (AI) Policy... Some of these are boilerplate (EEO, legal). We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The Accessibility and Accommodations, Security Notice, AI Policy might be considered legal/boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The Accessibility and Accommodations is about accommodations for disability, could be considered EEO? Might be considered legal. Safer to remove it. Security Notice and AI Policy also likely legal. So we should keep only substantive benefits: Competitive compensation and a 401(k) with employer contributions, Flexible paid time off and hybrid ways of working, Comprehensive health coverage—including medical, dental, vision, life, and disability insurance, A curated in-office experience designed to foster community, team connections, and innovation, Opportunities to give back through Sparksoft Cares, including annual company-wide fundraising events, Training and development programs that build new skills and prepare you for leadership roles, A collaborative, transparent, and fun culture—recognized as a Great Place to Work®. Pay: The posting does not give specific pay numbers, only "Competitive compensation". That's vague; we should not create Pay section unless posting actually states them. It says "Competitive compensation" but not a number or range. According to instruction: 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. "Competitive compensation" is vague but maybe considered placeholder? It's not a specific number. Safer to not create Pay section. Similarly Schedule: not mentioned. Benefits: we have specific benefits listed, so we can create Benefits section. Now we need to decide sections: - About the role: Could include the introductory paragraph about Sparksoft and mission. That's substantive. - Responsibilities: list. - Requirements: required experience. - Qualifications: education and certifications. - Skills: maybe combine preferred experience and required skills? Could put technical skills under Skills. But we have required experience includes experience with SQL, R, Python, QuickSight, PostgreSQL, AWS services, etc. That's more like skills. Could put under Skills. However we already have Requirements for experience. Might be okay to have Skills section for technical skills. But we must not duplicate content. Let's think: The posting has "REQUIRED EXPERIENCE:" includes many items: 5+ years experience, demonstrated experience analyzing healthcare data, excellent communication skills, hands-on experience assessing data quality, experience using AWS services, strong problem-solving skills, ability to work in fast-paced agile, must obtain Public Trust clearance, must have lived in US 3 out of past 5 years. Those are requirements/experience. Then "PREFERRED EXPERIENCE:" includes Master's degree, SAFe Agile Certification, data profiling, validate performance metrics, identify trends, experience developing dashboards, experience with agile methodologies and tools, experience with version control systems, experience in healthcare IT and understanding of regulatory requirements such as HIPAA, experience and/or knowledge of CMS processes and standards. Then "EDUCATION AND CERTIFICATIONS:" Bachelor’s degree or higher in Computer Science, Information Technology, Math, Data Analytics, or related field. Thus we can have: - Requirements: Required Experience (the list). - Qualifications: Education and Certifications (Bachelor's degree etc.) plus maybe Preferred Experience? But Preferred Experience is more like qualifications/skills. Could split: Qualifications for education, Skills for preferred experience and technical skills. But we have also required experience includes technical skills (SQL, R, Python, QuickSight, PostgreSQL, AWS). Those could go under Skills. Thus: Section About the role: intro paragraph. Section Responsibilities: list of duties. Section Requirements: required experience (including clearance, US residency, etc.) Section Skills: technical skills and preferred experience (maybe combine). But we must avoid duplication: we already listed some technical skills in required experience; we could still list them under Skills but that would duplicate. Better to separate: Requirements for experience/clearance, Skills for technical abilities and preferred qualifications. Thus we will extract: Skills: Experience with data analytics tools (SQL, R, Python) and data visualization tools (like QuickSight, python). Knowledge of databases (PostgreSQL) and data modeling. Experience using AWS services to query, process, monitor, secure, or visualize data, with practical knowledge of services relevant to cloud analytics and data quality. Experience with agile methodologies (SAFe, Scrum) and tools (Jira, Confluence). Experience with version control systems (GitHub). Experience in healthcare IT and understanding of regulatory requirements such as HIPAA. Experience and/or knowledge of CMS processes and standards. Master’s degree with a data or math focus (preferred). SAFe Agile Certification (preferred). Perform data profiling and exploratory analysis to identify anomalies, patterns, data quality issues, and opportunities for improvement. Validate performance metrics, quality indicators, and reporting outputs to ensure accuracy and consistency across data sources. Identify, analyze, and communicate trends, patterns, and anomalies in data to support operational and programmatic decision-making. Experience developing dashboards, performance reports, and analytical summaries using business intelligence tools. But note some of these are also in responsibilities (like perform data profiling etc). Actually responsibilities list includes many similar items: "Perform data profiling and exploratory analysis to identify anomalies, patterns, data quality issues, and opportunities for improvement." appears under PREFERRED EXPERIENCE. Also "Validate performance metrics..." etc. So there is overlap. We need to preserve all substantive information, but we should avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication, but we should not repeat lines? It says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. So we need to deduplicate identical sentences. Thus we need to combine responsibilities and preferred experience, removing duplicates. Let's extract responsibilities list (the long paragraph after ROLE AND RESPONSIBILITIES:). It's a series of sentences separated by periods. Let's list them: 1. Analyze healthcare data from a variety of sources, identifying and correcting errors and inconsistencies, and developing and implementing processes to improve data quality. 2. Define, calculate, and interpret data quality measures across dimensions such as accuracy, completeness, consistency, validity, timeliness, uniqueness, integrity, and conformity. 3. Work with healthcare and program subject matter experts to establish business rules, thresholds, tolerances, critical data elements, and fit-for-purpose quality expectations. 4. Work with a range of data types, including structured and unstructured data, and use a variety of tools and techniques to analyze and improve data quality. 5. Use tools and techniques such as statistical analysis, data cleansing and transformation tools, and data governance frameworks. 6. Document processes, prepare reports, and make recommendations for process improvements. 7. Collaborate with other teams to implement changes or updates in the existing reports. 8. Present responses and findings to business owners, customers, leadership. 9. Perform statistical tests on large datasets to determine data quality and integrity. 10. Review and understand artifacts related to data ingestion and transformation as it applies to data validation and analysis. 11. Provide quality assurance reports using tools like QuickSight. 12. Perform ad hoc data analysis to support programmatic questions and stakeholder requests. 13. Work as part of a project team to determine project requirements, goals, implementation, and schedules. 14. Provide training for internal users and customer stakeholders. 15. Provide technical leadership within the data analytics team and mentor junior team members. 16. Conduct peer reviews of team members’ work outputs for quality assurance. 17. Experience with data analytics tools (SQL, R, Python) and data visualization tools (like QuickSight, python). 18. Knowledge of databases (PostgreSQL) and data modeling. 19. Assess/evaluate to deliver timely data reporting, and data solutions against client requirements. 20. Ensure customer satisfaction through follow-up, client responsiveness, and thorough communication. 21. Participate in Agile ceremonies, such as sprint planning, daily stand-ups, and retrospectives, to provide input on testing progress and challenges. Note: Some of these are actually skills/experience (like 17,18,19). But they appear in responsibilities block. Now PREFERRED EXPERIENCE list: - Master’s degree with a data or math focus - SAFe Agile Certification - Perform data profiling and exploratory analysis to identify anomalies, patterns, data quality issues, and opportunities for improvement. - Validate performance metrics, quality indicators, and reporting outputs to ensure accuracy and consistency across data sources. - Identify, analyze, and communicate trends, patterns, and anomalies in data to support operational and programmatic decision-making. - Experience developing dashboards, performance reports, and analytical summaries using business intelligence tools. - Experience with agile methodologies (SAFe, Scrum) and tools (Jira, Confluence). - Experience with the version control systems (GitHub) - Experience in healthcare IT and understanding of regulatory requirements such as HIPAA. - Experience and/or knowledge of CMS processes and standards. Now we see duplicates: "Perform data profiling and exploratory analysis..." appears both in responsibilities (item 12? Actually responsibilities item 12 is "Perform ad hoc data