AWS Data Engineer

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Must not create sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes Salary Range: $85,389 - $116,975. That's pay info. So we can include Pay section with that range. Benefits? Not mentioned explicitly. No benefits listed. So we should not include Benefits section. Schedule? Not mentioned (full time). Could include Schedule? The posting says Type: Full Time. That's schedule info. Could include Schedule section with "Full Time". But we need to see if we should include Schedule only if posting actually states them. It does state Type: Full Time. So we can include Schedule. However, we need to avoid filler like "not specified. "Full Time" is specific. So include Schedule. Now sections: About the role: we have description of role: "Syms Strategic Group (SSG) is seeking a talented Senior Systems Engineer (Amazon Web Services (AWS) Data Engineer) Location: Remote Department: Veterans Affairs (VA) Type: Full Time Min. Experience: Experienced Security Clearance Level: Public Trust (MBI) Salary Range: $85,389 - $116,975". Also maybe "If you have previously applied..." but that's application instruction, remove. Also "Military Veterans are highly encouraged to apply!" that's encouragement but maybe considered boilerplate? It's not EEO but it's a encouragement; could be considered part of role? Might be considered fluff but it's substantive? Probably we can keep as part of About the role? It's not a duty. Might be considered encouraging but not required. The instruction says remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Military Veterans are highly encouraged to apply!" is not exactly EEO but it's a encouragement; could be considered part of EEO? Might be considered encouraging but not required. Safer to remove it as it's not a duty/responsibility/requirement. Also "If you have previously applied..." is application instruction, remove. Thus About the role paragraph can include location, remote, department, type, experience, security clearance, salary range? Actually salary range goes to Pay section. So About the role can include location, department, type, experience, security clearance. Also maybe mention that it's a Senior Systems Engineer (AWS Data Engineer). That's the role title but we shouldn't repeat job title as heading; but we can mention it in paragraph. Responsibilities: list of essential duties and responsibilities. We'll extract bullet points. Requirements: maybe "Required Skills and Experience" includes required skills. Could be split into Requirements and Skills? The instruction says use headings for sections like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. Typically Requirements could be mandatory qualifications (years experience, security clearance, citizenship, education). Skills could be technical skills. Qualifications could be education, certifications. But we can combine as appropriate. We must not create thin sections. Let's parse: From posting: - Essential Duties And Responsibilities (list) - Required Skills and Experience (list) - Professional Certifications: None but AWS certifications are a bonus - Years of Professional Experience: n/a (maybe not needed) - Desired experience: list (EDI X.12, HL7, FHIR, C#/.Net, Entity Framework, healthcare payer/PBM, clearinghouses, pharmacy operations, HIPAA) - Formal Education: Bachelor’s degree or higher in Computer Science, Engineering, or related technical discipline; 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 (remove) - Also location remote, department VA, type full time, min experience experienced, security clearance public trust MBI, salary range. Thus we can structure: About the role: location remote, department VA, type full time, experienced, security clearance Public Trust (MBI). Possibly also mention role title. Responsibilities: bullet list of essential duties. Requirements: maybe combine citizenship, security clearance, experience (8+ years), education (Bachelor's degree or higher). Could also include "U.S. Citizenship required", "Must possess or qualify for Public Trust (MBI)", "8+ years’ experience in software or data engineering with a strong AWS focus", "Bachelor’s degree or higher in Computer Science, Engineering, or related technical discipline; equivalent practical experience considered". Skills: technical skills list from Required Skills and Experience (AWS services, SQL, XML, etc.) plus desired experience maybe also skills. Qualifications: maybe professional certifications (AWS certifications a bonus) and maybe desired experience? But we can keep Qualifications for certifications and maybe desired experience? However we need to avoid thin sections. Could combine Qualifications into Skills? But we need to follow instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include those that have content. Thus we can have: About the role Responsibilities Requirements Skills Qualifications Pay Schedule We must not include Benefits if not present. Now we need to extract content precisely, preserving all substantive info, not inventing or summarizing away detail. Let's extract each piece. About the role paragraph: "Syms Strategic Group (SSG) is seeking a talented Senior Systems Engineer (Amazon Web Services (AWS) Data Engineer) 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 to Pay section. So About the role paragraph: "Syms Strategic Group (SSG) is seeking a talented Senior Systems Engineer (Amazon Web Services (AWS) Data Engineer). Location: Remote. Department: Veterans Affairs (VA). Type: Full Time. Minimum Experience: Experienced. Security Clearance Level: Public Trust (MBI)." We should keep "Min. Experience: Experienced" as is. Could phrase as "Minimum Experience: Experienced". That's fine. Now Responsibilities: list each duty from "Essential Duties And Responsibilities". Let's capture each sentence as bullet. Original: 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 detail. Slight typo: "chose" should be "chosen" but we keep as is? It's in original; we should preserve exactly? Probably keep as is but could correct? Instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Changing a typo could be considered altering detail. Safer to keep as is: "chose". We'll keep. Now Requirements: we need to include mandatory 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. Also citizenship requirement, security clearance, education. But some of these are more like skills. However we can separate: Requirements could be the mandatory baseline: 8+ years experience, education, citizenship, security clearance. Skills could be the technical skill list. Qualifications could be certifications and desired experience? But we need to avoid thin sections. Let's think. If we put all the long list under Skills, that'll be substantive. Requirements could be shorter: "8+ years’ experience in software or data engineering with a strong AWS focus", "Bachelor’s degree or higher in Computer Science, Engineering, or a related technical discipline; equivalent practical experience considered", "U.S. Citizenship required", "Must possess or qualify for a Public Trust (MBI) security clearance". That's four items. That's enough for a Requirements section. Skills: list of technical skills from Required Skills and Experience (including AWS services, SQL, XML, etc.) plus maybe desired experience (EDI, HL7, FHIR, C#/.Net, Entity Framework, healthcare payer/PBM, HIPAA). Also professional certifications: AWS certifications a bonus. Qualifications: maybe "Professional Certifications: None but AWS certifications are a bonus". That's thin but could be considered a qualification. However we could combine certifications into Skills as a bonus. But we need to avoid creating a section with filler like "None but AWS certifications are a bonus" - that's substantive (it says AWS certifications are a bonus). That's not filler. So we could have Qualifications section with that line.