Quality Assurance IV

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. We need to parse the posting. Content: - Intro: "We are hiring a Quality Assurance IV for one of our clients in Phoenix, AZ." That's location and role. Could be part of About the role? Probably "About the role" section. - Job Description paragraph: describes role responsibilities. - Skills Required list: many items. - Experience Required: 7-10 years functional testing, 3 years automated testing. - Education Required: Bachelor's degree ... OR Experience: 5 years combined. - Work Hours: 8:00 am to 5:00 pm - Additional Information: background check, fingerprinting, start time 8 AM, assignment duration approx 6 months, potential to hire, USC/GC candidates only. - About Us: description of recruiting firm. - Consent to receive text/SMS. We need to decide sections. Possible sections: - About the role (intro + job description) - Responsibilities (maybe from job description) - Requirements (experience, education, work hours, additional info like background check, citizenship) - Skills (list of skills) - Benefits? Not mentioned. - Pay? Not mentioned. - Schedule? Work hours given (8am-5pm). That could be Schedule section. But we need to avoid filler. If we include Schedule, we have actual content: "Work Hours 8:00 am to 5:00 pm". That's specific. Also maybe "Assignment duration is approximately 6 months, with potential to hire." Could be part of About the role or Requirements? Could be under "Contract Details" but not a standard heading. We could incorporate into About the role or Responsibilities. We must not create sections with filler like "commensurate with experience". We have actual content for Skills, Requirements, About the role, Schedule. We need to use

for each section heading. Inside sections, use

for prose,

• for lists. We must not repeat job title as heading. So no

  Quality Assurance IV

  . We need to preserve all substantive information; do not invent or summarize away detail. Thus we need to include all details: location Phoenix, AZ; role description; responsibilities; skills list; experience required; education required; work hours; additional info (background check, fingerprinting, start time, assignment duration, potential to hire, USC/GC only); About Us description; consent to receive text/SMS. We need to decide where each piece goes. Let's outline:

  About the role

  We are hiring a Quality Assurance IV for one of our clients in Phoenix, AZ. The Senior Quality Assurance Analyst / Automation Engineer provides the strategic mind and technical means for testing all aspects of a software solution, balancing both deep functional analysis and robust technical automation. In this hybrid role, you will be a key driver on a team responsible for both functional testing and expanding the automation infrastructure of our state-of-the-art web-based judicial case management system. This is an exciting opportunity for a professional who loves diving into business requirements, designing thorough test cases, and translating them into code. You will plug directly into a well-established automation framework utilizing the latest Selenium WebDriver, delivering continuous automated testing and reporting throughout the development cycle.

  That covers intro and job description.

  Responsibilities

  We could list responsibilities from the description: performing functional testing, black box testing, manual exploratory testing, writing/maintaining automated UI scripts, creating test plans, translating requirements into test cases, building/maintaining POM-based automation frameworks, writing SQL queries, utilizing XPath, using Azure DevOps/GitHub/Git/Visual Studio, communicating, acting as analytical gatekeeper and technical automation developer, working with minimal supervision, creating test plans, articulating measures, performing dual-role execution, AI-driven testing, test design, automation engineering, defect & data tracking, framework analysis, collaboration. We could put as
  • items. But we must not invent or summarize away detail; we need to preserve all substantive information. So we need to include each responsibility mentioned. Let's extract responsibilities sentences: - Act as both the analytical gatekeeper of business logic and the technical automation developer on a project. - Work efficiently with minimal supervision as a highly motivated self-starter. - Create comprehensive test plans and articulate successful measures for evaluating software. - Dual-Role Execution: Actively perform hands-on functional testing, black box testing, and manual exploratory testing while simultaneously writing and maintaining automated UI scripts for the same feature sets. - AI-Driven Testing: Leverage AI utilities, including GitHub Copilot, Modern Requirements, and Copilot for DevOps, to accelerate the development of test scenarios, test case documentation, and automated script execution. - Test Design: Translate complex business and functional requirements into highly structured, reusable test cases in Azure DevOps, maintaining a rigorous regression suite. - Automation Engineering: Utilize Selenium WebDriver and/or Playwright to create, execute, and maintain smoke and regression tests. - Defect & Data Tracking: Articulate defects with concise, technical steps enabling development teams to rapidly reproduce a condition. - Framework Analysis: Interpret daily automated test reports to isolate application defects versus script maintenance issues. - Collaboration: Partner with developers, fellow testers, and business stakeholders to ensure complete test coverage (positive/negative, cross-browser, integration) and meet strict sprint deadlines. Also earlier: "balancing both deep functional analysis and robust technical automation." "provides the strategic mind and technical means for testing all aspects of a software solution". "You will plug directly into a well-established automation framework utilizing the latest Selenium WebDriver, delivering continuous automated testing and reporting throughout the development cycle." That's more description. We could incorporate those into responsibilities as well. But we need to avoid duplication. We'll include all unique items. Now Skills Required list: - Advanced Functional Testing - Black Box Testing - Integration Testing - System Testing - ADA Testing (WCAG) - User Acceptance Testing (UAT) - UI Testing and Automated Testing strategies. - Web Service testing (SOAP/REST/JSON) - Agile development lifecycle (Scrum/Agile) - Balancing hands-on Functional Testing with Automated UI Testing seamlessly on a single project cycle. - Advanced test case design, requirements traceability matrices, and translating complex business rules into structured test scenarios. - Building and maintaining POM-based automation frameworks using Selenium WebDriver, Playwright, and C#/Java. - Writing SQL queries for data verification and back-end testing. - Utilizing relative XPath language/expressions and object-oriented design principles. - Azure DevOps, GitHub, Git, and source control using Visual Studio 2022 or above. - Effective verbal and written communication with all levels of the organization. We could list as
    • . Experience Required: - 7-10 years in functional testing - 3 years in automated testing Education Required: - Bachelor's degree in information technology, Computer Science, Business, or a related field. - OR Experience: Five (5) years of combined experience in both software functional analysis/testing and test automation engineering Work Hours: - 8:00 am to 5:00 pm Additional Information: - JBAZMC will conduct background check and fingerprinting. - Start time is 8 AM. - Assignment duration is approximately 6 months, with potential to hire. - USC/GC candidates only. About Us: - We are specialized in recruiting and deliver the best professional talent of industry and we are committed to deliver best experience for our clients and job seekers. - With over two decades of experience in the recruitment industry, we proudly help you to find the next job that matches your professional skills. - Our team understands your needs or requirement before starting the recruitment, that enables to find the high quality of talent with high success rate of talent delivery, keeps us continue to be the best in the industry. - By responding to this job posting, you are consenting to receive text/SMS messages from us. We need to decide sections: About the role, Responsibilities, Requirements (maybe combine experience, education, work hours, additional info), Skills, Schedule (work hours), maybe About Us? Not a standard heading but could be "About the company". However the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should stick to those. About Us could go under "About the role" or maybe omitted? But we must preserve ALL substantive information. So we need to include About Us somewhere. Could be under "About the role" as a paragraph about the company. Or we could create a section "About the company" but not in allowed headings. The instruction says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, not exclusive? It says "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It might be okay to use other headings if needed, but they gave examples. Safer to stick to those headings. We can put About Us under "About the role" or maybe under "Requirements"? Not ideal. Could add a section "About the company" but risk being considered not following instruction. However instruction says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests using those. I'd include About Us under "About the role" as a paragraph. Similarly, consent to receive text/SMS could be included in About the role paragraph. Now we need to avoid filler like "commensurate with experience". Not present. Now we need to ensure we don't create Pay/Benefits sections unless posting actually states them. Not present, so omit. Schedule: we have work hours, so we can include Schedule section with that. Now we need to output only HTML fragment, no /, no markdown. Let's craft. Structure:

      About the role

      ... (including location, role description, About Us, consent)

      Responsibilities

      • ...
      ...

      Requirements

      Maybe split into Experience, Education, Work Hours, Additional Info? Could be separate subheadings but we only have

      . Could use

      paragraphs inside Requirements. We could do:

      Requirements

      Experience: 7-10 years in functional testing; 3 years in automated testing.

      Education: Bachelor's degree in information technology, Computer Science, Business, or a related field. OR Experience: Five (5) years of combined experience in both software functional analysis/testing and test automation engineering.

      Work Hours: 8:00 am to 5:00 pm.

      Additional Information: JBAZMC will conduct background check and fingerprinting. Start time is 8 AM. Assignment duration is approximately 6 months, with potential to hire. USC/GC candidates only.

      That preserves details.

      Skills

      • Advanced Functional Testing
      • Black Box Testing
      • Integration Testing
      • System Testing
      • ADA Testing (WCAG)
      • User Acceptance Testing (UAT)
      • UI Testing and Automated Testing strategies
      • Web Service testing (SOAP/REST/JSON)
      • Agile development lifecycle (Scrum/Agile)
      • Balancing hands-on Functional Testing with Automated UI Testing seamlessly on a single project cycle