Founding Engineer

About the role

THE OPPORTUNITY

Hedge is hiring a founding engineer to build the agents that run an insurance company and the infrastructure that lets them scale. You’ll build systems that read messy submissions, chase missing information, navigate carrier requirements, and move accounts from a broker’s first email toward coverage.

Our agents are already in production, doing real work for paying customers. You’ll push them further: coordinating across carrier systems, recovering when things break, and improving through evals and feedback loops grounded in real outcomes.

You’ll build alongside the founders, inside the operation, with more than 100 insurance market partnerships already in place. The opportunity is to turn the work of placing insurance into software and give a small team the capacity to serve thousands of brokers.

HOW HEDGE STARTED

Luke Rosa and Luke Button worked together launching new markets at Traba, where Rosa built AI agents to manage $20 million in revenue. Buying insurance for Traba’s high-risk operations showed them how slow and manual the industry was.

Button later built Fernstone, an AI-native retail brokerage, and discovered a deeper bottleneck at the wholesale layer: access to carriers and control over the insurance product. They founded Hedge to address it, pairing Rosa’s experience automating operations with Button’s brokerage experience. Starting with wholesale distribution, Hedge is building toward an insurance company that combines distribution and underwriting.

WHAT YOU WILL OWN

- Turn operational work into software. Work alongside brokers and the founders, follow real submissions, and build systems around the details that determine whether an account gets quoted and placed.

- Productionize and scale the platform. Own architecture, data models, background jobs, integrations, monitoring, and failure recovery. Take responsibility for what happens after a feature ships.

- Put agents to work in production. Extend agents that handle emails, interpret submissions, gather missing information, prepare documents, and coordinate carrier workflows. Build evals and feedback loops that use real outcomes to improve performance, and own the reliability of the complete workflow.

- Make messy carrier data usable. Turn PDFs, emails, and API responses into consistent records of coverage, pricing, and outstanding requirements. Catch mistakes before they reach a broker or customer.

- Connect engineering to business results. Understand how your decisions affect turnaround, conversion, servicing effort, and carrier relationships.

WHO THRIVES HERE

You’re deeply technical, resourceful, and willing to learn the business in detail. You can move from a conversation with a broker to debugging a production failure to making an architecture decision.

We look for:

- Ownership from zero to one. You’ve taken an unclear problem to working software that people actually use. You can explain what you personally built, the decisions you made, and what happened after launch.