Data Platform Engineer

We need to output HTML fragment with sections: About the role? The posting includes description. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We have responsibilities (Essential Duties And Responsibilities). We have Required Skills and Experience (skills). We have Professional Certifications (none but AWS certifications are a bonus) - maybe not needed. We have Desired experience (some specifics). We have Formal Education. We have Citizenship Requirement, Security Clearance Requirements, etc. Those could be under Requirements or Qualifications. We need to avoid boilerplate like EEO, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove application instructions (like "If you have previously applied..."). We need to preserve all substantive info. So we need to include sections: Responsibilities, Requirements (maybe combine Required Skills and Experience, Desired experience, Formal Education, Citizenship, Security Clearance). Could also have Qualifications. But we should not create thin sections. Perhaps we can have sections: Responsibilities, Requirements, Qualifications, Skills? But we need to avoid duplication. Let's think: The posting includes: - Essential Duties And Responsibilities (list of duties) - Required Skills and Experience (list) - Desired experience (list) - Formal Education - Citizenship Requirement - Security Clearance Requirements - Professional Certifications (none but AWS certifications are a bonus) - Salary Range: $85,389 - $116,975 (Pay) - Location: Remote (maybe schedule? Not given) - Type: Full Time (maybe schedule? Not given) - Min. Experience: Experienced (maybe not needed) - Security Clearance Level: Public Trust (MBI) - Department: Veterans Affairs (VA) - etc. We need to include Pay section because salary range is given. Schedule? Not given. Benefits? Not given. So we should not include Benefits or Schedule sections. We need to include About the role? Could be a brief paragraph summarizing role. The posting includes location, department, type, etc. Could be considered About the role. But we need to avoid filler. We could create an About the role section with a paragraph summarizing the role: Data Platform Engineer remote for VA, focusing on modernizing healthcare data platform, migrating from MSSQL XML to AWS, etc. That is substantive. We must not repeat job title as heading. So no heading for "Data Platform Engineer". Use

for sections. We need to use

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

  for prose. We need to preserve all substantive info, not invent or summarize away detail. So we need to keep details like specific AWS services, etc. We need to remove boilerplate: EEO, equal-opportunity, scam-warning, etc. Also remove duplicated lines like "U.S Citizenship is required for this specific opportunity." appears twice; we keep once. Also remove "If you have previously applied..." etc. Also remove "Applications are still under review." maybe not needed? It's not substantive? Might be considered boilerplate. Probably remove. Also remove "Military Veterans are highly encouraged to apply!" maybe considered EEO? It's encouragement but could be kept? Might be considered EEO-related; safer to remove. Also remove "Powered by JazzHR ZiPWK4bB35" etc. Now craft HTML. Structure:

  About the role

  Syms Strategic Group (SSG) is seeking a Data Platform Engineer for a full‑time, remote position supporting the Veterans Affairs (VA) department. The role focuses on modernizing the healthcare data platform, migrating from a Microsoft SQL XML object store to a scalable, cloud‑native AWS architecture, and enabling business stakeholders to run performant SQL‑based reports and queries.

  Responsibilities

  • Lead the next phase of the healthcare data platform modernization
  • 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
  • Evaluate and decide the right AWS data strategy for the platform
  • 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
  • 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
  • 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
  • Build and maintain AWS data catalog, schemas, and metadata management so that object store data is discoverable and queryable by business users
  • Optimize query performance and cost across chosen AWS services – partitioning, compression, file formats, and query pattern tuning
  • Work directly with business stakeholders and analysts to understand reporting requirements and translate them into durable, performant data models and query patterns
  • Collaborate with back‑end C#/.Net engineer to ensure data flows cleanly from Electronic Data Interchange (EDI) processing pipelines into the new data layer
  • Implement and maintain CI/CD pipelines for data infrastructure using AWS‑native tooling (CodePipeline, CodeBuild, and CodeDeploy)
  • Apply Infrastructure as Code (IaC) practices using AWS Cloud Development Kit (CDK), CloudFormation, or Terraform
  • Document architecture decisions, data flows, and data dictionaries clearly for both technical and non‑technical audiences

  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
  • 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

  Desired Experience

  • Experience with 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

  Education

  Bachelor’s degree or higher in Computer Science, Engineering, or a related technical discipline; equivalent practical experience considered.

  Citizenship and Security Clearance

  U.S. Citizenship required for this specific opportunity. Must possess or qualify for a Public Trust (MBI) security clearance.

  Pay

  Salary range: $85,389 – $116,975.

  We should not include sections like Benefits, Schedule. Also we should not repeat job title. Ensure no extra whitespace? It's fine. Check for any boilerplate left: We removed EEO, etc. We kept "U.S. Citizenship required". Good. We kept "Public Trust (MBI)". Good. We kept "Remote" in About the role paragraph. We kept "Full Time" in About the role. We kept "Department: Veterans Affairs (VA)" in About the role. We kept "Min. Experience: Experienced" not needed; we omitted. We kept "Security Clearance Level: Public Trust (MBI)" we included. We kept "Location: Remote" included. We kept "Type: Full Time" included. We kept "Department: Veterans Affairs (VA)" included. We kept "Salary Range: $85,389 - $116,975" included. We kept "If you have previously applied..." removed. We kept "Applications are still under review." removed. We kept "Military Veterans are highly encouraged to apply!" removed. We kept "Recruiters or Third parties will not be considered" removed. We kept "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 substantive restriction; should we keep? It's a location restriction. It's substantive. Should we include? It's not a standard heading but could be part of About the role or a separate section like "Location Restrictions". However we only allowed headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could incorporate location restriction into About the role paragraph. That seems okay. Add to About the role: "This is a 100% U.S.-based remote position; however, candidates residing in CA, CO, IL, MN, NJ, NY, OR, or WA will not be considered." Also we have "This is a W-2 position". Could add. Also "All interviews will be conducted on Microsoft Teams with your camera on; there will be no exceptions" maybe not needed? It's process detail; could be considered boilerplate? Might be considered substantive but not in allowed headings. Could be omitted as it's not about role duties/requirements. Probably safe to omit. Also "As part of our screening process, you will be requested to provide a link to your LinkedIn profile" - could be omitted. Also "U.S Citizenship is required for this specific opportunity. Applicants selected will be subject to a government security investigation and must meet eligibility requirements for access to classified information and be able to obtain a government-granted security clearance. Individuals may also be subject to a background investigation including, but not limited to criminal history, employment and education verification, drug testing, and creditworthiness." This is substantive