AWS Data Engineer - II

We need to output HTML fragment with sections: About the role? The posting includes description, responsibilities, requirements, qualifications, skills, benefits, pay, schedule. We need to include only sections with real specific content. The posting includes salary range, so Pay section. It includes location remote, type full time, min experience, security clearance, citizenship requirement, etc. Those could be in About the role or Qualifications. We need to decide sections: maybe About the role (overview), Responsibilities, Requirements (skills/experience), Qualifications (education, citizenship, clearance), Benefits? Not mentioned benefits explicitly. Pay section present. Schedule? Not mentioned besides full time. Could include Schedule if full time specified. But rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It states Salary Range, so Pay section. It states Full Time, so Schedule section could be included (type: Full Time). It does not mention benefits, so omit Benefits. We must not repeat job title as heading. Use

for section headings. Use

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

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: EEO, scam warning, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove "If you have previously applied..." etc? That's application instruction? It says "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; should be removed. Also "Military Veterans are highly encouraged to apply!" maybe considered EEO? It's encouragement but could be considered boilerplate? Probably remove as it's not substantive duty. Also "Powered by JazzHR YZvXM73mB5" remove. We need to keep essential duties and responsibilities list. That's a big paragraph with many sentences; we can turn into

  • each duty? The instruction: Use
    • for any list of duties/requirements/benefits. So we should convert the duties into list items. Similarly required skills and experience into list. We need to preserve all substantive information; not summarize away detail. So we need to keep each duty sentence as separate list item, preserving the text. We also need to include sections: About the role (overview), Responsibilities, Requirements (maybe Skills), Qualifications (education, citizenship, clearance, experience), Pay, Schedule. We must not create sections with filler like "commensurate with experience". We have specific content. Let's extract: Overview: "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" We could put that in About the role

      . But we shouldn't repeat job title. So we can write a paragraph summarizing the role: "Syms Strategic Group (SSG) is seeking a Senior Systems Engineer (AWS Data Engineer) - II for a remote position supporting the Veterans Affairs department. This is a full-time role requiring experienced candidates with a Public Trust (MBI) security clearance. Salary range: $85,389 - $116,975." That preserves info. Responsibilities: list each duty sentence. Let's extract duties from "Essential Duties And Responsibilities" paragraph: - 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 keep each as list item. Required Skills and Experience: list each bullet. Extract: - 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 Also "Professional CertificationsNone but AWS certifications are a bonus" maybe include as note but not required. Could be included under Requirements as a note. "Years of Professional Experiencen/a" ignore. "Desired experienceElectronic 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" These are desired experience; we could include under Requirements or Qualifications as additional desired experience. "Formal EducationBachelor’s degree or higher in Computer Science, Engineering, or a related technical discipline; equivalent practical experience considered" "Citizenship RequirementU.S. Citizenship required for this specific opportunity" "Security Clearance RequirementsMust possess or qualify for a Public Trust (MBI)" "CRITICAL NOTES: SSG will not make assumptions regarding your qualifications. Your answers to the mandatory screening questions must be supported by the information on your resume. Applications with inconsistencies will not be consideredRecruiters or Third parties will not be consideredThis is a 100% U.S. based remote position. However, candidates from CA, CO, IL, MN, NJ, NY, OR, or WA will not be consideredThis is a W-2 position All interviews will be conducted on Microsoft Teams with your camera on; there will be no exceptionsAs part of our screening process, you will be requested to provide a link to your LinkedIn profile U.S Citizenship is required for this specific opportunity. 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. Individuals may also be subject to a background investigation including, but not limited to criminal history, employment and education verification, drug testing, and creditworthiness." We need to keep substantive info: remote, US based, W-2, no candidates from certain states, interview via Teams camera on, link to LinkedIn profile, citizenship requirement, security clearance, background investigation details. However some of that is more like application instructions or notes; but we should keep substantive info like location remote, citizenship requirement, security clearance, background investigation, W-2, no candidates from certain states, interview via Teams camera on, LinkedIn link request. However rule: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The LinkedIn request and interview details might be considered application instructions; but they are substantive? The instruction says remove application instructions. So we should remove those. Also remove "Recruiters or Third parties will not be considered". Remove "CRITICAL NOTES" etc. Keep citizenship requirement and security clearance maybe as part of Qualifications. Keep location remote, type full time, W-2 maybe as part of About the role or Schedule? W-2 is employment type; could be in About the role. We must not invent or summarize away detail. So we need to keep the exact phrasing for citizenship requirement and security clearance? We can paraphrase but must preserve info. Probably okay to rephrase slightly but keep meaning. We'll create sections:

      About the role

      Syms Strategic Group (SSG) is seeking a Senior Systems Engineer (AWS Data Engineer) - II for a remote, full-time position supporting the Veterans Affairs department. This is a W-2 role requiring U.S. citizenship and a Public Trust (MBI) security clearance. Salary range: $85,389 - $116,975.

      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