Infrastructure Engineer

Gyde•Austin, TX

2d•Hybrid

About The Position

Gyde is reimagining the insurance brokerage industry by building the first AI-native platform. We acquire traditional brokerages and transform them into data-driven organizations using AI to automate operations, power intelligent voice and chat experiences, and predict the right coverage and products. This role is crucial for owning the infrastructure that supports our growing AI-native brokerage platform. As we acquire and integrate agencies, our environment scales in size and tenancy, requiring a secure, auditable, and predictable infrastructure. The Infrastructure Engineer will work on the Infrastructure team, reporting to the Head of Infrastructure. This role blends infrastructure and application engineering, encompassing cloud layers (EKS, AWS in Pulumi, CI/CD, observability), and extends to full-stack project ownership from business problem identification to shipping code, managing workflows, and creating dashboards. It involves application engineering with TypeScript, Temporal workers, Postgres, and SQL migrations. A significant part of the job also includes evaluating vendor systems, designing approval workflows, and considering HIPAA and cost as core design principles. The engineer will often interface with security, data, finance, and legal teams, simplifying a complex, regulated, multi-tenant environment.

Requirements

5–10 years in infrastructure, platform, SRE, or DevOps engineering, with meaningful production ownership.
Production Kubernetes experience — EKS preferred: cluster upgrades, autoscaling, networking, and hands-on troubleshooting.
Strong AWS fundamentals: IAM, VPC and networking, compute, storage, KMS, and a working grasp of the cost model.
Infrastructure as code in a real codebase — Pulumi preferred; Terraform or CDK acceptable with a willingness to work in Pulumi.
Production TypeScript or Node — you will ship application code in a shared monorepo, not only 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.
Relational data modeling and SQL, Postgres preferred; comfortable writing and reviewing migrations.
Built and owned CI/CD pipelines (GitHub Actions or comparable), including deployment strategy and rollback.
Observability in practice — metrics, logs, and distributed tracing, plus alerting that engineers trust.
Experience operating in a HIPAA, SOC 2, or otherwise regulated and audited environment.
A writing habit — design docs, RFCs, or postmortems you can point to.
Fluency with AI coding tools in day-to-day work — we are an AI-native company and expect engineers to use agents well.

Nice To Haves

Durable workflow engines — Temporal especially — or comparable orchestration and job systems.
Hands-on administration of an IdP or SaaS admin surface (Okta, Entra) including SCIM, RBAC, and API integration.
Multi-tenant SaaS, or M&A integration work folding acquired companies onto a single platform.
Data warehouse pipelines (Redshift, BigQuery, Snowflake) and event-ingestion plumbing.
LLM infrastructure: gateways and virtual keys, provider rate limits, token and spend telemetry.
Secrets management at scale, policy-as-code, and supply chain hygiene (image signing, SBOMs).

Responsibilities

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 prove it works.
Build in the monorepo — production TypeScript in shared packages other engineers import, Temporal workers and scheduled workflows, data models and SQL migrations, internal services and tooling.
Run the cloud platform — EKS, AWS defined in Pulumi, CI/CD, secrets and workload identity, and the metrics, logging, and alerting that tell us something is wrong before a broker does.
Evaluate and integrate the systems we buy — identity, orchestration, model gateways, warehouse and vendor APIs.
Make security and compliance enforceable — least-privilege IAM and workload identity, BAA 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.
Own cost as an engineering surface — per-key LLM and infrastructure spend, estimated-versus-billed reconciliation, and alerting that fires before a runaway job becomes an invoice.