Manual Tester

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real content. The posting includes description of role, responsibilities, requirements, qualifications, skills, pay range. No explicit benefits or schedule. So we should have sections: About the role (maybe a brief intro), Responsibilities, Requirements, Qualifications, Skills, Pay. Possibly also "Location" but not required heading. We must not repeat job title. Must not include boilerplate like visa sponsorship etc? Actually we must preserve all substantive information, but remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The visa sponsorship line is substantive? It's a requirement about eligibility. Should we keep? It's not boilerplate; it's a condition. So we should keep it. The line "C2C or 1099 not available for this opportunity! Potential candidates will need to have the ability to work W2 on Prominents’ payroll." That's also substantive. So include in appropriate section maybe Requirements or About the role. We need to parse the posting: - Intro: "Prominent is helping our client find Manual Software Tester resources for their QA Team." That's about the role. - Preference given to candidates currently within a reasonable commute to Omaha, Nebraska or Greenwood Village, Colorado; however, remote may be a possibility. (Location preference) - As a Software Tester you will be responsible for ensuring the quality of products and services using Agile, Waterfall, DevOps with CI/CD in a fast-paced services environment. Then a list of tasks (responsibilities) starting with "Tasks Lead QA delivery team..." etc. Many sentences. Then "Skills:" list. Then qualifications: "Experienced QA Test Lead Minimum of a 4-year degree in Computer Science, Engineering, or other technical/analytical degrees. 4-7 years of related technical and business leadership experience with Quality Assurance and Testing discipline. 4-7 years of management in testing with large teams using various methodologies including Waterfall, Agile- Scrum and SDLC. Outstanding interpersonal and communication skills (oral, written, and interpersonal) including the ability to communicate technical concepts to a non-technical audience. Strong understanding in advancement of CI/CD or DevOps Testing Models with GitLab, Nexus, Harness, Tricentis Tosca (Automation Foundation), JIRA, Postman, SoapUI Ability to contribute and direct at all levels of testing including unit, functional, automation, performance, and scalability testing; be able to step in and provide leadership in test design and implementation. Proven experience in coordinating global teams for multiple portfolios. This includes, but not limited to, Daily Stand-ups, Estimations, Coverage, Test Strategy, Planning, Test Cases review, Defect triage, Statuses, Reporting, Test Results review & walkthrough sessions and represent the Corporate QA team during U.S. hours. Collaboration with Business, Development, and other testing teams. Should be a client focused individual adept with knowledge to execute programs of varying complexities and report “valuable” metrics along with key milestones, dependencies, risks, and issues. Preferred skills: Knowledge of QTest, TOSCA, JENKINS, SPLUNK, Oracle 11g, Jira, Confluence, TOAD, Microsoft Office, SharePoint" Then pay: "Anticipated pay range is $39/hr to $44/hr." We need to separate sections: About the role (intro + location preference maybe), Responsibilities (the tasks list), Requirements (maybe eligibility: visa sponsorship, W2, C2C not available), Qualifications (education, experience), Skills (the skills list), Pay. We must not create sections with filler. Ensure each heading has substantive content. We need to use

for each section heading. Use

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

  for prose. We need to decide what constitutes a list. The responsibilities are many sentences; could be turned into

  • . Similarly requirements (visa, W2, etc.) could be list. Qualifications could be list. Skills could be list. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep each piece of info. Let's extract each piece. About the role: "Prominent is helping our client find Manual Software Tester resources for their QA Team. Preference given to candidates currently within a reasonable commute to Omaha, Nebraska or Greenwood Village, Colorado; however, remote may be a possibility. As a Software Tester you will be responsible for ensuring the quality of products and services using Agile, Waterfall, DevOps with CI/CD in a fast-paced services environment." That's prose. Responsibilities: The block starting "Tasks Lead QA delivery team (onshore / offshore model), including strategy & operations, while directing testing and delivery of enterprise applications across multiple streams and portfolios according to the business requirements.Spearhead Test Strategy, Test Plans, Defect Management, Test Automation and Execution for various transaction types.Execute Test Planning and Automation for multiple strategic programs against well-defined milestones and business objectives. Proven experience in all aspects of SDLC & Agile - Scrum methodologies.Communicate and advise Senior Executive Leadership in matters of testing inclusive of statuses, health, risk, estimates, day-to-day operations, and long-term strategic roadmap.Have ability to provide expert solutions and testing recommendations.Provide recommendations for improvements in lower environments and infrastructure, data management including upgrades, integration, and architecture to meet the critical business needs.Participate in and contribute to project discussions including Requirements, Design discussions and weekly meetings.Define and track QA SLAs and Metrics to adhere to baseline quality standards. Robust QA process inclusive of Lessons Learned, Retrospective & Implementation of Resulting process improvement opportunities.Maintenance / tracking of QA KPIs, Metrics pertain to Quality (Total Defects, Defect Density, Defect per hour, Defect leakage), Automation (Coverage, Velocity, Failure Rate, Utilization rate, ROI, Script Creation effectiveness) and Time to Market (Defect turnaround, Defect retest turnaround time, Fix failure rate) with Root Cause assessments, Statistics and recommendations.Host automation demo sessions, test scope, test plan, test cases, test results walkthrough sessions with Business, Product owners, PMO, Tech Owners, Developers and Test teams and obtain approvals.Ensure that Service Delivery is in compliance with Fiserv Regulations and Policies, including Application Release Methodology.Mentoring, guiding, assisting QA team on the QA Best Practices, Strategy, Tools, and Testing techniques." We need to split into list items. Each sentence separated by period. We'll create
  • for each. Requirements (eligibility): "Candidates requiring visa sponsorship now or in the future are not eligible to apply for this opportunity. C2C or 1099 not available for this opportunity! Potential candidates will need to have the ability to work W2 on Prominents’ payroll." We could keep as list. Qualifications: "Minimum of a 4-year degree in Computer Science, Engineering, or other technical/analytical degrees. 4-7 years of related technical and business leadership experience with Quality Assurance and Testing discipline. 4-7 years of management in testing with large teams using various methodologies including Waterfall, Agile- Scrum and SDLC. Outstanding interpersonal and communication skills (oral, written, and interpersonal) including the ability to communicate technical concepts to a non-technical audience. Strong understanding in advancement of CI/CD or DevOps Testing Models with GitLab, Nexus, Harness, Tricentis Tosca (Automation Foundation), JIRA, Postman, SoapUI Ability to contribute and direct at all levels of testing including unit, functional, automation, performance, and scalability testing; be able to step in and provide leadership in test design and implementation. Proven experience in coordinating global teams for multiple portfolios. This includes, but not limited to, Daily Stand-ups, Estimations, Coverage, Test Strategy, Planning, Test Cases review, Defect triage, Statuses, Reporting, Test Results review & walkthrough sessions and represent the Corporate QA team during U.S. hours. Collaboration with Business, Development, and other testing teams. Should be a client focused individual adept with knowledge to execute programs of varying complexities and report “valuable” metrics along with key milestones, dependencies, risks, and issues." We could treat as list. Skills: "Skills: Experienced QA Test Lead" then list of skills: Actually the "Skills:" line then bullet list: "Experienced QA Test Lead Minimum of a 4-year degree..." Wait that seems overlapping with qualifications. Actually the text after "Skills:" includes many items that are more like qualifications. But we have already captured qualifications. The "Skills:" section maybe includes: "Experienced QA Test Lead Minimum of a 4-year degree in Computer Science, Engineering, or other technical/analytical degrees. 4-7 years of related technical and business leadership experience with Quality Assurance and Testing discipline. 4-7 years of management in testing with large teams using various methodologies including Waterfall, Agile- Scrum and SDLC. Outstanding interpersonal and communication skills (oral, written, and interpersonal) including the ability to communicate technical concepts to a non-technical audience. Strong understanding in advancement of CI/CD or DevOps Testing Models with GitLab, Nexus, Harness, Tricentis Tosca (Automation Foundation), JIRA, Postman, SoapUI Ability to contribute and direct at all levels of testing including unit, functional, automation, performance, and scalability testing; be able to step in and provide leadership in test design and implementation. Proven experience in coordinating global teams for multiple portfolios. This includes, but not limited to, Daily Stand-ups, Estimations, Coverage, Test Strategy, Planning, Test Cases review, Defect triage, Statuses, Reporting, Test Results review & walkthrough sessions and represent the Corporate QA team during U.S. hours. Collaboration with Business, Development, and other testing teams. Should be a client focused individual adept with knowledge to execute programs of varying complexities and report “valuable” metrics along with key milestones, dependencies, risks, and issues. Preferred skills: Knowledge of QTest, TOSCA, JENKINS, SPLUNK, Oracle 11g, Jira, Confluence, TOAD, Microsoft Office, SharePoint" Thus the "Skills:" section actually contains qualifications and preferred skills. To avoid duplication, we might treat the whole block after "Skills:" as Skills section, but we already used qualifications. However the instructions: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content appropriately. We have: - About the role: intro paragraph. - Responsibilities: the tasks list. - Requirements: visa sponsorship, W2, C2C not available. - Qualifications: education, years experience, interpersonal skills, etc. (the block after "Skills:"? Actually that block is labeled Skills but contains qualifications. However we can treat that as Qualifications. - Skills: the specific technical skills: "Strong understanding in advancement of CI/CD or DevOps Testing Models with GitLab, Nexus, Harness, Tricentis Tosca (Automation Foundation), JIRA, Postman, SoapUI" plus maybe "Ability to contribute and direct at all levels of testing..." but that's more ability. Also "Preferred skills: Knowledge of QTest, TOSCA, JENKINS, SPLUNK, Oracle 11g, Jira, Confluence, TOAD, Microsoft Office, SharePoint". So we can separate. But we must not lose any info. Let's parse the original text after "Skills:": "Skills: Experienced QA Test LeadMinimum of a 4-year degree in Computer Science, Engineering, or other technical/analytical degrees.4-7 years of