Quality Assurance Specialist 3(QAS3)

We need to output HTML fragment with sections for headings present: About the role? The posting has "Position Overview". That's a heading. Also "What You Will Be Doing" with sub-sections. "What’s Needed". "Compensation & Benefits". Also maybe "About Unicon". According to rules: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to those headings. We should not repeat job title. We need to include sections only when posting has real specific content. So we can have: -

Position Overview

maybe map to "About the role"? But they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we can still use other headings? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples; we can use other headings as needed but likely they expect those standard headings. However we have content like Position Overview, What You Will Be Doing (which includes responsibilities), What’s Needed (requirements/qualifications/skills), Compensation & Benefits, About Unicon (company info). We should map to appropriate headings: About the role (position overview), Responsibilities (what you will be doing), Requirements (what's needed), Qualifications (maybe part of what's needed), Skills (maybe part), Benefits (compensation & benefits). Pay: they gave compensation range $85-90k, so we need a Pay section. Schedule: not mentioned, so omit. We must not include boilerplate like EEO etc. Remove duplicated lines. We need to preserve all substantive information. So we need to include details from each section. Let's extract: Position Overview paragraph: "The QA Lead will plan, coordinate, govern, and report the end-to-end testing effort for enterprise applications and integrations. The role must bridge business requirements and technical validation, supervise other testers, ensure measurable requirements traceability, and provide management with clear release-readiness information. The QA Lead must also be capable of reviewing and writing automation code when needed." What You Will Be Doing: includes sub-bullets but not actual bullet list; it's paragraphs with bold headings. We need to convert to

• for any list of duties/requirements/benefits. The content includes headings like Test Leadership and Governance, Requirements Analysis and Coverage, Azure DevOps Test Plans, Test Design and Execution, Defect and Release Management. Under each there are sentences. We could treat each heading as a list item? Or we could keep as prose? The rule: Use
  • for any list of duties/requirements/benefits. The duties are enumerated via headings; we could make each heading a list item with its description as subtext? Probably better to make each duty as a
  • containing the description. We'll need to parse. Let's list duties: - Test Leadership and Governance: Act as Test Lead for assigned programs, releases, modules, and production-readiness efforts. Develop the overall test strategy, scope, entry/exit criteria, estimates, schedules, dependencies, and execution plan. Assign and supervise testing work, review test artifacts, mentor testers, and enforce QA standards. Coordinate with Business Analysts, Developers, Product Owners, Project Managers, DevOps, DBAs, and business stakeholders. - Requirements Analysis and Coverage Review: Review BRDs, Functional Requirements (FRs), user stories, acceptance criteria, workflow diagrams, interface specifications, data mappings, and API specifications. Identify missing, ambiguous, conflicting, or untestable requirements before execution begins. Translate requirements into Test Scenarios (TS), Test Cases (TC), test data, preconditions, expected results, and automation candidates. Drive complete, measurable traceability from requirements to executed tests and defects. - Azure DevOps Test Plans: Create and maintain Test Plans, Test Suites, Test Cases, configurations, test runs, evidence, and defect links in Azure DevOps (ADO). Establish consistent work-item relationships among BRDs/FRs, TSs, TCs, executions, defects, retests, and closure. Use ADO queries and dashboards to communicate progress, blockers, defects, coverage, and release readiness. - Test Design and Execution: Create and review Positive, Negative, Boundary Value, Equivalence Partitioning, Decision Table, State Transition, Role/Authorization, Data-Driven, and Risk-Based tests. Coordinate and participate in Smoke, Functional, API, Integration, System, Regression, End-to-End, UAT, Performance-support, Database, and Data Pipeline testing. Ensure failures are reproducible, evidence is complete, and test results are defensible. - Defect and Release Management: Lead or participate in defect triage and severity/priority decisions. Ensure defects contain environment/build information, reproducible steps, expected/actual results, evidence, and requirement/test links. Provide evidence-based release recommendations and clearly communicate residual quality risk. Now What’s Needed (requirements): List: - QA/testing experience in enterprise software environments - Required 7 Years QA Lead, Test Lead, or senior QA role with formal leadership responsibility. - Required 2 Years Extensive hands-on Playwright or Selenium automation experience; Playwright + TypeScript strongly preferred - Required Strong BRD/FR analysis, RTM design, requirements traceability, and coverage-management experience. - Required Strong API testing and SQL/database validation experience. - Required Experience supervising testers, reviewing test artifacts, leading defect triage, and reporting to management. - Required Experience with Git, code review, CI/CD, and modern software delivery practices. - Required Playwright + TypeScript framework design and migration experience from Selenium. - Highly desired Experience creating reusable fixtures, Experience with reusable fixtures, APIes, Page Objects, API clients, test-data factories, and custom reporting. (some duplication) - Highly desired Performance-testing exposure and ability to coordinate specialized performance or security testing. - Highly desired Bachelor's degree in Computer Science, Information Systems, Engineering, or equivalent professional experience - Highly desired Data pipeline / ETL validation experience. - Required Compensation & Benefits (actually this is a separate section) But note "Required Compensation & Benefits" appears under What’s Needed? Actually after the list there is "Required Compensation & Benefits Medical, dental, and vision insurance 401(k) Other standard benefits as applicable". That seems misplaced; but we will treat compensation & benefits as its own section. We need to extract compensation: "$85-90k Onsite". Also mention "Onsite interviews Columbus, Ohio 43215". That's location info. We need to include Pay section with compensation range. Benefits: Medical, dental, and vision insurance, 401(k), Other standard benefits as applicable. Schedule: not given, omit. About Unicon: description. We must not include boilerplate like EEO etc. Remove duplicated lines. Now produce HTML fragment with

    headings for each section we include: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly also About Unicon? Not in list but could be "About the company". But not required. Might be okay to include as a section but not in examples. Safer to include only those headings that have content. We have content for About the role (position overview), Responsibilities (what you will be doing), Requirements (what's needed), Qualifications (maybe overlapping), Skills (maybe overlapping), Benefits, Pay. We could combine Qualifications and Skills into Requirements? But rule: prefer few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements (which includes qualifications and skills), Benefits, Pay. That's 5 sections. Let's map: - About the role: Position Overview paragraph. - Responsibilities: list of duties (the five headings each as

    with description). - Requirements: combine the "What’s Needed" items (excluding compensation & benefits). We'll list each as

    . - Benefits: Medical, dental, and vision insurance; 401(k); Other standard benefits as applicable. - Pay: Compensation range $85-90k (onsite). Also maybe mention location? Location is not pay. Could include location in About the role? But we already have location in job posting; we could include location in About the role paragraph? Might be okay to add a short

    for location and work model? But rule: do not put Job ID/requisition numbers as headings — fold minor metadata into a short

    or drop it. So we can include a short

    for location and work model maybe under About the role or separate? Probably better to include a short

    after the overview: "Location: Columbus, OH (Onsite)". That's minor metadata. We must not repeat job title. Now produce HTML. We'll need to escape any special characters? Not needed. Let's craft:

    About the role

    The QA Lead will plan, coordinate, govern, and report the end-to-end testing effort for enterprise applications and integrations. The role must bridge business requirements and technical validation, supervise other testers, ensure measurable requirements traceability, and provide management with clear release-readiness information. The QA Lead must also be capable of reviewing and writing automation code when needed.

    Location: Columbus, OH (Onsite)

    Responsibilities

    • Test Leadership and Governance – Act as Test Lead for assigned programs, releases, modules, and production-readiness efforts. Develop the overall test strategy, scope, entry/exit criteria, estimates, schedules, dependencies, and execution plan. Assign and supervise testing work, review test artifacts, mentor testers, and enforce QA standards. Coordinate with Business Analysts, Developers, Product Owners, Project Managers, DevOps, DBAs, and business stakeholders.
    • Requirements Analysis and Coverage Review – Review BRDs, Functional Requirements (FRs), user stories, acceptance criteria, workflow diagrams, interface specifications, data mappings, and API specifications. Identify missing, ambiguous, conflicting, or untestable requirements before execution begins. Translate requirements into Test Scenarios (TS), Test Cases (TC), test data, preconditions, expected results, and automation candidates. Drive complete, measurable traceability from requirements to executed tests and defects.
    • Azure DevOps Test Plans – Create and maintain Test Plans, Test Suites, Test Cases, configurations, test runs, evidence, and defect links in Azure DevOps (ADO). Establish consistent work-item relationships among BRDs/FRs, TSs, TCs, executions, defects, retests, and closure. Use ADO queries and dashboards to communicate progress, blockers, defects, coverage, and release readiness.
    • Test Design and Execution – Create and review Positive, Negative, Boundary Value, Equivalence Partitioning, Decision Table, State Transition, Role/Authorization, Data-Driven, and Risk-Based tests. Coordinate and participate in Smoke, Functional, API, Integration, System, Regression, End-to-End, UAT, Performance-support, Database, and Data Pipeline testing. Ensure failures are reproducible, evidence is complete, and test results are defensible.
    • Defect and Release Management – Lead or participate in defect triage and severity/priority decisions. Ensure defects contain environment/build information, reproducible steps, expected/actual results, evidence, and requirement/test links. Provide evidence-based release recommendations and clearly communicate residual quality risk.

    Requirements

    • QA/testing experience in enterprise software environments
    • 7 years QA Lead, Test Lead, or senior QA role with formal leadership responsibility
    • 2 years extensive hands‑on Playwright or Selenium automation experience;