UAT Tester

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We need to parse the posting. We have: - Overview: "UAT Analyst (Digital Banking) Location: Honolulu, HI (Hybrid) 12-month Contract Opportunity Overview TEKsystems is partnering..." This is about the role. So we can have an "About the role" section with that overview. - Key Responsibilities: list bullet points. Should be under Responsibilities heading. - Online Banking Testing: details; could be part of Responsibilities or separate? The instruction: Use headings for sections like Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include subheadings? Not specified; only those headings. So we likely put all responsibilities under Responsibilities heading, possibly with sub-lists. - Online Account Opening Testing: also responsibilities. - Defect Management & Reporting: responsibilities. - Business & Project Collaboration: responsibilities. - Required Qualifications: that's qualifications. - Preferred Qualifications: could be under Qualifications or Skills? Probably Qualifications. - Why Apply?: could be under About the role? Or maybe a separate section like Benefits? But we have Benefits and Pay sections separate. Why Apply? is more like motivations; could be part of About the role. - Job Type & Location: location info; could be part of About the role or maybe Schedule? Not needed. - Pay And Benefits: includes pay range and benefits list. So we need Pay section (with pay range) and Benefits section (list of benefits). According to rules: include Pay and Benefits sections only if posting actually states them. Yes, they do. - Workplace Type: says fully remote position. That contradicts earlier Hybrid? But we need to include Schedule? Not present. Workplace Type maybe not a heading; we could include under About the role or maybe as a note. Not required. - Application Deadline: we should drop as per instruction: remove application instructions. So omit. - About TEKsystems etc: boilerplate, remove. Thus sections:

About the role

with overview paragraph.

Responsibilities

with

• items covering all responsibilities (including sub-items). Could nest? Probably just flat list.

  Qualifications

  with Required Qualifications and Preferred Qualifications combined? Could separate into Required and Preferred but headings only allow Qualifications. We can include both within that section, maybe using

  for required and

  for preferred, or list. We might also include

  Skills

  if there is specific skills content. The posting mentions proficiency with Microsoft Office Suite, ability to manage multiple priorities, etc. Could be under Skills. But we already have Qualifications covering those. To avoid thin sections, maybe combine into Qualifications only. However the instruction says prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Qualifications, Pay, Benefits. That's five sections. Pay section:

  Pay

  with paragraph stating pay range. Benefits section:

  Benefits

  with
  • list of benefits. We must not repeat job title as heading. Not include Job ID. We must not include placeholder text like "commensurate with experience". Not present. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from responsibilities, qualifications, pay, benefits. We must not include boilerplate like EEO, legal, etc. We must not include application instructions. We must not include duplicated lines. We need to ensure we include all bullet points from responsibilities. Let's extract responsibilities: Key Responsibilities: - User Acceptance Testing (UAT) * Execute UAT test scenarios and test cases for online banking and digital account opening platforms. * Validate functionality against business requirements, user stories, and acceptance criteria. * Conduct end-to-end testing of customer-facing digital banking processes. * Identify, document, and track defects through resolution. * Verify fixes and perform regression testing as needed. * Ensure testing activities are completed within established project timelines. - Online Banking Testing * Test And Validate Digital Banking Features Including - User registration and onboarding - Authentication and account access - Account balances and transaction history - Funds transfers - Bill pay functionality - Alerts and notifications - Mobile banking integrations - User profile and account maintenance functions * Evaluate overall customer experience and workflow usability. * Identify potential customer-impacting or operational issues before deployment. - Online Account Opening (OAO) Testing * Validate consumer and business account opening workflows. * Test disclosures, funding processes, and account setup functionality. * Verify integrations with internal and third-party systems. * Ensure compliance and business requirements are met throughout the account opening experience. * Validate data flow across connected platforms and downstream systems. - Defect Management & Reporting * Create detailed defect reports including: - Reproduction steps - Expected vs. actual results - Screenshots and testing evidence - Severity and priority assessments * Maintain test logs, defect trackers, and testing documentation. * Partner with development and technology teams to communicate and resolve issues. * Provide testing status updates and defect reporting throughout project execution. - Business & Project Collaboration * Participate in project meetings, requirements reviews, and testing planning sessions. * Work closely with Product Owners, Business Analysts, Operations teams, and Developers. * Support release readiness, implementation activities, and post-production validation efforts. * Contribute to UAT standards, procedures, templates, and best practices. We need to preserve all that. Could flatten into list items; but some are sub-bullets. We can keep nested
    inside
    • if needed. The instruction: Use
      • for any list of duties/requirements/benefits. It doesn't forbid nested lists. We'll do top-level
        for responsibilities, each major bullet as
        • , and inside we can have another
          for sub-items. Similarly for Qualifications: Required Qualifications: - Bachelor's degree in Business, Information Systems, Computer Science, Finance, or related field, or equivalent experience. - 2+ years of experience in: * User Acceptance Testing (UAT) * Quality Assurance * Business Analysis * Software Testing * Experience testing customer-facing applications or web-based platforms. - Strong understanding of: * Testing methodologies * Test case creation and execution * Defect management processes * Requirements validation * Experience documenting test results and defects. - Exceptional attention to detail and analytical problem-solving skills. - Strong verbal and written communication abilities. - Proficiency with Microsoft Office Suite (Excel, Word, PowerPoint, Teams). - Ability to manage multiple priorities in a fast-paced environment. Preferred Qualifications: - Banking, financial services, or fintech industry experience. - Experience testing: * Online Banking platforms * Mobile Banking applications * Online Account Opening (OAO) systems * Digital customer journeys - Familiarity with: * Jira * Azure DevOps * Quality Center * Other testing/defect tracking tools - Experience supporting: * System conversions * Integration projects * Digital transformation initiatives - Knowledge of Agile, Waterfall, or hybrid project methodologies. We can combine into Qualifications section with two sub-sections maybe using

          headings? But we cannot add extra headings besides the allowed ones. However we can use

          to label "Required Qualifications:" and "Preferred Qualifications:" inside the section. Similarly Benefits list: from posting: Benefits are subject to change and may be subject to specific elections, plan, or program terms. If eligible, the benefits available for this temporary role may include the following: - Medical, dental & vision - Critical Illness, Accident, and Hospital - 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available - Life Insurance (Voluntary Life & AD&D for the employee and dependents) - Short and long-term disability - Health Spending Account (HSA) - Transportation benefits - Employee Assistance Program - Time Off/Leave (PTO, Vacation or Sick Leave) We'll list those. Pay: The pay range for this position is $35.00 - $45.00/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors. Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. Benefits are subject to change and may be subject to specific elections, plan, or program terms. If eligible, the benefits available for this temporary role may include the following: ... (but we already have benefits). We'll keep pay paragraph with that info. We should not repeat benefits description in Pay section; just mention pay range and note that compensation depends on factors. Now About the role: Overview paragraph: "UAT Analyst (Digital Banking) Location: Honolulu, HI (Hybrid) 12-month Contract Opportunity Overview TEKsystems is partnering with a leading financial services organization seeking a detail-oriented UAT Analyst to support critical digital banking initiatives focused on Online Banking and Online Account Opening (OAO) platforms. This role will be responsible for planning, executing, documenting, and coordinating User Acceptance Testing (UAT) activities to ensure systems meet business requirements and deliver exceptional customer experiences. The ideal candidate will have experience testing customer-facing applications, documenting defects, collaborating with cross-functional stakeholders, and supporting large-scale technology initiatives." We should also include location and contract duration maybe. The overview includes location and hybrid and 12-month contract. We'll keep that. We must not include "Job Type & Location" separate; we can incorporate location in About the role. We must not include "Workplace Type" (fully remote) maybe contradictory; but we should include if it's substantive. It says "Workplace Type This is a fully remote position." That's a detail about workplace type. Should we include? It's substantive. Could be part of About the role or maybe a separate section like Schedule? Not exactly schedule. Since we don't have a heading for Workplace Type, we could include it in About the role as a note. But we already said Hybrid earlier; there is a conflict. The posting says Location: Honolulu, HI (Hybrid) then later Workplace Type: fully remote. Might be a mistake but we must preserve all substantive information. So we need to include both? We could mention that the role is hybrid based in Honolulu but also fully remote? That seems contradictory. Perhaps we should include both as stated: location Honolulu, HI (Hybrid) and also note that the workplace type is fully remote. We'll include both in About the role. Now About TEKsystems boilerplate: remove. Now ensure we don't include any application instructions like "Application Deadline", "How to apply", etc. Now produce HTML fragment:

          About the role

          ...

          Responsibilities

          • User Acceptance Testing (UAT)
            • Execute UAT test scenarios and test cases for online banking and digital account opening platforms.
            • Validate functionality against business requirements, user stories, and acceptance criteria.
            • Conduct end-to-end testing of customer-facing digital banking processes.
            • Identify, document, and track defects through resolution.
            • Verify fixes and perform regression testing as needed.
            • Ensure testing activities are completed within established project timelines.
          • Online Banking Testing
            • Test and validate digital banking features including:
            • User