Senior Systems Quality Assurance Analyst

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 remove boilerplate like EEO, legal, etc. Must preserve all substantive info. We need to parse the posting. Content: - About this role: description: "Wells Fargo is seeking a Systems Quality Assurance for our Consumer Lending and retail services position. In this role you will be responsible for automated testing, plan code and report automation testing as well as improve automation coverage in the overall testing plan. Wells Fargo is committed to serving our customers with dedication and integrity- a reflection of the trust they place on us every day. To continue earning that trust, we are looking for talented individuals who are passionate about putting customers at the center of everything we do- and who to thrive in an environment where everyone feels valued and inspired. We’re also deeply committed to supporting our employees’ career aspirations and growth. In recognition of that commitment, Wells Fargo once again ranked in the top five on the 2026 Linked Top Companies list of best workplaces “ to grow your career” in the U.S." That's about the role. - Then "In this role, you will:" list of responsibilities (many bullet-like sentences). Those are responsibilities. - Then "Required Qualifications:" line: "4+ years of Systems Quality Assurance experience, or equivalent demonstrated through one or a combination of the following: work experience, training, military experience, education" - Then "Desired Qualifications:" a long list. - Then "Job Expectations:" includes hybrid schedule, must reside within commutable distance, not eligible for Visa sponsorship, not eligible for Relocation, Posting End Date: 28 Sep 2026 *Job posting may come down early due to volume of applicants. We need to decide sections: About the role (we have content). Responsibilities (we have list). Requirements (maybe combine Required Qualifications? The spec says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map. We have Required Qualifications and Desired Qualifications. Could treat Required Qualifications as "Requirements". Desired Qualifications could be "Qualifications" or "Skills". The spec says we can have both Requirements and Qualifications sections. Likely "Requirements" for mandatory, "Qualifications" for desired/preferred. Skills could be extracted from desired qualifications (like experience with Agile, Jira, AI, etc). But we must not invent sections if content is thin. We have plenty of desired qualifications; we could put them under "Qualifications". Skills maybe we could extract specific skills like "Agile, Scrum, Kanban, Jira, Confluence, AI tools". But we need to avoid filler. Could create a Skills section listing those. Benefits: Not mentioned explicitly. No benefits info. So we should not create Benefits section. Pay: Not mentioned. So no Pay. Schedule: We have hybrid schedule: at least 3 days in office. That's schedule info. So we can create Schedule section with that detail. Also Job Expectations includes not eligible for Visa sponsorship, relocation, posting end date. Those could be considered metadata; we could fold into a short

maybe under About the role or separate? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a short paragraph for those expectations (like hybrid schedule, location, visa, relocation, posting end date). But we already have schedule section; we could put other expectations in a short

under About the role or maybe a separate "Job Expectations" but not a heading per spec. Since spec only allows those headings, we should not create a Job Expectations heading. So we can incorporate those details into a short

after About the role or within Schedule? Probably better to have a short

after About the role containing: "This position offers a hybrid work schedule with at least 3 days in the office; must reside within a commutable distance of the posted work location; not eligible for Visa sponsorship; not eligible for relocation; posting end date: 28 Sep 2026 (may come down early)." That's minor metadata. Now we need to preserve all substantive information. Let's extract responsibilities list: From "In this role, you will:" bullet points: - Plan, code, implement and report automation testing and improve automation coverage in the overall testing plan - Perform manual and automated testing - Document test cases and create test plans - Record test progress and results - Identify and track issues throughout testing - Consult with users providing advice and direction - Develop standards and procedures to determine product quality and release readiness - Drive innovation and streamline overall testing processes - Research system features being tested - Partner with Engineers to develop testing strategy - Log, track, and verify resolution of software and specification defects - Understand and ensure compliance and risk management requirements for supported area are met and work with other stakeholders to implement key risk initiatives - Collaborate and consult with peers, colleagues, and mid-level managers to resolve issues and achieve goals - Lead projects, teams or serve as a mentor for less experienced staff We need to put these in

• . Now Required Qualifications: "4+ years of Systems Quality Assurance experience, or equivalent demonstrated through one or a combination of the following: work experience, training, military experience, education" We can put that as a

  under Requirements heading. Desired Qualifications: a long list. Let's parse: - 4+ years of being test engineer, tester with at least 3+ years’ experience automating functional testing and/or developing automated test suite - Demonstrated ability to independently manage moderately complex work - Experience with Agile or product-driven environment - Experience working within Agile frameworks and tools including Scrum, Kanban, Jira, Confluence, and related product management platforms - Experience working directly with business issues, applications, and product owners - Experience identifying opportunities to improve efficiency, quality, scalability, and operational effectiveness through technology-enabled solutions - Experience establishing scalable and repeatable processes that improve delivery execution, team effectiveness, and customer experience - Experience using AI to bring in efficiency within functional and regression testing - Demonstrate foundational AI literacy by effectively using approved AI tools to support everyday work - Exercise sound judgment when interpreting and using AI‑generated outputs - Understand basic AI limitations and appropriate use cases within daily workflows - Use AI ethically and responsibly, in alignment with company policies and guidelines - Demonstrated success driving measurable operational improvements through workforce optimization technologies and process enhancements We could put these under Qualifications heading as a

  • . Or we could split into Skills and Qualifications. Since we have both headings allowed, we could put the more generic experience under Qualifications, and specific technical skills under Skills. But we need to avoid filler. Let's decide: Qualifications: maybe the desired qualifications list (the experience/abilities). Skills: maybe the specific tools/frameworks: Agile, Scrum, Kanban, Jira, Confluence, AI tools, etc. However the spec says "Prefer a few substantive sections over many thin ones." So maybe better to have just Qualifications section containing all desired qualifications, and not create Skills unless we have distinct skill list. But we have skills mentioned; we could still include them under Qualifications as part of list. Thus we will have sections: About the role (

    ), Responsibilities (

    ), Requirements (

    for required qualifications), Qualifications (

    for desired qualifications), Schedule (

    for hybrid schedule info). We'll also include a short

    for other job expectations (location, visa, relocation, posting end date) maybe after About the role or within Schedule? Since schedule section is for schedule info, we could put other expectations in a separate

    after About the role but before Responsibilities. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. So we can add a short

    after About the role containing those details. Thus final HTML:

    About the role

    Wells Fargo is seeking a Systems Quality Assurance for our Consumer Lending and retail services position. In this role you will be responsible for automated testing, plan code and report automation testing as well as improve automation coverage in the overall testing plan. Wells Fargo is committed to serving our customers with dedication and integrity- a reflection of the trust they place on us every day. To continue earning that trust, we are looking for talented individuals who are passionate about putting customers at the center of everything we do- and who to thrive in an environment where everyone feels valued and inspired. We’re also deeply committed to supporting our employees’ career aspirations and growth. In recognition of that commitment, Wells Fargo once again ranked in the top five on the 2026 Linked Top Companies list of best workplaces “ to grow your career” in the U.S.

    This position offers a hybrid work schedule with at least 3 days in the office; must reside within a commutable distance of the posted work location; not eligible for Visa sponsorship; not eligible for relocation; posting end date: 28 Sep 2026 (may come down early).

    Responsibilities

    • Plan, code, implement and report automation testing and improve automation coverage in the overall testing plan
    • Perform manual and automated testing
    • Document test cases and create test plans
    • Record test progress and results
    • Identify and track issues throughout testing
    • Consult with users providing advice and direction
    • Develop standards and procedures to determine product quality and release readiness
    • Drive innovation and streamline overall testing processes
    • Research system features being tested
    • Partner with Engineers to develop testing strategy
    • Log, track, and verify resolution of software and specification defects
    • Understand and ensure compliance and risk management requirements for supported area are met and work with other stakeholders to implement key risk initiatives
    • Collaborate and consult with peers, colleagues, and mid-level managers to resolve issues and achieve goals
    • Lead projects, teams or serve as a mentor for less experienced staff

    Requirements

    4+ years of Systems Quality Assurance experience, or equivalent demonstrated through one or a combination of the following: work experience, training, military experience, education

    Qualifications

    • 4+ years of being test engineer, tester with at least 3+ years’ experience automating functional testing and/or developing automated test suite
    • Demonstrated ability to independently manage moderately complex work
    • Experience with Agile or product-driven environment
    • Experience working within Agile frameworks and tools including Scrum, Kanban, Jira, Confluence, and related product management platforms
    • Experience working directly with business issues, applications, and product owners
    • Experience identifying opportunities to improve efficiency, quality, scalability, and operational effectiveness through technology-enabled solutions
    • Experience establishing scalable and repeatable processes that improve delivery execution, team effectiveness, and customer experience
    • Experience using AI to bring in efficiency within functional and regression testing
    • Demonstrate foundational AI literacy by effectively using approved AI tools to support everyday work
    • Exercise sound judgment when interpreting and using AI‑generated outputs
    • Understand basic AI limitations and appropriate use cases within daily workflows
    • Use AI ethically and responsibly, in alignment with company policies and guidelines
    • Demonstrated success driving measurable operational improvements through workforce optimization technologies and process enhancements

    Schedule

    Hybrid work schedule with at