Jobs · Quality Assurance · South Carolina

Quality Assurance, Analyst

The MIL Corporation · Charleston, SC · 1 mo ago
Quality Assurance$68k–$84k/yrFull-time
We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Learn more on the Why MIL?" etc? That's fluff but maybe considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Why MIL?" section seems like company description, not required to remove but could be considered fluff. However we need to preserve ALL substantive information; do NOT invent or summarize away detail. The "Why MIL?" includes awards etc. Might be considered substantive? It's about company culture; maybe we can keep under About the role? The posting already has a Summary paragraph describing role. We could put that under About the role. The "Why MIL?" could be considered extra but not required; but we could include as part of About the role or maybe omit as it's not directly about the role. The instruction: Prefer a few substantive sections over many thin ones. So we could combine company info into About the role or maybe omit if not essential. However we must preserve ALL substantive information; does that include company awards? It's substantive but not about the role. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not say to remove company description. So we should keep it. Could place under About the role or a separate section like "About the Company". But only allowed headings are the listed ones. So we must fit into those headings. About the role could include summary and company info. Responsibilities: list. Requirements: maybe combine Required Qualifications? The posting has "Required Qualifications" bullet list and "Desired Qualifications". Also "Education" and "Clearance". Also "US Citizenship: Required". Also "Clearance Required: Ability to Obtain a Secret". Also "Education Required: BA/BS". Also "US Citizenship: Required". Also "Clearance Must be eligible to obtain a Secret clearance and be able to upgrade to a Top Secret (TS) clearance as required." We need to map to headings: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have to decide what goes where. Typically: Requirements could be mandatory qualifications (education, clearance, citizenship, experience). Qualifications could be desired qualifications. Skills could be specific skills like MS Office, Control-M, SQL, etc. Benefits from compensation section. Pay from compensation range. Schedule from "This position requires a fully on-site schedule. Schedule is subject to change based on company and contract requirements." We must not create sections with placeholder text like "commensurate with experience". We have actual pay range: $68,000 - $84,000 per year. So we can include Pay section. Schedule: we have info. Benefits: we have description of benefits. Now we need to ensure we don't duplicate. Also we must not include headings with empty content. We'll produce HTML like:

About the role

... summary and maybe company description.

Responsibilities

  • ... each responsibility.

Requirements

  • ... mandatory items.

Qualifications

  • ... desired qualifications.

Skills

  • ... specific skills.

Benefits

  • ... benefits.

Pay

... salary range.

Schedule

... on-site schedule.

We need to ensure we don't include fluff like "Learn more on the Why MIL?" etc. We can incorporate company description into About the role paragraph. Let's extract substantive content: Summary: "The MIL Corporation seeks a Quality Assurance, Analyst to support a Federal Government client in Charleston, SC. This role is responsible for independently analyzing and testing complex PeopleSoft ERP payroll software applications, including cross-system applications supporting financial reporting and interfaces. This position requires a fully on-site schedule. Schedule is subject to change based on company and contract requirements." We could put that in About the role. Also the "Why MIL?" section includes awards and culture. Could be included in About the role as extra. But we must not repeat job title. Already not. Now Responsibilities list: - Analyze complex business and system requirements to identify testable conditions, risks, and edge cases; develop and document alternative testing approaches as needed. - Design, develop, and maintain automated and manual test plans, test cases, and test scripts aligned with industry standards and SDLC best practices. - Execute automated and manual test suites, document results, and clearly communicate defects, trends, and quality risks to development teams and stakeholders. - Translate business and regulatory requirements into effective test scenarios that validate both functional and non-functional system behavior. - Provide subject matter expertise on system functionality, testing methodologies, and automation frameworks to support continuous improvement of QA practices. - Utilize Control-M for testing batch processing, job scheduling, dependency management, and monitoring. Now Requirements (mandatory): - Ability to obtain a Secret clearance (and ability to upgrade to TS as required). - BA/BS education (or High School diploma with equivalent experience? Actually Education says BA/BS or High School diploma with equivalent experience. That's under Education. But also "Education Required: BA/BS". There's also "Education BA/BS or High School diploma with equivalent experience" under Desired Qualifications? Actually after Desired Qualifications there is "Education BA/BS or High School diploma with equivalent experience". That seems like education requirement. We'll treat as requirement: BA/BS or HS diploma with equivalent experience. - US Citizenship: Required. - 3 years of experience with software development lifecycle (analysis/design, development, testing, implementation, support) - Quality Assurance experience - Expertise with MS Office (Project, Word, Excel, PowerPoint, Outlook) - Strong verbal and written communication skills - Ability to multi-task while maintaining a professional demeanor Also "Travel None Required" maybe not needed. Now Qualifications (desired): - Experience with government payroll or accounting systems - Experience with Waterfall and Agile software development methodologies - Experience with Control-M for batch processing, scheduling - Experience writing and executing SQL or other queries Also maybe "Experience with Control-M for batch processing, scheduling" already listed under responsibilities but also desired. Now Skills: Could be specific technical skills: MS Office, Control-M, SQL, etc. But we already have some in Requirements and Qualifications. To avoid duplication, we could put Skills as: MS Office (Project, Word, Excel, PowerPoint, Outlook), Control-M, SQL/query writing, etc. But we need to avoid repeating same bullet points. Perhaps we can treat Skills as the technical tools: MS Office, Control-M, SQL. However the instruction says preserve ALL substantive information; we must not lose info. If we put some info in Requirements and some in Qualifications, we still preserve. Skills could be optional; we could omit if we think it's thin. But we have specific skills listed: MS Office, Control-M, SQL. We could put them under Skills. But we already have MS Office in Requirements (expertise). Control-M appears in Responsibilities and Desired Qualifications. SQL appears in Desired Qualifications. To avoid duplication, we could still list them under Skills but note they are also elsewhere. However duplication is allowed? The instruction says remove duplicated lines. So we should not duplicate same exact line. But we can mention them in different contexts if not identical lines. For example, "Expertise with MS Office" is a line; we could put that under Requirements. If we also put "MS Office" under Skills, that's a duplication of the concept but not identical line. Might be considered duplication? Safer to avoid repeating same content. We could decide to put MS Office under Requirements, Control-M under Responsibilities (already there), SQL under Qualifications (desired). Then we might not need a separate Skills section. But the instruction wants us to use headings only when there is real specific content. If we don't have distinct content for Skills, we could omit it. However we have specific skills that are not captured elsewhere? Actually MS Office is captured under Requirements; Control-M is captured under Responsibilities and Desired Qualifications; SQL is under Desired Qualifications. So we could omit Skills section. But we have "Expertise with MS Office (Project, Word, Excel, PowerPoint, Outlook)" which is a skill. Could be placed under Requirements. That's fine. Thus we may have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. We need to ensure we don't create empty sections. Now Benefits: from compensation paragraph: "The MIL Corporation values your contributions and offers a range of benefits to support your overall well-being. We are pleased to offer a comprehensive range of benefits to our full-time employees which include health, life, disability, and retirement plans, as well as paid time off, opportunities for professional growth and tuition assistance. Additional benefits and incentives may also apply, which will be communicated during the hiring process." We can turn that into a list: health, life, disability, retirement plans, paid time off, professional growth opportunities, tuition assistance. Also mention additional benefits may apply. Pay: "$68,000 - $84,000 per year" plus note about factors. Schedule: "This position requires a fully on-site schedule. Schedule is subject to change based on company and contract requirements." Now About the role: combine summary and maybe company description. Let's include summary paragraph and maybe a brief about MIL from the "Why MIL?" but we can keep it short: "MIL Corporation is a dynamic workforce delivering world-class solutions in cyber, engineering, financial management, and information technology, known for collaborative, people-first culture and numerous workplace awards." That's substantive but not duplicated. We'll include that. Now we must ensure we don't include boilerplate like EEO statement at end. Remove that. Now produce HTML. Check for any duplicated lines: We'll avoid repeating same exact sentences. Let's craft. About the role paragraph:

The MIL Corporation seeks a Quality Assurance Analyst to support a Federal Government client in Charleston, SC. This role is responsible for independently analyzing and testing complex PeopleSoft ERP payroll software applications, including cross-system applications supporting financial reporting and interfaces. MIL Corporation is a dynamic workforce delivering world-class solutions in cyber, engineering, financial management, and information technology, known for a collaborative, people-first culture and numerous workplace awards.

That's fine. Now Responsibilities list as above. Now Requirements list: - Ability to obtain a Secret clearance (with potential upgrade to Top Secret as required) - BA/BS degree or high school diploma with equivalent experience - U.S. citizenship - Minimum 3 years of experience with software development lifecycle (analysis/design, development, testing, implementation, support) - Quality Assurance experience - Expertise with MS Office (Project, Word, Excel, PowerPoint, Outlook) - Strong verbal and written communication skills - Ability to multi-task while maintaining a professional demeanor Now Qualifications list (desired): - Experience with government payroll or accounting systems - Experience with Waterfall and Agile software development methodologies - Experience with Control-M for batch processing and job scheduling - Experience writing and executing SQL or other queries Now Benefits list: - Health, life, disability, and retirement plans - Paid time off - Opportunities for professional growth - Tuition assistance - Additional benefits and incentives may apply (details communicated during hiring) Now Pay:

The projected compensation range is $68,000 - $84,000 per year.

Similar jobs