Data Platform Engineer

We need to output HTML fragment with sections: About the role? Not present. Responsibilities: Essential Duties And Responsibilities. Requirements: Required Skills and Experience. Possibly Benefits? Not given. Pay: Salary Range given. Schedule? Not given. Location: Remote. Could include a short paragraph for metadata: location, type, min experience, security clearance, salary range. Should not repeat job title. Should not include boilerplate like EEO, etc. Should not include application instructions. Should not include duplicated lines. We need to preserve all substantive info. So include: - A paragraph with location, department, type, min experience, security clearance, salary range maybe. - Then

Responsibilities

with

• each duty. - Then

  Required Skills and Experience

  with
  • each bullet. - Possibly

    Desired experience

    ? The posting includes "Desired experience" after Professional Certifications. It lists specific desired experience items. Should we include as a section? The instruction: include a section ONLY when posting has real, specific content for it. Desired experience is specific content. Could be a section "Desired experience". But we already have Required Skills and Experience; maybe combine? The instruction: prefer a few substantive sections over many thin ones. Could merge desired experience into Required Skills? But they are separate. However we could include a section "Desired experience" if we think it's substantive. It lists items like EDI X.12, etc. That is substantive. Could create a section "Desired experience". Also "Professional Certifications" is minimal: "None but AWS certifications are a bonus". That's not substantive? It says none but AWS certifications are a bonus. That's maybe not worth a section. "Years of Professional Experience n/a" is placeholder; we should not include. "Desired experience" we should include. Also "Formal Education" and "Citizenship Requirement" and "Security Clearance Requirements" and "CRITICAL NOTES" etc. Many of those are substantive but some are boilerplate (citizenship requirement, security clearance). However they are specific: U.S. Citizenship required, Public Trust (MBI). Should we include? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Citizenship requirement and security clearance are not boilerplate; they are specific requirements. Could include in a paragraph with other metadata. Also "CRITICAL NOTES" includes many statements: SSG will not make assumptions..., Recruiters or Third parties will not be considered, This is a 100% U.S. based remote position..., candidates from certain states will not be considered, This is a W-2 position, All interviews will be conducted on Microsoft Teams..., link to LinkedIn profile, U.S Citizenship is required..., background investigation..., etc. Some of that is boilerplate but some is specific (states excluded, W-2, interview method, LinkedIn). We need to decide what to keep. The instruction: remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The CRITICAL NOTES includes application instructions? It says "As part of our screening process, you will be requested to provide a link to your LinkedIn profile". That's an application instruction (provide LinkedIn). Should remove. Also "All interviews will be conducted on Microsoft Teams with your camera on; there will be no exceptions" is maybe application instruction? Could be considered process detail; maybe keep? It's not exactly application instruction but could be considered part of hiring process. The instruction says remove application instructions. Might be safer to remove that line. Also "U.S Citizenship is required for this specific opportunity." is duplicate of earlier citizenship requirement; we can keep once. "Applicants selected will be subject to a government security investigation..." is security clearance detail; keep maybe. "Individuals may also be subject to a background investigation including, but not limited to criminal history, employment and education verification, drug testing, and creditworthiness." That's also security/background check detail; could keep. "Syms Strategic Group, LLC is an Equal Opportunity Employer..." is EEO boilerplate; remove. "Powered by JazzHR zPgSC4O5Kn" is boilerplate; remove. Thus we need to extract substantive info: location remote, department Veterans Affairs, type full time, min experience experienced (maybe "Experienced" but they gave Min. Experience: Experienced), security clearance Public Trust (MBI), salary range $85,389 - $116,975, citizenship US required, maybe note about state exclusions (candidates from CA, CO, IL, MN, NJ, NY, OR, or WA will not be considered), W-2 position, maybe note about background investigation. We should not create sections for Pay or Schedule unless stated. Pay is stated (salary range) so we can include a Pay section. Schedule not stated, so omit. Benefits not stated, omit. Thus sections: About the role? Not present. Could skip. We'll have a short paragraph for metadata: maybe

    Location: Remote | Department: Veterans Affairs (VA) | Type: Full Time | Min. Experience: Experienced | Security Clearance: Public Trust (MBI) | Salary Range: $85,389 - $116,975 | Citizenship: U.S. Citizenship required | State Restrictions: Candidates from CA, CO, IL, MN, NJ, NY, OR, or WA will not be considered | Employment Type: W-2

    Then Responsibilities section with list. Then Required Skills and Experience section with list. Then Desired experience section with list. We must not repeat job title. We must output only HTML fragment. Let's extract responsibilities list exactly as given: 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 ensure each as
  • . Now 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 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 Now 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 Also Professional Certifications: None but AWS certifications are a bonus. Could be omitted as not substantive. Formal Education: Bachelor’s degree or higher in Computer Science, Engineering, or a related technical discipline; equivalent practical experience considered. Could be included maybe as a subsection? But we already have many sections; maybe we can add a "Qualifications" section for education. The instruction: use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They gave examples. So we could use "Qualifications" for education and certifications. But we already have Required Skills and Experience (skills). Could treat education as part of Qualifications. However we must not create thin sections. Education is substantive. Could add a

    Qualifications

    with

    Bachelor’s degree or higher in Computer Science, Engineering, or a related technical discipline; equivalent practical experience considered.

    Also maybe include Professional Certifications note there. But we already have Required Skills and Experience; maybe we can combine education into that as a bullet? But it's not a skill. Could add a separate Qualifications section. We need to decide: The instruction says prefer a few substantive sections over many thin ones. Adding Qualifications may be okay if we have only a few sections: Responsibilities, Required Skills and Experience, Desired experience, Qualifications. That's four sections. Could be okay. Alternatively we could embed education into Required Skills and Experience as a bullet: "Bachelor’s degree or higher in Computer Science, Engineering, or a related technical discipline; equivalent practical experience considered." That seems plausible as a qualification. But the heading "Required Skills and Experience" might be stretched. However the instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So they expect Qualifications separate. Let's add Qualifications. Thus sections: - Metadata paragraph (maybe not a heading) -

    Responsibilities

    with ul -