> Markdown version of [/jobs/ext/3868913-infrastructure-engineer](https://www.wearedevelopers.com/jobs/ext/3868913-infrastructure-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Infrastructure Engineer

- **Company:** Alt Platform Inc.
- **Location:** New York, NY, United States (Remote available)
- **Experience:** Expert
- **Salary:** $200,000.0 - $250,000.0
- **Contract:** Permanent contract
- **Skills:** Artificial Intelligence, Amazon Web Services, Amazon Elastic Compute Cloud, Code Review, Databases, Continuous Integration, Data Systems, Programming Tools, Identity and Access Management, Software Engineering, Datadog, Agentic-AI, Cloudformation, Infrastructure Automation Frameworks, Sentry, Build Tools, Virtual Agents, Terraform
- **Published:** October 22, 2026
- **Apply:** https://www.indeed.com/viewjob?jk=5087ee8e6ef7ebfe

## About the Role

* 7+ years of infrastructure, platform, or SRE experience with deep AWS expertise (ECS, RDS/Aurora, EC2, ALB, IAM, CloudFormation or Terraform)
 * A track record of owning and improving CI/CD pipelines, deployment infrastructure, and developer tooling at a growing company
 * Experience building or managing non-production environments: staging, ephemeral environments, seed data systems, or similar
 * Strong opinions on observability. You've instrumented systems, built dashboards, and improved incident response.
 * Strong collaboration and communication skills. You write great docs, ask smart questions, and give thoughtful feedback.
 * Bonus: Experience with cost optimization at scale

## Description

* Build reproducible environments: Lead the effort to give every engineer (and every AI agent) the ability to spin up isolated, prod-like instances of Alt on demand. This means database cloning, per-branch services, routing, seed data, and auto-teardown. This is the substrate for how we want to build software.
 * Fix staging: Make non-production environments reliable and representative, so engineers can stop testing in production, stop setting up test state by hand, and stop working around flaky search infrastructure.
 * Bring Terraform under control: Fix infrastructure-as-code drift, build CI/CD automation, and make infrastructure changes safe and reviewable.
 * Own observability and incident response: We run Datadog, Sentry, and Posthog across the stack. Rationalize our monitoring, improve alerting, and make sure we catch issues before our users do.
 * Be a multiplier: You'll be the infrastructure leader for a growing engineering team. Level up the org through documentation, tooling, code reviews, and mentorship. Set the standard for how we operate., * Think in systems, not tickets: You see the connection between a flaky staging env, a rising cloud bill, and engineering velocity. You want to fix the root cause, not patch symptoms.
 * Care about developer experience: You measure your success by how much faster and more confidently your teammates can ship. You build tools and platforms, not just infrastructure.
 * Are cost-conscious by instinct: You know the difference between saving money and cutting corners. You think about unit economics when you see over-provisioned instances.
 * Are excited about AI-native engineering: You see reproducible environments as the substrate for AI agents to do real work, and you want to build that substrate.
 * Want to lead, not just execute: This isn't a role where someone hands you Terraform tickets. You'll define the infrastructure roadmap, make trade-off decisions, and own outcomes.