Infrastructure Engineer

Infrastructure Engineer

Austin, Texas, United States, New York City, New York, United States

Insurance brokers sit at the intersection of care, cost, and access — yet remain one of the most underleveraged assets in the $5T healthcare value chain. They guide millions of Americans through plan selection, coverage questions, and care navigation, yet still rely on spreadsheets, manual workflows, and outdated tools that limit their growth and impact.

Gyde is reimagining this. We're building the first AI-native insurance brokerage platform—a system that learns from every client interaction to automate operations, power intelligent voice and chat experiences, and predict the right coverage and products for every individual or business.

Our approach combines acquisition and AI: we acquire traditional brokerages and transform them into next-generation, data-driven organizations. Through Gyde's platform, agencies run more efficiently, serve clients more personally, and scale faster than ever before.

Join us if you're excited to:

• Redefine how millions of people access and understand their healthcare coverage, by building systems that turn unstructured data, human conversations, and fragmented processes into intelligence.
• Build AI systems that improve how people access healthcare
• Design production-grade voice, chat, and predictive models for a highly regulated domain
• Launch technologies that augment human judgment and make complex decisions transparent and scalable
• Help reinvent an entire industry from the inside out

Our founding team boasts pedigrees from Oscar, Stripe, Vista Equity Partners, Bain & Company and Alpine. Lightspeed led Gyde's $60M financing, with participation from Optum Ventures, Crystal Venture Partners, Virtue, MVP Ventures, and multiple endowment funds, among others. Hear why on LSVP Investment Memo.

You own the infrastructure that Gyde's AI-native brokerage platform runs on — but at our size, the title undersells the job. We acquire insurance agencies and fold them onto one platform, which means our environment grows in scale and in tenancy every quarter, and it has to stay secure, auditable, and predictable while it does. You sit on the Infrastructure team and report to our Head of Infrastructure.

The work deliberately blurs the usual line between infrastructure and application engineering. The cloud layer — EKS, AWS in Pulumi, CI/CD, the observability stack — is table stakes, but it is rarely the whole deliverable. A typical project runs the full chain: a business problem lands ("we can't tell which agency this contract belongs to", "we can't tell whether that email arrived", "we don't know what we're spending on LLMs"), and you own it from audit and data model through to the Type Script that ships in a shared package, the Temporal workflow that runs it, the IAM role behind it, and the dashboard that proves it works.

So this is real application engineering as well as platform work — Type Script in our monorepo, Temporal workers, Postgres and SQL migrations, packages other engineers depend on. A third part of the job is neither infrastructure nor application code: evaluating a vendor's permission model closely enough to know what it can actually enforce, designing an approval workflow with named humans and SLAs, and treating HIPAA and cost as design inputs rather than review gates.

Because we're small, you are often the interface to security, data, finance, and legal  will write the decision doc, then defend it in a comment thread with someone who cares about the price rather than the architecture.

The through line is simplification. Anyone can add another tool. We want someone who takes a complex, regulated, multi-tenant environment and makes it feel simple to the people using it — and who knows that the mechanism is usually the short part, while the carve-outs, the sequencing, and the question of whether a control is truly enforced are the job.

• Own the chain from problem to running control — take an ambiguous business or platform problem, establish what is actually true today rather than what the docs claim, design the fix, build it, and instrument it so you can…