Software Tester
About the role
then... content. Then responsibilities: The paragraph after "As a quality assurance specialist..." includes duties: work with software architects and developers, help develop and implement test plan, generate problem resolutions, track QA standards, document results, communicate defects, expand experience in various types of testing, broaden skills in documenting and solving system deficiencies, creating test plans and test reports. That's responsibilities. Requirements: "You Have:" list: Experience testing software control systems, Knowledge of real-time software development and sub-second timing requirements, Secret clearance, Bachelor's degree in a Technology field and 1+ years of experience in software testing, or 2+ years of experience in software testing in lieu of a degree. Qualifications: maybe "Nice If You Have:" list: Experience with automated testing suites such as Cucumber or Selenium, Knowledge of software test planning, Ability to read and comprehend system-level requirements to verify tests. Skills: Could be combined with requirements? But we have separate sections: Requirements (must-have) and Qualifications (nice-to-have). Could also have Skills section for specific technical skills like automated testing suites, etc. But we already have Nice If You Have. Could treat that as Skills. However guidelines: Use sections only when posting has real specific content. We have content for Requirements, Nice If You Have (could be Skills or Qualifications). Also Benefits: there is a paragraph about benefits: health, life, disability, financial, retirement, paid leave, professional development, tuition assistance, work-life programs, dependent care, recognition awards program, eligibility details. That's benefits. Pay: "Salary at Booz Allen is determined... The projected compensation range for this position is $61,900.00 to $141,000.00 (annualized USD)." That's pay. Schedule: Not explicitly mentioned. There's Work Model section describing remote/hybrid/onsite expectations. That could be considered Schedule? It's about work model. The guideline says include Schedule section only if posting actually states them. There's no explicit schedule like full-time/part-time hours, but there is mention of full-time and part-time employees working at least 20 hours a week eligible for benefits. That's about eligibility, not schedule. There's no explicit schedule like "Monday-Friday 9-5". So we should not create Schedule section. We also have "Work Model" description; could be considered "Work Model" but not in allowed headings. Allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could put work model under Responsibilities? Not ideal. Could create a "Skills" section for technical skills like automated testing suites, etc. But we already have Nice If You Have which could be Skills. Let's map: - About the role: The Opportunity paragraph. - Responsibilities: The paragraph starting "As a quality assurance specialist..." (including duties). - Requirements: You Have list. - Skills: Nice If You Have list (automated testing suites, test planning, reading requirements). Could also include knowledge of real-time software development etc but that's in Requirements. - Qualifications: maybe we could treat "Nice If You Have" as Qualifications, but we already used Skills. Could also have Qualifications for education/experience? But that's in Requirements. Might be okay to have only Requirements and Skills, and omit Qualifications. However guidelines: Prefer a few substantive sections over many thin ones. We have About the role, Responsibilities, Requirements, Skills, Benefits, Pay. That's six sections. Could also combine Skills into Requirements? But they'd be thin. Better to keep separate. Benefits: paragraph about benefits. Pay: compensation range. We must not include boilerplate like EEO, legal, etc. Remove Identity Statement, Candidate AI Usage Policy, Work Model, Commitment to Non-Discrimination, etc. Also remove Job Number line. We must preserve all substantive information. So we need to include the details from Benefits paragraph: health, life, disability, financial, retirement benefits, paid leave, professional development, tuition assistance, work-life programs, dependent care, recognition awards program, eligibility details (full-time and part-time employees working at least 20 hours a week regular basis eligible; individuals that do not meet threshold only eligible for select offerings, not inclusive of health benefits). Also mention to learn more about total benefits by visiting Resource page etc. That's substantive. Pay: include the projected compensation range and note that salary determined by factors. We must not include "This posting will close within 90 days from the Posting Date." That's maybe not substantive? It's about timeline; could be considered metadata but not required. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. The closing date is minor metadata; we could drop it. Probably drop. Also drop "Identity Statement", "Candidate AI Usage Policy", "Work Model", "Commitment to Non-Discrimination". Also drop "As part of the hiring process..." etc. Now produce HTML. Structure:
About the role
When a user tries a new system, they expect it to be intuitive and run smoothly. Functionality, reliability, and user experience are key to successful information systems, and that means rigorous testing. That’s why we need a quality assurance analyst like you who’s eager to help thoroughly test software and ensure that our team releases the best system possible.
Responsibilities
As a quality assurance specialist on our team, you’ll work with software architects and developers that evaluate developed systems for U.S. Navy clients. You’ll help develop and implement a test plan based on requirements. Using software quality assurance best practices, you’ll generate problem resolutions and track quality assurance standards to observe how the system performs, then document the results and communicate defects to the development team so they can start improving the tool. You’ll expand upon your experience in various types of testing, including manual, automation, performance, usability, and testing process improvement. This is an opportunity to broaden your skills in documenting and solving system deficiencies as well as creating test plans and test reports.
Requirements
- Experience testing software control systems
- Knowledge of real-time software development and sub-second timing requirements
- Secret clearance
- Bachelor's degree in a Technology field and 1+ years of experience in software testing, or 2+ years of experience in software testing in lieu of a degree
Skills
- Experience with automated testing suites such as Cucumber or Selenium
- Knowledge of software test planning
- Ability to read and comprehend system-level requirements to verify tests
Benefits
At Booz Allen, we celebrate your contributions, provide you with opportunities and choices, and support your total well-being. Our offerings include health, life, disability, financial, and retirement benefits, as well as paid leave, professional development, tuition assistance, work-life programs, and dependent care. Our recognition awards program acknowledges employees for exceptional performance and superior demonstration of our values. Full-time and part-time employees working at least 20 hours a week on a regular basis are eligible to participate in Booz Allen’s benefit programs. Individuals that do not meet the threshold are only eligible for select offerings, not inclusive of health benefits.
Pay
Salary at Booz Allen is determined by various factors, including but not limited to location, the individual’s particular combination of education, knowledge, skills, competencies, and experience, as well as contract-specific affordability and organizational requirements. The projected compensation range for this position is $61,900.00 to $141,000.00 (annualized USD). The estimate displayed represents the typical salary range for this position and is just one component of Booz Allen’s total compensation package for employees.
We should not include extra sections like Schedule. Make sure no markdown fences. Output only HTML. Check for any leftover boilerplate: removed. Check for any repeated content: fine. Check for any missing substantive info: The "Join us. The world can’t wait." is a tagline; could be included in About the role? It's after The Opportunity paragraph. It's a motivational line. Might be considered substantive but could be dropped as fluff. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. "Join us. The world can’t wait." is not really substantive detail about job; it's a tagline. Might be considered boilerplate? Not exactly legal. But it's not a duty/requirement. It's optional. I'd consider it non-essential and could drop. However to be safe, we could include it in About the role paragraph after the first paragraph. Let's add a sentence: "Join us. The world can’t wait." as part of About the role. Thus About the role paragraph becomes two sentences? We'll combine. Let's adjust About the role:When a user tries a new system, they expect it to be intuitive and run smoothly. Functionality, reliability, and user experience are key to successful information systems, and that means rigorous testing. That’s why we need a quality assurance analyst like you who’s eager to help thoroughly test software and ensure that our team releases the best system possible. As a quality assurance specialist on our team, you’ll work with software architects and developers that evaluate developed systems for U.S. Navy clients. You’ll help develop and implement a test plan based on requirements. Using software quality assurance best practices, you’ll generate problem resolutions and track quality assurance standards to observe how the system performs, then document the results and communicate defects to the development team so they can start improving the tool. You’ll expand upon your experience in various types of testing, including manual, automation, performance, usability, and testing process improvement. This is an opportunity to broaden your skills in documenting and solving system deficiencies as well as creating test plans and test reports. Join us. The world can’t wait.
But that merges responsibilities into About the role. Better keep About the role as just the Opportunity paragraph plus tagline, and Responsibilities separate. So we keep About the role short: The Opportunity paragraph + tagline. Thus:About the role
When a user tries a new system, they expect it to be intuitive and run smoothly. Functionality, reliability, and user experience are key to successful information systems, and that means rigorous testing. That’s why we need a quality assurance analyst like you who’s eager to help thoroughly test software and ensure that our team releases the best system possible. Join us. The world can’t wait.
Then Responsibilities as earlier. Check that we didn't lose any responsibility details: we have them. Now ensure we didn't include any boilerplate like "This posting will close within 90 days from the Posting Date." Not included. Check that we didn't include "Clearance: Applicants selected will be subject to a security investigation and may need to meet eligibility requirements for access to classified information; Secret clearance is required." That's covered in Requirements (Secret clearance). The extra sentence about security investigation is boilerplate; we can drop. Check that we didn't include "Compensation At Booz Allen, we celebrate your contributions..." That's benefits. Check that we didn't include "Salary at Booz Allen is determined..." That's pay. Check that we didn't include "Identity Statement..." etc. Not included. Check that we didn't include "Work Model..." Not included. Check that we didn't include "Commitment to Non-Discrimination..." Not included. All good. Now output HTML.