Coalition Senior Software Engineer, Underwriting leads product strategy across underwriting, claims, and security risk lifecycle areas. This people-leadership role manages product managers and drives integration of risk functions.
Responsibilities
This is a new role leading a new grouping of three areas that together form Coalition's risk lifecycle: Underwriting (how we select and price risk), Claims (how we close the loop and mitigate losses when something goes wrong), and Security (the Control and Wirespeed products that help policyholders reduce risk in the first place). Each of these has historically been run as its own domain. Your job is to be strategic about how these areas come closer together, recognizing that risk selection, loss mitigation, security telemetry, and claims outcomes are not separate problems but one continuous feedback loop.
This is a people-leadership role. You will manage a team of product managers across all three areas, help to steer the strategy that connects them, and be accountable for how the combined areas perform. You'll report into product leadership and partner closely with Engineering, Design, Data, Underwriting, Claims, Actuarial, Finance, Operations, and more.
Most of the value in Active Insurance comes from the connections between these functions, not the functions themselves. Security signals from Control and Wirespeed should sharpen how we underwrite. How a claim develops should feed back into how we price risk. The quality of underwriting should shape our loss exposure and therefore our claims load. Today these loops exist, but they aren't owned by anyone as a whole.
This role is deliberately the one seat that spans them. It is not a preview of how the rest of the company is organized, and we want to be explicit about that. Engineering leadership for each of these areas reports through the CTO in separate lines. Underwriting, Claims, and Security operate as genuinely different businesses with different economics, different stakeholders, and different rhythms, and we are not trying to merge them. What we are doing is deliberately creating a single product seat that sits across all three, because the connective work is real and currently unowned, and because product is the function best positioned to do it. That means the primary instrument of this role is influence, clarity, and a credible point of view rather than formal authority over the full stack. If that sounds like the interesting part of the job rather than the frustrating part, we should talk.
Why Security sits in a risk group. Control is our attack surface monitoring and login security product: we continuously monitor policyholders' external attack surface, watch their Google and Microsoft environments, and lock down accounts that look compromised. It's provided free to all 100,000+ policyholders, and it exists because reducing their exposure directly reduces our loss ratio. That makes it a risk lifecycle product, not a side business, and it is why it belongs alongside underwriting and claims. Wirespeed MDR is a different motion: a paid, growing revenue line sold both into our policyholder base and to companies who don't buy insurance from us at all. Both matter, and part of the judgment this role requires is holding those two very different mandates at the same time without letting either starve the other.
Underwriting. The internal risk decisioning stack: underwriting models and the real-time systems that execute them, the underwriter workbench and tooling, automation and risk selection, scanning and data collection, and insurance product development. Actuarial builds the pricing models; this organization is accountable for the systems that put them into production correctly, ensuring the right customer data reaches the right model at the right moment, that changes are testable and auditable, and that pricing behaves in production the way it was designed to. This portfolio is about the quality, consistency, speed, and auditability of underwriting decisions through better software and model-driven workflows.
Claims. The claims operations engine: intake, adjudication, and enablement systems, workflow tools, automation, platform migrations, and ML-assisted insights. The center of gravity is operational excellence and reducing manual overhead so claims professionals can focus on judgment, empathy, and resolution strategy, while claims data feeds back into how we understand risk.
Security (Control & Wirespeed). Control as the connective layer between security telemetry, the policyholder experience, and underwriting workflows, including its growing role as an underwriting-facing platform (underwriting integrations, outbound ticketing, large-market and multi-tenant support). And Wirespeed's MDR/ADR capabilities, integrations, reporting, and competitiveness in a crowded market. The two remain distinct products with distinct goals: Control's job is adoption and measurable risk reduction across the insured base; Wirespeed's job is to win on product merit against dedicated MDR competitors.
Ensure that our product strategy across underwriting, claims, and security is consistent and treats them as one risk lifecycle, and make the deliberate trade-offs about where to invest across the three.
Build and develop the product team beneath you, including hiring, coaching, and holding a group of PMs to a high standard across three distinct domains, each with its own stakeholders and technical depth.
Own the feedback loops between areas: ensure security telemetry informs underwriting, claims development informs pricing, and underwriting quality is measured against realized loss outcomes.
Own the product surface that makes security adoption possible and scalable: the in-product activation, onboarding, and value-demonstration motions that drive policyholders into Control, and the product-led growth capabilities that convert engaged Control users into paid Wirespeed customers. The commercial motion spans GTM and the broker channel, and you'll partner closely with both, but the product mechanics that make the funnel work are in your domain.
Qualification
Familiarity with cybersecurity products
Preferred
Experience with the business of insurance or other regulated financial products due to the underwriting, pricing, claims, policy administration, and compliance-heavy workflows.
Familiarity with cybersecurity products, MDR/EDR, security operations, or incident response.
Prior work shipping products built on predictive models, risk scores, or automated decisioning while managing operational and regulatory constraints.
