Senior Quality Analyst (1153620)
for each section heading. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to parse the posting.
Key info:
Location: LOS ANGELES, CA, USA (but also says Remote (U.S.-Based)). So location: Remote (U.S.-Based). Salary: $80,000 - $90,000 annually. Also says Compensation: Up to $90,000 annually, depending on experience and qualifications, plus a comprehensive benefits package.
Employment Type: Full-Time.
About The Opportunity: description.
Position Overview: description.
What You'll Do: includes QA & Testing bullet list and Leadership & Team Contribution bullet list.
Required Qualifications: list.
Preferred Qualifications: list.
Education: Bachelor's degree...
Why Join Us?: bullet list.
Career Growth Opportunities: description.
Also there is a consent text about phone number etc. That's boilerplate/application instructions? It says "By providing your phone number, you consent..." That's likely application instructions/boilerplate; we should remove.
Contact email etc also likely boilerplate; remove.
We need to decide sections.
We have:
- About the role (maybe combine About The Opportunity and Position Overview). Could be "About the role" heading.
- Responsibilities: from "What You'll Do" (two subcategories). Could be combined.
- Requirements: maybe "Required Qualifications" as Requirements.
- Qualifications: maybe "Preferred Qualifications" as Qualifications? Or we could combine Required and Preferred under Requirements and Qualifications? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly.
We have:
- About the role: description of organization, opportunity.
- Responsibilities: QA & Testing and Leadership & Team Contribution.
- Requirements: Required Qualifications.
- Qualifications: Preferred Qualifications? Or maybe Skills: list of skills? Could treat Required Qualifications as Requirements, Preferred Qualifications as Qualifications, and maybe Skills as something else? But we have no explicit skills list besides those in qualifications. Could combine.
- Benefits: "comprehensive benefits package" mentioned, plus "Why Join Us?" includes benefits like work with brands, collaborative team, exposure, career growth, culture. Those are more like benefits. So we can create Benefits section with those bullet points.
- Pay: Salary range: $80,000 - $90,000 annually, up to $90,000 depending on experience. So we have pay info.
- Schedule: Employment Type: Full-Time. Could be schedule.
Thus we will include sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule.
We must not include sections with placeholder/filler. All have content.
We must not repeat job title as heading.
We must not include Job ID etc.
We must output only HTML fragment, no /, no markdown.
We need to use
for each section heading.
Inside sections, use
for prose,
- for lists.
We need to preserve all substantive information. Let's extract.
About the role: From "About The Opportunity Join a highly respected digital experience organization that partners with globally recognized brands across industries including hospitality, financial services, travel, luxury, and consumer products. This is an opportunity to work on high-visibility, customer-facing digital products within a collaborative Agile environment. You'll enjoy the agility and close-knit culture of a mid-sized team while benefiting from the resources and stability of a larger global enterprise. The organization is committed to innovation, quality, continuous improvement, and professional growth."
Also Position Overview: "We are seeking a Senior Quality Assurance Analyst to play a key role in ensuring the quality, reliability, and performance of modern digital applications. This individual will contribute throughout the software development lifecycle, partnering closely with product managers, developers, and stakeholders to deliver exceptional user experiences. The ideal candidate has strong manual testing expertise, experience working in Agile environments, and a passion for improving software quality through best practices, mentorship, and process improvement."
We can combine these into About the role prose.
Responsibilities: Two sub-sections: QA & Testing and Leadership & Team Contribution. We can combine into a single list or keep subheadings? The instruction says use
for section headings only; we could still use for subheadings? Not specified; better to keep as a single list with items. But we need to preserve all detail; we can keep bullet points as they are.
List items:
- Develop test cases and test scripts based on business requirements, user stories, and acceptance criteria.
- Execute manual testing across multiple phases of the development lifecycle.
- Perform functional, regression, and feature validation testing.
- Identify, document, and track defects through resolution.
- Evaluate defect severity and provide detailed reproduction steps.
- Maintain and enhance existing test case repositories.
- Collaborate with development and product teams to ensure quality standards are met.
- Participate in project status reporting and quality reviews.
- Lead QA efforts within Agile teams and project discussions.
- Mentor and support junior QA team members.
- Contribute to process improvements that enhance quality and team productivity.
- Assist with effort estimation, risk assessments, and resource planning.
- Help create onboarding materials, documentation, and knowledge-sharing sessions.
- Promote QA best practices across the organization.
- Participate in interviewing and evaluating new team members.
That's all.
Requirements (Required Qualifications): list:
- 3+ years of professional experience in software quality assurance and testing.
- Strong understanding of software testing methodologies and best practices.
- Experience working in Agile development environments.
- Proficiency with Jira or similar project and defect tracking tools.
- Experience using test management tools such as Zephyr.
- Solid understanding of the Software Development Life Cycle (SDLC), release processes, and testing environments.
- Strong analytical and problem-solving skills.
- Excellent communication and collaboration abilities.
- Exceptional attention to detail and organizational skills.
Qualifications (Preferred Qualifications): list:
- ISTQB Foundation Level Certification.
- Experience with accessibility testing.
- Experience with non-functional testing.
- Passion for continuous learning and staying current with emerging technologies and testing practices.
Education: Bachelor's degree in Computer Science, Software Engineering, Information Technology, or equivalent professional experience. This could be part of Requirements or Qualifications? Could be separate but we have no heading for Education. Could include under Requirements as part of list. But we already have Required Qualifications list; we could add Education as an item there. However the instruction says we must preserve ALL substantive information; we can add it under Requirements as an item.
Alternatively we could create a separate section "Education" but not in allowed headings list. The allowed headings are limited to those; we should not create extra headings. So we should fold Education into Requirements or Qualifications. Probably Requirements.
Thus Requirements list will include the education item.
Benefits: From "Why Join Us?" plus "comprehensive benefits package". Also "Career Growth Opportunities" maybe part of benefits. Let's extract:
Why Join Us? bullet list:
- Work with globally recognized brands on impactful digital experiences.
- Collaborative and supportive team environment.
- Exposure to a wide variety of technologies and projects.
- Opportunities for career growth and advancement.
- Strong culture focused on quality, innovation, and continuous improvement.
Career Growth Opportunities: "This Role Offers Multiple Advancement Paths, Including Quality Assurance Lead (Leadership Track) Test Engineer (Automation & Technical Track)". That's also a benefit.
Also "comprehensive benefits package" mentioned earlier.
Thus Benefits section bullet list:
- Work with globally recognized brands on impactful digital experiences.
- Collaborative and supportive team environment.
- Exposure to a wide variety of technologies and projects.
- Opportunities for career growth and advancement.
- Strong culture focused on quality, innovation, and continuous improvement.
- Career advancement paths: Quality Assurance Lead (Leadership Track) or Test Engineer (Automation & Technical Track).
- Comprehensive benefits package (health, retirement, etc.) – but we only have phrase "comprehensive benefits package". We'll keep that as is.
Pay: Salary range: $80,000.00 USD Annually - $90,000.00 USD Annually. Also Compensation: Up to $90,000 annually, depending on experience and qualifications, plus a comprehensive benefits package. We'll include both.
Thus Pay section: maybe a paragraph: "Salary range: $80,000 – $90,000 per year (up to $90,000 depending on experience and qualifications). Includes a comprehensive benefits package."
Schedule: Employment Type: Full-Time. So schedule: Full-Time.
Thus Schedule section: paragraph: "Full-time position."
Now we need to output HTML.
Structure:
About the role
...combined prose...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
Benefits
- ...
...
Pay
...
Schedule
...
Make sure no extra whitespace? It's fine.
Now craft prose for About the role.
Combine:
"Join a highly respected digital experience organization that partners with globally recognized brands across industries including hospitality, financial services, travel, luxury, and consumer products. This is an opportunity to work on high-visibility, customer-facing digital products within a collaborative Agile environment. You'll enjoy the agility and close-knit culture of a mid-sized team while benefiting from the resources and stability of a larger global enterprise. The organization is committed to innovation, quality, continuous improvement, and professional growth. We are seeking a Senior Quality Assurance Analyst to play a key role in ensuring the quality, reliability, and performance of modern digital applications. This individual will contribute throughout the software development lifecycle, partnering closely with product managers, developers, and stakeholders to deliver exceptional user experiences. The ideal candidate has strong manual testing expertise, experience working in Agile environments, and a passion for improving software quality through best practices, mentorship, and process improvement."
That's good.
Now Responsibilities list as above.
Requirements list: include education item.
Let's list:
- 3+ years of professional experience in software quality assurance and testing.
- Strong understanding of software testing methodologies and best practices.
- Experience working in Agile development environments.
- Proficiency with Jira or similar project and defect tracking tools.
- Experience using test management tools such as Zephyr.
- Solid understanding of the Software Development Life Cycle (SDLC), release processes, and testing environments.
- Strong analytical and problem-solving skills.
- Excellent communication and collaboration abilities.
- Exceptional attention to detail and organizational skills.
- Bachelor's degree in Computer Science, Software Engineering, Information Technology, or equivalent professional experience.
Qualifications list (Preferred):
- ISTQB Foundation Level Certification
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting. Key info: Location: LOS ANGELES, CA, USA (but also says Remote (U.S.-Based)). So location: Remote (U.S.-Based). Salary: $80,000 - $90,000 annually. Also says Compensation: Up to $90,000 annually, depending on experience and qualifications, plus a comprehensive benefits package. Employment Type: Full-Time. About The Opportunity: description. Position Overview: description. What You'll Do: includes QA & Testing bullet list and Leadership & Team Contribution bullet list. Required Qualifications: list. Preferred Qualifications: list. Education: Bachelor's degree... Why Join Us?: bullet list. Career Growth Opportunities: description. Also there is a consent text about phone number etc. That's boilerplate/application instructions? It says "By providing your phone number, you consent..." That's likely application instructions/boilerplate; we should remove. Contact email etc also likely boilerplate; remove. We need to decide sections. We have: - About the role (maybe combine About The Opportunity and Position Overview). Could be "About the role" heading. - Responsibilities: from "What You'll Do" (two subcategories). Could be combined. - Requirements: maybe "Required Qualifications" as Requirements. - Qualifications: maybe "Preferred Qualifications" as Qualifications? Or we could combine Required and Preferred under Requirements and Qualifications? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - About the role: description of organization, opportunity. - Responsibilities: QA & Testing and Leadership & Team Contribution. - Requirements: Required Qualifications. - Qualifications: Preferred Qualifications? Or maybe Skills: list of skills? Could treat Required Qualifications as Requirements, Preferred Qualifications as Qualifications, and maybe Skills as something else? But we have no explicit skills list besides those in qualifications. Could combine. - Benefits: "comprehensive benefits package" mentioned, plus "Why Join Us?" includes benefits like work with brands, collaborative team, exposure, career growth, culture. Those are more like benefits. So we can create Benefits section with those bullet points. - Pay: Salary range: $80,000 - $90,000 annually, up to $90,000 depending on experience. So we have pay info. - Schedule: Employment Type: Full-Time. Could be schedule. Thus we will include sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. We must not include sections with placeholder/filler. All have content. We must not repeat job title as heading. We must not include Job ID etc. We must output only HTML fragment, no /, no markdown. We need to use
for each section heading. Inside sections, use
for prose,
- for lists.
We need to preserve all substantive information. Let's extract.
About the role: From "About The Opportunity Join a highly respected digital experience organization that partners with globally recognized brands across industries including hospitality, financial services, travel, luxury, and consumer products. This is an opportunity to work on high-visibility, customer-facing digital products within a collaborative Agile environment. You'll enjoy the agility and close-knit culture of a mid-sized team while benefiting from the resources and stability of a larger global enterprise. The organization is committed to innovation, quality, continuous improvement, and professional growth."
Also Position Overview: "We are seeking a Senior Quality Assurance Analyst to play a key role in ensuring the quality, reliability, and performance of modern digital applications. This individual will contribute throughout the software development lifecycle, partnering closely with product managers, developers, and stakeholders to deliver exceptional user experiences. The ideal candidate has strong manual testing expertise, experience working in Agile environments, and a passion for improving software quality through best practices, mentorship, and process improvement."
We can combine these into About the role prose.
Responsibilities: Two sub-sections: QA & Testing and Leadership & Team Contribution. We can combine into a single list or keep subheadings? The instruction says use
for section headings only; we could still use
for subheadings? Not specified; better to keep as a single list with items. But we need to preserve all detail; we can keep bullet points as they are. List items: - Develop test cases and test scripts based on business requirements, user stories, and acceptance criteria. - Execute manual testing across multiple phases of the development lifecycle. - Perform functional, regression, and feature validation testing. - Identify, document, and track defects through resolution. - Evaluate defect severity and provide detailed reproduction steps. - Maintain and enhance existing test case repositories. - Collaborate with development and product teams to ensure quality standards are met. - Participate in project status reporting and quality reviews. - Lead QA efforts within Agile teams and project discussions. - Mentor and support junior QA team members. - Contribute to process improvements that enhance quality and team productivity. - Assist with effort estimation, risk assessments, and resource planning. - Help create onboarding materials, documentation, and knowledge-sharing sessions. - Promote QA best practices across the organization. - Participate in interviewing and evaluating new team members. That's all. Requirements (Required Qualifications): list: - 3+ years of professional experience in software quality assurance and testing. - Strong understanding of software testing methodologies and best practices. - Experience working in Agile development environments. - Proficiency with Jira or similar project and defect tracking tools. - Experience using test management tools such as Zephyr. - Solid understanding of the Software Development Life Cycle (SDLC), release processes, and testing environments. - Strong analytical and problem-solving skills. - Excellent communication and collaboration abilities. - Exceptional attention to detail and organizational skills. Qualifications (Preferred Qualifications): list: - ISTQB Foundation Level Certification. - Experience with accessibility testing. - Experience with non-functional testing. - Passion for continuous learning and staying current with emerging technologies and testing practices. Education: Bachelor's degree in Computer Science, Software Engineering, Information Technology, or equivalent professional experience. This could be part of Requirements or Qualifications? Could be separate but we have no heading for Education. Could include under Requirements as part of list. But we already have Required Qualifications list; we could add Education as an item there. However the instruction says we must preserve ALL substantive information; we can add it under Requirements as an item. Alternatively we could create a separate section "Education" but not in allowed headings list. The allowed headings are limited to those; we should not create extra headings. So we should fold Education into Requirements or Qualifications. Probably Requirements. Thus Requirements list will include the education item. Benefits: From "Why Join Us?" plus "comprehensive benefits package". Also "Career Growth Opportunities" maybe part of benefits. Let's extract: Why Join Us? bullet list: - Work with globally recognized brands on impactful digital experiences. - Collaborative and supportive team environment. - Exposure to a wide variety of technologies and projects. - Opportunities for career growth and advancement. - Strong culture focused on quality, innovation, and continuous improvement. Career Growth Opportunities: "This Role Offers Multiple Advancement Paths, Including Quality Assurance Lead (Leadership Track) Test Engineer (Automation & Technical Track)". That's also a benefit. Also "comprehensive benefits package" mentioned earlier. Thus Benefits section bullet list: - Work with globally recognized brands on impactful digital experiences. - Collaborative and supportive team environment. - Exposure to a wide variety of technologies and projects. - Opportunities for career growth and advancement. - Strong culture focused on quality, innovation, and continuous improvement. - Career advancement paths: Quality Assurance Lead (Leadership Track) or Test Engineer (Automation & Technical Track). - Comprehensive benefits package (health, retirement, etc.) – but we only have phrase "comprehensive benefits package". We'll keep that as is. Pay: Salary range: $80,000.00 USD Annually - $90,000.00 USD Annually. Also Compensation: Up to $90,000 annually, depending on experience and qualifications, plus a comprehensive benefits package. We'll include both. Thus Pay section: maybe a paragraph: "Salary range: $80,000 – $90,000 per year (up to $90,000 depending on experience and qualifications). Includes a comprehensive benefits package." Schedule: Employment Type: Full-Time. So schedule: Full-Time. Thus Schedule section: paragraph: "Full-time position." Now we need to output HTML. Structure:
About the role
...combined prose...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Benefits
- ... ...
Pay
...
Schedule
...
Make sure no extra whitespace? It's fine. Now craft prose for About the role. Combine: "Join a highly respected digital experience organization that partners with globally recognized brands across industries including hospitality, financial services, travel, luxury, and consumer products. This is an opportunity to work on high-visibility, customer-facing digital products within a collaborative Agile environment. You'll enjoy the agility and close-knit culture of a mid-sized team while benefiting from the resources and stability of a larger global enterprise. The organization is committed to innovation, quality, continuous improvement, and professional growth. We are seeking a Senior Quality Assurance Analyst to play a key role in ensuring the quality, reliability, and performance of modern digital applications. This individual will contribute throughout the software development lifecycle, partnering closely with product managers, developers, and stakeholders to deliver exceptional user experiences. The ideal candidate has strong manual testing expertise, experience working in Agile environments, and a passion for improving software quality through best practices, mentorship, and process improvement." That's good. Now Responsibilities list as above. Requirements list: include education item. Let's list: - 3+ years of professional experience in software quality assurance and testing. - Strong understanding of software testing methodologies and best practices. - Experience working in Agile development environments. - Proficiency with Jira or similar project and defect tracking tools. - Experience using test management tools such as Zephyr. - Solid understanding of the Software Development Life Cycle (SDLC), release processes, and testing environments. - Strong analytical and problem-solving skills. - Excellent communication and collaboration abilities. - Exceptional attention to detail and organizational skills. - Bachelor's degree in Computer Science, Software Engineering, Information Technology, or equivalent professional experience. Qualifications list (Preferred): - ISTQB Foundation Level Certification