AWS Data Engineer - II

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 section? Yes, salary range is provided. Schedule: Full Time is given, but it's a type. Should we include Schedule? The rule: include section only when posting has real, specific content. Full Time is specific. Could include Schedule section with "Full Time". However they said prefer few substantive sections over many thin ones. Might combine Pay and Schedule? But they said use headings for sections like Pay, Schedule. If we have both, we could include both. But maybe better to include Pay and not Schedule because Full Time is obvious? But rule: include section only when posting has real, specific content for it. It does have "Type: Full Time". That's specific. So include Schedule. Benefits: none given, so omit. We need to remove boilerplate: EEO, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove "If you have previously applied..." etc. Also remove "Military Veterans are highly encouraged to apply!"? That's not boilerplate but maybe keep? It's a statement encouraging veterans; it's substantive? Might keep as part of About the role? But we have no About the role section. Could include a short paragraph under Responsibilities? Better to keep as a separate note? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The veteran encouragement is not boilerplate; it's a statement. Could keep as a paragraph under Responsibilities or maybe under About the role. Since we don't have About the role, we could create a brief "About the role" paragraph that includes that encouragement? But we must not invent content. We can include that statement as a paragraph under Responsibilities? Might be odd. Better to create a section "About the role" with that statement? But that would be adding a heading not originally present. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we can use those headings if content exists. Does the posting have content for "About the role"? It has a brief intro: "Syms Strategic Group (SSG) is seeking a talented Senior Systems Engineer (Amazon Web Services (AWS) Data Engineer) - II Location: Remote Department: Veterans Affairs (VA) Type: Full Time Min. Experience: Experienced Security Clearance Level: Public Trust (MBI) Salary Range: $85,389 - $116,975". That's basically role overview. Could treat that as About the role. However they said do NOT repeat the job title as a heading (the page already shows it). But About the role is okay. We need to preserve all substantive information. So we need to include location remote, department VA, type full time, min experience experienced, security clearance public trust MBI, salary range. Also note about citizenship requirement, etc. Those are requirements. We need to decide sections: About the role (intro), Responsibilities (essential duties), Requirements (required skills and experience plus desired experience, certifications, education, citizenship, clearance). Pay section (salary range). Schedule section (full time). Possibly Qualifications? Could merge with Requirements. We must not create sections with filler like "commensurate with experience". We have specific content. Let's extract: About the role: Syms Strategic Group (SSG) is seeking a talented Senior Systems Engineer (Amazon Web Services (AWS) Data Engineer) - II Location: Remote Department: Veterans Affairs (VA) Type: Full Time Min. Experience: Experienced Security Clearance Level: Public Trust (MBI) Salary Range: $85,389 - $116,975 But we will move Salary Range to Pay section, and Type to Schedule. So About the role could be: Syms Strategic Group (SSG) is seeking a talented Senior Systems Engineer (Amazon Web Services (AWS) Data Engineer) - II. Location: Remote. Department: Veterans Affairs (VA). Min. Experience: Experienced. Security Clearance Level: Public Trust (MBI). (We could also mention that U.S. Citizenship required later.) Responsibilities: list of duties from "Essential Duties And Responsibilities". We'll convert each sentence into

. Requirements: combine Required Skills and Experience, Desired experience, Professional Certifications, Years of Professional Experience (n/a), Formal Education, Citizenship Requirement, Security Clearance Requirements, plus maybe other notes like "CRITICAL NOTES" etc. But we need to preserve substantive info. The CRITICAL NOTES includes: SSG will not make assumptions regarding your qualifications... Recruiters or Third parties will not be considered... This is a 100% U.S. based remote position... candidates from certain states will not be considered... This is a W-2 position... All interviews will be conducted on Microsoft Teams with camera on... link to LinkedIn profile... U.S Citizenship is required... background investigation... Equal Opportunity Employer... Some of that is boilerplate (EEO) but some is substantive: remote position, state restrictions, W-2, interview method, LinkedIn request, citizenship requirement, background investigation. We should keep those substantive notes. However the instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The CRITICAL NOTES includes application instructions (provide LinkedIn link, camera on Teams, etc.) Those are application instructions, which we should remove. Also "Recruiters or Third parties will not be considered" is a policy, maybe keep? It's not boilerplate but could be considered a note. Might keep as part of Requirements? But it's more about process. The instruction says remove application instructions. So we should remove lines about providing LinkedIn link, camera on Teams, etc. Also remove "Recruiters or Third parties will not be considered" maybe considered a policy but not application instruction. Might keep? Safer to keep only substantive qualifications: citizenship requirement, security clearance, state restrictions, W-2, maybe remote. Also "U.S Citizenship is required for this specific opportunity." duplicate. We'll keep: U.S. Citizenship required. Must possess or qualify for a Public Trust (MBI). Candidates from CA, CO, IL, MN, NJ, NY, OR, or WA will not be considered. This is a W-2 position. (Remote already in About the role). Also maybe "All interviews will be conducted on Microsoft Teams with your camera on; there will be no exceptions" is application instruction, remove. "As part of our screening process, you will be requested to provide a link to your LinkedIn profile" remove. "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 substantive about clearance process; keep? It's part of security clearance requirements. Could keep under Requirements. We'll also keep "Syms Strategic Group, LLC is an Equal Opportunity Employer." That's EEO boilerplate, remove. Now format. We'll produce:

About the role

Syms Strategic Group (SSG) is seeking a talented Senior Systems Engineer (Amazon Web Services (AWS) Data Engineer) - II. Location: Remote. Department: Veterans Affairs (VA). Minimum experience: Experienced. Required security clearance: Public Trust (MBI).

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 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

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 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
• 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