AWS Data Engineer - II

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, duplicate lines, application instructions, EEO, etc. We need to parse the posting. Key info: Company: Syms Strategic Group (SSG) seeking a talented Senior Systems Engineer (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 If previously applied, no need to reapply. Applications still under review. Military Veterans encouraged. Essential Duties And Responsibilities: list of duties. Required Skills and Experience: list. Professional Certifications: None but AWS certifications are a bonus Years of Professional Experience: n/a Desired experience: list of desired (EDI X.12, HL7, FHIR, C#/.Net, Entity Framework migration, healthcare payer/PBM, HIPAA compliance) Formal Education: Bachelor’s degree or higher in CS, Engineering, or related; equivalent practical experience considered Citizenship Requirement: U.S. Citizenship required Security Clearance Requirements: Must possess or qualify for a Public Trust (MBI) CRITICAL NOTES: etc (screening questions, recruiters not considered, 100% US based remote, candidates from certain states not considered, W-2 position, interviews on Teams, camera on, link to LinkedIn, US Citizenship required again, security investigation, background investigation, EEO statement, Powered by JazzHR. We need to remove boilerplate: EEO, equal opportunity, scam warning, cookie/navigation/legal, duplicated lines, application instructions. Also remove "If you have previously applied..." maybe considered application instruction? It's about reapplying; could be considered meta but maybe keep? The instruction says remove application instructions. That line is about not needing to reapply if previously applied. That's an application instruction. So remove. "Military Veterans are highly encouraged to apply!" That's encouragement but maybe considered boilerplate? It's not EEO but it's a encouragement. Might be considered part of posting but could be kept? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Encouragement to veterans is not EEO but could be considered similar; but it's not a protected class statement; it's encouragement. Might keep? Safer to keep as it's substantive? It's not a requirement. Might be considered fluff. I'd lean to remove as it's not essential info. However, we need to preserve ALL substantive information. Encouragement is not substantive for qualifications. I'd remove. We need to include sections only when posting has real specific content. We have: - About the role: could include location, department, type, remote, etc. That's substantive. - Responsibilities: the Essential Duties And Responsibilities list. - Requirements: maybe combine Required Skills and Experience? Could be "Requirements" section. - Qualifications: maybe Formal Education, Citizenship, Security Clearance. - Skills: maybe Required Skills and Experience (technical). But we already have Requirements; maybe we separate Skills (technical) and Qualifications (education, clearance). However we must not create thin sections. Prefer few substantive sections. We could have:

About the role

with location, department, type, remote, salary range, security clearance, citizenship.

Responsibilities

with the duties list.

Requirements and Qualifications

combine required skills, experience, education, citizenship, clearance. But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include. We have Pay: salary range given. So we should include Pay section. We have Schedule: not mentioned (full time). Could infer full time but schedule not specified; we should not create Schedule unless posting states it. It says Type: Full Time. That's schedule? Might be considered schedule but not explicit hours. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It states Type: Full Time, which is schedule info. So we could include Schedule with "Full Time". However they might consider that as schedule. I'd include Schedule. Benefits: not mentioned. No benefits info. So omit Benefits. Skills: we have Required Skills and Experience; we could put that under Skills section. Requirements: maybe include experience years, security clearance, citizenship, etc. Qualifications: formal education, certifications. But we need to avoid duplication. Let's decide sections: - About the role: location (Remote), department (VA), type (Full Time), maybe also note it's 100% US based remote, but note state restrictions? That's a restriction; could be included. - Responsibilities: list duties. - Skills: list required skills and experience (technical). - Requirements: maybe years of experience, security clearance, citizenship, etc. - Qualifications: formal education, certifications. - Pay: salary range. - Schedule: Full Time. We must not repeat job title. We must not include duplicated lines. Ensure we capture all substantive info. Let's extract details. About the role: - Location: Remote (100% U.S. based remote) - Department: Veterans Affairs (VA) - Type: Full Time - Note: Candidates from CA, CO, IL, MN, NJ, NY, OR, WA will not be considered (restriction) - W-2 position - All interviews on Microsoft Teams with camera on - Request to provide LinkedIn link - Security clearance: Public Trust (MBI) required - U.S. Citizenship required - Military Veterans encouraged (maybe remove) - Previously applied note (remove) We need to keep substantive: location, department, type, remote, citizenship requirement, security clearance, W-2, interview method, LinkedIn request, state restrictions. Responsibilities: list each duty bullet. Let's copy duties: - 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 preserve all. Skills: Required Skills and Experience list: - 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 Also Professional Certifications: None but AWS certifications are a bonus. Desired experience (maybe under Skills or Requirements): 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 We could include these under Skills as desired/experience. Requirements: maybe years of experience, security clearance, citizenship, W-2, interview method, LinkedIn request, state restrictions. Qualifications: Formal Education: Bachelor’s degree or higher in Computer Science, Engineering, or related technical discipline; equivalent practical experience considered. Certifications: None but AWS certifications are a bonus. We need to avoid duplication: skills list includes many technical items; we can put them under Skills section. Requirements could include experience years, clearance, citizenship, W-2, interview, LinkedIn, state restrictions. Qualifications could include education and certifications. Pay: salary range $85,389 - $116,975. Schedule: Full Time. Now produce HTML. We must not include markdown fences. Just raw HTML. We'll structure:

About the role

...

maybe include multiple paragraphs or a list? For metadata we can use

with sentences. Better to use

for prose. For list of duties we use

• . For skills we can use
  • . For requirements maybe
    • . For qualifications maybe
      • . Pay:

        Salary range: $85,389 - $116,975

        Schedule:

        Full Time

        Now craft content. About the role paragraph: include location remote, department VA, type full time, 100% US based remote, W-2 position, interviews on Microsoft Teams with camera on, request LinkedIn link, U.S.