Remote AWS Data Engineer II: Healthcare Analytics

Syms Strategic Group, LLC

Warner Robins (GA)

On-site

USD 85,000 - 117,000

Full time

4 days ago

Be an early applicant

Application generator

Don’t send a generic resume — generate a resume and cover letter tailored to this exact role.

Get past ATS filters

Job summary

Syms Strategic Group, LLC seeks a Senior Systems Engineer (AWS Data Engineer) to advance a healthcare data platform. This remote, US-based role focuses on migrating XML object stores to scalable AWS architectures and delivering reliable SQL-based reporting for business users.

Requirements include 8+ years in AWS-focused data engineering, experience with data migrations, and CI/CD with Git. US citizenship and Public Trust clearance are required; veterans are encouraged to apply.

Qualifications

8+ years of 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 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.

Responsibilities

Lead the next phase of the healthcare data platform modernization.
Implement the evolution from a MSSQL XML object store toward a scalable, cloud-native AWS data architecture for SQL-based reports and queries.
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 (S3 + Athena, Aurora, DynamoDB, Redshift, OpenSearch) based on query patterns, reporting needs, cost, and scalability.
Design and build the reporting and query layer that allows business stakeholders 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 and partitioning strategies.
Build and maintain AWS data catalog, schemas, and metadata management for discoverability.
Optimize query performance and cost across AWS services – partitioning, compression, file formats, and query pattern tuning.
Work with business stakeholders to translate reporting requirements into durable data models and query patterns.
Collaborate with back-end C#/.Net engineer to ensure data flows from EDI processing pipelines into the new data layer.
Implement and maintain CI/CD pipelines for data infrastructure using AWS-native tooling.
Apply IaC practices using AWS CDK, CloudFormation, or Terraform.
Document architecture decisions, data flows, and data dictionaries clearly for technical and non-technical audiences.