Data Platform Engineer

We need to output HTML fragment with sections: About the role? The posting includes location, department, type, min experience, security clearance, salary range. Those could be in a short paragraph. Then Essential Duties and Responsibilities as a list. Then Required Skills and Experience as a list. Possibly also Professional Certifications? It says None but AWS certifications are a bonus – could be a bullet. Also Desired experience etc. We need to include sections only when there is real specific content. We have: About the role (maybe combine location, department, type, min experience, security clearance, salary). Could be a paragraph. Then Responsibilities (Essential Duties And Responsibilities). Then Requirements (Required Skills and Experience). Possibly also Qualifications (Professional Certifications, Desired experience, Formal Education, Citizenship Requirement, Security Clearance Requirements). But we should avoid thin sections. We can combine qualifications into one section "Qualifications". But we need to preserve all substantive info. Let's decide sections: About the role (location, department, type, min experience, security clearance, salary). Responsibilities (list). Required Skills and Experience (list). Qualifications (maybe combine Professional Certifications, Desired experience, Formal Education, Citizenship Requirement, Security Clearance Requirements). However, some of those are already covered: security clearance already in About the role? Might duplicate. Better to keep security clearance in About the role. Then Qualifications includes Professional Certifications, Desired experience, Formal Education, Citizenship Requirement. Also maybe "Benefits", "Pay", "Schedule" only if present. Pay is present as salary range, we could put Pay section. But we already included salary in About the role. The instruction: Prefer a few substantive sections over many thin ones. So maybe we have About the role (including location, department, type, min experience, security clearance, salary). Responsibilities. Required Skills and Experience. Qualifications (including certifications, desired experience, education, citizenship). That's four sections. We must not repeat job title as heading. Use

for section headings. Use

• for any list. Use

  for prose. We must not include boilerplate like EEO, etc. Remove duplicated lines. Let's extract content. About the role: Location: Remote. Department: Veterans Affairs (VA). Type: Full Time. Min. Experience: Experienced (maybe "Experienced" but not specific years? It says Min. Experience: Experienced). Security Clearance Level: Public Trust (MBI). Salary Range: $85,389 - $116,975. Also note: U.S. Citizenship required. Could include citizenship here or in qualifications. Since citizenship is a requirement, maybe include in About the role or Qualifications. I'd put in About the role: U.S. Citizenship required. Thus About the role paragraph: "Syms Strategic Group (SSG) is seeking a talented Data Platform Engineer. Location: Remote. Department: Veterans Affairs (VA). Type: Full Time. Minimum experience: Experienced. Security clearance: Public Trust (MBI). Salary range: $85,389 – $116,975. U.S. citizenship required." Now Responsibilities: list each bullet from Essential Duties And Responsibilities. Need to preserve all substantive info. Let's extract bullet points: - 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 chose 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 Now Required Skills and Experience list: - 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 Now Qualifications section: include Professional Certifications (None but AWS certifications are a bonus), Desired experience (list), Formal Education, Citizenship Requirement (maybe already in About role but we can keep), Security Clearance Requirements (maybe duplicate). Since we already put security clearance in About role, we might not repeat. But to preserve all info, we could keep it in About role and not duplicate. However the instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we put security clearance only in About role, it's preserved. Good. Desired experience list: - 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. (Already in About role but we could keep; but to avoid duplication maybe we keep only in About role and not repeat. However the instruction says do not repeat job title as heading, but doesn't forbid repeating info. But better to avoid duplication. We'll keep citizenship in About role and not repeat in Qualifications. Professional Certifications: None but AWS certifications are a bonus. Thus Qualifications section will have sub-lists? We can just make a

  with items, some items containing sublists? Could embed
  • with inner
    . But simpler: we can make separate
    for each category? But that would be many thin sections. Instead we can make a single
    where each
    • contains a phrase possibly with commas. For desired experience we can list each as separate
    • . For formal education as
    • . For certifications as
    • . That seems fine. Thus Qualifications
      items: - 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. We need to embed nested list for desired experience. That's okay. Now we need to output only HTML fragment, no markdown fences. Let's craft:

      About the role

      Syms Strategic Group (SSG) is seeking a talented Data Platform Engineer. Location: Remote. Department: Veterans Affairs (VA). Type: Full Time. Minimum experience: Experienced. Security clearance: Public Trust (MBI). Salary range: $85,389 – $116,975. U.S. citizenship required.

      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