Data Platform Engineer

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Key info: - Company: Syms Strategic Group (SSG) seeking Data Platform Engineer. - Location: Remote - Department: Veterans Affairs (VA) - Type: Full Time - Min. Experience: Experienced - Security Clearance Level: Public Trust (MBI) - Salary Range: $85,389 - $116,975 - If previously applied, no need to reapply (application instruction) -> remove. - Applications still under review (maybe not needed) - Military Veterans encouraged (maybe keep as note? It's substantive? Might be considered EEO boilerplate? It's a encouragement but not EEO? Might be considered a note but could be kept as part of About the role? Probably we can include as a short paragraph under About the role. Essential Duties And Responsibilities: a long list. Required Skills and Experience: list. Professional Certifications: None but AWS certifications are a bonus. Years of Professional Experience: n/a (maybe ignore) Desired experience: list of specific items (EDI X.12, etc.) Formal Education: Bachelor’s degree or higher in CS, Engineering, or related; equivalent practical experience considered. Citizenship Requirement: U.S. Citizenship required. Security Clearance Requirements: Must possess or qualify for Public Trust (MBI). CRITICAL NOTES: many notes about screening, no third parties, remote position but certain states excluded, W-2, interviews on Teams, camera on, link to LinkedIn, US Citizenship required again, security investigation, background investigation, EEO statement, Powered by JazzHR. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus we should keep substantive content: role description, responsibilities, required skills, desired experience, education, citizenship, security clearance, salary range, location, department, type, maybe note about veterans encouraged. We must not include Pay/Benefits/Schedule sections unless posting actually states them. Pay is stated (salary range). Benefits not stated. Schedule not stated (full time is type but schedule not given). So we include Pay section with salary range. Benefits and Schedule omitted. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections with real specific content. Let's map: - About the role: could include location, department, type, remote, veterans encouraged, maybe summary. We have info: Location Remote, Department VA, Type Full Time, Veterans encouraged. Also maybe mention it's a Data Platform Engineer role. So we can create About the role paragraph. - Responsibilities: we have Essential Duties And Responsibilities (long list). Use

• for each duty. - Requirements: could include required skills and experience (the "Required Skills and Experience" list). Also maybe security clearance, citizenship, etc. But we have separate sections for Qualifications, Skills. The instruction says use headings for those categories. We need to decide what goes where. Typically: Requirements could be mandatory requirements (like years experience, security clearance, citizenship). Qualifications could be education, certifications. Skills could be technical skills list. But we can also combine. However we must not create thin sections; prefer few substantive sections. We could have: About the role, Responsibilities, Required Skills & Experience (maybe as Requirements), Qualifications (education), Pay. But we need to follow heading names exactly: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can assign content accordingly. Let's decide: - About the role: brief summary: Syms Strategic Group (SSG) seeks Data Platform Engineer supporting VA, remote full-time, veterans encouraged. - Responsibilities: list of duties from Essential Duties And Responsibilities. - Requirements: maybe include mandatory items: 8+ years experience in software/data engineering with strong AWS focus, proven experience architecting/executing cloud data platform migrations, track record evaluating/selecting AWS data services, experience delivering reporting/analytics solutions for non-technical users, deep hands-on AWS experience across data-oriented services, strong SQL skills, ability to design relational query layers over semi-structured data, experience with XML-heavy data stores, ability to evaluate trade-offs, familiarity with AWS analytics/reporting services, proficiency with Git/GitHub, familiarity with CI/CD and AWS-native tooling, IaC experience, strong communication skills, ability to gather/translate business requirements, comfort driving ambiguous decisions, experience with Agile/Scrum/Kanban and JIRA, strong documentation habits. Also security clearance (Public Trust MBI), US citizenship required. Also maybe note about no third parties, but that's boilerplate. - Qualifications: education: Bachelor’s degree or higher in Computer Science, Engineering, or related technical discipline; equivalent practical experience considered. Also maybe professional certifications: AWS certifications a bonus. Also maybe desired experience list (EDI, HL7, FHIR, C#/.Net, Entity Framework, healthcare payer/PBM, HIPAA). Those could be under Qualifications or Skills? They are desired experience, could be under Qualifications. - Skills: maybe list of technical skills: AWS services (S3, Athena, Glue, Aurora, DynamoDB, Redshift, OpenSearch, Lambda, IAM, CloudWatch), SQL, XML parsing, CI/CD, IaC tools, Git, etc. But we already listed many in Requirements. To avoid duplication, we could split: Requirements = experience and mandatory qualifications; Skills = technical competencies; Qualifications = education and certifications. However we must avoid duplication of same content. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include all details, but we can organize them without duplication. Duplication is okay if it's originally duplicated? The posting has some duplication (e.g., AWS services listed both in Required Skills and Experience and also maybe elsewhere). We should preserve but not invent. Duplication is okay if it's in original. But we should aim to not repeat same sentence verbatim unnecessarily? The instruction says remove duplicated lines (i.e., lines that are exactly same). So we should avoid repeating identical lines. But we can keep similar content if phrased differently. Thus we need to extract unique bullet points. Let's list all unique points from posting: From Essential Duties And Responsibilities: 1. Lead the next phase of the healthcare data platform modernization 2. Implement the evolution from a Microsoft SQL eXtensible Markup Language (MSSQL XML) object store toward a scalable, cloud-native AWS data architecture that enables business stakeholders and analysts to run performant, SQL-based reports and queries against healthcare data seamlessly 3. Evaluate and decide the right AWS data strategy for the platform 4. Evaluate and recommend the optimal AWS-native data storage and query architecture for the XML object store data, assessing options such as S3 + Athena, Aurora, DynamoDB, Redshift, and OpenSearch based on query patterns, reporting needs, cost, and scalability 5. Design and build the reporting and query layer that allows business stakeholders and non-technical users to run relational SQL queries against healthcare data using familiar tooling 6. Architect the migration path for XML object store data from MSSQL into the target AWS platform, defining storage formats, partitioning strategies, and data organization for optimal query performance 7. Build and maintain AWS data catalog, schemas, and metadata management so that object store data is discoverable and queryable by business users 8. Optimize query performance and cost across chosen AWS services – partitioning, compression, file formats, and query pattern tuning 9. Work directly with business stakeholders and analysts to understand reporting requirements and translate them into durable, performant data models and query patterns 10. Collaborate with back-end C#/.Net engineer to ensure data flows cleanly from Electronic Data Interchange (EDI) processing pipelines into the new data layer 11. Implement and maintain CI/CD pipelines for data infrastructure using AWS-native tooling (CodePipeline, CodeBuild, and CodeDeploy) 12. Apply Infrastructure as Code (IaC) practices using AWS Cloud Development Kit (CDK), CloudFormation, or Terraform 13. Document architecture decisions, data flows, and data dictionaries clearly for both technical and non-technical audiences From Required Skills and Experience: - 8+ years’ experience in software or data engineering with a strong AWS focus - Proven experience architecting and executing cloud data platform migrations in production enterprise or healthcare environments - Track record of evaluating and selecting AWS data services to meet business reporting and query requirements - Experience delivering reporting or analytics solutions that serve non-technical business users - Deep hands-on AWS experience across data-oriented services – S3, Athena, Glue, Aurora, DynamoDB, Redshift, OpenSearch, Lambda, IAM, and Cloudwatch - Strong SQL skills with the ability to design relational query layers over semi-structured or non-relational data (XML, JSON) - Experience working with XML-heavy data stores – parsing, querying, and transforming XML at scale - An ability to evaluate trade-offs across AWS data services and make architecture recommendations based on cost, performance, and business requirements - Familiarity with AWS analytics and reporting services, including Athena, QuickSight, RedShift, or equivalent Business Intelligence (BI) tooling - Proficiency with Git and GitHub - branching strategies, pull requests, and collaborative workflows - Familiarity with CI/CD practices and AWS-native tooling (CodePipeline, CodeBuild, and CodeDeploy) - IaC experience (AWS CDK, CloudFormation, or Terraform) - Strong ability to communicate technical architecture decisions and trade-offs to non-technical stakeholders - Experience gathering and translating business reporting requirements into technical data models - Comfort driving ambiguous architecture decisions to resolutions with limited direction - Experience with Agile methodologies (Scrum, Kanban) and JIRA - Strong documentation habits – architecture diagrams, data dictionaries, migration runbooks Professional Certifications: None but AWS certifications are a bonus Desired experience: - Electronic Data Interchange X.12 (EDI) Medical Claims X.12, Medical Claims (837, 835, 277CA, etc), Health Level (HL7), Fast Healthcare Interoperability Resources (FHIR) - Familiarity with C#/.Net back-end services for integration touchpoints - Experience with Entity Framework migration or deprecation projects - Experience with healthcare payer/Pharmacy Benefit Management (PBM) systems, clearinghouses, or pharmacy operations - Knowledge of HIPAA compliance requirements in cloud data architecture Formal Education: Bachelor’s degree or higher in Computer Science, Engineering, or a related technical discipline; equivalent practical experience considered Citizenship Requirement: U.S. Citizenship required for this specific opportunity Security Clearance Requirements: Must possess or qualify for a Public Trust (MBI) Also notes: Recruiters or Third parties will not be considered (maybe remove as boilerplate). This is a 100% U.S. based remote position. However, candidates from CA, CO, IL, MN, NJ, NY, OR, or WA will not be considered (this is a restriction, substantive). This is a W-2 position (substantive). All interviews will be conducted on Microsoft Teams with your camera on; there will be no exceptions (maybe considered process detail, could be kept? It's not boilerplate but it's about interview process; maybe we can keep as part of About the role or a separate note? The instruction says remove application instructions. This is interview instruction, maybe considered application instruction? It's about interview process; could be considered part of the posting but not essential to role. Might be considered boilerplate? It's specific to this job. However the instruction says remove application instructions. Interview details could be considered part of application process. Safer to remove. Also: As part of