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, 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
- Note about previous applications, etc (boilerplate)
- Military Veterans encouraged (maybe keep? It's not boilerplate? It's a statement encouraging veterans; could be considered substantive? Might be considered EEO? It's encouraging veterans, not EEO boilerplate. Might keep as part of About the role? Probably we can include in About the role paragraph.
- Essential Duties And Responsibilities: a long list.
- 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 EDI, HL7, FHIR, C#/.Net, Entity Framework, healthcare payer/PBM, HIPAA.
- Formal Education: Bachelor’s degree or higher in CS, 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: many notes about screening, etc. Some are boilerplate but some are specific: "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." Also EEO statement.
We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The EEO statement is boilerplate; remove. The critical notes include some specifics that are not boilerplate: location restrictions, W-2, interview method, LinkedIn link request, citizenship requirement (already covered), security clearance background investigation details. We should keep those as part of About the role or maybe a separate section like "Additional Information". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can put extra info under About the role or Requirements etc. Probably About the role can contain overview, location, type, clearance, citizenship, W-2, interview details, LinkedIn, location restrictions.
Responsibilities: the Essential Duties And Responsibilities block.
Requirements: maybe the Required Skills and Experience block? Or we could separate Requirements (hard requirements) and Qualifications (education, certifications) and Skills (technical). The instructions: Use headings for those categories if content exists. We need to decide what goes where.
We have:
- Required Skills and Experience (list of 8+ years, AWS focus, etc.) This could be under Requirements or Skills.
- Professional Certifications: None but AWS certifications are a bonus -> could be under Qualifications.
- Desired experience: list of EDI, HL7, FHIR, C#/.Net, Entity Framework, healthcare payer/PBM, HIPAA. This could be under Skills or Requirements? Might be under Skills.
- Formal Education: Bachelor's degree or higher... -> Qualifications.
- Citizenship Requirement: U.S. Citizenship required -> could be under Requirements (or About the role). Since it's a requirement, maybe under Requirements.
- Security Clearance Requirements: Must possess or qualify for a Public Trust (MBI) -> Requirements.
- Additional notes: W-2, location restrictions, interview method, LinkedIn, background investigation details -> could be under About the role.
- Benefits, Pay, Schedule: we have Pay (salary range). Benefits not mentioned. Schedule not mentioned (full time). So we can include Pay section with salary range. Benefits: none specific, so omit. Schedule: we have Full Time, but that's a type; could be under Schedule? The instruction: include Schedule section only if posting actually states them. It states Type: Full Time. That's a schedule. So we can include Schedule with Full Time.
Thus sections:
- About the role: overview, location remote, department VA, type full time, W-2, remote, military veterans encouraged, LinkedIn request, location restrictions (states excluded), maybe note about no third-party recruiters.
- Responsibilities: the essential duties.
- Requirements: security clearance, citizenship, maybe years experience? Actually years experience is part of Required Skills and Experience. Could be under Requirements.
- Qualifications: education, professional certifications (AWS bonus).
- Skills: technical skills list (AWS services, SQL, XML, CI/CD, IaC, Git, Agile, etc.) plus desired experience (EDI, HL7, FHIR, C#/.Net, Entity Framework, healthcare payer/PBM, HIPAA).
- Pay: salary range.
- Schedule: Full Time.
We must not repeat job title. Must not include Job ID/requisition numbers.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the details exactly as given, but we can rephrase into HTML lists/paragraphs. Must not lose any detail.
We need to be careful not to omit any specifics like "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". Keep that sentence.
We need to turn list items into
- . For prose, use
.
We must not include boilerplate like "If you have previously applied to Syms Strategic Group (SSG), there is no need to reapply. Applications are still under review." That's application instructions? It's about reapplying; maybe considered application instructions, remove. Also "Military Veterans are highly encouraged to apply!" Could be considered encouraging but not boilerplate; maybe keep as part of About the role.
"Recruiters or Third parties will not be considered" - that's a note about recruiters; could be kept under About the role.
"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" - keep.
"This is a W-2 position" - keep.
"All interviews will be conducted on Microsoft Teams with your camera on; there will be no exceptions" - keep.
"As part of our screening process, you will be requested to provide a link to your LinkedIn profile" - keep.
"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." - keep.
EEO statement: remove.
"Powered by JazzHR uFDuchL1qD" - remove.
Now we need to output HTML fragment only.
Let's craft.
Structure:
About the role
Syms Strategic Group (SSG) is seeking a talented Senior Systems Engineer (Amazon Web Services (AWS) Data Engineer) - II. This is a full‑time, remote position supporting the Veterans Affairs (VA) department. The role is a W‑2 position; candidates must be U.S. citizens and eligible for a Public Trust (MBI) security clearance. Military veterans are highly encouraged to apply. As part of the screening process, you will be asked to provide a link to your LinkedIn profile. Please note that recruiters or third‑party agencies will not be considered, and candidates residing in CA, CO, IL, MN, NJ, NY, OR, or WA are not eligible for this role. All interviews will be conducted via Microsoft Teams with camera on, with no exceptions. Selected applicants will undergo a government security investigation and background check (including criminal history, employment and education verification, drug testing, and creditworthiness) to obtain the required security clearance.
That covers many points.
Now Responsibilities:
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, 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
Now Requirements:
We need to include security clearance, citizenship, years experience? Actually years experience is in Required Skills and Experience. Could be under Requirements: "8+ years’ experience in software or data engineering with a strong AWS focus". Also "Proven experience architecting and executing cloud data platform migrations in production enterprise or healthcare environments". Also "Track record of evaluating and selecting AWS data services to meet business reporting and query requirements". Also "Experience delivering reporting or analytics solutions that serve non‑technical business users". Also "Deep hands‑on AWS experience across data‑oriented services – S3, Athena, Glue, Aurora, DynamoDB, Redshift, OpenSearch, Lambda, IAM, and Cloudwatch". Also "Strong SQL skills with the ability to design relational query layers over semi‑structured or non‑