Hex Software Engineer, Infrastructure at Hex responsible for owning cloud infrastructure, CI/CD, and observability across multi-tenant and single-tenant environments. Lead projects to improve infrastructure speed, cost, and security.
Responsibilities
Hex's infrastructure team owns all of our cloud infrastructure (compute, networking, datastores) 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.
Qualification
You make the people around you betterStrong Kubernetes operationsSolid AWS fundamentals (EKSInfrastructure as codeYou can take a vagueYou write clearlyPlus depth in at least one ofNetworking — VPC designDatabases — Postgres at scale
Required
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
