Data Platform Engineer

We need to output only HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes: location remote, department VA, type full time, min experience experienced, security clearance public trust, salary range. Also essential duties and responsibilities (list). Required skills and experience (list). Also desired experience (list). Also professional certifications (none but AWS certifications a bonus). Formal education. Citizenship requirement. Security clearance requirements (already). Critical notes (some boilerplate). We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "If you have previously applied..." etc. Also remove "Military Veterans are highly encouraged to apply!" maybe not boilerplate but could be considered encouragement but it's okay? It's not boilerplate but maybe keep? It's not a section heading. Could be part of About the role? Probably we can include in a paragraph under About the role. We need to not repeat job title as heading. So we start with maybe

About the role

then a paragraph summarizing location, department, type, clearance, salary range, etc. Use

. Then

Responsibilities

with

• for each duty. Then

  Requirements

  maybe combine Required Skills and Experience and Desired experience? Could separate Qualifications and Skills? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose which to include. We have Responsibilities, Requirements (maybe combine required skills and experience), Qualifications (education, citizenship, clearance), Skills (maybe list of technical skills), Benefits (none given), Pay (we have salary range), Schedule (full time). We should include Pay and Schedule only if posting actually states them. It does: Salary Range given, Type: Full Time. So we can include Pay and Schedule sections. We must not emit sections with filler like "commensurate with experience". We have concrete salary range and full time. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all duties, all required skills, desired experience, certifications, education, citizenship, clearance, etc. We must not repeat job ID etc. We need to avoid duplication: The posting repeats "U.S Citizenship is required for this specific opportunity." twice; we should include once. Also "CRITICAL NOTES:" includes many boilerplate; we should remove those lines (like SSG will not make assumptions..., Recruiters or Third parties will not be considered, This is a 100% U.S. based remote position..., etc). Those are mostly boilerplate or application instructions; we should drop them. Also "As part of our screening process, you will be requested to provide a link to your LinkedIn profile" maybe also boilerplate; drop. Also "Individuals may also be subject to a background investigation..." maybe part of security clearance; but could be considered substantive? It's about clearance process; maybe keep as part of Security Clearance Requirements? But it's more boilerplate. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The background investigation details could be considered part of security clearance process; but it's somewhat boilerplate. However it's specific to the role (government security investigation). Might be considered substantive. But the instruction says remove legal/EEO etc. This is not EEO but security clearance details. Might be okay to keep. However we already have Security Clearance Requirements heading; we could include details there. We need to decide sections: About the role (location, department, type, clearance, salary). Responsibilities (list). Requirements (maybe combine required skills and experience). Qualifications (education, citizenship). Skills (maybe list of technical skills). Benefits (none given, so omit). Pay (salary range). Schedule (full time). Also maybe Desired experience could be under Requirements or Skills. But we have separate "Desired experience" list; we could include under Requirements or Skills. Since we have both Required Skills and Experience and Desired experience, we could make a Requirements section that includes both required and desired? Or we could have Qualifications (education, citizenship, clearance) and Skills (technical). The desired experience could be under Skills as "Desired experience". But we need to preserve all detail; we can include both required and desired under Requirements as sub-bullets maybe with note. But better to follow headings: Requirements (maybe for required skills), Qualifications (education, citizenship, clearance), Skills (technical skills and desired experience). However the instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have those headings. Thus:

  About the role

  Remote position within the Veterans Affairs (VA) department. Full‑time, W‑2 role requiring a Public Trust (MBI) security clearance. U.S. citizenship is required. Salary range: $85,389 – $116,975.

  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

  Requirements

  • 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

  Qualifications

  • Bachelor’s degree or higher in Computer Science, Engineering, or a related technical discipline; equivalent practical experience considered
  • U.S. citizenship required for this specific opportunity
  • Must possess or qualify for a Public Trust (MBI) security clearance

  Skills

  • Desired 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
  • AWS certifications are a bonus

  Pay

  $85,389 - $116,975

  Schedule

  Full Time

  We need to ensure no duplicated content. We included salary range in About the role and also Pay section; that duplicates. The instruction: do not repeat job title as heading, but duplication of content maybe okay? It says "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't explicitly forbid duplication, but better to avoid duplication. We could put salary range only in Pay section and not in About the role. But About the role we need to convey location, department, type, clearance, citizenship. We can omit salary there and keep only in Pay. Similarly schedule only in Schedule section. Thus adjust About the role paragraph: Remote position within the Veterans Affairs (VA) department. Full‑time, W‑2 role requiring a Public Trust (MBI) security clearance. U.S. citizenship is required. Now Pay section: Salary range: $85,389 – $116,975. Schedule section: Full Time. Check for any other duplicated lines: We have "U.S. citizenship required" appears in Qualifications and About the role? We removed from About the role, kept only in Qualifications. Good. Check for any boilerplate left: We removed critical notes etc. Ensure no mention of "Recruiters or Third parties will not be considered", "As part of our screening process, you will be requested to provide a link to your LinkedIn profile", etc.