Quality Assurance Tester/Test Engineer Manual and Automation

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills?, Benefits, Pay, Schedule. Use

for each section heading. Only include sections that have real specific content. We must not repeat job title as heading. Must preserve all substantive info. Remove boilerplate: About Peraton paragraph, EEO, application statements, etc. Also remove duplicated lines. Keep details: About The Role paragraph (the description). Then responsibilities list (Key Responsibilities). Then qualifications: Required Qualifications and Preferred Qualifications. Possibly combine into Requirements and Qualifications sections. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content. We have content: - About The Role: paragraph describing role. - Key Responsibilities: list of bullet points (multiple paragraphs). Should be under Responsibilities heading. - Qualifications: Required Qualifications and Preferred Qualifications. Could be under Requirements (maybe required) and Qualifications (preferred) or combine. The instruction says use headings like Requirements, Qualifications, Skills. We can put Required Qualifications under Requirements, Preferred under Qualifications, or maybe Skills separate. But we have skills mentioned in qualifications (experience with tools). Could treat Skills as separate but we may not have a dedicated skills section; we could put skills under Qualifications. However instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Required and Preferred into Qualifications section, and maybe have Requirements for education/clearance etc. But we need to follow instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must use all; only include when posting has real specific content. We have: - About the role: yes. - Responsibilities: yes. - Requirements: maybe we can put US Citizenship, Public Trust Clearance, education/experience (5 years BS/BA or 3 years MS/MA). That's requirements. - Qualifications: maybe the hands-on experience with tools etc. Could be qualifications. - Skills: maybe we could list specific tools/experience as skills, but we already have them in qualifications. Could create Skills section listing tools: Selenium, JUnit, utPLSQL, GitLab, Fortify, LoadRunner, etc. But that might be thin. Better to put them under Qualifications. - Benefits: yes, we have Benefits Statement. - Pay: yes, Target Salary Range. - Schedule: we have "This position is 100% remote." That's schedule/location info. Could be under Schedule heading (remote). Or we could include under About the role? But we have schedule info: remote. So we can create Schedule section with that. We must not include boilerplate like "About Peraton", "Application Statements", "EEO", etc. We must preserve all substantive information: ensure we don't lose any details from responsibilities, qualifications, benefits, pay, schedule. We need to format lists with

• . For prose use

  . We must not repeat job title as heading. We must not include Job ID/requisition numbers. We must not include placeholder text like "commensurate with experience". Not present. We must not create Pay/Schedule/Benefits sections unless posting actually states them. We have them. Now craft HTML. Structure:

  About the role

  Peraton is seeking a QA Tester / Test Engineer who will support Department of War (DoW) customers applications modernization and cloud migration program by performing comprehensive testing across Agile development cycles, DevSecOps pipelines, incremental deployments, and security compliance processes. This role ensures all software modules, database changes, integrations, and releases meet functional, security, performance, and compliance standards required by the customer and the DoW. This position is 100% remote.

  But note schedule info remote could be moved to Schedule section; but we already mentioned remote in About the role. Might duplicate. Better to keep remote in Schedule section and not repeat. However About the role paragraph currently includes "This position is 100% remote." If we move that to Schedule, we should remove from About the role to avoid duplication. But we must preserve all substantive information; we can keep it in Schedule and still mention remote there. The About the role paragraph can omit that sentence. Let's check: The About the role paragraph originally: "This position is 100% remote." It's a substantive detail. We'll place it under Schedule. So About the role paragraph will be without that sentence. Thus About the role paragraph: "Peraton is seeking a QA Tester / Test Engineer who will support Department of War (DoW) customers applications modernization and cloud migration program by performing comprehensive testing across Agile development cycles, DevSecOps pipelines, incremental deployments, and security compliance processes. This role ensures all software modules, database changes, integrations, and releases meet functional, security, performance, and compliance standards required by the customer and the DoW." Now Responsibilities: list each bullet. We have bullet points under Key Responsibilities: - User Story & Sprint-Level Testing - Develop and execute unit tests, regression tests, security tests, and acceptance tests for all user stories. - Managing RITM (Requirements Traceability Matrix) and writing required manual/automated test cases - Maintain documented testing tasks for each closed and deployed user story. - Validate user story functionality aligns with functional and technical requirements (including Zero Trust, RMF, audit logging). - Automated Testing & DevSecOps Pipeline Support - Build, run, and maintain automated tests within GitLab pipelines using customer approved tools including Selenium, JUnit, utPLSQL, Fortify SCA, Fortify WebInspect, LoadRunner. - Ensure automated testing gates (SAST/DAST/QA checks) are enforced prior to code promotion. - Integration & Incremental Deployment Testing - Support integration testing to ensure new modules work seamlessly with legacy DRAS components during Strangler Pattern migration. - Validate data flows, orchestration behavior, and module interactions during incremental deployments during incremental deployments. - Release Testing - Perform release-level testing for combined deployments staged for production. - Ensure release testing follows the established Release Test Strategy and IMS timelines. - Security & Compliance Testing - Perform security testing, static/dynamic scans, Zero Trust validation, and vulnerability assessments. - Support Security Control Assessments (SCA/ED-SCA), FISMA/FedRAMP testing requirements, and Zero Trust validation. - Database & Data Migration Testing - Validate data mapping accuracy between legacy DRAS systems and the consolidated DRAS-M database. - [Test ETL data migration processes for correctness, completeness, and timing as tables and schemas evolve. - Performance Testing - Execute performance and load tests using LoadRunner and ensure system scalability. - Documentation & Reporting - Produce test plans, cases, scripts, logs, defect reports, and test metrics (e.g., defect density, escaped defects, velocity). - Provide testing evidence for ATO packages (SSP, BIA, SCA results, etc.) We need to preserve all. Note there is a stray bracket in Database & Data Migration Testing: "[Test ETL data migration processes...". Likely a formatting error; we should keep as is but maybe fix bracket? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The bracket is part of the text; we should keep it exactly as appears? It seems like a stray opening bracket. We'll keep it as "[Test ETL data migration processes for correctness, completeness, and timing as tables and schemas evolve." Might be missing closing bracket. We'll keep as is. Now Requirements: we have Required Qualifications: 5 years experience with a BS/BA degree or 3 years with a MS/MA degree. US Citizenship. Ability to obtain and maintain a Public Trust Clearance. We could also include maybe "Hands-on experience with automated testing frameworks such as Selenium, JUnit, and utPLSQL." but that's more qualifications. We'll keep those under Qualifications. Thus Requirements section: list those three items. Now Qualifications: includes both Required? Actually we already used Required for Requirements. Qualifications could include Preferred Qualifications and the hands-on experience etc. But we might also include the hands-on experience under Qualifications (since they are qualifications). Let's parse: Under "Qualifications" heading in original: "Required Qualifications: ... Preferred Qualifications: ..." Thus we can treat Required Qualifications as Requirements, Preferred Qualifications as Qualifications (or maybe Skills). But we also have many specific tool experiences listed under Required Qualifications (Hands-on experience with automated testing frameworks such as Selenium, JUnit, and utPLSQL. Experience with CI/CD pipelines (GitLab preferred). Knowledge of secure coding and security testing tools (Fortify, ACAS, WebInspect). Familiarity with performance testing tools (LoadRunner). Experience testing APIs, integrations, data migrations, and database-driven applications.) Those are also required qualifications. So maybe we should keep Required Qualifications under Requirements (including education, citizenship, clearance, experience, tools). Then Preferred Qualifications under Qualifications (or Skills). But the instruction says we can have Requirements, Qualifications, Skills sections. We could put Required under Requirements, Preferred under Qualifications, and maybe Skills under Skills (but we might not need separate Skills). However we have many specific skills (tools) that could go under Skills. But to avoid many thin sections, we could combine Preferred Qualifications and Skills into Qualifications section. Let's decide: - Requirements: education/experience, citizenship, clearance. - Qualifications: hands-on experience with tools, CI/CD, security tools, performance tools, API/testing experience, plus Preferred Qualifications items (Agile testing practices, DevSecOps understanding, DoD cybersecurity frameworks, RMF/ATO experience, mainframe-to-cloud migration, financial/entitlement systems). Thus Qualifications section will be a list combining both. Now Benefits: we have Benefits Statement paragraph. Pay: Target Salary Range paragraph. Schedule: remote work statement. Now we must ensure we don't include any boilerplate like "Application Statements", "EEO", etc. Now produce HTML. We'll need to wrap each section in

  heading then content. For lists: use

  • for each bullet. We need to be careful to not lose any details. Let's draft. About the role:

    About the role

    Peraton is seeking a QA Tester / Test Engineer who will support Department of War (DoW) customers applications modernization and cloud migration program by performing comprehensive testing across Agile development cycles, DevSecOps pipelines, incremental deployments, and security compliance processes. This role ensures all software modules, database changes, integrations, and releases meet functional, security, performance, and compliance standards required by the customer and the DoW.

    Responsibilities:

    Responsibilities

    • User Story & Sprint-Level Testing
      • Develop and execute unit tests, regression tests, security tests, and acceptance tests for all user stories.
      • Managing RITM (Requirements Traceability Matrix) and writing required manual/automated test cases
      • Maintain documented testing tasks for each closed and deployed user story.
      • Validate user story functionality aligns with functional and technical requirements (including Zero Trust, RMF, audit logging).
    • Automated Testing & DevSecOps Pipeline Support
      • Build, run, and maintain automated tests within GitLab pipelines using customer approved tools including Selenium, JUnit, utPLSQL, Fortify SCA, Fortify WebInspect, LoadRunner.
      • Ensure automated testing gates (SAST/DAST/QA checks) are enforced prior to code promotion.
    • Integration & Incremental Deployment Testing
      • Support integration testing to ensure new modules work seamlessly with legacy