Quality Engineer II
- for any list of duties/requirements/benefits. Use
for prose. We need headings: maybe "About the role" (purpose), "Responsibilities" (essential duties), "Qualifications" (education and experience), "Skills" (knowledge and skills), "Benefits" (why join ICW group), "Pay" (salary range). Possibly "Schedule" not present, so omit. Also "Physical Requirements" maybe not a standard heading; but we could include under "Work Environment" or separate? The instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use h3 for section headings (e.g. those). Likely they expect only those headings. But we can include other headings if needed? Probably better to stick to those categories. We can map content: About the role = purpose paragraph. Responsibilities = essential duties + supervisory responsibilities. Qualifications = education and experience + certificates/licenses (N/A maybe omitted). Skills = knowledge and skills. Benefits = why join ICW group (benefits). Pay = salary range. Schedule not present, omit. We must not include sections with filler like "N/A". So for certificates/licenses we can omit that line. We need to preserve all substantive info: include details like location (Headquartered in San Diego with regional offices...), mission, etc. That belongs in About the role maybe. We need to include bullet lists for duties, responsibilities, qualifications, skills, benefits. Let's extract content. About the role: The first paragraph up to "Learn more about why you want to be here!" plus "PURPOSE OF THE JOB" paragraph. Actually "PURPOSE OF THE JOB The Quality Engineer II is an established, technical professional..." That's the purpose. Also earlier marketing fluff about ICW Group. We'll combine into About the role. Responsibilities: Essential Duties And Responsibilities list (many bullet-like sentences). Also Supervisory Responsibilities paragraph. Qualifications: Education And Experience paragraph. Also maybe "CERTIFICATES, LICENSES, REGISTRATIONS N/A" we can drop. Skills: Knowledge And Skills paragraph (list of skills). Also maybe "Preferred skills include strong Insurance domain background..." that's part of skills. Benefits: WHY JOIN ICW GROUP? bullet list: Challenging work..., voice..., competitive benefits package..., bonus potential..., PTO, paid holidays, support learning 100%, etc. Pay: The current range for this position is $83,017.13 - $140,002.70 ... plus note about fringe benefits etc. We should not include "We are currently not offering employment sponsorship for this opportunity." That's maybe part of work environment but could be included under About the role? It's substantive but not fitting categories; maybe we can include under About the role as a note. But instruction: preserve ALL substantive information. So we need to include it somewhere. Could add a short p under About the role or Work Environment. Since we don't have a Work Environment heading, we could add a paragraph under About the role or maybe under Responsibilities? Better to add a small paragraph under About the role after the purpose. We also have Physical Requirements and Work Environment paragraphs. Those are substantive. Could we include them under a heading like "Work Environment"? Not in the list but maybe acceptable as it's substantive. The instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Prefer a few substantive sections over many thin ones." Could combine Physical Requirements and Work Environment into a "Work Environment" section. That seems reasonable. Thus we could have sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay, Work Environment. But the instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot add Work Environment. However to be safe, maybe we can incorporate Physical Requirements and Work Environment into About the role or Responsibilities? Might be thin. Better to add a Work Environment section; it's substantive. Let's decide: We'll include About the role, Responsibilities, Qualifications, Skills, Benefits, Pay, Work Environment. Now we need to format lists. Responsibilities: list each duty as
- . The duties are many sentences separated by periods. We'll split each sentence that starts with a verb. We'll create list items.
Let's extract duties:
- Own the complete test strategy and test planning for the assigned Projects – defining scope, approach, risk assessment, entry/exit criteria, and test coverage targets for each release and sprint.
- Act as the QE lead within the team and drive quality discussions during grooming, sprint planning, and design reviews; set quality objectives; and ensure the team delivers against them.
- Develop, execute, and maintain comprehensive test plans, test cases, and test scripts for functional, regression, integration, API, and exploratory testing.
- Build, maintain, and extend automated test suites using frameworks such as Playwright for UI, Postman/Newman for API, following clean code practice.
- Execute API-level testing including payload validation, error handling, and contract verification for in-house and third-party service integrations.
- Contribute automated tests to CI/CD pipelines (Jenkins, GitHub Actions), supporting continuous testing across regression, smoke, and feature validation stages.
- Validate data integrity across integrated systems including ETL pipelines, data transformations, and end-to-end data reconciliation.
- Identify, record, and thoroughly document defects; perform root cause analysis by reviewing logs, stack traces, and database states to diagnose systemic issues.
- Participate in code reviews to provide quality-focused feedback on testability, error handling, and edge-case coverage.
- Recommend enhancements to testing processes, tools, and standards to improve efficiency and effectiveness within the POD and broader team.
- Own test data management, mock services, and QA environment configurations for reliable, repeatable test execution.
- Leverage AI tools to assist in test case generation, coverage analysis, and failure triage.
- Track and report quality metrics including defect density, escape rate, test coverage, and automation progress. Uses data to influence quality decisions.
- Coordinate quality activities with distributed teams and offshore/nearshore vendor partners on test assignments, status calls, and triage.
- Coach, guide, and review the work of junior team members; provide training on quality engineering practices and tools.
Supervisory Responsibilities: This role does not have direct reports but may mentor and/or train less experienced members.
We can incorporate that as a list item maybe.
Now Qualifications: Education And Experience: Bachelor’s degree in computer science, Information Systems, or related field (or equivalent experience); 3+ years in quality engineering or software testing with 2+ years in test automation.
We could also add that certificates/licenses N/A omitted.
Skills: Knowledge And Skills list: many items. We'll split each sentence or clause.
Let's extract:
- Practical, hands-on proficiency in at least one programming language (Java, Python, JavaScript/TypeScript) with the ability to read, understand, and debug production code.
- Demonstrated experience designing test strategies and owning end-to-end test planning for a product, team, or release.
- Hands-on experience building and maintaining automated tests using Playwright, Selenium, Cypress, REST Assured, or Postman/Newman.
- Solid understanding of API testing concepts: request/response validation, status codes, error handling, and RESTful service patterns.
- Working knowledge of SQL and database concepts – ability to write queries for data validation, verify data transformations, and support ETL testing.
- Experience contributing automated tests to CI/CD pipelines (Jenkins, GitHub Actions) and understanding of continuous testing principles.
- Familiarity with version control (Git), branching strategies, and pull request workflows.
- Understanding of the test automation pyramid and strategic allocation of coverage across unit, API, UI, and data layers.
- Exposure to performance testing concepts and tools (JMeter, k6, or equivalent).
- Awareness of AI-assisted testing tools and willingness to adopt AI workflows for test generation and defect analysis.
- Solid understanding of Agile/Scrum practices, shift-left testing, and the software development lifecycle.
- Ability to work independently on moderately complex assignments with limited supervision; strong problem-solving skills drawing from prior experience and analysis.
- Good communication skills; able to influence within the team and communicate with contacts within and occasionally outside the department.
- Demonstrated ability to coordinate quality tasks, delegate work, and review the output of junior team members.
- Preferred skills include strong Insurance domain background, specifically in Claims Management and/or Insurance Billing business workflows.
Benefits: WHY JOIN ICW GROUP? list:
- Challenging work and the ability to make a difference
- You will have a voice and feel a sense of belonging
- We offer a competitive benefits package, with generous medical, dental, and vision plans as well as 401K retirement plans and company match
- Bonus potential for all positions
- Paid Time Off
- Paid holidays throughout the calendar year
- Want to continue learning? We’ll support you 100%
Also maybe "ICW Group is committed to creating a diverse environment..." but that's EEO boilerplate; we should remove.
Pay: The current range for this position is $83,017.13 - $140,002.70 This range is exclusive of fringe benefits and potential bonuses. If hired at ICW Group, your final base salary compensation will be determined by factors unique to each candidate, including experience, education and the location of the role and considers employees performing substantially similar work.
Work Environment: Physical Requirements paragraph and WORK ENVIRONMENT paragraph plus "We are currently not offering employment sponsorship for this opportunity." plus maybe "This description is a general statement of essential job functions and responsibilities. The position may include other duties as assigned."
We'll combine.
Now produce HTML.
We need to use
for each section heading. Inside each section, we can have
for prose and
- for lists. We must not include markdown fences. Let's craft. First, About the role: combine introductory fluff and purpose. Paragraph: "Are you looking to make an impactful difference in your work, yourself, and your community? Why settle for just a job when you can land a career? At ICW Group, we are hiring team members who are ready to use their skills, curiosity, and drive to be part of our journey as we strive to transform the insurance carrier space. We're proud to be in business for over 50 years, and its change agents like yourself that will help us continue to deliver our mission to create the best insurance experience possible. Headquartered in San Diego with regional offices located throughout the United States, ICW Group has been named for the twelfth consecutive year in a row and for the 20th time overall as a Top 50 performing P&C organization offering the stability of a large, profitable and growing company combined with a focus on all things people. It's our team members who make us an employer of choice and the vibrant company we are today. We strive to make both our internal and external communities better everyday! Learn more