Quality Assurance Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate like EEO, legal, etc. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - About the role: The initial paragraph describing mission and role: "At Clerri, we’re a team of builders... Clerri is seeking a talented QA Engineer to join the team behind our practice and patient experiences, where you'll safeguard the quality of our award winning software products. You'll work closely with software engineers to rigorously test features across the stack, building and maintaining automated suites against the React and Vue interfaces our customers use every day and the NestJS/Node microservices and REST and gRPC APIs behind them, while also designing and executing thorough manual test cases. You will ensure developed code meets stated objectives and adheres to the team's quality standards. You will also help our customers and internal stakeholders maintain frictionless, reliable experiences as we build, enhance, and scale the product. If you are passionate about delighting and dazzling customers, take pride in delivering bug-free software, and want to be the last line of defense on products practices depend on every day, then come and be a part of our incredible story." That's about the role. - Responsibilities: The "Day-to-Day" bullet list: "Collaborate in an Agile environment to test and deliver high-quality features across our React and Vue frontends and the NestJS/Node microservices behind them, designing, building, and maintaining automated end-to-end and UI tests in Cypress and PlaywrightDesign, document, and execute detailed manual test cases with clear, reproducible results, exercising the REST and gRPC endpoints that power our interfaces and writing SQL to validate data and backend behaviorPartner with stakeholders to triage and prioritize issues to quickly identify and resolve defects, leveraging AI-powered tools to accelerate test creation, coverage, and improve defect detectionProbe beyond the happy path - edge cases, boundary conditions, error states - and verify features are intuitive and consistent, not just functionally correct" We need to split into list items. - Key Skills: Under "Key Skills" heading: list items: "Testing craft on both sides of the house: hands-on automated QA experience, preferably with Cypress and Playwright, alongside real skill in designing, executing, and documenting detailed manual test casesDepth in data and APIs: strong SQL skills for data validation and investigation, which is important to us, plus a solid background testing API frameworks with Postman, SoapUI, or similar toolsStrong debugging skills focused on root cause and on supporting engineers in resolving issues, experience using AI tools for QA, familiarity with CI/CD pipelines and integrating automated tests into the delivery processYou are legally authorized to work permanently in the US without employer sponsorship" We can break into separate bullet points. - Typical Experience & Education: "4+ years of experience in quality engineering at a fast-growing SaaS company; healthcare experience is a plusExperience building software with a distributed, remote teamBachelor’s degree in a technical discipline or equivalent years of experience" - Our Advantage: description of team values etc. Could be part of "About the role" or "Qualifications"? Might be considered "Qualifications" or "Benefits"? It's more about culture. Could be "Qualifications" or "Benefits"? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content. "Our Advantage" describes team culture, values, commitment. Could go under "Qualifications"? Actually qualifications are about experience/education. Benefits are about what they offer. Our Advantage is more about team culture, maybe "Qualifications"? But we have a separate "Qualifications" heading for experience/education. "Our Advantage" could be considered "Benefits"? Not exactly benefits like pay, schedule. Could be "About the role"? Might be better to put under "Qualifications"? But we already have Typical Experience & Education. The "Our Advantage" is about team values, could be part of "About the role" as description of environment. However we already have About the role covering mission and role description. Could add a paragraph about team culture under About the role. But we must not create sections with filler. We'll include sections: About the role, Responsibilities, Skills (Key Skills), Qualifications (Typical Experience & Education). Possibly Benefits? The posting does not mention specific benefits like health insurance, PTO, etc. It mentions remote work priority, location preference. That's more about schedule/location. Could be Schedule? It says "This role is open to fully remote candidates, with priority given to applicants based in or near Utah, or within the Mountain time zone." That's schedule/location info. Could be placed under Schedule section. Also maybe Pay? No pay info. So we should not create Pay or Benefits sections unless stated. So we will not include Pay or Benefits. We need to include Schedule section if we have schedule info. The posting mentions remote, priority location. That's schedule/location. So we can create a Schedule section with that info. We also have "Our Commitment to You" about inclusivity, but that's EEO boilerplate? It's about inclusive culture. Might be considered part of About the role or Qualifications? It's not boilerplate? It's about commitment to diversity. Could be included under About the role as a paragraph. However the instruction says remove EEO/equal-opportunity boilerplate. This is similar but it's about commitment to inclusivity. Might be considered EEO boilerplate. Safer to remove it. Also "Abilities required" about physical demands is boilerplate; remove. Thus final sections: - About the role: combine mission description and role description plus maybe "Our Commitment to You"? We'll omit that. - Responsibilities: list items from Day-to-Day. - Skills: list items from Key Skills. - Qualifications: list items from Typical Experience & Education. - Schedule: note about remote and location priority. We must not repeat job title. Use

for each section heading. We need to output only HTML fragment. Let's craft. About the role: combine paragraphs. We'll produce:

About the role

At Clerri, we’re a team of builders, believers, and bold thinkers driven by one mission: to remove the barriers between patients and providers through memberships that improve access to care and help practices thrive. Simply put, we bring care closer. Backed by a smart platform and a thoughtful team, we deliver the most trusted solution in the market. Clerri is seeking a talented QA Engineer to join the team behind our practice and patient experiences, where you'll safeguard the quality of our award winning software products. You'll work closely with software engineers to rigorously test features across the stack, building and maintaining automated suites against the React and Vue interfaces our customers use every day and the NestJS/Node microservices and REST and gRPC APIs behind them, while also designing and executing thorough manual test cases. You will ensure developed code meets stated objectives and adheres to the team's quality standards. You will also help our customers and internal stakeholders maintain frictionless, reliable experiences as we build, enhance, and scale the product. If you are passionate about delighting and dazzling customers, take pride in delivering bug-free software, and want to be the last line of defense on products practices depend on every day, then come and be a part of our incredible story.

Responsibilities:

Responsibilities

• Collaborate in an Agile environment to test and deliver high-quality features across our React and Vue frontends and the NestJS/Node microservices behind them, designing, building, and maintaining automated end-to-end and UI tests in Cypress and Playwright
• Design, document, and execute detailed manual test cases with clear, reproducible results, exercising the REST and gRPC endpoints that power our interfaces and writing SQL to validate data and backend behavior
• Partner with stakeholders to triage and prioritize issues to quickly identify and resolve defects, leveraging AI-powered tools to accelerate test creation, coverage, and improve defect detection
• Probe beyond the happy path - edge cases, boundary conditions, error states - and verify features are intuitive and consistent, not just functionally correct

Skills:

Skills

• Hands-on automated QA experience, preferably with Cypress and Playwright, alongside real skill in designing, executing, and documenting detailed manual test cases
• Strong SQL skills for data validation and investigation, plus a solid background testing API frameworks with Postman, SoapUI, or similar tools
• Strong debugging skills focused on root cause and on supporting engineers in resolving issues, experience using AI tools for QA, familiarity with CI/CD pipelines and integrating automated tests into the delivery process
• Legally authorized to work permanently in the US without employer sponsorship

Qualifications:

Qualifications

• 4+ years of experience in quality engineering at a fast-growing SaaS company; healthcare experience is a plus
• Experience building software with a distributed, remote team
• Bachelor’s degree in a technical discipline or equivalent years of experience

Schedule:

Schedule

This role is open to fully remote candidates, with priority given to applicants based in or near Utah, or within the Mountain time zone.

We must ensure no extra sections like Benefits, Pay. Check for any leftover boilerplate: we removed EEO, Abilities required, Our Commitment to You, Our Advantage? Actually we omitted Our Advantage (team values). Could be considered part of About the role but we omitted. The instruction: "Prefer a few substantive sections over many thin ones." Our Advantage is substantive but we could incorporate into About the role as a paragraph about team culture. However we already have About the role long; we could add a sentence about team values. But we might be okay to omit as it's not critical? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must include Our Advantage content. It describes team values: "Our team is constantly growing, learning, and adapting. You will be joining a team that is crazy smart. We ask hard questions and challenge each other to improve continuously. We are self-driven but team oriented. Clerri lives its values, and we manage our work and relationships accordingly. Our values are: Be Scrappy & Find a WayApply First Principles ThinkingNo Politics, The Idea WinsSpeed over perfection—we launch and learn". That's substantive. We should include it somewhere. Could be part of About the role or maybe a separate section like "About the team" but not in allowed headings. Could be included under About the role as additional paragraph. Let's add a paragraph after the role description. Thus About the role will have two paragraphs: first as before, second about team values. We'll need to ensure we don't create a heading for it. Let's craft About the role paragraph 2: "

Our team is constantly growing, learning, and adapting. You will be joining a team that is crazy smart. We ask hard questions and challenge each other to improve continuously. We are self-driven but team oriented. Clerri lives its values, and we manage our work and relationships accordingly. Our values are: Be Scrappy & Find a Way, Apply First Principles Thinking, No Politics – The Idea Wins, Speed over perfection—we launch and learn.

" Make sure to keep the list of values as text. Now ensure we didn't miss any other substantive info: "Our Commitment to You" about inclusivity; we removed as EEO boilerplate but it's about inclusive culture. Might be considered substantive. However the instruction says remove EEO/equal-opportunity boilerplate. This is similar to EEO but it's a commitment statement. Safer to remove? The instruction says remove EEO/equal-opportunity