Lead QA Automation Engineer

We need to output HTML fragment with headings

for sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must include sections only if posting has real specific content. Must use

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

  for prose. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "For information and details on employment benefits offered with this position, please visit here." etc. Also remove California Pay Equity etc. Also remove EOE statements, etc. We need to preserve all substantive information: date posted? Probably not needed as heading; but we can include as a short

  maybe. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can include date posted, hiring organization, position number maybe as a short paragraph. But we might drop them if not needed. However we need to preserve ALL substantive information; but minor metadata can be folded into a short

  or dropped. So we could include a short

  with date posted, hiring organization, location, work model, shift, employment type, estimated duration, hourly rate range. Those are substantive but not headings. Could be in a

  . However we need to decide sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections if posting has real specific content. Let's extract content: - Job Title: Lead QA Automation Engineer (but we don't repeat as heading) - Hiring Organization: Rose International - Position Number: 508257 (metadata) - Industry: Manufacturing - Job Location: Peoria, IL, USA, 61629 - Work Model: Onsite - Shift: M-F, 8 am - 4:30 pm - Employment Type: Temporary FT/PT: Full-Time - Estimated Duration (In months): 12 - Min Hourly Rate($): 55.00 - Max Hourly Rate($): 57.00 - Must Have Skills/Attributes: PowerBI, Quality Analyst, Regression Testing, SDLC, SQL, Test 3 (maybe "Test 3"? unclear) - Experience Described: Software Quality Assurance & Test Engineering (10+ yrs); QA Leadership & Agile Project Delivery (3+ yrs); Software Testing Methodologies (SDLC, Regression, Integration, UAT, Performance Testing)7+ (7+ yrs); Technical Tools (AWS, SQL, Azure DevOps (ADO), Power BI) (5+ yrs) - Required Minimum Education: Bachelor’s Degree - Job Description: includes paragraphs about role, typical task breakdown, responsibilities, etc. - Required Education/Experience: Bachelor's Degree in Computer Science or equivalent - Required Qualifications: "We are looking for a Lead QA Specialist..." repeated. - Typical Task Breakdown: list of duties. - What You Will Have: decision making, effective communications, software product testing, software development life cycle. - Required Technical Skills: Typically have 7+ years of experience in software test and/or software development; knowledge of SDLC, Agile, QA/QC; leadership/project management experience; knowledge of AWS, SQL, ADO, Power BI, Excel; strong analytical skills and data mining; excellent presentation skills. - Benefits: "For information and details on employment benefits offered with this position, please visit here." That's not specific; we should not create Benefits section because no real specific content. So we omit Benefits. - Pay: we have min and max hourly rate. That's specific. So we can include Pay section with that info. - Schedule: we have shift M-F, 8 am - 4:30 pm. That's specific. So we can include Schedule section. - About the role: we have description paragraphs. Could be About the role. - Responsibilities: we have typical task breakdown list. - Requirements: we have experience desired, required education, required qualifications, required technical skills. - Skills: maybe we can combine Must Have Skills/Attributes and Technical Tools into Skills section. - Qualifications: maybe we can have Qualifications section for education and experience. We need to avoid duplication. Let's structure:

  Date Posted: 09/28/2026

  Hiring Organization: Rose International

  Job Location: Peoria, IL, USA, 61629

  Work Model: Onsite

  Shift: M-F, 8 am - 4:30 pm

  Employment Type: Temporary Full-Time

  Estimated Duration: 12 months

  But maybe we can combine into one

  with semicolons. However instruction: "fold minor metadata into a short

  or drop it." So a short

  containing all metadata is fine. Then sections:

  About the role

  ... prose from job description ...

  Responsibilities

  • ... list items from typical task breakdown ...

  Requirements

  • ... list items from experience desired, required education, required qualifications, required technical skills ...
  Alternatively separate Qualifications and Skills sections. But we need to avoid thin sections. Could combine Requirements and Skills into one? But we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include Requirements and Skills separately if there is enough content. Let's extract: Experience Desired: - Software Quality Assurance & Test Engineering (10+ yrs) - QA Leadership & Agile Project Delivery (3+ yrs) - Software Testing Methodologies (SDLC, Regression, Integration, UAT, Performance Testing) (7+ yrs) - Technical Tools (AWS, SQL, Azure DevOps (ADO), Power BI) (5+ yrs) Required Minimum Education: Bachelor’s Degree Required Qualifications: (the paragraph about looking for Lead QA Specialist) but that's more about role. Required Technical Skills: - Typically have 7+ years of experience in software test and/or software development - Knowledge of SDLC, Agile, Quality Assurance and Quality Control methodologies - Leadership and/or project management experience in cross-functional high-paced environment - Knowledge of AWS, SQL, ADO, Power BI, and Excel - Strong analytical skills and data mining skills - Excellent presentation skills to different levels within organization Must Have Skills/Attributes: PowerBI, Quality Analyst, Regression Testing, SDLC, SQL, Test 3 (maybe "Test 3"? unclear). We'll include as skills. Thus Skills section could list: Power BI, Quality Analyst, Regression Testing, SDLC, SQL, Test 3, AWS, Azure DevOps, Excel, etc. Qualifications section could list education and experience desired. But we might have overlapping. To avoid duplication, we can have:

  Qualifications

  • Bachelor’s Degree in Computer Science or equivalent
  • 10+ years experience in Software Quality Assurance & Test Engineering
  • 3+ years experience in QA Leadership & Agile Project Delivery
  • 7+ years experience in Software Testing Methodologies (SDLC, Regression, Integration, UAT, Performance Testing)
  • 5+ years experience with Technical Tools (AWS, SQL, Azure DevOps, Power BI)

  Skills

  • Power BI
  • Quality Analyst
  • Regression Testing
  • SDLC
  • SQL
  • Test 3
  • AWS
  • Azure DevOps (ADO)
  • Excel
  • Strong analytical and data mining skills
  • Excellent presentation skills
  • Knowledge of Agile, QA/QC methodologies
  • Leadership/project management experience
  But some of these overlap with qualifications. Might be okay. Now Pay section: we have min and max hourly rate. So:

  Pay

  Hourly rate: $55.00 – $57.00

  Schedule section: we have shift.

  Schedule

  Monday–Friday, 8:00 am – 4:30 pm (Onsite)

  Now About the role: we need to capture the job description prose (not duplicated). Let's extract unique prose: From job description: "We are looking for a Lead QA Specialist to join our Quality Assurance team The quality assurance team is working with talented cross-functional engineering team that is building new platform utilizing cutting-edge technologies QA team is leading relentless pursuit of quality including defect management on multiple large-scale programs for the CLIENT Digital Platform." It repeats. We'll combine into a concise paragraph: "The Quality Assurance team works with a talented cross‑functional engineering team building a new platform using cutting‑edge technologies. The team leads relentless pursuit of quality, including defect management on multiple large‑scale programs for the client’s Digital Platform." Then "Typical Task Breakdown" is responsibilities. "What You Will Have" is maybe about competencies; could be part of About the role or separate? Could be included in About the role as bullet? But we have no heading for competencies. Could include in About the role as a list? But we already have Responsibilities and Requirements sections. The "What You Will Have" describes decision making, communication, software product testing, SDLC knowledge. Those are more like required competencies/skills. Could be placed under Skills or Requirements. But we already have Skills section covering technical skills; we could add those under Skills as well. Thus About the role paragraph can be the description of team and purpose. Now Responsibilities: list from Typical Task Breakdown: - Lead QA strategy, test planning, and automation execution across multiple projects and releases. - Works directly on complex application/technical problem identification and resolution. - Independently lead testing, project management, and quality assurance assignments without close supervision; normally assigned the more complex aspects of systems work. - Use your understanding of systems, regression, integration, performance, and user acceptance testing to identify gaps in system test. - Perform all validation activities of new and existing defects within software products. - Responsible for quality assurance and defect management activities. - Performs testing to reproduce defects and collect artifacts necessary for analysis and resolution. - Participate in field follow testing of features that require careful planning and execution to ensure timely quality results. - Communicate with end users and internal customers to help direct development, debugging, and testing of application software for accuracy, integrity, interoperability, and completeness. - Coordinate with product owner to resolve open issues/enhancements/upgrades and understand the use of a specific functionality as needed. - Identify high impact issues, drive them to resolution, perform root cause analysis, and assist leadership to make right decision through data and quantitative decision making. - Mentor QA team members and provide technical guidance on testing best practices, standards, and tools. We need to ensure each as
• . Now Requirements: maybe we combine education and experience desired? But we already have Qualifications and Skills sections. The instruction says we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide which to include. We have About the role, Responsibilities, Qualifications, Skills, Pay, Schedule. That's six sections. We could also include Requirements if we have content not covered elsewhere. But we might combine Requirements with Qualifications? However we already have Qualifications separate. Could we drop Requirements and keep Qualifications and Skills? The instruction: "Prefer a few substantive sections over many thin ones." So we can omit Requirements if its content is covered elsewhere. But we need to preserve all substantive information;