Test Engineering, Associate

We need to output HTML fragment with sections: About the role (but note we already have "About The Role" heading in source; we should use

for section headings). We should not repeat job title. We need to include sections only when there is real content. We have content for responsibilities (the bullet list under "The position will be responsible for the following but not limited too:" and subsequent paragraphs). Also we have Qualifications section. Also we have Preferred Qualifications. Also we have Details (Target Salary Range, Benefits Statement). Also we have maybe "About Peraton" but that's boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Peraton" paragraph is generic company description; might be considered boilerplate? It's not about the role. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The "About Peraton" is substantive? It's generic marketing but maybe considered boilerplate. Usually they'd want to keep it? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Peraton" is not those. It's company overview. Might be considered substantive? Not sure. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep it unless it's boilerplate like EEO etc. The "About Peraton" is not EEO. It's a description of the company. I'd keep it as a paragraph maybe under a heading? But we only use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings. If we include "About Peraton", we would need a heading maybe "About the company"? Not in list. So better to omit it, as it's not one of the allowed headings. However we could embed it in a

without heading. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use

for section headings (e.g. those). It might be okay to use other headings but they gave examples. Safer to follow: only use those headings if we have content. So we can have paragraphs without headings for company overview. But they said "Output ONLY the HTML fragment — no /, no markdown code fences." So we can output a series of

and

,

etc. We need to include sections only when posting has real, specific content. So we need to decide which sections to include: - About the role: we have a paragraph describing the role. Yes. - Responsibilities: we have a list of duties. Yes. - Requirements: we have Qualifications (maybe "Qualifications" heading). Could also have "Requirements". The posting has "Qualifications" and "Preferred Qualifications". We could combine into Requirements and Preferred Qualifications? But instruction: prefer a few substantive sections over many thin ones. Could have "Qualifications" covering both required and preferred? But we need to preserve all detail. Could split into "Qualifications" (required) and "Preferred Qualifications". Both are substantive. - Skills: maybe not separate; we could embed skills within qualifications. - Benefits: we have Benefits Statement. - Pay: we have Target Salary Range. - Schedule: we have "This position is remote." That's schedule/location info. Could be considered Schedule section. The instruction: include a section ONLY when posting has real, specific content for it. The posting says "This position is remote." That's specific content about schedule/location. So we can have a Schedule section with that. Thus sections: About the role, Responsibilities, Qualifications, Preferred Qualifications, Benefits, Pay, Schedule. We need to avoid headings like "About the role" exactly? The example uses "About the role". We'll use that. Now we need to extract content. About the role paragraph: "Peraton is seeking a motivated Software Quality Assurance Engineer to support quality assurance and test automation activities on the BASIS program. Working under the guidance of senior QA engineers and program leads, the Junior QA Engineer will contribute to the program's automation-first QA mandate. The selected candidate will develop and execute automated test scripts, support test documentation, assist in defect tracking, and contribute to the program's rigorous quality standards across the deployment pipeline." We should keep that as

. Responsibilities: The bullet list after "The position will be responsible for the following but not limited too:" includes several paragraphs each starting with a bold heading? Actually the text: "Develop, implement, and maintain automated test scripts for unit, integration, and end-to-end functional testing under the guidance of senior QA engineers, in alignment with Agile sprint schedules and program quality standards.Ensure all automated test cases are executable by the end of each Agile sprint and delivered for incorporation into the Government-managed DevSecOps pipeline.Support the program's Test-Driven Development (TDD) methodology by writing test cases prior to code development in collaboration with software developers.Contribute to the Test Automation State Assessment and associated automation completion project plan by analyzing assigned application areas for coverage gaps.Automate adjacent legacy test cases to expand overall regression test coverage across the portfolio.Execute non-automated test cases. Test Planning & Documentation Assist in the development and maintenance of Requirements Traceability Matrices (RTMs) at the end of each development cycle/sprint, supporting complete testing coverage of all requirements.Document all test activities, execution results, and defect findings accurately within the Government-provided Test Case Management System.Contribute to the preparation of Testing Reports, Release Notes, and Software Version Descriptions (SVDs) per release cadence requirements. Quality Assurance & Defect Management Support adherence quality thresholds.Triage and track defects in JIRA; conduct initial analysis, determine if issues were previously identified, and attempt replication prior to escalation to product teams; submit JIRA tickets prior to escalation.Support weekly defect escalation reporting and assist with monitoring customer-reported defects. Section 508 / Accessibility Testing Conduct accessibility testing against WCAG 2.0 Level AA standards at planned intervals throughout the development lifecycle.Assist in the preparation of Voluntary Product Accessibility Templates (VPATs) including test results, remediation reports, and documentation of conformance levels.Contribute Section 508 compliance testing status reporting.Performance & Environment TestingSupport stress and load testing activities conducted in the ProdSim (Production Simulation) environment per Government-approved test schedules.Assist in coordinating and supporting Disaster Recovery (DR) testing activities in collaboration with the technical and operations teams.Support Independent Verification & Validation (IV&V) of all application changes. Agile Actively participate in Agile ceremonies including sprint planning, backlog grooming, daily stand-ups, sprint reviews, and retrospectives.Maintain and update sprint-level defect tracking, test case completion status, and burn-down metrics in JIRA.Adhere to the full deployment pipeline standards and quality gates at each stage." We need to turn this into a list

• items. Each sentence seems to be a responsibility. We can split by periods that start a new capital letter after a period? But easier: we can treat each distinct responsibility as a list item. The text has no clear bullet markers; we need to infer items. We can split by the headings like "Develop, implement, and maintain..." then "Ensure all automated test cases..." then "Support the program's Test-Driven Development..." then "Contribute to the Test Automation State Assessment..." then "Automate adjacent legacy test cases..." then "Execute non-automated test cases." then "Test Planning & Documentation Assist..." then "Document all test activities..." then "Contribute to the preparation of Testing Reports..." then "Quality Assurance & Defect Management Support adherence quality thresholds." then "Triage and track defects in JIRA..." then "Support weekly defect escalation reporting..." then "Section 508 / Accessibility Testing Conduct accessibility testing..." then "Assist in the preparation of Voluntary Product Accessibility Templates..." then "Contribute Section 508 compliance testing status reporting." then "Performance & Environment TestingSupport stress and load testing..." then "Assist in coordinating and supporting Disaster Recovery (DR) testing..." then "Support Independent Verification & Validation (IV&V) of all application changes." then "Agile Actively participate in Agile ceremonies..." then "Maintain and update sprint-level defect tracking..." then "Adhere to the full deployment pipeline standards..." That's many items. We'll create
• for each distinct responsibility. We'll keep the text as is. Qualifications: The section "Qualifications" includes: "0 years with Bachelor's degree in Computer Science, Software Engineering, Information Technology, or a related technical field equivalent experience considered or 4 years experience in software quality assurance, test automation, or software testing roles with HS diploma.Ability to obtain Public Trust clearanceFoundational understanding of test automation principles and experience writing automated test scripts in at least one framework or scripting language (e.g., Selenium, JUnit, TestNG, Python, Java, or equivalent).Familiarity with Agile/Scrum development methodologies and DevSecOps principles.Basic experience with defect tracking tools, preferably JIRA.Understanding of the software testing lifecycle including unit, integration, regression, and user acceptance testing.Familiarity with Test-Driven Development (TDD) practices.Strong attention to detail, analytical thinking, and ability to document test activities and results clearly and accurately.Ability to work collaboratively within a team environment and communicate effectively with developers, senior engineers, and Government stakeholders." We need to split into list items. Each sentence seems separated by a period but there are no spaces after periods sometimes. We'll split by periods and trim. Preferred Qualifications: list: "ISTQB (International Software Testing Qualifications Board) Foundation Level certification or equivalent.Exposure to static code analysis (SAST) or dynamic application security testing (DAST) tools such as Fortify, Sonatype, or BURP.Experience with Section 508 / WCAG 2.0 Level AA accessibility testing.Familiarity with CI/CD pipelines and automated test integration within a DevSecOps environment.Prior experience supporting DoD or Federal government IT programs.Exposure to Oracle or PL/SQL database environments.Familiarity with ServiceNow for incident tracking and management." Again split. Benefits: "Peraton offers eligible employees a variety of benefits including medical, dental, vision, life, health savings account, short/long term disability, EAP, parental leave, 401(k), paid time off (PTO) for vacation, and company paid holidays. A full listing of available benefits can be viewed at https://www.careers.peraton.com/benefits." We can keep as

  maybe with a link. Pay: "Target Salary Range: $66,000 - $106,000. This represents the typical salary range for this position. Salary is determined by various factors, including but not limited to, the scope and responsibilities of the position, the individual's experience, education, knowledge, skills, and competencies, as well as geographic location and business and contract considerations. Depending on the position, employees may be eligible for overtime, shift differential, and a discretionary bonus in addition to base pay." Schedule: "This position is remote." We should not include application instructions, EEO, etc. Now produce HTML. We'll start with

  About the role

  ...

  Then

  Responsibilities

  • ...
  ...
  Then

  Qualifications

  ...
  Then

  Preferred Qualifications

  ...
  Then

  Benefits