AWS Data Engineer - II
Syms Strategic Group, LLC (SSG) · Melbourne, FL · 3 wk ago
On-siteInformation Technology$85k–$117k/yrFull-time
We need to output HTML fragment with sections: About the role? Not present. Responsibilities: Essential Duties And Responsibilities. Requirements: Required Skills and Experience. Possibly Qualifications? Could combine. Benefits? Not given. Pay: Salary Range given. Schedule: Not given (Full Time). Should we include Pay and Schedule sections only if posting actually states them. Salary Range is given, so include Pay section. Schedule: "Full Time" is given, so include Schedule section. Benefits: none. So sections: Responsibilities, Requirements (or Skills), Pay, Schedule. Also maybe Qualifications? The posting includes Required Skills and Experience, plus Professional Certifications, Years of Professional Experience, Desired experience, Formal Education, Citizenship Requirement, Security Clearance Requirements. Those could be under Requirements or Qualifications. We'll make a Requirements section covering required skills and experience, plus qualifications like education, citizenship, clearance. Could also have a Qualifications section for education/certifications. But we should avoid thin sections. Maybe combine all into Requirements. Use
- for list items. For prose use
. Need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title. Must not include boilerplate like EEO, etc. Remove duplicated lines. Also remove "If you have previously applied..." etc. Also remove recruitment notes like "CRITICAL NOTES:"? Those are substantive? They contain important info: SSG will not make assumptions, etc. Might be considered boilerplate? It's about application process; maybe we should remove as it's not core job content. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The CRITICAL NOTES includes application instructions (must answer screening questions). Likely to be removed. Also "Recruiters or Third parties will not be considered" etc. Remove. Also "This is a 100% U.S. based remote position..." maybe keep as it's location info? It's about remote and state restrictions. That's substantive. Keep. Also "All interviews will be conducted on Microsoft Teams..." maybe remove as application instruction. Remove. Also "As part of our screening process, you will be requested to provide a link to your LinkedIn profile" remove. Also "U.S Citizenship is required..." duplicate. Keep citizenship requirement once. Also EEO statement remove. Also "Powered by JazzHR..." remove. We need to preserve all substantive information: duties, responsibilities, required skills, experience, desired experience, education, citizenship, clearance, salary range, full-time, remote, location restrictions, etc. Let's extract sections. Responsibilities: list of duties from "Essential Duties And Responsibilities" paragraph. It's a long paragraph with multiple sentences. We should break into bullet points for each duty. The instruction: Use
- for any list of duties/requirements/benefits. So we need to make a list. We'll parse each duty sentence.
Sentences:
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
That's all.
Now Requirements: Required Skills and Experience list. Also Professional Certifications, Years of Professional Experience, Desired experience, Formal Education, Citizenship Requirement, Security Clearance Requirements.
We'll create a Requirements section with sub-lists? Could just list all items as bullet points.
Let's extract each bullet:
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
Professional Certifications:
- None but AWS certifications are a bonus
Years of Professional Experience:
- n/a (maybe we should not include if it's n/a? The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. For Years of Professional Experience, it's "n/a". That's placeholder; we should omit that line.
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
Citizenship Requirement:
- U.S. Citizenship required for this specific opportunity
Security Clearance Requirements:
- Must possess or qualify for a Public Trust (MBI)
Also note: "U.S Citizenship is required for this specific opportunity." duplicate; we keep once.
Also "Applicants selected will be subject to a government security investigation and must meet eligibility requirements for access to classified information and be able to obtain a government-granted security clearance." That's part of clearance requirement; we can include.
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 also part of clearance/background; we could include but maybe it's boilerplate? It's about security clearance process; could be considered substantive. We'll include as part of Security Clearance Requirements.
Now Pay section: Salary Range: $85,389 - $116,975
Schedule section: Full Time (also remote). Could also include location restrictions: Remote but candidates from certain states not considered. That's location info; maybe include in Schedule or a separate Location section? Not required headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No Location heading. Could put location info in Schedule section as note. Or we could add a short paragraph under Schedule about remote and state restrictions. Since Schedule heading is allowed, we can include both full-time and remote details.
We must not create Benefits section because none.
We must not create Qualifications section unless we have specific content; we could but we already have Requirements covering qualifications. Might be okay to have Qualifications for education/certifications. But to avoid thin sections, we can combine everything into Requirements.
Thus output:
Responsibilities
- ... ...
Requirements
- ... ...
Pay
$85,389 - $116,975
Schedule
Full‑time, 100% remote (U.S.–based). Candidates from CA, CO, IL, MN, NJ, NY, OR, or WA will not be considered.
We need to ensure we preserve all substantive information: also mention that it's a W-2 position? That's employment type; could be included in Schedule or a separate note. Could add to Schedule: "W‑2 position". Also mention that interviews will be conducted on Microsoft Teams with camera on? That's application instruction; remove. Also mention that recruiters/third parties not considered; remove. Also mention that military veterans encouraged; that's a substantive note? Could be included maybe in Responsibilities? Not exactly. Could add a short paragraph under Requirements? Might be considered EEO? It's encouragement of veterans is not EEO but a preference. Might keep as a note in Schedule or a separate line. The instruction: remove EEO/equal-opportunity/scam-warning boilerplate. Veteran encouragement is not EEO but a specific encouragement; could be considered substantive. I'd keep it maybe as a note in Schedule or a separate short paragraph under Requirements? Might be better to include in Schedule section as a note: "Military veterans are highly encouraged to apply." However that's more about application encouragement; could be considered application instruction? It's not instruction to apply but encouragement. I'd keep it. Also "If you have previously applied to Syms Strategic Group (SSG), there is no need to reapply. Applications are still under review." That's application instruction; remove. Also "CRITICAL NOTICES" etc removed. Also "This is a W-2 position" keep. Also "All interviews will be conducted on Microsoft Teams with your camera on; there will be no exceptions" remove. Also "As part of our screening process, you will be requested to provide a link to your LinkedIn profile" remove. Also "U.S Citizenship is required for this specific opportunity." duplicate; we have
- for any list of duties/requirements/benefits. So we need to make a list. We'll parse each duty sentence.
Sentences:
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
That's all.
Now Requirements: Required Skills and Experience list. Also Professional Certifications, Years of Professional Experience, Desired experience, Formal Education, Citizenship Requirement, Security Clearance Requirements.
We'll create a Requirements section with sub-lists? Could just list all items as bullet points.
Let's extract each bullet:
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
Professional Certifications:
- None but AWS certifications are a bonus
Years of Professional Experience:
- n/a (maybe we should not include if it's n/a? The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. For Years of Professional Experience, it's "n/a". That's placeholder; we should omit that line.
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
Citizenship Requirement:
- U.S. Citizenship required for this specific opportunity
Security Clearance Requirements:
- Must possess or qualify for a Public Trust (MBI)
Also note: "U.S Citizenship is required for this specific opportunity." duplicate; we keep once.
Also "Applicants selected will be subject to a government security investigation and must meet eligibility requirements for access to classified information and be able to obtain a government-granted security clearance." That's part of clearance requirement; we can include.
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 also part of clearance/background; we could include but maybe it's boilerplate? It's about security clearance process; could be considered substantive. We'll include as part of Security Clearance Requirements.
Now Pay section: Salary Range: $85,389 - $116,975
Schedule section: Full Time (also remote). Could also include location restrictions: Remote but candidates from certain states not considered. That's location info; maybe include in Schedule or a separate Location section? Not required headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No Location heading. Could put location info in Schedule section as note. Or we could add a short paragraph under Schedule about remote and state restrictions. Since Schedule heading is allowed, we can include both full-time and remote details.
We must not create Benefits section because none.
We must not create Qualifications section unless we have specific content; we could but we already have Requirements covering qualifications. Might be okay to have Qualifications for education/certifications. But to avoid thin sections, we can combine everything into Requirements.
Thus output: