QA Automation Engineer II - IntelliScript (Remote)

We need to output HTML fragment with sections: About the role? The posting includes "What We Do" (company description) maybe not needed as section? The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and 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 decide which sections to include: The posting includes: "What We Do" (company description) maybe not needed but could be "About the role"? Actually "What We Do" is about the team/company, not role. Could be "About the role" but we have "What You'll Be Doing" (responsibilities). "What We Need" (requirements). "What You Bring To The Table" (skills/qualifications). "Location" (maybe schedule? Not schedule). "Compensation" (Pay). "Benefits". Also "Equal Opportunity" boilerplate to remove. Also "Visit our LinkedIn page..." etc maybe remove as boilerplate? It's not legal/EEO but maybe promotional; but we should preserve substantive info? It says "Visit our LinkedIn page for a closer look at our company, and learn more about our cultural values here." That's not essential job info; could be considered boilerplate? Probably remove as it's not required. Also "Milliman invests in skills training..." etc maybe part of benefits? Could be considered benefits but we already have benefits list; but we could keep as part of benefits description? However instructions: remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The training and ERGs etc maybe not boilerplate but could be considered benefits? Might be okay to keep as part of benefits? But we already have a Benefits section with list; we could add extra paragraphs about training etc. However they said prefer a few substantive sections over many thin ones. So maybe combine company description and training into an "About the team" but not a standard heading. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can also add other headings if needed? Probably stick to those. Thus we need sections: - Responsibilities: from "What You'll Be Doing" (list of duties). Use

  • . - Requirements: from "What We Need" (list). Use
    • . - Qualifications/Skills: from "What You Bring To The Table" (list). Could be Skills or Qualifications. We'll make a Skills section. - Benefits: from "Benefits" list. - Pay: from "Compensation" details. - Location? Not in allowed headings but we could put as a short paragraph under maybe "About the role"? But location is substantive; maybe we can include as a short

      after Benefits or Pay. Since not a standard heading, we can just include as a

      without heading. - Schedule: not mentioned; no schedule info; so omit. - About the role: maybe we could include a brief description of role from "What You'll Be Doing" but we already have Responsibilities. Could omit About the role. Thus produce HTML:

      Responsibilities

      • Design, document, maintain, and execute test cases for new features, enhancements, integrations, and regression coverage
      ... etc. Make sure each duty is separate
      • . Similarly for Requirements. Skills: list. Benefits: list. Pay: maybe a

        with the compensation ranges. We need to preserve all substantive info: include location info, travel expectations, application deadline? The deadline is "The expected application deadline for this job is November 30, 2026." That's substantive; we could include as a

        maybe under a minor metadata paragraph. Since we shouldn't put Job ID/requisition as heading, we can fold minor metadata into a short

        or drop it. The deadline is minor metadata; we can include in a short

        after Pay or before Benefits. Also location: "This position is open to remote work. Applicants must be willing to travel to the Milliman office in Brookfield, WI as needed and travel nationwide for meetings, conferences, and team events." Include as

        . Also "Individual(s) must be legally authorized to work in the United States without the need for immigration support or sponsorship from Milliman now or in the future." That's a requirement; maybe include in Requirements list? Could add as a bullet. Also "All other locations the range is $78,800 - $126,200." etc. We need to preserve all substantive info; not invent. Let's extract details: What We Do: company description; maybe we can include as a brief

        under no heading? Could be considered "About the role"? But we might skip as not required; but it's substantive about the team. However instructions: prefer a few substantive sections over many thin ones. Could include as a short paragraph before Responsibilities without heading. That's okay. Now list responsibilities bullet points: - Design, document, maintain, and execute test cases for new features, enhancements, integrations, and regression coverage - Perform functional, exploratory, integration, smoke, regression, and end-to-end testing across web-based user interfaces and APIs - Validate user workflows, business rules, field behavior, navigation, error handling, usability, and cross-browser behavior - Test REST APIs using tools such as Postman, including requests, responses, status codes, payloads, authentication, validation rules, and negative scenarios - Use SQL and available logs or diagnostic information to validate data and investigate issues across application layers - Review requirements, user stories, acceptance criteria, and technical designs to identify gaps, edge cases, dependencies, and quality risks before development is complete - Create clear, reproducible defect reports that include expected and actual results, supporting evidence, business impact, and appropriate severity - Collaborate with developers to troubleshoot issues, verify fixes, and determine appropriate regression coverage - Maintain test cases, execution results, and traceability in Zephyr or a comparable test management tool - Participate actively in Agile ceremonies, including refinement, sprint planning, daily stand-ups, demonstrations, and retrospectives - Provide concise input on release readiness, unresolved risks, and recommended follow-up testing - Identify stable, repetitive test scenarios that are strong candidates for automation - Execute and review automated test suites where applicable, troubleshoot basic failures, and partner with automation-focused engineers to improve coverage - Contribute to UI or API automation over time based on experience, interest, and team priorities Now Requirements bullet points: - 2+ years of software quality assurance or software testing experience - Strong hands-on experience manually testing web-based applications - Experience testing APIs with Postman or a similar tool - Ability to create effective test cases, test scenarios, and exploratory test charters from requirements and acceptance criteria - Experience with functional, integration, regression, negative, and end-to-end testing techniques - Experience documenting and managing defects in Jira or a similar tracking tool - Working knowledge of SQL for test data setup, backend validation, or defect investigation - Experience using generative AI tools to support software testing activities—such as test case development, exploratory testing, test data creation, defect investigation, or test automation—with appropriate review and validation of AI-generated outputs - Experience working within an Agile or Scrum delivery team - Individual(s) must be legally authorized to work in the United States without the need for immigration support or sponsorship from Milliman now or in the future. (maybe include as bullet) Now Skills/Wish list bullet points: - Strong analytical, troubleshooting, communication, and collaboration skills - Ability to learn unfamiliar business workflows and technical systems with appropriate guidance - Experience with Zephyr, TestRail, or another test management platform - Exposure to UI or API test automation through professional experience, training, or personal projects - Familiarity with automation tools or frameworks such as Playwright, RestSharp, Reqnroll, Selenium, or comparable technologies - Basic programming or scripting experience in C#, JavaScript, TypeScript, Java, Python, or a similar language - Experience executing automated tests through a CI/CD pipeline and reviewing results - Experience using generative AI tools to support test design, test data creation, defect analysis, or automation, with appropriate human review - Experience testing software-as-a-service (SaaS) or other complex business applications Now Benefits bullet points (as given): - Medical, Dental and Vision - Coverage for employees, dependents, and domestic partners. - Employee Assistance Program (EAP) - Confidential support for personal and work-related challenges. - 401(k) Plan - Includes a company matching program and profit-sharing contributions. - Discretionary Bonus Program - Recognizing employee contributions. - Flexible Spending Accounts (FSA) - Pre-tax savings for dependent care, transportation, and eligible medical expenses. - Paid Time Off (PTO) - Begins accruing on the first day of work. Full-time employees accrue 15 days per year, and employees working less than full-time accrue PTO on a prorated basis. - Holidays - A minimum of 10 paid holidays per year. - Family Building Benefits - Includes adoption and fertility assistance. - Paid Parental Leave - Up to 11 weeks of paid leave for employees who meet eligibility criteria. - Life Insurance & AD&D - 100% of premiums covered by Milliman. - Short-Term and Long-Term Disability - Fully paid by Milliman. Now Pay: compensation ranges. We need to include the location-based ranges: "The overall range for this role is $78,800 - $145,130. For candidates residing in: Alaska, California, Connecticut, Illinois, Maryland, Massachusetts, New Jersey, New York City, Pennsylvania, Virginia, Washington, or the District of Columbia the range is $90,620 - $145,130. All other locations the range is $78,800 - $126,200." We'll put as a

        . Now Location paragraph: "This position is open to remote work. Applicants must be willing to travel to the Milliman office in Brookfield, WI as needed and travel nationwide for meetings, conferences, and team events." Also maybe include application deadline: "The expected application deadline for this job is November 30, 2026." We can combine location and deadline in a short

        or separate. Now we need to avoid duplication: The posting also includes "Visit our LinkedIn page..." etc; we remove. Now produce HTML fragment:

        Responsibilities

        ...

        Requirements

        ...

        Skills

        ...

        Benefits

        ...

        Pay

        ...

        Location: This position is open to remote work. Applicants must be willing to travel to the Milliman office in Brookfield, WI as needed and travel nationwide for meetings, conferences, and team events. The expected application deadline for this job is November 30, 2026.