AWS Data Engineer - II
Syms Strategic Group, LLC (SSG) · Tampa, FL · 4 wk ago
On-siteInformation Technology$85k–$117k/yrFull-time
We need to output HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also must not include sections with filler like "commensurate with experience". We have salary range given: $85,389 - $116,975. So we can include Pay section with that. Benefits? Not mentioned explicitly. No benefits listed. So we should not include Benefits. Schedule? Not mentioned (full time). Could include Schedule? The posting says Type: Full Time. That's schedule info. Could include Schedule section with "Full Time". But we need to check rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Type: Full Time, so we can include Schedule. However we also have Location: Remote, Department: Veterans Affairs (VA), Min. Experience: Experienced, Security Clearance Level: Public Trust (MBI), Citizenship Requirement: U.S. Citizenship required, etc. Those could go under About the role or Requirements. We need to decide sections.
We have:
- About the role: could include location, remote, department, type, security clearance, citizenship, etc.
- Responsibilities: the list of essential duties.
- Requirements: maybe years experience, AWS focus, etc.
- Qualifications: maybe education, certifications, professional certifications none but AWS certs a bonus, desired experience, etc.
- Skills: maybe list of required skills.
But we must avoid duplication. The posting already has "Required Skills and Experience" and then a list. Also "Professional Certifications", "Years of Professional Experience", "Desired experience", "Formal Education", "Citizenship Requirement", "Security Clearance Requirements". We need to map these to sections.
We need to preserve all substantive info. So we need to include everything except boilerplate.
We need to decide sections to avoid too many thin ones. Perhaps combine some.
We could have:
. Ensure we captured all. Let's list them:
1. Lead the next phase of the healthcare data platform modernization
2. 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
3. Evaluate and decide the right AWS data strategy for the platform
4. 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
5. 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
6. 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
7. Build and maintain AWS data catalog, schemas, and metadata management so that object store data is discoverable and queryable by business users
8. Optimize query performance and cost across chose AWS services – partitioning, compression, file formats, and query pattern tuning
9. Work directly with business stakeholders and analysts to understand reporting requirements and translate them into durable, performant data models and query patterns
10. Collaborate with back-end C#/.Net engineer to ensure data flows cleanly from Electronic Data Interchange (EDI) processing pipelines into the new data layer
11. Implement and maintain CI/CD pipelines for data infrastructure using AWS-native tooling (CodePipeline, CodeBuild, and CodeDeploy)
12. Apply Infrastructure as Code (IaC) practices using AWS Cloud Development Kit (CDK), CloudFormation, or Terraform
13. Document architecture decisions, data flows, and data dictionaries clearly for both technical and non-technical audiences
We have all.
Now Requirements: we used the list from "Required Skills and Experience". That list includes many items. Let's verify we captured all.
From posting:
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
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
We captured all.
Now Qualifications: we need to include Professional Certifications, Years of Professional Experience (n/a), Desired experience, Formal Education, Citizenship Requirement, Security Clearance Requirements maybe. But we already included citizenship and security clearance in About the role. Could also include them there. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also must not include sections with filler like "commensurate with experience". We have salary range given: $85,389 - $116,975. So we can include Pay section with that. Benefits? Not mentioned explicitly. No benefits listed. So we should not include Benefits. Schedule? Not mentioned (full time). Could include Schedule? The posting says Type: Full Time. That's schedule info. Could include Schedule section with "Full Time". But we need to check rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Type: Full Time, so we can include Schedule. However we also have Location: Remote, Department: Veterans Affairs (VA), Min. Experience: Experienced, Security Clearance Level: Public Trust (MBI), Citizenship Requirement: U.S. Citizenship required, etc. Those could go under About the role or Requirements. We need to decide sections.
We have:
- About the role: could include location, remote, department, type, security clearance, citizenship, etc.
- Responsibilities: the list of essential duties.
- Requirements: maybe years experience, AWS focus, etc.
- Qualifications: maybe education, certifications, professional certifications none but AWS certs a bonus, desired experience, etc.
- Skills: maybe list of required skills.
But we must avoid duplication. The posting already has "Required Skills and Experience" and then a list. Also "Professional Certifications", "Years of Professional Experience", "Desired experience", "Formal Education", "Citizenship Requirement", "Security Clearance Requirements". We need to map these to sections.
We need to preserve all substantive info. So we need to include everything except boilerplate.
We need to decide sections to avoid too many thin ones. Perhaps combine some.
We could have:
About the role
Remote position supporting the Veterans Affairs (VA) department. Full‑time. Requires U.S. citizenship and eligibility for a Public Trust (MBI) security clearance.
Responsibilities
- Lead the next phase of the healthcare data platform modernization... ... etc.
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 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
- AWS certifications are a bonus (no formal certifications required)
- 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
Pay
Salary range: $85,389 – $116,975 per year.
Schedule
Full‑time.
We should not include Benefits because none given. We must ensure we didn't include any boilerplate like EEO, etc. We removed those. Check for duplicate content: We included responsibilities list exactly as in posting. We need to ensure we didn't miss any responsibilities. Let's copy the responsibilities from posting: Essential Duties And 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 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 We need to include each as separateor drop it." So we can include citizenship and security clearance in About the role paragraph. We also have "Professional CertificationsNone but AWS certifications are a bonus". We included that