AWS Data Engineer - II

We need to output HTML fragment with sections: About the role? The posting includes description. We should not repeat job title. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting: It includes location remote, department VA, type full time, min experience experienced, security clearance public trust MBI, salary range $85,389 - $116,975. Also note about not reapplying, military veterans encouraged, etc. Those are boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should drop lines like "If you have previously applied...", "Military Veterans are highly encouraged to apply!", "CRITICAL NOTES:", etc. Also drop "U.S Citizenship is required..." repeated, etc. Also drop "Powered by JazzHR drHqrnbJSk". Also drop "Applications are still under review." Might be considered boilerplate? It's not exactly legal but maybe considered application instruction? Probably drop. We need to preserve substantive info: duties, responsibilities, required skills, qualifications, etc. Also salary range and maybe benefits? No benefits listed. So we should not create Benefits section unless present. Pay section: we have salary range, so include Pay section. Schedule: not specified (full time). Full time is schedule? Could be considered schedule but they said do not create Schedule unless posting actually states them. It states Type: Full Time. That's schedule info. So we can include Schedule section with "Full Time". However they said avoid filler like "not specified". Full time is specific. So include Schedule. Also we have Location: Remote, Department: Veterans Affairs (VA). Could be part of About the role? Maybe we can put location/department in About the role paragraph. We need sections: About the role (maybe a brief summary), Responsibilities (list), Requirements (maybe qualifications?), Skills (maybe required skills). But we must not create thin sections. We can combine some. We have: Essential Duties And Responsibilities (list). That's responsibilities. We have Required Skills and Experience (list). That's skills/experience. We have Professional Certifications (None but AWS certifications are a bonus) - that's not specific; maybe we can omit as filler. We have Desired experience (list) - could be part of Requirements or Skills. We have Formal Education (Bachelor’s degree or higher...). That's qualifications. We have Citizenship Requirement (U.S. Citizenship required) - that's a requirement. We have Security Clearance Requirements (Must possess or qualify for a Public Trust (MBI)). That's requirement. We have Salary Range. We have Location remote, department VA, type full time. Thus we can create sections: - About the role: brief paragraph summarizing role, location, department, type. - Responsibilities:

• ... from Essential Duties And Responsibilities. - Requirements: maybe combine citizenship, security clearance, education, experience? Could be Qualifications. - Skills: Required Skills and Experience list plus Desired experience maybe. - Pay: salary range. - Schedule: Full Time. We must not repeat job title as heading. We must not include duplicated lines. We need to preserve all substantive info; do not invent or summarize away detail. So we need to keep each bullet point essentially as is, but we can format as
• . Must not omit any duty or requirement. Let's extract responsibilities list: From "Essential Duties And Responsibilities" paragraph after that heading, it's a long sentence with multiple duties separated by line breaks? Actually it's a paragraph with multiple sentences. We need to break into list items per duty. The instruction: Use
  • for any list of duties/requirements/benefits. So we need to convert each duty into a list item. The original text is a paragraph with multiple duties separated by line breaks? Let's copy: "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" Each line seems a duty. We'll make each a
  • . Now Required Skills and Experience list: It's a paragraph with many items separated by line breaks? Let's 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" We'll make each a
  • . Desired experience 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 treat as separate list items, but it's a bit run-on. We can split by commas? Better to keep as one item? But we need to preserve all substantive info; we can break into separate items for clarity. However we must not invent detail. Splitting may be okay as it's still same info. We'll split by commas and "Experience with". Let's parse: - 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'll make each a
  • . Now Formal Education: "Bachelor’s degree or higher in Computer Science, Engineering, or a related technical discipline; equivalent practical experience considered" We'll make a

    maybe under Qualifications. Citizenship Requirement: "U.S. Citizenship required for this specific opportunity" Security Clearance Requirements: "Must possess or qualify for a Public Trust (MBI)" We can combine these under Requirements or Qualifications. We need to decide sections: About the role, Responsibilities, Requirements, Skills, Pay, Schedule. We could put education, citizenship, clearance under Requirements. Skills: Required Skills and Experience plus Desired experience. Pay: salary range. Schedule: Full Time. Now About the role: we need to include location remote, department VA, type full time? But schedule separate. We'll include location and department. Paragraph: "Syms Strategic Group (SSG) is seeking a Senior Systems Engineer (AWS Data Engineer) - II for a remote position within the Veterans Affairs (VA) department." But we must not repeat job title? 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 we can mention the role in About the role paragraph. We must not include boilerplate like "If you have previously applied..." etc. So we will omit those. Now produce HTML fragment:

    About the role

    Syms Strategic Group (SSG) is seeking a Senior Systems Engineer (AWS Data Engineer) - II for a fully remote position within the Veterans Affairs (VA) department.

    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