Software Engineer, Infrastructure

Hex is growing our team of builders on a mission to make everyone a data person. Our platform solves key pain points with today’s data and analytics tooling, and empowers anyone to explore data using natural language, with or without code, on trusted context. Thousands of customers like Ramp, Figma, Stubhub, Anthropic, and Gamma love Hex for our beautiful UI, agentic superpowers, and boundless flexibility.

Hex has raised over $100M from leading investors like Sequoia, a16z, Snowflake and Amplify. With office hubs in San Francisco and New York, as well as remote team members throughout the US and UK, we’re a high-agency team that ships fast and has fun doing it. Check out our Intro to Hex video and employee handbook to learn more about what it’s like to work at Hex.

Hex's infrastructure team owns all of our cloud infrastructure (compute, networking, data stores) along with CI/CD and observability, across a multi-tenant platform and single-tenant environments. Every engineer at Hex depends on what the infrastructure team builds.

We're growing in customers, in users, and in the kinds of data workflows our workload compute backend has to support. That growth has opened up a set of projects that would meaningfully change how fast the rest of engineering ships, and we're hiring to take them on.

We're looking for someone who will pick up one of those projects, own it start to finish, and leave it better than they found it. Bring your opinions, including the ones that disagree with ours. Infrastructure tooling is changing quickly right now, and we want someone who's paying attention to that as we improve the foundational components that power Hex.

Your first few months, we'll pick two or three of these together based on where you're strongest and where we're looking to invest:

• CI/CD. Hex’s CI/CD pipelines need a glow-up: optimizing for speed, cost, and providing more flexibility.

• Stack lifecycle. Setup, teardown, partial teardown, and updates for single-tenant stacks, today too much of this is manual and runs through our team.

• Postgres at scale. Performance, migrations, and capacity for our multi-tenant production database.

• Cost. Infrastructure spend visibility and reduction.

• Security posture. Workload and container isolation, plus compliance work as we move upmarket.

• Platform features. Customer-facing infrastructure capabilities: private connectivity, customer defined networking, and making single-tenant deployments easier to operate.

• 5+ years building and operating production infrastructure, including on-call

• You make the people around you better, whether or not you've had the title

• Strong Kubernetes operations: you can reason about scheduling, networking, and failure modes, not just apply manifests

• Solid AWS fundamentals (EKS, RDS, VPC networking, IAM)

• Infrastructure as code, ideally Terraform

• Comfortable writing and reading enough application code to change a pipeline, a controller, or a service

• You can take a vague, long-standing problem and turn it into something shippable without waiting to be told how

• You write clearly, design docs and runbooks that engineers outside infra can follow

Plus depth in at least one of

• Networking — VPC design, private connectivity (Private Link, peering), DNS, TLS and certificate management, agentic sandboxing

• Databases — Postgres at scale: replication, tuning, connection pooling, major version upgrades, migrations under load

• Deployment systems — CI/CD platform ownership, build performance and cost, release and artifact management

• Cloud
  : AWS (EKS, RDS, Elasti Cache)

• Databases
  :
  PostgreSQL (RDS), Redis, LanceDB, DynamoDB, MSK

• Languages
  :
  Type Script (Node.js), Python, Rust, Go

• Infrastructure-as-code
  :
  Terraform

• Monitoring
  :
  Datadog

T…