Gyde - Infra Eng
Vault Talent, United States
Vault Talent, United States
Infrastructure Engineer Austin, Texas, United States, New York City, New York, United States About Us 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:
systems that turn unstructured data, human conversations, and fragmented processes into intelligence.
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. Role Summary 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 TypeScript 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 — TypeScript 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 at once. You will write the decision doc, then defend it in a comment thread with someone who cares about the price rather than the architecture.
The throughline 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. Key Responsibilities
problem, establish what is actually true today rather than what the docs claim, design the fix, build it, and instrument it so you can prove it works. Most projects here cross the infra/app line and you own both sides.
Temporal workers and scheduled workflows, data models and SQL migrations, internal services and tooling. Not just YAML wrapped around someone else’s code.
the metrics, logging, and alerting that tell us something is wrong before a broker does.
warehouse and vendor APIs. Read a permission model and plan tier closely enough to know what a tool enforces versus what a person is merely promising to do, then build the glue that makes them agree.
before PHI access, data classification, PHI-aware logs and metric labels, and audit trails that hold up in a carrier audit because the system produces them, not because someone remembered.
estimated-versus-billed reconciliation, and alerting that fires before a runaway job becomes an invoice. What you bring and who you are
would stake a release on, and observability people actually act on. You have operated clusters through upgrades and incidents, not just deployed to them. Here this is table stakes rather than the whole job.
Durable workflows, relational data modeling, migrations, and packages other engineers import. You are comfortable opening a pull request in application code you do not own, and you know when a shared abstraction earns its keep.
its marketing page. You check plan tiers and API surfaces before committing to a design, and you can tell the difference between a control a system enforces and a process a human promises to follow.
You know where PHI leaks in a stack – logs, traces, metric labels, backups, third-party payloads
invoice.
think in blast radius, carve-outs, and reversible-first rollout, because the first casualty of enforcing something early is usually a business process. You write the one-page decision doc with ranked options and open questions, and you can defend it to a non-engineer. Technical Requirements
ownership.
and hands-on troubleshooting.
grasp of the cost model.
a willingness to work in Pulumi.
infrastructure definitions. We care that you have shipped real application code and will work primarily in TypeScript; which language you did it in matters less.
migrations.
strategy and rollback.
trust.
engineers to use agents well. Nice to have
systems.
and API integration.
SBOMs). What we offer Gyde offers a competitive benefits package to all employees.
GydeNew York, New York +1
Pay not posted
Posted Jun 18, 2026
GydeAustin, Texas, New York City, New York +2
$215K–$245K / yr
Posted 13 days ago
GydeAustin, Texas, United States, New York, New York +2
$175K–$250K / yr
Posted Sep 21, 2026
TruvoNew York City
$125K–$225K / yr
Posted Feb 21, 2026
Source: the company job board. We last checked this job 1 h ago. We first saw it 1 h ago. A job on a job board does not always mean that the team interviews people now. We found this job board in a public list. We did not yet compare it with the careers page of the company.
AxleNew York, New York
$180K–$250K / yr
Posted Aug 11, 2026
$200K–$250K / yr
Posted Sep 28, 2026
No one has reported an interview at Vault Talent yet. Did you interview there? Add the questions.