Senior Quality Engineer - Underwriting

We need to output HTML fragment with sections: About the role? Actually the posting includes sections: About Bestow (company description), About The Team, What You'll Do, Who You Are, What To Expect, TOTAL REWARDS. Also there is mention of flexible remote/hybrid work, benefits etc. We need to use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we can adapt headings to match content. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those exact headings if applicable, but we can also use other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they want us to use those headings when appropriate. However the posting doesn't have explicit "About the role" heading; it has "About Bestow", "About The Team", "What You'll Do", "Who You Are", "What To Expect", "TOTAL REWARDS". We need to map to the allowed headings? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It may be that they expect us to use those headings as needed, but we can also use other headings if they match content? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. But later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we should create sections for content we have. Thus we can have sections: About the company (maybe "About Bestow") but they said do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings. So we can use "About Bestow" as heading? It's not job title. Probably okay. But they gave examples of headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Maybe they want us to map content to those categories. For instance: "About Bestow" could be "About the role"? Not exactly. However "About the role" could be a summary of the role. The posting includes "About The Team" and "What You'll Do" etc. Could treat "About The Team" as "About the role"? Might be okay. Better to follow the examples: Use headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We need to decide which sections we have content for. We have: - About Bestow (company overview) -> could be "About the role"? Not exactly but maybe we can treat as "About the role" describing the role context. - About The Team -> maybe also part of "About the role". - What You'll Do -> Responsibilities. - Who You Are -> Requirements/Qualifications. - What To Expect -> maybe additional notes, could be part of Responsibilities or Qualifications. - TOTAL REWARDS -> Benefits (and maybe Pay). They mention competitive salary and equity, benefits list. Thus we can map:

About the role

: combine About Bestow and About The Team.

Responsibilities

: What You'll Do.

Requirements

: Who You Are (core requirements).

Qualifications

: maybe Nice to have? Could be separate but we can combine. But we need to avoid thin sections. Perhaps we can have About the role, Responsibilities, Requirements, Benefits. We also have Pay info: "Competitive salary and equity based on role". That's Pay. So we could have a Pay section. Schedule: flexible remote/hybrid work mentioned. So we could have Schedule section. Thus we can have sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. We must not include headings with filler. Ensure each has substantive content. Now we need to strip boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. At end there is EEO statement and "Thanks for considering a job at Bestow!" - that's boilerplate; remove. Also remove "Bestow uses E-Verify..." that's legal boilerplate; remove. Also remove "Recent Employer Awards Include ..." maybe that's part of Benefits? It's about awards; could be part of Benefits or company culture. Might keep as part of Benefits? It's not a benefit per se but could be part of company culture. Might keep under Benefits? But it's not a benefit; maybe we can include under Benefits as "Awards and recognition". However the instruction: only include sections when posting has real specific content. Awards is specific content; we could include under Benefits or maybe a separate section like "Culture". But we only have allowed headings; we could put under Benefits as part of benefits? Might be okay. We need to preserve all substantive information; do not invent or summarize away detail. Thus we need to extract the substantive paragraphs. Let's parse the posting: First paragraph: "About Bestow Life insurance is one of the world's most important products. It's also one of the hardest to build, distribute, and modernize. Bestow exists to change that. Bestow is a leading vertical technology platform serving some of the largest and most innovative life insurers. Our platform unifies the fragmented, legacy value chain, enabling carriers to launch products in weeks instead of years. Carriers choose us to scale and operate at unprecedented speed, powered by AI and automation. Bestow isn't selling policies. We're building the infrastructure that helps an entire industry move faster, reach more people, and deliver on its promise. Backed by leading investors (Goldman Sachs, Hedosophia, NEA, Valar, 8VC) and trusted by major carriers, Bestow is powered by a team that moves with precision, purpose, and heart. If you want to help reimagine a centuries-old industry with lasting impact, join us. Bestow offers flexible remote/hybrid work, meaningful benefits, equity, and substantial growth opportunities." Second paragraph: "Bestow uses E-Verify to confirm the employment eligibility of all newly hired employees. To learn more about E-Verify, including your rights and responsibilities, please visit E-Verify.gov." -> remove. Third: "About The Team The Quality Engineering (QE) team makes sure the decisions Bestow's platform produces for carrier partners are correct, not just technically functional. This role is our reference authority on underwriting correctness. You'll partner with underwriters, actuaries, product, and engineering to make sure every rule change, evidence integration, and risk classification holds up before it reaches a carrier. We're hiring a senior individual contributor whose main qualification is deep life insurance underwriting expertise. You've spent years working in or testing underwriting operations and systems, and you can look at a decision output and know whether it's right before anyone writes a defect report. Domain depth is the requirement. Test automation skill is highly valued, but we can train it. If you're an expert automation engineer with light insurance exposure, this probably isn't the right fit. If you're an underwriting systems expert, underwriting business analyst, or QA specialist who has lived inside rules engines and evidence workflows and wants to grow your engineering skills, then you are on the right path. Reports to the Quality Engineering Director." Fourth: "What You'll Do Own test strategy and quality signal for underwriting decisioning, including rules changes, evidence ingestion, risk classification, and case outcomes.Design test scenarios that reflect real underwriting complexity: combinations of impairments, evidence sources, table ratings, and edge cases that generic test coverage misses.Validate rules engine behavior across releases, running regression on decision outcomes and not just API contracts.Translate underwriting requirements into testable acceptance criteria with underwriters, actuaries, and product before code is written.Build and extend API-level and data-level automated checks with the core QE team, growing toward full ownership of automation for the underwriting domain.Investigate production underwriting discrepancies and take them from root cause analysis through defect prevention.Serve as the QE organization's go-to authority on underwriting correctness." Fifth: "Who You Are 7+ years in life insurance, with substantial time in or directly adjacent to underwriting: underwriting operations, underwriting systems analysis, new business, or testing underwriting platforms.Working fluency with underwriting evidence and process, including application Part 1 and Part 2, Medical Information Bureau (MIB), prescription (Rx) and motor vehicle record (MVR) data, attending physician statement (APS) handling, table ratings, not in good order (NIGO) workflows, and accelerated or automated underwriting programs.Hands-on experience configuring, analyzing, or testing at least one underwriting rules engine or decisioning platform (for example AURA, Magnum, FAST, or a carrier-built engine).SQL skills strong enough to independently verify data outcomes.Experience writing structured test cases or acceptance criteria and defending quality judgments to engineering and business stakeholders.Nice to have (we'll help you grow here): test automation in code (JavaScript/TypeScript, Playwright, pytest, or similar), API testing tools and CI/CD familiarity, and annuities exposure such as suitability review, 1035 exchanges, and income rider mechanics." Sixth: "What To Expect A few honest notes so nobody is surprised in month two. This is a senior IC role, not a pure automation role and not a management role. Your leverage comes from domain judgment first and tooling second. Some of the systems you'll test integrate with legacy carrier and vendor platforms, so the work includes ambiguity, incomplete documentation, and some archaeology. You'll also be the deepest underwriting expert on the QE team, which means real influence and sometimes being the only person in the room who can answer the question." Seventh: "TOTAL REWARDS At Bestow, we’re proud to be awarded for our team members, innovative products, and culture. Our standard benefits include: Competitive salary and equity based on rolePolicies and managers that support work/life balance, like our flexible paid time off and parental leave programs100% paid-premium option for medical, dental, and vision insuranceLifestyle stipend to support your physical, emotional, and financial wellbeingFlexible work-from-home policy and open to remoteRemote and WFH options, as well as a beautiful, state-of-the-art office in Dallas’ Deep Ellum, for those who prefer an office settingEmployee-led diversity, equity, and inclusion initiatives Recent Employer Awards Include Best Place for Working Parents 2023 + 2024 + 2025Great Place to Work Certified, 2022 + 2023 + 2024 + 2025Built In Best Places to Work, 2022 + 2023 + 2025Fortune’s Best Workplaces in Texas 2022 + 2023Fortune’s Best Workplaces in Financial Services and Insurance 2022 + 2023 + 2024" Then EEO statement and thanks. We need to format into HTML with

headings and

or

• for lists. We need to decide which content is list-like. Many sections have sentences separated by periods; we could keep as paragraphs. For lists like benefits, we can make
  • . Benefits list: "Competitive salary and equity based on role", "Policies and managers that support work/life balance, like our flexible paid time off and parental leave programs", "100% paid-premium option for medical,