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. We must include sections only if posting has 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 (list). We have Formal Education. Citizenship Requirement. Security Clearance Requirements. Also Salary Range given: $85,389 - $116,975. That's Pay. So we should include Pay section. No explicit Benefits or Schedule. So we omit those. We need to preserve all substantive info, not invent. Remove boilerplate like EEO, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove "If you have previously applied..." etc. Also remove "Applications are still under review." etc. Also remove "Military Veterans are highly encouraged to apply!" maybe keep? It's substantive? It's encouragement but maybe considered boilerplate? It's not required but could be kept as part of About the role? Probably we can keep as part of About the role. But we need to avoid fluff. Might keep as a note. We need to structure: maybe

About the role

with a paragraph summarizing role location remote, department VA, type full time, min experience experienced, security clearance Public Trust (MBI), salary range. Then

Responsibilities

with

• each duty. Then

  Required Skills and Experience

  with
  • . Then

    Desired Experience

    with
    • . Then

      Education

      with

      . Then

      Citizenship and Security Clearance

      maybe combine? Could have separate sections: Citizenship Requirement, Security Clearance Requirements. But we need to avoid thin sections. Could combine into one

      Eligibility Requirements

      . But spec says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It didn't forbid other headings? It says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we can use those headings, but not limited? Probably we should stick to those headings where applicable. We have Pay, Responsibilities, Skills (maybe Required Skills and Experience maps to Skills), Requirements (maybe includes experience, clearance, citizenship), Qualifications (maybe education). Let's map: - About the role: location, department, type, min experience, security clearance, salary? Salary is Pay section separate. - Responsibilities: essential duties. - Requirements: maybe security clearance, citizenship, US based remote restrictions, etc. - Qualifications: education, certifications. - Skills: required skills and experience. - Pay: salary range. We should not include Benefits or Schedule. We need to avoid filler like "commensurate with experience". Not present. Let's extract details. About the role: Syms Strategic Group (SSG) is seeking a talented 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 Also note: "If you have previously applied..." etc remove. "Military Veterans are highly encouraged to apply!" maybe keep as a note but could be considered boilerplate? It's encouragement but not required. Might keep as part of About the role? It's not essential but we can keep as a sentence. We'll include: "Military Veterans are highly encouraged to apply!" as a paragraph. Now Responsibilities: list each bullet from "Essential Duties And Responsibilities". Need to break into separate li. Let's copy them: - 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 each bullet. - 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 Now Professional Certifications: "None but AWS certifications are a bonus" - maybe we can include under Qualifications as a note. 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. Security Clearance Requirements: Must possess or qualify for a Public Trust (MBI) Also note: "CRITICAL NOTES: SSG will not make assumptions regarding your qualifications..." etc remove boilerplate. Also "Recruiters or Third parties will not be considered" remove. "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" - that's a requirement (location restriction). Should we include? It's substantive. Could be part of Requirements. Also "This is a W-2 position". Also "All interviews will be conducted on Microsoft Teams with your camera on; there will be no exceptions". Also "As part of our screening process, you will be requested to provide a link to your LinkedIn profile". Also "U.S Citizenship is required for this specific opportunity." duplicate. Also "Applicants selected will be subject to a government security investigation..." etc maybe part of security clearance. Also "Individuals may also be subject to a background investigation including, but not limited to criminal history, employment and education verification, drug testing, and creditworthiness." That's part of security clearance process. Might include under Security Clearance Requirements. We need to preserve all substantive info, but we can condense into paragraphs/lists. We must not repeat job title as heading. Already not. We must not put Job ID/requisition numbers as headings. We need to output only HTML fragment. Let's decide sections:

      About the role

      Syms Strategic Group (SSG) is seeking a Data Platform Engineer for a remote, full‑time position supporting the Veterans Affairs (VA). The role requires experienced candidates with a Public Trust (MBI) security clearance. Military veterans are highly encouraged to apply.

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

      But Pay section separate. We could put salary in Pay section. Let's follow spec: Pay section for salary. So About the role will not include salary. We'll put salary in Pay. Thus About the role: location remote, department VA, type full time, min experience experienced, security clearance Public Trust (MBI), note about veterans. Now Pay: salary range. Now Responsibilities: as above. Now Requirements: maybe include citizenship, location restrictions (states excluded), W-2, interview process, LinkedIn link request, security clearance details (must possess or qualify for Public Trust (MBI), subject to govt security investigation, background check). Also maybe include "Must be US based remote, but candidates from CA, CO, IL, MN, NJ, NY, OR, WA not considered". Also "This is a W-2 position". Also "All interviews will be conducted on Microsoft Teams with your camera on; there will be no exceptions". Also "As part of our screening process, you will be requested to provide a link to your LinkedIn profile". Also maybe "SSG will not make assumptions regarding your qualifications..." but that's more procedural; could be omitted as boilerplate? It's a note about screening but maybe keep? It's not essential job content. Might drop. We'll keep substantive: citizenship, location restriction, W-2, interview method, LinkedIn request, security clearance details. Now Qualifications: education, professional certifications (AWS certifications bonus). Also maybe "equivalent practical experience considered". Now Skills: required skills and experience list. Now maybe also include Desired Experience as a separate section? Could be under Skills or Qualifications. But spec only lists Skills, Benefits, Pay, Schedule,