SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
Salary: USD 180,000 - 250,000 / annual
Thatch is building software that gives employees real control over their health benefits. The Infrastructure Engineer role owns the reliability, security, and performance of the platform that powers the entire product organization.
You will be responsible for designing and operating infrastructure in a HIPAA-compliant environment handling sensitive healthcare data. Every product team depends on the systems you design and operate. Key responsibilities include:
- Own infrastructure health, performance, and reliability across the full stack
- Make architectural decisions and improve how the engineering organization builds and operates systems
- Design and evolve infrastructure using Terraform
- Improve CI/CD pipelines, deployments, and developer workflows to enable faster shipping
- Strengthen security posture across access controls, vulnerability management, and dependency management
- Identify and eliminate reliability risks before they impact customers
The ideal candidate has:
- Production experience operating infrastructure, platform, DevOps, or SRE systems
- A track record of owning critical systems end-to-end
- Strong production experience with PostgreSQL or comparable relational databases
- Hands-on experience managing infrastructure as code using Terraform
- Sound judgment balancing reliability, performance, and security tradeoffs
- A bias toward automation and improving developer productivity
The tech stack includes Ruby on Rails, PostgreSQL, Terraform, and modern cloud infrastructure with CI/CD tooling. Experience with HIPAA or SOC 2 environments, PostgreSQL performance tuning, internal developer tooling, and observability/incident response is particularly valued.
Thatch is a fully distributed early-stage company focused on transforming how America approaches healthcare. The interview process typically takes 2–3 weeks and includes a recruiter conversation, collaborative pair programming, systems design discussion, team conversations, and leadership discussion.
