Staff Software QA Specialist 1

We need to output HTML fragment with sections: headings

for sections like 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. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info. Let's parse the posting. Content: - Opening: "Because of our work with the defense community, applicants must be U.S. citizens.*** ARA is seeking a Staff Software QA Specialist 1 to be part of our team in Baton Rouge, Louisiana. We are a 100% employee-owned scientific research and engineering company dedicated to solving critical national problems to improve our safety, security, and way of life. You will work with other developers and engineers to design and implement quality assurance solutions for a wide range of applications. As a member of our development team, you will work in an agile environment focused on delivering high-quality software to our clients." - "What You Will Do You will be a key member of ARA supporting multiple teams developing enterprise technologies to aid real-world operations for the Navy and military communities. As a valued member of our team your responsibilities will include: Collaborate with cross-functional teams to plan and execute manual and automated testingWork with cross-functional teams to define a testing vision/test plan with respect to stakeholder goals and customer feedbackReview requirements, specifications, and technical design documents to create test casesSupport code reviews and ensure the team is creating adequate unit, regression, and system testsIdentify, record, and document findings and create reports" - "Staff Software QA Specialist 1 Required Technologies And Skills BA/BS in Computer Science or a related fieldKnowledge of Quality Assurance processes, principles, and methodologiesExperience in one or more object-oriented programming languagesPractical experience authoring software test functions using test automation frameworksDemonstrated problem-solving and debugging skills Licenses & Certifications US citizen with the ability to obtain DoD Secret clearance Preferred Qualifications Experience with one or more frontend libraries (React, Vue, Angular, etc.)Experience with C#Experience or familiarity with automating QA processes using a continuous integration/continuous delivery (CI/CD) platform such as GitLab" - "Benefits Include 401K MatchingEmployee Stock Ownership Plan (ESOP)Health, Dental, and Vision InsurancePaid holidays and Paid Time Off" - "About Us Applied Research Associates, Inc. (aka ARA) is an employee-owned international research and engineering company known for providing technically superior solutions to complex and challenging problems in the physical sciences. We were founded in Albuquerque, NM in 1979 as the disco era was, thankfully, closing out and the personal computer era was beginning. We employ over 2,200 professionals and continue to grow. ARA offices throughout the U.S. and Canada provide a broad range of technical expertise in defense, civil, and health technologies, computer software and simulation, systems analysis, environmental technologies, and testing and measurement. Around ARA you are equally likely to hear a conversation about Kubernetes clusters as you are a debate on merits of a reverse polish notation (RPN) calculator! While this is all of the Year One and Beyond stuff, Day One is highly impressive too. These are things like our competitive salary, Employee Stock Ownership Plan (ESOP) & 401(k) with matching program, benefits package which includes medical, dental vision, flex spending, telehealth services, company-paid life & disability insurance including paid maternity disability leave through our company-paid short-term disability benefit, domestic partner coverage, dependent care flex spending, daycare discounts, pet insurance, relocation opportunities, floating holidays, tuition reimbursement, professional development as well as flexible schedules. ARA also prides ourselves on having a challenging culture where innovation & experimentation are the norm. At ARA, employees are our greatest assets, so we give our employees the tools, training, and opportunities to take active roles as owners. The motto, “Engineering and Science for Fun and Profit” sums up the ARA experience. The company realizes employee ownership spawns greater creativity and initiative along with higher performance and customer satisfaction levels." We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. There's no explicit EEO but there is "Because of our work with the defense community, applicants must be U.S. citizens." That's a requirement, not EEO. Keep that. We need to format sections. Potential sections: - About the role (maybe "About the role" or "About the position") – we have description of role and responsibilities. Could combine responsibilities. - Responsibilities: list of duties. - Requirements: required technologies and skills (BA/BS, QA knowledge, OOP language, test automation, problem solving, US citizen, ability to obtain DoD Secret clearance). Also maybe "Licenses & Certifications" part. - Qualifications: Preferred Qualifications (frontend libs, C#, CI/CD). Could be under "Preferred Qualifications" but we only have headings list: 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 can use those headings. We need to decide which sections to include based on content. We have content for About the role (intro). Responsibilities (list). Requirements (required tech/skills). Qualifications (preferred). Skills (maybe we could combine required tech/skills under Skills? But we have both Requirements and Skills headings; we could put required tech under Requirements, and maybe Skills could be something else? But we don't have separate skills list besides required tech. Could put required tech under Skills and requirements under Requirements (education, citizenship). However we need to avoid duplication. Better: Use sections: - About the role: intro paragraph about role, company, location, agile environment. - Responsibilities: bullet list of duties. - Requirements: education (BA/BS in CS or related), US citizen, ability to obtain DoD Secret clearance, knowledge of QA processes, experience in OOP language, practical experience authoring software test functions using test automation frameworks, demonstrated problem-solving and debugging skills. - Qualifications (Preferred): experience with frontend libraries, experience with C#, familiarity with automating QA processes using CI/CD platform such as GitLab. - Benefits: list of benefits (401K matching, ESOP, health/dental/vision insurance, paid holidays and PTO). Also from About Us we have many more benefits (flex spending, telehealth, etc.) but those are in About Us section. The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we need to include all benefits mentioned anywhere. The Benefits Include section lists some; the About Us paragraph lists many more benefits: competitive salary, ESOP & 401(k) with matching, benefits package includes medical, dental vision, flex spending, telehealth services, company-paid life & disability insurance including paid maternity disability leave through company-paid short-term disability benefit, domestic partner coverage, dependent care flex spending, daycare discounts, pet insurance, relocation opportunities, floating holidays, tuition reimbursement, professional development, flexible schedules. We should combine all benefits into a Benefits section. Also note that "competitive salary" is mentioned but we should not create a Pay section unless posting actually states them. It does state "competitive salary" but not a specific number. The instruction says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. It says "competitive salary" is stated, so we can include Pay section? The heading list includes Pay. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state "competitive salary" (though vague). Is that considered stating them? It's not a specific number but it's stating that salary is competitive. I'd argue it's stating Pay info, albeit vague. But the instruction also says never emit a heading followed by filler/placeholder text like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "competitive salary" is not exactly filler but it's vague. Might be considered placeholder? The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Since they do state "competitive salary", we could include Pay section with that phrase. However they also say "Prefer a few substantive sections over many thin ones." So maybe we can incorporate salary info into Benefits or About the role. But they specifically list Pay as a possible heading. I'd lean to include Pay section with the phrase "competitive salary". However we must avoid filler like "commensurate with experience". "competitive salary" is not exactly filler but it's vague. I'd include it. Schedule: The posting mentions "flexible schedules" in About Us. So we can include Schedule section with "flexible schedules". That's stated. Thus we can have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. We must not repeat job title as heading. Good. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information. So we need to include all details from the posting, not omit any. Let's extract all substantive info pieces: From opening: - Because of our work with the defense community, applicants must be U.S. citizens. - ARA is seeking a Staff Software QA Specialist 1 to be part of our team in Baton Rouge, Louisiana. - We are a 100% employee-owned scientific research and engineering company dedicated to solving critical national problems to improve our safety, security, and way of life. - You will work with other developers and engineers to design and implement quality assurance solutions for a wide range of applications. - As a member of our development team, you will work in an agile environment focused on delivering high-quality software to our clients. From "What You Will Do": - You will be a key member of ARA supporting multiple teams developing enterprise technologies to aid real-world operations for the Navy and military communities. - As a valued member of our team your responsibilities will include: - Collaborate with cross-functional teams to plan and execute manual and automated testing - Work with cross-functional teams to define a testing vision/test plan with respect to stakeholder goals and customer feedback - Review requirements, specifications, and technical design documents to create test cases - Support code reviews and ensure the team is creating adequate unit, regression, and system tests - Identify, record, and document findings and create reports From "Staff Software QA Specialist 1 Required Technologies And Skills": - BA/BS in Computer Science or a related field - Knowledge of Quality Assurance processes, principles, and methodologies - Experience in one or more object-oriented programming languages - Practical experience authoring software test functions using test automation frameworks - Demonstrated problem-solving and debugging skills - Licenses & Certifications: US citizen with the ability to obtain DoD Secret clearance From "Preferred Qualifications": - Experience with one or more frontend libraries (React, Vue, Angular, etc.) - Experience with C# - Experience or familiarity with automating QA processes using a continuous integration/continuous delivery (CI/CD) platform such as GitLab From "Benefits Include": - 401K Matching - Employee Stock Ownership Plan (ESOP) - Health, Dental, and Vision Insurance - Paid holidays and Paid Time Off From About Us paragraph (benefits and other info): - Competitive salary - Employee Stock Ownership Plan (ESOP) & 401(k) with matching program - Benefits package which includes medical, dental vision, flex spending