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 as heading. Must not include Job ID etc. Remove boilerplate. We need to parse the posting. Key info: - Company: Syms Strategic Group (SSG) - Position: 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 (multiple paragraphs). - Required Skills and Experience: list. - Professional Certifications: None but AWS certifications are a bonus. - Years of Professional Experience: n/a (maybe ignore) - Desired experience: list of specific items (EDI X.12, HL7, FHIR, C#/.Net, Entity Framework, healthcare payer/PBM, HIPAA). - 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 Public Trust (MBI). - Critical notes: SSG will not make assumptions; answers must be supported; recruiters/third parties not considered; 100% US based remote; candidates from certain states not considered; W-2 position; interviews on Teams camera on; link to LinkedIn requested; US Citizenship required; selected subject to gov security investigation; background investigation; EEO statement. We need to include sections: About the role (maybe summary), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Pay: Salary Range given. So include Pay section. Schedule: Not explicitly given; only Full Time. Could infer schedule? The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It says Type: Full Time. That's schedule? Might be considered schedule info. But "Schedule" heading expects maybe work schedule details (e.g., Monday-Friday 9-5). Not given. So we should not create Schedule section unless explicit. So omit Schedule. Benefits: Not mentioned. No benefits listed. So omit Benefits. About the role: Could be a brief summary: The role is Senior Systems Engineer (AWS Data Engineer) II, remote, supporting VA, full-time, requiring Public Trust clearance, US citizenship. We can craft a short paragraph using info. Responsibilities: Use the Essential Duties And Responsibilities block. Convert to

• items. Requirements: Could include security clearance, citizenship, experience, education. Might be separate from Skills. We'll decide. Qualifications: Could include education, certifications, years experience. Skills: Could list technical skills: AWS services, SQL, XML, CI/CD, IaC, etc. We must not invent or summarize away detail. Must preserve all substantive information. So we need to include all details from posting, not lose any. Thus we need to ensure each piece of info appears somewhere in the HTML. Let's list all substantive info bullets: - Position: Senior Systems Engineer (AWS Data Engineer) - II - Location: Remote - Department: Veterans Affairs (VA) - Type: Full Time - Min. Experience: Experienced (maybe not needed) - 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 highly encouraged. - Essential Duties And Responsibilities (list): - Lead the next phase of the healthcare data platform modernization - Implement the evolution from a 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 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 - 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 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 - Professional Certifications: None but AWS certifications are a bonus. - Years of Professional Experience: n/a (maybe ignore as not substantive) - Desired experience: - 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 - Formal Education: Bachelor’s degree or higher in Computer Science, Engineering, or a related technical discipline; equivalent practical experience considered. - Citizenship Requirement: U.S. Citizenship required for this specific opportunity. - Security Clearance Requirements: Must possess or qualify for a Public Trust (MBI). - Critical notes (some are boilerplate but some substantive): - 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 considered. - Recruiters or Third parties will not be considered. - This is a 100% U.S. based remote position. However, candidates from CA, CO, IL, MN, NJ, NY, OR, or WA will not be considered. - This is a W-2 position. - All interviews will be conducted on Microsoft Teams with your camera on; there will be no exceptions. - As 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. - Syms Strategic Group, LLC is an Equal Opportunity Employer. Qualified applicants will receive consideration for employment without regard to race, color, religion, sex, age, national origin, marital status, disability, veteran status, sexual orientation, or genetic information. - Powered by JazzHR rCtMtw1N26 (maybe ignore as boilerplate). We need to omit cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The EEO statement is boilerplate; we should remove it. Also the "Powered by JazzHR" is boilerplate. The "Applications still under review" maybe not needed? It's not a boilerplate but maybe considered application instruction? It's a statement about status; could keep? The instruction: remove duplicated lines, application instructions. "Applications are still under review." Not an instruction; maybe keep as part of About the role? Might be considered filler. Safer to keep only substantive content about the job. The "If you have previously applied to Syms Strategic Group (SSG), there is no need to reapply." That's an application instruction; should be removed. "Military Veterans are highly encouraged to apply!" That's encouragement; maybe keep as part of About the role? Could be considered boilerplate? It's not EEO but still encouragement; maybe keep. We need to decide sections. Let's craft:

  About the role

  Syms Strategic Group (SSG) is seeking a Senior Systems Engineer (AWS Data Engineer) II for a full‑time, remote position supporting the Veterans Affairs (VA) department. The role requires U.S. citizenship and a Public Trust (MBI) security clearance, with a salary range of $85,389‑$116,975. Military veterans are encouraged to apply.

  That captures location, department, type, citizenship, clearance, salary, encouragement.

  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