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, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove things like "If you have previously applied..." etc. Also remove "Military Veterans are highly encouraged to apply!" maybe that's EEO? It's encouragement but could be considered EEO? Might be okay to keep? The instruction: remove EEO/equal-opportunity boilerplate. That line is encouragement but could be considered EEO. Safer to remove. We need to extract sections: - About the role: maybe a brief description: "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 must not repeat job title. Also we should not include location? It's part of About the role. We can include location, department, type, min experience, security clearance, salary range. However salary range is Pay section; we should put Pay separately if present. The posting includes Salary Range. So we should create a Pay section with that range. Also we should not duplicate. Thus About the role could include: Syms Strategic Group (SSG) is seeking a talented Senior Systems Engineer (AWS Data Engineer) - II. Location: Remote. Department: Veterans Affairs (VA). Type: Full Time. Minimum Experience: Experienced. Security Clearance Level: Public Trust (MBI). (We might omit salary as it goes to Pay.) But we must not repeat job title; we can still mention "Senior Systems Engineer (AWS Data Engineer) - II" as part of description? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid mentioning it in prose. So okay. Responsibilities: list of essential duties and responsibilities. We need to capture each bullet. The posting has a paragraph with many sentences. We should break into list items for each duty. Let's extract: - 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 That's responsibilities. Requirements: maybe "Required Skills and Experience" section. But we have separate headings: Requirements, Qualifications, Skills. We need to decide what to put where. The posting has "Required Skills and Experience" with a list. Also "Professional Certifications", "Years of Professional Experience", "Desired experience", "Formal Education", "Citizenship Requirement", "Security Clearance Requirements". We need to map to headings. We should avoid thin sections. Perhaps combine into Requirements (mandatory) and Qualifications (education/certifications) and Skills (technical). But we must not invent sections lacking content. Let's see content: Required Skills and Experience list (many items). That's definitely skills/experience. Professional Certifications: "None but AWS certifications are a bonus" - that's a statement; we could include under Qualifications maybe. Years of Professional Experience: "n/a" - that's placeholder; we should not include if it's just "n/a". So skip. Desired experience: list of desired experience (EDI X.12, HL7, FHIR, C#/.Net, Entity Framework, healthcare payer/PBM, HIPAA). That's desirable, not required. Could be under Qualifications or Skills? Might be better as "Desired Experience" but we don't have that heading. Could put under Qualifications? Or maybe under Skills as "Desired skills". But instruction: only include sections when posting has real specific content. We have content for desired experience; we could include under "Qualifications" or "Skills". But we need to avoid thin sections. Perhaps we combine Required Skills and Experience and Desired experience into a single "Skills" section, separating required vs desired? But we must preserve all substantive info; we can list required skills and then desired skills as sublist. Qualifications: Formal Education, Citizenship Requirement, Security Clearance Requirements, maybe Professional Certifications. Pay: Salary Range. Schedule: Not mentioned; maybe full time indicated but not schedule details. Could skip Schedule. Benefits: Not mentioned; skip. Thus sections: About the role, Responsibilities, Skills (maybe split Required and Desired), Qualifications, Pay. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not include boilerplate like EEO, etc. Also remove duplicated lines like "U.S Citizenship is required for this specific opportunity." appears twice; we should keep only once. Also remove "CRITICAL NOTES:" etc. Those are instructions to applicants; maybe considered boilerplate? They are not EEO but are application instructions. The instruction says remove application instructions. So we should remove CRITICAL NOTES block, also the lines about LinkedIn, camera on Teams, etc. Also remove "Recruiters or Third parties will not be considered". Also remove "This is a 100% U.S. based remote position..." etc. Those are job details maybe relevant to About the role? Location remote, citizenship requirement, etc. Some of that is relevant. But the instruction says remove application instructions. The CRITICAL NOTES includes many items that are not exactly application instructions but conditions. Might be considered part of job posting details. However they include specifics like "candidates from CA, CO, IL, MN, NJ, NY, OR, or WA will not be considered" - that's location restriction, relevant. Also "This is a W-2 position". Also "All interviews will be conducted on Microsoft Teams with your camera on; there will be no exceptions". That's application instruction. Also "As part of our screening process, you will be requested to provide a link to your LinkedIn profile". That's instruction. Also "U.S Citizenship is required for this specific opportunity." duplicates. Also "Applicants selected will be subject to a government security investigation..." that's security clearance detail, relevant. Also "Individuals may also be subject to a background investigation...". That's also relevant. We need to decide what to keep. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove lines that are purely application instructions (like LinkedIn, camera, interview format). Keep substantive job details like location restrictions, citizenship, security clearance, W-2, background investigation maybe? The background investigation is part of security clearance process; could be considered substantive. But it's also somewhat boilerplate. I'd keep security clearance requirement and citizenship requirement. Remove the interview camera and LinkedIn request. Remove the "Recruiters or Third parties will not be considered". Remove the "If you have previously applied..." line. Remove "Military Veterans are highly encouraged to apply!" maybe EEO. Remove the "Powered by JazzHR QyM9k8dniL". Also remove the duplicated citizenship line. Thus we need to extract: About the role: Syms Strategic Group (SSG) is seeking a talented Senior Systems Engineer (AWS Data Engineer) - II. Location: Remote. Department: Veterans Affairs (VA). Type: Full Time. Minimum Experience: Experienced. Security Clearance Level: Public Trust (MBI). (We might also mention that it's a W-2 position? That's employment type; could be included.) But we also have location restriction: candidates from certain states will not be considered. That is a location restriction; could be included in About the role or maybe as a note. We'll include in About the role: "Note: Candidates from CA, CO, IL, MN, NJ, NY, OR, or WA will not be considered." Also "This is a W-2 position." Could be included. Pay: Salary Range: $85,389 - $116,975. Responsibilities: as list. Skills: Required Skills and Experience list (the long list). Also maybe include desired experience as a sublist under "Desired experience" but we don't have heading; we could include under Skills as a separate subsection with heading? But we cannot add arbitrary headings besides the allowed ones? The instruction only says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It might be okay to use other headings but they'd be non-standard. Safer to stick to those headings. So we can put desired experience under Skills as a list with a note "Desired experience:" inside a

  or as a

  with a preceding

  . But we need to preserve all substantive info; we can include desired experience as part of Skills section, maybe as a separate

  with a preceding

  stating "Desired experience includes:". Qualifications: Formal Education, Citizenship Requirement, Security Clearance Requirements, Professional Certifications (None but AWS certifications are a bonus). Also maybe years of experience? Not needed. We must not include placeholder like "n/a". So skip years. We need to ensure we don't repeat info. Let's craft. HTML:

  About the role

  Syms Strategic Group (SSG) is seeking a talented Senior Systems Engineer (AWS Data Engineer) - II. This is a full‑time, remote position supporting the Veterans Affairs (VA) department. Minimum experience: experienced. Security clearance: Public Trust (MBI). Employment type: W‑2. Note: Candidates from CA, CO, IL, MN, NJ, NY, OR, or WA will not be considered.

  Responsibilities

  • Lead the next phase of the healthcare data platform modernization
  • Implement the evolution from a Microsoft SQL eXtensible Markup Language (MSSQL XML) object